Kernel Power 41 error.

[drifterx]

Howdy, i was installing drivers and this started happening. Im still a bit new to drivers and was installing all of them......... Can I just wipe my harddrive and install a fresh copy of windows? will this have different drivers? It restarts after i run a game and quit.

[Bad 💀 Motha]

Just keep rebooting Win10; 3 failed boots and Win10 should auto enter the Recovery Mode.
From here just do a System Restore to an earlier date before your driver updates.

Its best to never do driver updates in the form of an update. Rather go download the very latest driver, then uninstall the current one from Control Panel > Programs & Features; reboot when done, then install the new driver.

[drifterx]

Publicado originalmente por Bad 💀 Motha:

Just keep rebooting Win10; 3 failed boots and Win10 should auto enter the Recovery Mode.
From here just do a System Restore to an earlier date before your driver updates.

Its best to never do driver updates in the form of an update. Rather go download the very latest driver, then uninstall the current one from Control Panel > Programs & Features; reboot when done, then install the new driver.

Its far too late and this is already a restore. If I format and reinstall, Im worried that I might have corrupted the MOBO, CMOS or other things that have external information from the harddrive if I corrupted those files? Im looking to essentialy nuke from orbit at this point.

[Bad 💀 Motha]

Just cause you got a blue screen, doesn't mean any harm to hardware has been done.
This can be a simple driver issue, or a terrible unreliable Power Supply.

There is no need to wipe the OS and start over; going back in time before this issue was occurring is really all you should need to do. Now test the system for stability by running a good stress test; such as 3DMark TimeSpy or Unigine Superposition

[drifterx]

Publicado originalmente por Bad 💀 Motha:

Just cause you got a blue screen, doesn't mean any harm to hardware has been done.
This can be a simple driver issue, or a terrible unreliable Power Supply.

There is no need to wipe the OS and start over; going back in time before this issue was occurring is really all you should need to do. Now test the system for stability by running a good stress test; such as 3DMark TimeSpy or Unigine Superposition

So I went and tried out OCCP. I took a screenshot of the activity:

https://i.imgur.com/fwsMgyi.png

I this ok, or should I run the ones you said to? This was a stress test done.

[Bad 💀 Motha]

Judging by the screenshot and all the info there; that bencharmk doesn't appear to be very demanding enough to fully stress the system.

Yes I would try the two above when you find the time.

Another good method testing both CPU and GPU high stress power levels, which will in turn stress the rest such as PSU, Mobo and RAM... is running these two at the same time...
> Prime95 > Small FFTs loop test
> MSI Kombuster > GPU VRAM # GB > Stress Test (which is a loop, the Benchmark is not)

Both of those ran at the same time will be extremely demanding for any PC no matter the specs and should be to help determine if you have a weak or faulty PSU to blame, or perhaps just a driver issue. However its not always simple to understand how to point to faulty hardware without having a means to swap parts and then re-test again with those; like a different PSU, to see if the system still does the same things or problems once only a single part has been changed for testing purposes. As lets say you have a weak PSU and its the reason the system is locking up, rebooting on its own or giving Windows Blue Screen of Death errors. This could be a PSU, but it could also be a faulty, corrupted or simple un-stable Device Driver.

[drifterx]

Publicado originalmente por Bad 💀 Motha:

Judging by the screenshot and all the info there; that bencharmk doesn't appear to be very demanding enough to fully stress the system.

Yes I would try the two above when you find the time.

Another good method testing both CPU and GPU high stress power levels, which will in turn stress the rest such as PSU, Mobo and RAM... is running these two at the same time...
> Prime95 > Small FFTs loop test
> MSI Kombuster > GPU VRAM # GB > Stress Test (which is a loop, the Benchmark is not)

Both of those ran at the same time will be extremely demanding for any PC no matter the specs and should be to help determine if you have a weak or faulty PSU to blame, or perhaps just a driver issue. However its not always simple to understand how to point to faulty hardware without having a means to swap parts and then re-test again with those; like a different PSU, to see if the system still does the same things or problems once only a single part has been changed for testing purposes. As lets say you have a weak PSU and its the reason the system is locking up, rebooting on its own or giving Windows Blue Screen of Death errors. This could be a PSU, but it could also be a faulty, corrupted or simple un-stable Device Driver.

Wow, thanks ill work on it like you said.

[Castyles]

I hate this ♥♥♥♥♥♥♥ problem. Here are many solutions - that didn't worked out for me:

https://blog.pcrisk.com/windows/12891-how-to-fix-kernel-power-error

[Carlsberg]

Don't think a stress test will solve this issue which is most likely a driver conflict.

Latest chipset drivers followed by Sound, Network and Wireless Adapter, Gpu and any others you need. Windows update should have driver updates disabled otherwise it will install generic microsoft drivers which do not work the best.

Not saying that this is a solution but should rule out a driver conflict in which case it may be a hardware fault. Now would be the time to suspect the psu as a possible fault and the stress tests would be relevant in the event its not.

[drifterx]

you know what i have no ran the thing without a psu plugged in let me do some testing that way. lol
low expectations.....

[Carlsberg]

Publicado originalmente por drifterx:

you know what i have no ran the thing without a psu plugged in let me do some testing that way. lol
low expectations.....

Is this a laptop? Psu and LT power supply are not same thing. And your issues all started because you were installing drivers so its not a likely cause. Make sure you have the correct drivers for your machine and are not trying to install desktop or W32/W64 bit drivers by mistake.

[drifterx]

So I think i solved the issue. I used DDU to remove all my video and sound drivers including any extra files, registry entrys etc. After that windows - whether I wanted it to or not - reinstalled the drivers immediately. Im no longer experiencing shutdowns and im even having better performance in my games. Thanks to all of you for caring, really appriciate it.

Fingers crossed it stays this way lol.

[Alukat]

I have the same issue, I did windows update at 23rd of march and that's where the issues started.

No other driver updates have happened before the first restarts.

So, i'd say they messed up with the latest version.

[iceman1980]

Publicado originalmente por drifterx:

Howdy, i was installing drivers and this started happening. Im still a bit new to drivers and was installing all of them......... Can I just wipe my harddrive and install a fresh copy of windows? will this have different drivers? It restarts after i run a game and quit.

If this is a kernel layer issue running DISM might fix it.


Run via command prompt

 
DISM /online /cleanup-image /RestoreHealth

[Bad 💀 Motha]

^ This

Cause a Driver isn't going to address this issue.
It's often times... a faulty PSU, faulty Motherboard, corrupted OS

[Carlsberg]

Publicado originalmente por Bad 💀 Motha:

Just cause you got a blue screen, doesn't mean any harm to hardware has been done.
This can be a simple driver issue, or a terrible unreliable Power Supply.

There is no need to wipe the OS and start over; going back in time before this issue was occurring is really all you should need to do. Now test the system for stability by running a good stress test; such as 3DMark TimeSpy or Unigine Superposition

Publicado originalmente por Bad 💀 Motha:

^ This

Cause a Driver isn't going to address this issue.
It's often times... a faulty PSU, faulty Motherboard, corrupted OS

Changed your mind?