Occasional unexpected shutdowns and system crashes
Occasional unexpected shutdowns and system crashes
Hello everyone. I've been facing occasional crashes and freezes lately, trying to figure out the cause. My PC was set up in December 2023 with XMP enabled from the start for a few months. Around March, the issues began sporadically, but they were rare at first. As usage increased, the problems became more frequent. By mid-May, the system would frequently crash or freeze without warning. Recently, it froze three times in a row. I've noticed that every couple of hours, sometimes once a day, the PC would randomly BSOD or shut down. When it freezes, I can still see the last screen capture, but everything stops responding, and audio stutters briefly before restarting. Here are my basic system details:
- Motherboard: Asus TUF GAMING Z790-PRO WIFI ATX (LGA1700)
- BIOS Version: 1656
- CPU: Intel Core i7-14700K at 3.4 GHz
- Cooler: Thermalright Peerless Assassin 120
- RAM: G.Skill Ripjaws S5 64 GB (2×32 GB) DDR5-6000 CL30-40-40-96, 1.40V
- Storage: Samsung 980 Pro 2 TB M.2-2280 PCIe 4.0 X4 NVME
- GPU: PNY XLR8 Gaming VERTO EPIC-X RGB GeForce RTX 4070
- PSU: EVGA SuperNOVA 850 P2 850W (80+ Platinum)
- OS: Windows 11 Pro x64
I added extra case fans to improve airflow and kept the BIOS updated, but that's all I've changed since launch. Most crashes don't trigger a BSOD; instead, I experience random freezes or BSODs after a few seconds, followed by a restart. Occasionally, apps on the system drive get corrupted, showing partial zero-byte files.
I've collected various minidumps and run stress tests. Usually, I don’t see a consistent cause, but when I do, it's often related to memory corruption or driver issues. For example:
- **Prime95** with XMP can cause crashes or BSODs; sometimes Worker #7 fails after ~60 seconds.
- **Memory swap** helped slightly, but not a long-term fix.
- **Driver verifier** revealed issues with Razer Synapse and voice-meeter banana drivers.
- **CPU reseating** didn’t resolve the problem.
- **Memtest86** showed no errors.
I’m still trying to pinpoint the exact cause and need advice on next steps. Any suggestions would be greatly appreciated.
Hey! I handle tech support for a big PC OEM company, and while your system isn’t exactly one of those (unless you missed it), most of what’s going on is part of my regular work. If I had to tally how often reinstalling Windows helps, I’d probably count it in the hundreds. This approach works well for us because a clean install can really help pinpoint whether the problem lies with software or hardware.
For troubleshooting, a fresh Windows setup is great—it might narrow things down to hardware issues if Windows isn’t the culprit. As an extra tip, consider getting a very affordable SSD or HDD (the cheapest you can find from a trusted brand) and install a fresh Windows version on it. This way, you avoid having to wipe your main drives just for testing.
If the problem disappears after switching drives, you’ve likely hit a software issue. If it persists, we might need to check the motherboard or RAM instead.
The issue seems linked to data stored in the dump files. Memory isn’t always RAM, but it’s often the main concern. Windows moves low-priority RAM information into the page file and retrieves it when needed, making storage appear as memory. The controller inside the CPU can cause this behavior; failure here would make it seem like memory is present. If storage is involved, half of the dumps point to storage or its drivers—this isn’t present here, suggesting it’s not storage-related. If there are overclocking or voltage issues, remove them. Lowering RAM speed to 5600MT/s is recommended since that’s the maximum Intel supports for this chipset. Power problems mainly affected the 13900K and 14900K models, though other K series might be impacted too. Have you tried activating the Intel Baseline Profile in the Extreme Tweaker section of the BIOS? Since you’re already using the latest version, that setting should be enabled. Test RAM by running the machine normally with one stick at a time. If only one stick causes crashes, it’s likely a faulty stick. If both cause issues, the CPU may be the culprit. Memory testers often miss defective RAM, especially DDR4 and newer types. Due to frequent freezes, RAM isn’t usually the clear suspect—it’s not a typical symptom. The stack in the dumps shows no signs of corruption either. Crash-related file damage is common, so running an SFC scan can help detect hidden issues without false BSODs. Don’t depend solely on SFC fixes; it usually identifies corruption, even if it claims resolution.
Thanks for your feedback and detailed review. Here’s a concise summary of the updates:
I revisited the Asus website after posting and found the new BIOS version (1658) released. The changelog mentioned adopting Intel’s “Intel Default Settings” and adjusting several power limits. After flashing, I confirmed the changes: the “Current Long Duration Package Power Limit” was updated from 253W to 4095W, and the “Current Package Power Time Window” changed from 96 seconds to 56 seconds. The “ASUS MultiCore Enhancement” option is now disabled with all limits enforced.
I also noticed stability improvements after running Prime95 with XMP enabled and performing benchmarks like Cinebench and OCCT. No failures observed so far. I continued using the system normally, hoping for further stability.
EDIT: Performed an extra power cycle and double-checked BIOS settings; defaults now show 307A / 253W / 253W, matching the CPU specifications. The previous version had different values (511.75A / 253W / 4095W / -1/unlimited).