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

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:

1. 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.
2. 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.
3. 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.
4. 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.
5. Check memory health and configuration
   • Microsoft recommends verifying memory health and that all memory runs at the same speed and is configured correctly.
6. 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.
7. 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.

• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"
• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"
• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"
• Troubleshooting Windows unexpected restarts and stop code errors