Question Random restarts on Windows 11?
Question Random restarts on Windows 11?
Hello, recently I've faced some unexpected restarts within the first 2 to 3 minutes after loading. At times, these issues are severe enough that I can't even access my Windows. I've already changed my PSU, RAM, and reinstalled Windows. Interestingly, I haven't experienced these reboots when running Windows in safe mode during testing.
Here is the dump file I obtained using WinDbg Crash Analyzer:
https://textbins.online/kphycnnqyg
And the dump file:
https://files.catbox.moe/tnb1fn.dmp
CPU: i7 14700K
Motherboard: Z790 AORUS ELITE AX rev 1.x
Motherboard BIOS: FLb (last bios available)
RAM: Corsair Vengeance RGB DDR5 RAM 32GB (2x16GB) 6000MHz CL30 AMD Expo iCUE
PSU: Corsair RMx Series RM850x 850W black 127V
OS & Version: Windows 11
I'm also sharing the errors I'm encountering in the Event Viewer:
https://imgur.com/a/GC2DUU7
View: https://imgur.com/a/GC2DUU7
https://imgur.com/a/qbKIVUW
The error shown in the analyzer is associated with the following address: ffffa80fd6d38028. Does this issue consistently appear with this input? I’m unsure about the exact nature of the problem, but if the same address repeats each time, it might indicate a specific hardware configuration. If the address varies, it could point to another component rather than a single piece of hardware.
Triple hardware exceptions are built to halt operations immediately to safeguard your disk and storage from further damage. The x86 architecture uses interrupts to signal the CPU about upcoming actions (via an IRQ vector table), and in case of failure, it has mechanisms to handle such situations. However, reaching a triple failure leaves no viable options for recovery without risking total data loss.
You’ve swapped the power supply, but sometimes it’s actually the power line connected to it that causes trouble. Many people overlook this connection. If your power supply uses a surge protector, it guards against sudden spikes. Yet, a more subtle issue is a brownout—voltage too low to run stably but still present. This is why some buyers opt for an UPS with brownout protection. If the address keeps changing and not remaining consistent, it may suggest your power line is involved. Consider getting a brownout-protected UPS or checking your socket wiring, as incorrect connections can affect stability.
Thank you for your kind words. Your explanation was very useful in clarifying my issue. At the moment I'm operating in safe mode without any reboots. I experience two kinds of restarts: one that works smoothly and another that triggers a blue screen with the WHEA_UNCORRECTABLE_ERROR message. Additionally, I have a PSU from CyberPower called CST135XLU. I’m not very familiar with it, but the specs say it supports "Line Interactive Topology" and mentions brownouts.
For testing purposes, attempt to operate your system without the UPS. Occasionally, the UPS itself may begin to fail—such as due to a worn battery—and not perform optimally. Check if the failure pattern remains consistent without a direct connection to the wall outlet (though you could place it on a surge protector, just remember not to connect a surge protector to an UPS or vice versa).
The dump bugcheck corresponds to a 0x124, classified as a WHEA_UNCORRECTABLE_ERROR. The logs clearly indicate hardware-related WHEA errors. WHEA is responsible for identifying and handling hardware faults, aiming to resolve them when feasible. Within this dump, the specific issue is a machine check exception, representing a critical hardware failure. It's reassuring that the system does not trigger a BSOD in Safe Mode, though a hardware fault remains possible. The initial concern centers on RAM; despite having 6000MHz RAM installed, it isn't overclocked and operates at its standard speed of 4800MHz. From a troubleshooting standpoint, this is positive. I recommend removing one of the 16GB modules (in B2) to test stability with a single stick. After a short period, swap the sticks and place the other in A2 to verify stability on that one. If the system still BSODs on both sticks individually, it likely points away from RAM issues. Prior to addressing CPU concerns, it's wise to check for unstable drivers. Although rare, faulty drivers can cause 0x124 BSODs, and Safe Mode stability supports this theory. I suggest enabling Driver Verifier, but only in a specific configuration.
Driver Verifier automatically tests selected drivers—typically third-party ones—each time they are accessed. These additional checks help detect drivers that behave erratically. Should any driver fail these verification steps, Driver Verifier will trigger a BSOD. The resulting minidump should provide sufficient details to pinpoint the problematic driver.
Therefore, it's crucial to retain all minidumps generated during Driver Verifier use.
To activate Driver Verifier:
1. Save a System Restore point or create a disk image of your system drive using software like Acronis or Macrium Reflect. Driver Verifier might cause a BSOD during boot if certain drivers are loaded, potentially trapping you in a boot loop. If this occurs, restart using the Windows installation media to restore from the saved point and remove Driver Verifier.
2. Launch the Driver Verifier setup by typing 'verifier' in the Run dialog or command prompt.
3. On the initial screen, select 'Create custom settings (for code developers)' and proceed to the next step.
4. In the second screen, enable the checkboxes for tests such as Special Pool, Force IRQL checking, Pool Tracking, Deadlock Detection, Security Checks, Miscellaneous Checks, Power framework delay fuzzing, and DDI compliance.
5. Click Next.
6. On the following dialog, choose 'Select driver names from a list' and then Next.
7. In the subsequent section, verify all drivers except those with Microsoft as the provider (i.e., scan third-party drivers).
8. Then, within the same dialog, confirm the presence of these high-level Microsoft drivers:
- Wdf01000.sys
- ndis.sys
- fltMgr.sys
- Storport.sys
These are essential for managing lower-level drivers.
9. Finish the setup and reboot your system. Driver Verifier will be activated.
Please note that Driver Verifier must remain enabled after reboots and shutdowns; it can only be manually disabled. We anticipate BSODs as a necessary condition to gather sufficient diagnostic information. Ensure all minidumps are preserved while Driver Verifier is active, as this step is critical for identifying the faulty driver.
To exit Driver Verifier:
- Enter 'verifier /reset' in the Run dialog or command prompt and restart.
- To verify it's off, run 'verifier /query'. If drivers appear, it's enabled; if not, it's disabled.
- After disabling, go to C:\Windows\Minidump, locate all .dmp files from the period of Driver Verifier activity (adjust timestamps), compress them if desired, and upload them to the cloud with a public link.
This process ensures you capture the necessary evidence for driver analysis.
I didn't fully understand everything you said. But one possible solution is to restart your system using your OS—whether it's a physical hard drive or a bootable USB—and use the built-in repair or fix options in the install menu. If that doesn't help, I recommend completely reformatting your drives and starting over. Sorry for any confusion.