Windows 10: Event id: 161, 162 and then 41

I’ve recently encountered recurring issues with my PC, which started three days ago. Initially, the monitor lost signal, followed by the screen turning black. After a short period, the system restarted on its own, and everything returned to normal.However, the issue has since persisted intermittently. At times, the screen freezes on a single frame, and while I can still communicate on Discord, the system becomes unresponsive to inputs like Alt + F4. On other occasions, the screen turns black, and the system restarts without warning.The most recent occurrence happened while I was playing a game

:)

 

BSoD: Error volmgr Event ID: 161, Error volmgr Event ID: 162, Critical Kernel-Power Event ID: 41, Task category 63, BugcheckCode 313, BugcheckParameter1 0x3.

My pc has suddenly begun getting BSoD. I've tried updating all my drivers, running memory diagnostics, and I've done a fresh install of Windows, but the problem persists.

Log Name: System Source: volmgr Date: 01/02/2023 17.17.40 Event ID: 161 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Mads-stationær Description: Dump file creation failed due to error during dump creation. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 161 0 2 0 0 0x80000000000000 1458 System Mads-stationær \Device\HarddiskVolume2 000000000100000000000000A10004C004000200010000C000000000000000000000000000000000

Log Name: System Source: volmgr Date: 01/02/2023 17.17.40 Event ID: 162 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Mads-stationær Description: Dump file generation succeded. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 162 0 2 0 0 0x80000000000000 1459 System Mads-stationær \Device\HarddiskVolume2 000000000100000000000000A2000400663202000000000000000000000000000000000000000000

Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 01/02/2023 17.17.40 Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: Mads-stationær Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 41 9 1 63 0 0x8000400000000002 1463 System Mads-stationær 313 0x3 0xffff8386fd4d5d60 0xffff8386fd4d5cb8 0x0 0 0 0 0 false 0 0 false 0 0 false false 0 0 3

 

Kernal power 41 (61) id 161

Hello

So lately I have have this issue where my computer would unexpectedly restart without any information. This never happens when a game is running like battlefield 4 only and it occurs more often when chrome is open. When I go to event viewer it says "event
critical kernel power 41 (63) id 161. When the computer restarts the mouse freezes and then the monitors turn off and the computer restarts. How could I fix this problem?

So far I tried:

• factory reset windows
• check mnd dump

-Szczepulec7

 

Kernel-Power event id 41. BugcheckCode 0

Hello,

Thank you for writing to Microsoft Community Forums.

In-order to get more clarity on this issue and to assist you with appropriate troubleshooting steps, reply with answers to the below questions:

1. Are you aware of any changes made on your PC, prior to this issue?
   
2. Is this issue specific while playing a particular game?
   
3. Which edition of Windows are you currently using?
   

A Kernel Power Event 41 can occur in the following scenarios.

Scenario 1: The computer restarts, and there is a Stop error BugcheckCode in the event data.

Scenario 2: The computer is shut down by pressing and holding the power button.

Scenario 3: The system randomly restarts and no Stop error BugcheckCode is listed, or the computer is completely unresponsive (hard hang).

I suggest you refer the article on Kernel
Power Event ID 41 and follow the steps for the scenario that is causing this error on your PC.

Additionally, you can refer the article on Windows
Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows
and check if that helps.

Regards,

Sandeep Kumar M

Microsoft Community – Moderator