Pc regularly crashing, sporadically

Question

Hello!

My computer has been having issues with crashing for the better part of a while now, it always does crashes within a few minutes of the first start up of the day, and then normally once more after i put it under heavy load.

after those first few crashes are out of the way though, it'll be stable for sometimes multiple hours. even under heavy load.

I did as much trouble shooting as i could on my own, and I've disabled all of the overclocks and bios tweaks ive done, freshly installed windows OS, Ran DDU, done health checks on most everything and it always comes back healthy. but the problem persists and im kind of at a loss.

I have a couple mini dump files, if that helps at all -

https://drive.google.com/open?id=1uj5sRaGwf2bv6A0qbueUzdK8FwxJxdJt&usp=drive_copy

https://drive.google.com/open?id=1SFHMlbIt60rtFXyBvEoBXVzLuSaBp3FQ&usp=drive_copy

Answer 1

I tried to download your minidump files, but Google Drive indicates the files are not shared, please try sharing the files again, and please let me know here when the files are shared, I will then analyze your data for you.

Answer 2

Based on the description and the fact that minidumps are available, the next step is to analyze those dump files to identify the failing driver or component.

Follow these steps on a working Windows PC:

1. Configure the crashing PC to generate full dumps
   • Ensure it is set to create at least a kernel or complete memory dump so future crashes are more informative. See the guidance under Create and analyze kernel-mode memory dump files and Generate a kernel or complete crash dump.
2. Install WinDbg (Debugging Tools for Windows)
   • On another computer, install the Windows 10 SDK and select Debugging Tools for Windows during setup. This installs WinDbg.
3. Set up symbols in WinDbg
   • Open WinDbg.
   • Go to File → Symbol File Path.
   • Set the symbol path to the Microsoft public symbol server:
     • https://msdl.microsoft.com/download/symbols
   • Select OK.
4. Open and analyze the dump files
   • In WinDbg, select File → Open Crash Dump and open each of the .dmp files.
   • Let WinDbg load symbols, then use the basic analysis commands (for example, !analyze -v) to identify:
     • The bug check (stop) code.
     • The faulting module or driver.
   • Use the stack trace and module information to see whether the crashes are caused by a third‑party driver (GPU, storage, antivirus, etc.) or by hardware.
5. If crashes persist and analysis is complex
   • Advanced kernel‑mode dump analysis can be challenging. If the dumps point to low‑level components (kernel, storage stack, graphics stack) and the cause is not obvious, use the advanced references and techniques described in the Advanced troubleshooting for stop code errors and Kernel-mode dump files documentation to dig deeper, or share the analyzed output with a Windows expert.

If the dump analysis indicates a specific driver, update, roll back, or temporarily remove that driver and test again. If dumps consistently implicate different, unrelated components, suspect underlying hardware (RAM, motherboard, PSU, or storage) even if basic health checks pass.

---

References:

• Advanced troubleshooting for stop code errors
• Kernel-mode dump files