Windows 10: Critical Kernel Power failure with multiple bugcheckcodes

I am facing these issues since last 3 4 months and have tried updating drivers and reinstalled windows 11 multiple times. Still, I am getting these BSOD.

:)

 

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

 

Critical Event 41, Kernel-Power, BugcheckCode 307

Hey,

For the past several weeks I've been experiencing some technical issues on my PC that result in the system freezing and then shutting down after app. 1-2 minutes.

The event viewer throws up a number of errors within the period of several minutes prior to the system shut-down, with the critical event 41 related to Kernel-Power (BugcheckCode 307) and other.

Errors

Some help will be much appreciated!

 

BSOD Kernel-Power 41, BugcheckCode 10

Hi LeLedg,

Welcome to 10Forums.

This will explain the lack of dumps.




There do not seem to be any other records about any crashes. For now, we have to wait until another crash occurs hoping it will save a dump file.

If you want to do something meanwhile, I would suggest to temporarily revert the overclock. Even though you have stress-tested the overclock to ensure stability, there's no way those tests guarantee stability in every possible situation.
Whenever we suspect a hardware issue with the GPU or CPU, for example, we suggest the same (or similar) tests to test the stability but we are aware of the limits of those tests. To be sure the overclock is not causing any problems, regardless of the tests it's been put through, I suggest reverting the overclock while troubleshooting.