Deep System Reboot – Kernel Controls
Deep System Reboot – Kernel Controls
Alright folks i need some help trying to identify a very annoying problem. The Problem: - Hard PC reset with no warnings or BSOD Occurs: - Heavy games - Palworld & Red Dead Redemption 2 - Does not do it on Destiny 2, BeamNG Drive - Has done it randomly on idle - Hard to manually trigger the Problem. Troubleshooting I've Done - turned off Automatic Restart to try see info - Memtest & Windows Memory Check Passed - Brand new PSU - Stress test GPU & CPU - Hard drive checks - Updated & Reset BIOS - Fresh Windows Install - I've unplugged an RGB strip and turned off 1 of 4 Noctua case fans (in case there's some sort of power limit reach?) - Stock clocks on all hardware - Thermals all seem fine. CPU max temps (celsius) ~80 / GPU max ~70 Event Viewer - Critical Kernel Power error, Incorrectly shut down etc. PC Specs Ryzen 5900X Gigabyte X570 AORUS PRO WIFI MSI RTX 2080 Super Noctua NH-U12S 2x Corsair Vengeance (4x16GB) 3200MHz CL16 DDR4 CORSAIR RM850x Focusrite Scarlett 2i4 USB Interface My Thoughts - at first i thought a dodgy capacitor on the PSU under load, brand new PSU this weekend did the same thing. - Could it be dodgy VRAM? How can i run a test for that? - will reseat cpu cooler & refresh thermal paste (my understanding is a thermal shudown, would shutdown, not restart) - Would a dying usb audio interface trigger a hard reset? I'm open to ideas on how to identify this.
Open Event Viewer → Windows Logs → System. Choose "Filter Current Log" on the side. In the new window, locate the "Event Sources" dropdown and pick "WHEA-logger". Click OK to apply the filter. If you see any WHEA events, highlight them, right-click and save. Upload the .evtx file to the forum. If there are no WHEA events, power is likely the issue.
PSU testing in OCCT could involve CPU and GPU stress like Core Cycler or Prime95 plus Furmark. It seems stable under high Furmark loads—no crashes detected. A 3DMark Stability check would show normal scores. No undervolts or overclocking applied. VRM issues might trigger shutdowns or hard resets without a BSOD. Ensure the latest SSD firmware is installed and monitor temperatures.
The details in the general section indicate who reported the issue, not what triggered it. To understand the root cause, you need to analyze the error packet within the RawData fields using the UEFI guidelines. The processor is initiating shutdowns, which appear as "Previous Error," indicating it's responding to a prior failure rather than the actual fault. These logs don't reveal the original problem. Approximately 90% of cases involve the CPU, though other components like PCIe devices or motherboard sections may also be responsible. We frequently encounter voltage problems in 5000-series models, so adjusting a fixed static voltage has resolved many crashes on CPUs such as 5900x and 5950x. In the BIOS, configure the CPU to run at 1.3V and set the SoC to 1.1V (CPU Vcore and SoC VCORE on this board).
I don't have any options then. I'm not into adjusting voltages or overclocking, which isn't something I'm familiar with. I noticed you mentioned missing a step about enabling Precision Boost Overdrive (PBO) in the BIOS. You might also want to try changing the voltage again once it's turned off if it was previously active.
Initially, the primary issue was a defective CPU, which was being addressed to restore stability. If further troubles persist, the CPU is probably faulty. It's also possible this relates to a PCIe device, as many motherboard components connect via PCIe internally, such as audio, network, and storage controllers.
I experienced this kind of restart issue before too, so I reported it to the manufacturer and even sent it back for replacement. The same problem continued with the new CPU. Eventually, it was my GPU—an RX 5600 XT used—that caused the issue. You might want to check if someone has a spare GPU or try swapping your current one to see if it works.