Kernel 41 power issue.

[GrimReality]

When I run certain games the pc loses power all of a sudden and then restarts. it says its a kernel power issue, ive tried most fixes but nothing is working. Please help.

[andreasaspenberg575]

that suggests that your power supply is too weak. here is what you can do to help me diagnose it: post your specs, including the limit of your power supply. it is a known fact that some stores sells pcs with too weak power supplies. elkjøp for example.

[GrimReality]

Originally posted by andreasaspenberg575:

that suggests that your power supply is too weak. here is what you can do to help me diagnose it: post your specs, including the limit of your power supply. it is a known fact that some stores sells pcs with too weak power supplies. elkjøp for example.

Its not a new pc, ive had it for.. a while, maybe 10 years or so. PSU IS 650 Evga P2. Radeon RX 580 series, 16 gb ram, i5-6600K CPU 3.5GHz. It usually happens when i run a heavy game, or even dota crashes after an hour or so, sometimes it just restarts when nothing is going on either. Ive tried to update everything and make sure the drivers are good. Is it possible a heating issue?

[_I_]

Originally posted by andreasaspenberg575:

that suggests that your power supply is too weak. here is what you can do to help me diagnose it: post your specs, including the limit of your power supply. it is a known fact that some stores sells pcs with too weak power supplies. elkjøp for example.

that error has nothing to do with the psu

it could be heat or unstable oc
oc does get less stable over time, try turning it down a bit or back to stock to see if the errors stop

[Illusion of Progress]

Event ID 41 is just Windows saying "the operating system terminated without telling itself to shutdown first".

That happened because of a loss of power, but it's not what caused it. The inverse is true; it's a symptom, not a cause.

To find the cause, you need to look at other clues

1. Check this directory for memory dumps (from BSODs).

Windows/Minidump

2. Check these directories for other dumps from the WHEA logger.

Windows/LiveKernelReports/WHEA
Windows/LiveKernelReports/WATCHDOG

If any are present, WinDbg can open and analyze them.

3. Describe the restarts. These are indeed restarts and not shutodwns, yes? Does the power ever cut out during the restart, or does it stay on and simply loop back to the POST/BIOS process?

If it's doing what I think I is, it's encountering a machine check exception and restarting as a result. You may also find other Event ID logs in Event Viewer if so. If these logs are present, give the three most recent examples of it.

Preliminary stuff I'd suggest is to return all things to stock (including memory profiles), and to test RAM with MemTest86. You can also download OCCT and do testing with its suite of stress tests. If the PC is dusty or hasn't been cleaned or repasted in a while (including video card), you might entertain that. With a 10 year old PC, there's extra considerations here including simple wear and tear and something may have eventually failed. A lot of machine check exceptions are either a failing component or a momentary "power value isn't correct". This can be something on the motherboard, the video card, anything.

[Iron Knights]

Power supply units can fail in an old system, may have been minimally ok at some point but now it's defective.
As for heating, set your fans 100% at 60C, may need new thermal paste on CPU.

[r.linder]

Kernel Power ID 41 errors appear when the system loses power unexpectedly for any reason, it won't tell you a thing on what caused it to happen and it can be basically anything.

Overheating, unstable overclocks, power loss at the outlet, etc.

[andreasaspenberg575]

your cpu is unlocked, which means that it can be overlocked. that may cause it to draw too much power.

[Phénomènes Mystiques]

I had this issue with conflicting applications.

It is a generic error/warning that may or may not pertain the hardware. In my experience PC issues are 95% of the time caused by software conflicts and is not the hardware failing.

Use HWiNFO to monitor for overheating, as well as voltage and clocks.

Check Event Viewer for any application conflicts, also can use Reliability History.

And as always, run SFC scan.

Can the error be caused by outdated drivers, including BIOS and Chipset? Yes.

Can the issue be caused by integrated phone apps pertaining Android and iOS? Yes.

Can the issue be caused by certain Windows Updates? Yes.

Can the issue be caused by a GPU fan slowdown? Yes.

Find the issue that happened right before the time of the kernel 41 in EV, use a custom view. You will see the conflict pop up right BEFORE the Kernel event, unless it shows another generic error/warning.

[GrimReality]

Thanks guys alot of helpful stuff, ill tinker around and hopefully I can fix it!

[Neozoon]

Some games somehow overcrank my FPS before main menu and crash my PC.
Happens when the devs don't implement an FPS limit and Radeon FPS limit doesn't activate in time.

[GrimReality]

Originally posted by Illusion of Progress:

Event ID 41 is just Windows saying "the operating system terminated without telling itself to shutdown first".

That happened because of a loss of power, but it's not what caused it. The inverse is true; it's a symptom, not a cause.

To find the cause, you need to look at other clues

1. Check this directory for memory dumps (from BSODs).

Windows/Minidump

2. Check these directories for other dumps from the WHEA logger.

Windows/LiveKernelReports/WHEA
Windows/LiveKernelReports/WATCHDOG

If any are present, WinDbg can open and analyze them.

3. Describe the restarts. These are indeed restarts and not shutodwns, yes? Does the power ever cut out during the restart, or does it stay on and simply loop back to the POST/BIOS process?

If it's doing what I think I is, it's encountering a machine check exception and restarting as a result. You may also find other Event ID logs in Event Viewer if so. If these logs are present, give the three most recent examples of it.

Preliminary stuff I'd suggest is to return all things to stock (including memory profiles), and to test RAM with MemTest86. You can also download OCCT and do testing with its suite of stress tests. If the PC is dusty or hasn't been cleaned or repasted in a while (including video card), you might entertain that. With a 10 year old PC, there's extra considerations here including simple wear and tear and something may have eventually failed. A lot of machine check exceptions are either a failing component or a momentary "power value isn't correct". This can be something on the motherboard, the video card, anything.

So this shows up, it says its ahead in time of the critical kernel power loss...

Log Name: System
Source: EventLog
Date: 5/27/2024 1:18:18 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-G69C6PK
Description:
The previous system shutdown at 1:17:10 AM on ‎5/‎27/‎2024 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-05-27T05:18:18.5141217Z" />
<EventRecordID>227229</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DESKTOP-G69C6PK</Computer>
<Security />
</System>
<EventData>
<Data>1:17:10 AM</Data>
<Data>‎5/‎27/‎2024</Data>
<Data>
</Data>
<Data>
</Data>
<Data>117337</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E807050001001B00010011000A00D302E807050001001B00050011000A00D3023C0000003C000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

Then the actual kernel powerloss which is timed before this, but in the log its ahead of it.

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 5/27/2024 1:18:11 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: DESKTOP-G69C6PK
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:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>8</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2024-05-27T05:18:11.1772541Z" />
<EventRecordID>227242</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>DESKTOP-G69C6PK</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
<Data Name="CsEntryScenarioInstanceIdV2">0</Data>
<Data Name="LongPowerButtonPressDetected">false</Data>
</EventData>
</Event>

here is the list of stuff that happens in the 30 secs around it: https://imgur.com/aGB0kmQ

The power goes out in the mouse and keyboard, and the pc restarts yeah, the lights inside the pc go out and back on.

[Bad 💀 Motha]

While that Windows Error doesn't mean much since it's due to loss of power. The reason you are having that issue could be the Power Supply, thermal issues, or unstable OC; causing the PC to reboot or shutdown without warning when under high loads.

[Illusion of Progress]

Originally posted by GrimReality:

So this shows up, it says its ahead in time of the critical kernel power loss...

...The power goes out in the mouse and keyboard, and the pc restarts yeah, the lights inside the pc go out and back on.

Sorry for not mentioning it, but yeah, Events 6008/63 are sort of counterparts to 41 and aren't too useful on their own. They are logs for sake of information keeping but they too are a symptom of the issue, not a cause, so not useful in tracking down the issue.

Sort by severity and look at Critical and Error type logs.

If that fails, check the directories I listed for dump files. Those are typically a little more valuable.

It's rare that there will be absolutely zero logs of anything but if there aren't, you need to start a process of elimination, and given the symptoms (power restarting, possibly powering off briefly in the interim), you would want to start with PSU and motherboard in that order. You need to ensure power delivery is good.

Before even swapping those parts though, ensure your BIOS (and all drivers) are up to date, and revert any BIOS settings (and overclocks like XMP/EXPO) back to stock. Test RAM as well. So basically, the other stuff I advised. You'd want to do the basics before having to swap parts out.