Kernel Power 41 Error in games

[zzziggy]

I've been facing this problem since 4-5 months ago, first it happened only on FIFA 23, then on Battlefield V and Battlefield 1, the problem is that my pc reboots randonmly after a while playing, sometimes after an hour, sometimes after and hour and half, sometimes after 5 minutes.
First I thought this was a problem with games that uses the EA Launcher (all those 3 are EA games if you didn't noticed), because I was palying other games like Red Dead Redemption 2 for hours (Even more than 7/8 hours) without any problem.
And now, I was playing Sekiro and this problem came back, I beat the entire game (including the final boss) and I have +62 hours of playing and never had a reboot problem. But now in the final scene (exactly the same frame I think) my pc reboots for no reason.
I don't really know how to post images and I don't want to give spoilers, but the reboots happens at the final scene where Kuro says "My sworn shinobi, now..." and always at that exact time my pc reboots.
IS NOT an overheating problem and I don't think is a PSU problem because as I said I've been playing games like Red Dead Redemption 2 or Sekiro for hours without any problems.
I need urgent help with this, I'm afraid those reboots could damage my hardware.

[emoticorpse]

Herr Lopes の投稿を引用：

Hey folks, I am facing the same issue that our disappearing friend described.

However, my story is a bit more curious. I recently moved from my parent's house I brought my computer with me. Well, as soon as I unpacked all my stuff, I decided to test the machine, but as soon as I turn it on I got stuck on the windows loading screen. So I contacted a local company specialized on repairing, and I few days later my baby was back again to my place.

Fortunately the loading screen issue was resolved, but surprisingly a new issue appeared: the infamous, Kernel Power 41. Once again, I took my computer to the local technician. They made several test (like testing each hardware and gaming for the whole day) and installed Win 11, but they did not find anything out of ordinary. After that I brought my PC back home and decided to install some hardcore games, like Days Gone and Red Dead 2... and there it was again, Kernel Power 41. At the highest point of the games, my PC turned off (again). However, this time it was a little bit different: it shut down, tried to restart again, but soon gave up and turned off.. And when I tried to turn it on by pressing the power button, there was no sign of life. I had to turn the PSU off and on to get the computer back to life. At that time, I was certainly that was something wrong with my GPU and its temperature. At the climax, the temperature was reaching 75°C. So I noticed that a OC Software (Expertool) was installed on my PC and decided to remote the little b******. Surprisingly , the performance became much better and the issue disappeared for 7 days. However, last night, I was playing Days Gone and the issue came back again.

It turns out that maybe the GPU is not the issue... Do you guys have any guess? Should I contact a local electrician?

Operating System: Windows 11 Pro 64-bit
BIOS: 3202 (type: UEFI)
Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 CPUs), ~3.2GHz
Memory: 32768MB RAM
Available OS Memory: 32690MB RAM
DirectX Version: DirectX 12
Card name: NVIDIA GeForce RTX 3060
Power Supply: Corsair 600W

From what I understand the last person to install Windows was the technician? meaning that troublesome OC software was installed by them?. No, I wouldn't take it back to them. Not at least without trying to fix this yourself because seems like they're repeatedly failing.

If I'm right on the installation part, just re-install Windows 11 yourself and see what happens. Download it from the Microsoft website and put it on USB to install.

If that doesn't work you might also want to create your own thread on this and maybe reference this thread if you think it's similar enough to make a point.

[A&A]

Just disable CPU C-states and test again.

[Illusion of Progress]

Herr Lopes の投稿を引用：

Hey folks, I am facing the same issue that our disappearing friend described.

It would be best to start your own thread, for future reference. I maybe still would, as it would give you more exposure. The "same" issue isn't always the same.

In your case, it's hard to tell if the issue starting after moving is coincidental or not, but the fact that the issue didn't occur at the shop when testing all day is sort of suggesting there's an issue at your new place? On the other hand, you sometimes go days (up to a week) with not having the issue at home, so it's also possible the PC might have just lucked out at the time at the shop and your new place isn't the issue.

If you're able to, and I know this might be a pain given how long you might need to test it, try other plugs (meaning, might need to try the PC in other locations, and for up to long time periods). That's if you suspect the new place is the issue. Try other power strips (if you're using any), and try other power cables.

I personally wouldn't suspect the new place (or a given outlet within it) as the issue, but that would be a way to see if it is.

I would also reseat everything in the PC from cables to adapter cards to RAM (CPU would be fine to leave I think unless you want to go that far). Something may have gotten "knocked" during one of the moves.

Have you checked Event Viewer for logs? People like to avoid this for some reason even though it can point you in the right direction and skip some rabbit holes as to what's wrong.

Event Viewer 41 itself won't tell you the exact cause but it does tell you that you have a problem. Windows, at every startup, does a check, and if the prior shutdown was not expected, a log for Event 41 gets created. And it makes sense when the PC spontaneously shuts off as Windows was not expecting that (this is almost always the cause for that event getting created, but pressing and holding the power button to force a restart will result in it as well). But if you see this get logged and there's no other logs of other issues around the time of the shutdown (note that event ID gets created on next startup and won't reflect the exact time of the shutdown), and you're also observing the PC spontaneously shut down, then it does heavily suggest that something is likely going wrong electrically. Though, that means with the PC and not necessarily your house so an electrician won't be able to help (unless they're also a PC tech). As for what's going wrong...

Low voltage on some part at one moment here (like the above example with C-states wouldn't hurt to try as maybe it's not enough voltage at the moment of a state change), a bad connection between a cable there, a PSU that can't cope with a given load here, etc... there's a lot of "causes" but it's almost always electrical somehow (or a given particular component on a part that has failed or is failing under certain conditions).

Parts-wise, PSU > motherboard > rest would typically be the usual order of suspects and I'd test about in that order.

Thermal issues are the other one that can cause that. 75C is nowhere near warm enough to be suspect so you can rule that out (at least for the graphics card).

[Herr Lopes]

Guys, I will open my own thread like you suggested, but do not worry I will respond each one of your replies here before.

Oh, and I will include some new details about my story on the thread.

Here: https://steamcommunity.com/discussions/forum/11/3815166994156216763/

[Herr Lopes]

emoticorpse の投稿を引用：

Herr Lopes の投稿を引用：

Hey folks, I am facing the same issue that our disappearing friend described.

However, my story is a bit more curious. I recently moved from my parent's house I brought my computer with me. Well, as soon as I unpacked all my stuff, I decided to test the machine, but as soon as I turn it on I got stuck on the windows loading screen. So I contacted a local company specialized on repairing, and I few days later my baby was back again to my place.

Fortunately the loading screen issue was resolved, but surprisingly a new issue appeared: the infamous, Kernel Power 41. Once again, I took my computer to the local technician. They made several test (like testing each hardware and gaming for the whole day) and installed Win 11, but they did not find anything out of ordinary. After that I brought my PC back home and decided to install some hardcore games, like Days Gone and Red Dead 2... and there it was again, Kernel Power 41. At the highest point of the games, my PC turned off (again). However, this time it was a little bit different: it shut down, tried to restart again, but soon gave up and turned off.. And when I tried to turn it on by pressing the power button, there was no sign of life. I had to turn the PSU off and on to get the computer back to life. At that time, I was certainly that was something wrong with my GPU and its temperature. At the climax, the temperature was reaching 75°C. So I noticed that a OC Software (Expertool) was installed on my PC and decided to remote the little b******. Surprisingly , the performance became much better and the issue disappeared for 7 days. However, last night, I was playing Days Gone and the issue came back again.

It turns out that maybe the GPU is not the issue... Do you guys have any guess? Should I contact a local electrician?

Operating System: Windows 11 Pro 64-bit
BIOS: 3202 (type: UEFI)
Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 CPUs), ~3.2GHz
Memory: 32768MB RAM
Available OS Memory: 32690MB RAM
DirectX Version: DirectX 12
Card name: NVIDIA GeForce RTX 3060
Power Supply: Corsair 600W

From what I understand the last person to install Windows was the technician? meaning that troublesome OC software was installed by them?. No, I wouldn't take it back to them. Not at least without trying to fix this yourself because seems like they're repeatedly failing.

If I'm right on the installation part, just re-install Windows 11 yourself and see what happens. Download it from the Microsoft website and put it on USB to install.

If that doesn't work you might also want to create your own thread on this and maybe reference this thread if you think it's similar enough to make a point.

So, when I contacted the local technicians and left my computer there, they actually reinstall the OS. Back then I had Win 10.

[Herr Lopes]

A&A ✠ の投稿を引用：

Just disable CPU C-states and test again.

That's actually a good ideia. It was on "AUTO" mode, now is "DISABLE".

[Herr Lopes]

Illusion of Progress の投稿を引用：

Herr Lopes の投稿を引用：

Hey folks, I am facing the same issue that our disappearing friend described.

It would be best to start your own thread, for future reference. I maybe still would, as it would give you more exposure. The "same" issue isn't always the same.

In your case, it's hard to tell if the issue starting after moving is coincidental or not, but the fact that the issue didn't occur at the shop when testing all day is sort of suggesting there's an issue at your new place? On the other hand, you sometimes go days (up to a week) with not having the issue at home, so it's also possible the PC might have just lucked out at the time at the shop and your new place isn't the issue.

If you're able to, and I know this might be a pain given how long you might need to test it, try other plugs (meaning, might need to try the PC in other locations, and for up to long time periods). That's if you suspect the new place is the issue. Try other power strips (if you're using any), and try other power cables.

I personally wouldn't suspect the new place (or a given outlet within it) as the issue, but that would be a way to see if it is.

I would also reseat everything in the PC from cables to adapter cards to RAM (CPU would be fine to leave I think unless you want to go that far). Something may have gotten "knocked" during one of the moves.

Have you checked Event Viewer for logs? People like to avoid this for some reason even though it can point you in the right direction and skip some rabbit holes as to what's wrong.

Event Viewer 41 itself won't tell you the exact cause but it does tell you that you have a problem. Windows, at every startup, does a check, and if the prior shutdown was not expected, a log for Event 41 gets created. And it makes sense when the PC spontaneously shuts off as Windows was not expecting that (this is almost always the cause for that event getting created, but pressing and holding the power button to force a restart will result in it as well). But if you see this get logged and there's no other logs of other issues around the time of the shutdown (note that event ID gets created on next startup and won't reflect the exact time of the shutdown), and you're also observing the PC spontaneously shut down, then it does heavily suggest that something is likely going wrong electrically. Though, that means with the PC and not necessarily your house so an electrician won't be able to help (unless they're also a PC tech). As for what's going wrong...

Low voltage on some part at one moment here (like the above example with C-states wouldn't hurt to try as maybe it's not enough voltage at the moment of a state change), a bad connection between a cable there, a PSU that can't cope with a given load here, etc... there's a lot of "causes" but it's almost always electrical somehow (or a given particular component on a part that has failed or is failing under certain conditions).

Parts-wise, PSU > motherboard > rest would typically be the usual order of suspects and I'd test about in that order.

Thermal issues are the other one that can cause that. 75C is nowhere near warm enough to be suspect so you can rule that out (at least for the graphics card).

I've checked Event Viewer and there were 2 events related to Kernel-Power that preceded KP 41: ID 125 and ID 172.

Before I try to change location, I'll disable CPU C-State and jump into Days Gone. I'll let you guys know if the KP 41 persist or not. Just remember that It can take some time for the error appear. The machine has some spirit there - Praise the Omnissiah.

[Illusion of Progress]

Herr Lopes の投稿を引用：

I've checked Event Viewer and there were 2 events related to Kernel-Power that preceded KP 41: ID 125 and ID 172.

If you can, provide the full text of those logs (and do so in your other post so things don't remain split and confusing). Looking up the first event ID is giving me results of it accompanying others with shutodwn errors and the text they provide suggests it's a thermal throttling issue?

But please provide your log contents so I'm not presuming another speaks for your own. If yours is the same though, I'll preemptively suggest reseating the CPU cooler and reapplying thermal paste. I did also recommend reseating everything but I mentioned the CPU should be fine. Might as well get it if you're doing the cooler though.

[TheStrategist93]

I'm not sure if any of you might be able to help with any advice or insights. I'm facing a similar problem. My system is unstable.

My PC will crash and reboot randomly. Sometimes after a few minutes, 30 minutes, an hour or a few hours. This has been an annoying issue to track down to say the least.

I've ran Memtest for RAM and that all checks out.

I'm leaning towards a PSU problem. I really hope it's not the MBD. I've gone in and out of the PC several times at this point.

Here are the specs:

Windows 11
Mbd Asus Tuf x670ePlus Wifi
CPU 7 7700x
GPU 7900xtx
PSU Corsair RM1000x Watt 80 plus gold
RAM G. Skill Trident Z5 NEO expo 32GB

I've got 7 corsair rgb fans with 2 separate hubs as well. I think the PSU is struggling to keep up with enough power output.

I'm so tired of my pc crashing it takes away the immersion from gaming. Hoping to play BG3 without needing to save every 5 minutes from all the paranoia.

Thank you to anyone who can offer help!!

[Illusion of Progress]

I'd recommend starting your own thread, but your initial list of things to check would be the following.

Is it a BSOD or a MCE?

If there's no BSOD shown or logged (memory.dmp files) then it's likely the latter. If it's the latter, you'll find clues in Event Viewer and possibly also in...

Windows/LiveKernelReports/WHEA

Windows/LiveKernelReports/WATCHDOG

If there's DMP files in there and they correspond with the time of the restarts, they may hold clues as to a cause. You can use WinDbg to open and analyze these if they are present.

There's an endless list of causes for both BSODs and MCEs (the latter usually rules out software and signifies a hardware issue though), but I had the same occurring on a system after I added a 7800 XT and RDNA3 seems to have a lot of people reporting this "Black screen of death" restart with it. Fix is usually an RMA. I did that and mine stopped as well.

A 1000W PSU should definitely be enough wattage to handle a 7900 XTX even accounting for spikes, but that's not the say the PSU isn't faulty for other reasons. If you want to test this you can limit the clock speed or power limit of the 7900 XTX in Adrenalin. If it lessens or removes the crashes it does suggest a lack of wattage might be the cause (or the power stages on the video card itself are bad and the lower power is less likely to trip the fault).

[Phénomènes Mystiques]

TheStrategist93 の投稿を引用：

I'm not sure if any of you might be able to help with any advice or insights. I'm facing a similar problem. My system is unstable.

My PC will crash and reboot randomly. Sometimes after a few minutes, 30 minutes, an hour or a few hours. This has been an annoying issue to track down to say the least.

I've ran Memtest for RAM and that all checks out.

I'm leaning towards a PSU problem. I really hope it's not the MBD. I've gone in and out of the PC several times at this point.

Here are the specs:

Windows 11
Mbd Asus Tuf x670ePlus Wifi
CPU 7 7700x
GPU 7900xtx
PSU Corsair RM1000x Watt 80 plus gold
RAM G. Skill Trident Z5 NEO expo 32GB

I've got 7 corsair rgb fans with 2 separate hubs as well. I think the PSU is struggling to keep up with enough power output.

I'm so tired of my pc crashing it takes away the immersion from gaming. Hoping to play BG3 without needing to save every 5 minutes from all the paranoia.

Thank you to anyone who can offer help!!

If it is Kernel Power generic attached to a WHEA Logger - Cache Hierarchy Error - it is C-States.

[Nanami]

This thread was quite old before the recent post, so we're locking it to prevent confusion.