Why Does My New PC Keep Crashing After 8 Hours of Use?

0
9
Asked By TechWizard42 On

I recently built a new PC and I keep running into this frustrating issue: it crashes about 8 hours after booting each day. I dual boot Windows 11 and Ubuntu, but the problem crops up on both systems, leading me to suspect it's either a hardware or BIOS issue. Here's a rundown of my build:

- **CPU:** AMD Ryzen 7 9800X3D
- **Motherboard:** GIGABYTE X870 GAMING WIFI6 (latest BIOS)
- **RAM:** G.SKILL Flare X5 Series (4 x 16GB)
- **GPU:** Gigabyte RX 7900 XTX GAMING OC 24G
- **Power Supply:** Corsair RM750x
- **SSDs:** WD Blue SN570 NVMe 1TB (Windows), WD Blue SN550 NVMe 1TB (Ubuntu)

I've tried tweaking various settings like enabling/disabling XMP/Expo for the RAM and disabling Secure Boot. I also reinstalled my graphics drivers and ran Memtest86+, which didn't reveal any issues. The bluescreen errors in Windows have been 139 and 3b, indicating possible RAM or driver problems, but I'm stuck on figuring out the root cause. My temperatures are fine, staying below 60 degrees even under load due to my custom water cooling loop. Any insights or tips would be greatly appreciated!

4 Answers

Answered By MemoryMaster88 On

It sounds like you’re dealing with a possible memory leak. Keep an eye on your memory usage as it could provide some clues. However, I agree with the others about getting those dump files for a proper analysis of the BSODs.

Answered By DumpDiver99 On

You should definitely get some crash dump files for better insight into the BSODs. Check the C:WindowsMinidump folder and zip any files you find there. Sharing multiple dump files can really help in pinpointing the issue.

Answered By BenchmarkBard On

Have you tried running benchmarks again? It's a good idea to stress test your system with Cinebench or 3DMark to see if the problem persists during intensive tasks. It might reveal stability issues you missed before.

Answered By KernelHunter On

It looks like `ntoskernl.exe` is mentioned in the crash dump, which typically indicates a kernel panic. It's a bit generic, though—it may not point directly to your issue. You might want to explore other factors like drivers or hardware compatibility.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.