Pc crashes

Question

My PC randomly crashes and reboots without warning, but it only happens at most once per day. After a crash, it can also go several days without any issues. It has never crashed twice in the same day.

Sometimes the crash happens while the PC is just sitting idle and I return to find it has restarted. Other times it happens shortly after opening my web browser. There’s no clear pattern.

My specs are:

• GPU: GeForce RTX 4060 Ti

PSU: ASUS 850W TUF Gaming Gold, 80 Plus Gold

Motherboard: ASUS TUF GAMING B650-PLUS (ATX)

CPU: AMD Ryzen 5 7600X

RAM: Kingston 32GB (2x16GB) Fury Beast DDR5 6000MHz CL36

• OS Drive: Kingston SA400S37960G

(Here are the minidumps)

https://drive.google.com/file/d/1_ekAqy6slafffwOiS35rUJ0MbmXcofvq/view?usp=sharing

Answer 1

The minidump files do not indicate any driver or hardware causes, only memory corruption.

Try forcing Windows to show failed drivers and produce minidump files, enable Driver Verifier for this.

Before running Driver Verifier, create a new system restore point.

Click on start menu and type "verifier".

Select "Create custom settings (for code developers)" > "Next".

Check all options except "DDI compliance checking" and "Randomized low resource simulation".

Click Next > Select "Select driver names from a list".

Next Select all drivers NOT provided by Microsoft. > Next > Finish.

Restart the system until the BSOD occurs 3 times and minidump files are generated.

If you have problems starting Windows after enabling Driver Verifier, follow these steps:

Start your PC, as soon as Windows tries to load (spinning dots appear), press and hold the power button for 5 to 10 seconds to perform a forced shutdown

Do this three times.

Windows will boot into the Recovery Environment.

Go to Troubleshoot > Advanced Option > Startup Settings and click Restart.

When restarting, press 4 to enter safe mode.

Open command prompt as administrator, run these two commands and restart your PC.

verifier /reset

verifier /bootmode resetonbootfail

Answer 2

Random crashes and reboots can be caused by various factors, including hardware issues, driver problems, or system configuration. Here are some troubleshooting steps you can take to identify and potentially resolve the issue:

1. Check Event Viewer: Look for any critical errors or warnings in the Event Viewer that occurred around the time of the crashes. This can provide insights into what might be causing the issue.
2. Memory Check: Since your crashes can occur while idle, it might be worth running the Windows Memory Diagnostics tool to check for memory issues. Faulty RAM can lead to random crashes.
3. Power Supply Check: Ensure that your power supply unit (PSU) is functioning correctly and providing enough power to your components, especially under load. An insufficient or failing PSU can cause random reboots.
4. Overheating: Monitor the temperatures of your CPU and GPU to ensure they are not overheating. High temperatures can lead to system instability and crashes.
5. Driver Updates: Ensure that all your drivers, especially for the GPU and motherboard, are up to date. Outdated or incompatible drivers can lead to system crashes.
6. Check for Overclocking: If you have overclocked any components, revert them to their default settings to see if that resolves the issue.
7. Run Hardware Diagnostics: Use any built-in diagnostics tools provided by your motherboard manufacturer to check for hardware issues.
8. Review Minidumps: Analyzing the minidump files can provide more specific information about what caused the crashes. You can use tools like WinDbg to analyze these files.
9. Software Conflicts: Consider whether any new software installations coincide with the start of the crashes. Uninstalling or disabling recently added software may help identify the issue.

By following these steps, you should be able to narrow down the cause of the crashes and take appropriate action to resolve them.

---

References:

• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"
• Troubleshoot bug checks (stop code errors)
• Advanced troubleshooting for stop code errors
• Crashdump Support Test (LOGO)
• More information