PC Reboots - Kernel-Power Event 41 Task Group 63 - Unknown Reason?
PC Reboots - Kernel-Power Event 41 Task Group 63 - Unknown Reason?
The WHEA notifications indicate a shutdown command from the CPU due to critical issues it can't resolve quickly enough. The definition remains vague, with no clear explanation of what qualifies as a "core component." It appears this functionality is bundled into WHEA by Windows for compatibility reasons. BERT (Boot Error Record Table) handles this but lacks substantial documentation; its contents are mostly unreadable. No guidance exists on interpreting the error packet or identifying the source—whether it's the CPU itself or a PCIe device like USB controllers, storage units, or network interfaces. Generally, the CPU is the most common culprit. Eliminate any overclocking or undervolting settings, especially RAM speeds exceeding 3200MT/s. Verify that Precision Boost Overdrive is turned off in the BIOS.
Thank you so much for the quick response. I am always wondering if it is PSU related somehow but I'd rather know before replacing blindly. Processor is currently running at stock - I suppose I could try to remove any XMP profile and see what happens / reset BIOS to default. Thank you for the great insights and extra information - I have been trying to play around with ChatGPT as well to try to guide through ideas in case something random comes up.
Today marked the third crash in three days. My system often runs around seven Chrome tabs with no games open. I typically spend about five hours a day using this PC. I’ve restored the BIOS to the default settings and the RAM is set at 2133 MHz (no XMP profile). I’m weighing the pros and cons of getting another power supply, hoping it might resolve the issue but nothing is certain.
Hi, have you received any news from the original poster? I’m seeing some similar restarts happening, and I’m wondering if switching to a different PSU would be a good idea for me.
Hello, I'm refreshing this thread while trying to resolve the problem, possibly with an update. I've installed a new PSU – a Corsair 1000W RMX (RMx) – which you can find here: https://www.corsair.com/ca/en/p/psu/cp-9...9020271-na. It was set up on January 31st. Until then, I expected a crash within about 15 days, but everything seemed normal until today when another similar issue occurred with a slight difference. I checked the Event Viewer and noticed it happened once more on February 25th without me realizing it. At that time, my computer was running for three consecutive days straight (unusual for me – I usually shut down at night and still use the machine daily). Right when it crashed, I was uploading media to Facebook (~500 photos in an album). Here’s what the Event Viewer showed: Windows Log → System. In the custom administrative view, the events look different from previous restarts. I’m wondering if anyone knows what might be causing this now? I thought the first restart after the new PSU was the last one, but it seems it could have happened again in February, though much less often. Thank you in advance for any insights!
Occurred twice within an hour yesterday—suggests the PSU wasn't the correct solution.
I'm facing the same issue as you did. After replacing my PSU, the problem continued. My system specs include a Ryzen 5 5600 CPU, a RTX3080 GPU, 10GB of VRAM, an Asus TUF 550M+ motherboard, an MSI 850W power supply, and 2TB NVMe storage. The issue appears when I play games—processing and graphics hit their limits, causing freezing and a restart. If you find a fix, let me know. Have you made any improvements yet?
I made multiple adjustments, it's hard to tell which improved things, but at first the issue ceased. - Updated all BIOS settings. - Restored default values for the motherboard. - Enabled the GPU Resize Bar on the board. - Set fans (CPU, GPU, CHA) to run more vigorously even at low temps (near 70ºC they reach nearly 100%). - Turned off Windows Fast Startup. - Removed the GPU driver using DDU and reinstalled it. With these changes I successfully completed stress tests for GPU and CPU using FurMark2 for 15 minutes without issues. I'll keep testing and share updates.