Kernel Power 41 63

Question

Kernel Power 41 63

Anonymous

My PC has been randomly shutting down for seemingly no reason a lot as of late and it's gotten to a point where I want to work out whats causing it - this is the event details, please help. If any other details are required LMK what and where to find them please.

-	System

			-	Provider	<br>	---	---	<br><br><br>				[ Name]	Microsoft-Windows-Kernel-Power	<br>	---	---	---	---	---	<br><br><br><br>				[ Guid]	{331c3b3a-2005-44c2-ac5e-77220c37d6b4}	<br>	---	---	---	---	---

				EventID	41	<br>	---	---	---

				Version	9	<br>	---	---	---

				Level	1	<br>	---	---	---

				Task	63	<br>	---	---	---

				Opcode	0	<br>	---	---	---

				Keywords	0x8000400000000002	<br>	---	---	---

			-	TimeCreated	<br>	---	---	<br><br>				[ SystemTime]	2024-05-11T10:39:33.3850813Z	<br>	---	---	---	---	---

				EventRecordID	11459	<br>	---	---	---

				Correlation	<br>	---	---

			-	Execution	<br>	---	---	<br><br><br>				[ ProcessID]	4	<br>	---	---	---	---	---	<br><br><br><br>				[ ThreadID]	8	<br>	---	---	---	---	---

				Channel	System	<br>	---	---	---

				Computer	PC	<br>	---	---	---

			-	Security	<br>	---	---	<br><br>				[ UserID]	S-1-5-18	<br>	---	---	---	---	---

-	EventData

		BugcheckCode	209

		BugcheckParameter1	0x498

		BugcheckParameter2	0x2

		BugcheckParameter3	0x0

		BugcheckParameter4	0xfffff80361f41358

		SleepInProgress	0

		PowerButtonTimestamp	0

		BootAppStatus	0

		Checkpoint	16

		ConnectedStandbyInProgress	false

		SystemSleepTransitionsToOn	1

		CsEntryScenarioInstanceId	5

		BugcheckInfoFromEFI	false

		CheckpointStatus	0

		CsEntryScenarioInstanceIdV2	5

		LongPowerButtonPressDetected	false

		LidReliability	false

		InputSuppressionState	0

		PowerButtonSuppressionState	0

		LidState	3

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

7 answers

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

Sorry to let you wait, upon looking at your event log, we found below log which might indicate the cause of this problem:

| Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 5/11/2024 6:39:44 PM Event ID: 1001 Task Category: None Level: Error Keywords: User: SYSTEM Computer: PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000498, 0x0000000000000002, 0x0000000000000000, 0xfffff80361f41358). A dump was saved in: C:\WINDOWS\Minidump\051124-19156-01.dmp. Report Id: 07ad5b51-4e40-4513-9dba-c063336ede27. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{abce23e7-de45-4366-8631-84fa6c525952}" /> <EventID>1001</EventID> <Version>1</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2024-05-11T10:39:44.5559174Z" /> <EventRecordID>11489</EventRecordID> <Correlation /> <Execution ProcessID="1116" ThreadID="1120" /> <Channel>System</Channel> <Computer>PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="param1">0x000000d1 (0x0000000000000498, 0x0000000000000002, 0x0000000000000000, 0xfffff80361f41358)</Data> <Data Name="param2">C:\WINDOWS\Minidump\051124-19156-01.dmp</Data> <Data Name="param3">07ad5b51-4e40-4513-9dba-c063336ede27</Data> </EventData> </Event> | | --- | | Log Name: System Source: volmgr Date: 5/11/2024 6:39:27 PM Event ID: 162 Task Category: None Level: Error Keywords: Classic User: N/A Computer: PC Description: Dump file generation succeded. ------------------------------------------------------------------ Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="volmgr" /> <EventID Qualifiers="4">162</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2024-05-11T10:39:27.3453238Z" /> <EventRecordID>11454</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="168" /> <Channel>System</Channel> <Computer>PC</Computer> <Security /> </System> <EventData> <Data>\Device\HarddiskVolume4</Data> <Binary> 000000000100000000000000A2000400B60F000000000000000000000000000000000000 00000000 </Binary> </EventData> </Event> | | --- |

You see from the first log we could found it have bugcheckcode 209 which is corresponding to your problem description; so it should be the log we want. Following that path is the memory dump file we could use to debug your issue.

The second log we could found one clue that there seem to be an issue with volmgr and the system generate the *.dmp too. But I still does not found too many realible resource about the supposed location of this dump file. I would suggest you search the dmp file under the path " C:\WINDOWS" and give all the dump file just in case.

Also, may I know how long have you been using this computer, randomly shutdown usually could be hardware issue which is pretty hard to locate. The fastest way might just be send your computer to the service center or if you have replace component to have an experiment.

Let me know your thoughts. Hope you have a smooth path towards the solution.

Best Regards

Benjamin- MSFT | Microsoft Community Support Specialist

Answer 3

The main purpose of event log is to know the cause of event 41, so in principle it should be the event in proximity with 41, but in your case if you have no idea. Just export all the event it will be fine. Thank you!

Finally, if you are not comfortable with sharing with cloud drive; you can send the file via private message

You can send a private message via the Messages link at the top right side of the page, right below the Last updated date.

2) And check your sent PM by going to My Profile and then selecting View Private Messages from the left pane of your profile page.

Best Regards

Benjamin- MSFT | Microsoft Community Support Specialist

Answer 4

Hello,

So I've gone through device manager and found no devices with a yellow warning sign, those drivers all seem to be okay on the surface.

I've gone into event viewer and exported each of my 12 crashes in the last 2 months for now - just to clarify is it the events leading up to Event 41 you want exported or just event 41 by itself? Also forgive my stupidity, I can't seem to work out how to upload the logs I've saved to this message chain, if you could let me know how that'd be appreciated, thanks in advance.

Answer 5

Hi, Jordan Powell1.

Welcome to Microsoft support community.

We noticed you are having problem with randomly shutdown computer. Which is pretty annoying I have to say. Let us work through this step by step.

What change have you made to your computer that might be the cause of your problem, if you could remember.

From the event detail you provided, we could see the Event id 41 which can be caused by various factors.

The detail could be determined by the BugcheckCode 209 which is equal to hex number 0xD1(D stand for 13 in hex number, 13 * 16 + 1 = 209 209). From: Bug Check 0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUAL - Windows drivers | Microsoft Learn. We could reference your error.

Basically it could cause by corrupt driver. In that case, my suggestion is:

Export event viewer log

Event 41 usually come with a series of events that could give us more detail about the error. Upload the event log and share with us could help with the problem. You could reference: How to Export Windows Event Logs | Dell US

Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate and safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Check device manager

Right click Windows icon, select Device Manager. At the device tree, expand the normal day used device to have a check see if there is yellow waring sign marked which might be the indicator of error.

Alternatively, some report had been made state it might be caused by network driver, chipset driver; you could try to reinstall those driver at the device manager for right-click the device and select uninstall driver and select update driver again see if you are lucky enough to escape the long troubleshooting phase.

While above solution might not solve your problem instantly, I hope at least it will help you; feel free to keep the situation updated so we could continue investigation. Looking forward about your reply.

Best Regards

Benjamin- MSFT | Microsoft Community Support Specialist