My PC crashes twice a day with Critical Kernel-Power EVEN ID 41 TASK CATEGORY (63). Advice?

Question

My PC crashes twice a day with Critical Kernel-Power EVEN ID 41 TASK CATEGORY (63). Advice?

Will Tofunk 20

Here are the crash details:

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (70368744177664),(2)

User: SYSTEM

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:

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

<EventID>41</EventID>

<Version>10</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2026-09-08T02:56:16.6106488Z" />

<EventRecordID>223412</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

</System>

<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>

<Data Name="LidReliability">false</Data>

<Data Name="InputSuppressionState">0</Data>

<Data Name="PowerButtonSuppressionState">0</Data>

<Data Name="LidState">3</Data>

<Data Name="WHEABootErrorCount">0</Data>

</EventData>

</Event>

Here are the PC details:

Processor AMD Ryzen 7 2700X Eight-Core Processor (3.70 GHz)

Installed RAM 32.0 GB

Graphics card AMD Radeon RX 580 2048SP (8 GB)

Storage 694 GB of 954 GB used

System type 64-bit operating system, x64-based processor

Edition Windows 11 Pro

Version 25H2

Installed on ‎3/‎14/‎2025

Adrenaline tuning after last IT person helped us realize the GPU was overclocked when we bought it. We thought the new tuning fixed it but it's back to crashing

Current TEst MHz 9-2-26

0 comments

2 answers

Your answer

Answer 1

Thileep Kumar 4,220 Independent Advisor

Hi, when the crash happens, do you see a blue screen (BSOD)?

The error code Kernel-Power 41(63) usually indicates a power-related issue, often caused by a sudden or unexpected system shutdown or restart. This can be due to hardware issues, particularly with the power supply or power management settings.

1). If this is a desktop, check your Power Supply Unit (PSU). If possible, try a different PSU to rule out unstable power delivery.

2). Enter your BIOS/UEFI settings > Disable CPU power-saving features such as C-States > Save and reboot to check for stability.

Also, please check if your system is generating minidump files:

Open File Explorer and go to C:\Windows\Minidump

If you see any .dmp files, compress (zip) them

Upload the zipped file to Google Drive, OneDrive, Dropbox, or any file-sharing service

Share the link here

Once you provide the minidump files, I’ll review them to help identify the cause of the crashes.

You can refer to this guide for sharing files: https://support.microsoft.com/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

Will Tofunk 20 Reputation points

2026-09-08T04:43:25.9966667+00:00

Hi Thileep! Thank you for your reply! I will pull the dmp files tomorrow if there are any. I had this issue last December and replaced the PSU fully for an 850W 80 Plus Gold model but the issue persisted so I do not believe that to be the cause. I will check BIOS to make sure the power saving settings did not revert tomorrow as well.

We do NOT see a blue screen of death when it happens. We continue to hear audio and those we're on discord calls with can hear us for a few moments as well. This leads me to think it's something to do with the weird graphics card that came built into this PC considering they overclocked a low performing model and sold it to us as a better model. I'll never buy a PC from NewEgg again!!
Thileep Kumar 4,220 Reputation points Independent Advisor

2026-09-08T09:33:27.4566667+00:00

Since there’s no BSOD and audio continues briefly, this points more toward a GPU/driver-related issue rather than the PSU (especially since you’ve already replaced it). I recommend performing a clean reinstall of your graphics drivers using DDU (Display Driver Uninstaller) and then installing the latest drivers from the manufacturer’s website.
Will Tofunk 20 Reputation points

2026-09-09T03:16:19.71+00:00

https://1drv.ms/f/c/1b076613a62f4240/IgB70PVFpNTDSIctDlUrioXJAZokLuDyjQcrDsBRwE679ck?e=iFZ31e
Will Tofunk 20 Reputation points

2026-09-09T03:18:06.37+00:00

Hopefully I got that minidump uploaded okay, it kept telling me error 0x80070005 access denied when I tried to zip it so I uploaded it without zipping
Will Tofunk 20 Reputation points

2026-09-09T03:19:07.9+00:00

I did the driver cleanup and that didn't fix the crashing only added a new annoying flickering
Will Tofunk 20 Reputation points

2026-09-09T03:28:42.23+00:00

I couldn't find this in the MSI Bios menu: Enter your BIOS/UEFI settings > Disable CPU power-saving features such as C-States > Save and reboot to check for stability.
Thileep Kumar 4,220 Reputation points Independent Advisor

2026-09-10T05:34:07.2533333+00:00

Thank you for sharing the minidump file.

The analysis indicates that the crashes are related to the AMD chipset driver. I recommend visiting your PC or motherboard manufacturer’s support page and installing the latest chipset drivers they provide. Also check if a BIOS update is available, as this can help improve system stability and resolve similar issues.
Will Tofunk 20 Reputation points

2026-09-10T15:04:07.52+00:00

Awesome! I really appreciate your guidance! And you were right! After reverting the drivers (which were up to date) to a previous version there haven't been anymore crashes. Fingers crossed it stays thay way! Thank you SO SO MUCH for all you guidance. I can't express how much I appreciate you!
Thileep Kumar 4,220 Reputation points Independent Advisor

2026-09-11T04:31:59.3566667+00:00

That’s great news, and it does confirm the issue was likely driver-related. Hopefully it continues to stay stable going forward. If you have any more questions, don't hesitate to reach out. Otherwise, please take a moment to rate the thread. Wishing you good luck!

Answer 2

Event ID 41 does not identify the exact root cause by itself. It only means Windows detected that the PC restarted without a clean shutdown. In the posted event, BugcheckCode = 0 and PowerButtonTimestamp = 0, which matches the documented scenario where Windows could not record a stop error and the problem often points to power, hardware, overheating, overclocking, or failure to write crash data.

Because the GPU was previously overclocked, start with the hardware-stability path first:

Disable all overclocking completely
- In AMD Adrenalin, return GPU tuning to default values.
- Also verify CPU/RAM are not overclocked in firmware/BIOS.
- Microsoft specifically recommends disabling overclocking when Event ID 41 with zero values is involved.
Check whether crash dump creation is failing
- Open Event Viewer → Windows Logs → System.
- Look for Event ID 46 from volmgr around the same time as the restart.
- If present, check page file configuration, because Windows may be hitting a bugcheck but failing to write the dump.
Check for overheating
- The documented guidance for this Event ID 41 scenario includes checking internal hardware temperature and overheating components.
- Since crashes happen twice a day, note whether they occur during gaming, idle, or heavy GPU load.
Check the power path
- Event ID 41 with all-zero bugcheck values can indicate interrupted power or an underpowered/faulty PSU.
- This is especially relevant if the GPU had been running outside normal settings before.
- If this is a desktop, verify the PSU has enough wattage for the installed devices and that power interruptions are not occurring.
Check memory health and configuration
- Microsoft recommends verifying memory health and that all memory runs at the same speed and is configured correctly.
Use the stop-code troubleshooting path if a blue screen appears later
- If the system eventually shows a stop code instead of all-zero Event ID 41 data, use that stop code for targeted troubleshooting.
Interpret the current event correctly
- PowerButtonTimestamp = 0 means this does not match the documented pattern for a forced power-button shutdown.
- BugcheckCode = 0 means Windows did not capture a usable stop error in this event.

Given the details provided, the most relevant next actions are:

keep GPU tuning at stock/default,
remove any remaining overclocking,
check for volmgr Event ID 46,
verify PSU adequacy/stability,
check temperatures,
check RAM configuration.

If Event ID 46 is present, focus on page file / dump configuration first. If no dump-related event exists and crashes continue with all-zero Event ID 41 entries, the documented guidance says the symptoms typically indicate a hardware problem.