Multiple BSODs occurring; memory is only a couple of years old.
Multiple BSODs occurring; memory is only a couple of years old.
Hello everyone! I've been using sleep mode more often instead of shutting down completely to keep my browser tabs open. But this has led to more crashes, always triggering a FAULTY_HARDWARE_CORRUPTED_PAGE error. The first time it froze completely during the BSOD, I waited 20 minutes before powering it off. The second time today it worked fine and generated a proper crash dump. I'm still running Windows 10 (European version, with updates), a 64-bit system. My specs are: Ryzen 5 5600 CPU, 2x8GB RAM, 3600 CL18 Corsair Vengeance RX 6600, Sapphire Pulse GPU B550M-DS3H, Miron 2200 SSD, 512GB, Cooler Master MWE 600 Bronze, and a B550M-DS3H PSU. I'll attach the dump file for you! Any assistance would be greatly appreciated. 010726-13890-01.dmp
If you suspect ram at all, how about you test the ram? I'd use either memtest86 or memtest86+ from a boot USB. Have you made any adjustments to the CPU settings?
The issue usually stems from problems with the page file, a storage component rather than RAM. The dump data confirms crashes during storage access. While memory errors can sometimes appear unpredictable, they often originate in RAM before reaching the page file. If such crashes occur frequently, the storage drive containing the page file—especially if it has multiple drives—becomes the likely culprit. A BSOD displaying 0% is also a common sign of storage-related faults.
You can check your storage usage by using built-in tools like Disk Management or Task Manager to see how much space is occupied. Since you only have the SSD, ensure it’s properly recognized and monitor its free space regularly.
I haven't changed anything at all! I'll try testing the RAM later.
When using SATA, you can view SMART data with CrystalDiskInfo. For NVMe, the SMART information has been significantly reduced and is largely irrelevant beyond basic temperature readings. There are no dependable tools available for NVMe drives. If you're unsure about the displayed values, feel free to share a screenshot. The portion of CDI above is largely meaningless. Drive health reports have been inconsistent for over a decade, as manufacturers control how much failure is tolerated before status changes, and many are unreliable. The percentage value is often incorrectly linked to overall drive health, but it only reflects remaining write capacity and offers little insight into current condition. Focus on the parameters in the lower half of CDI for more accurate information (unless it's NVMe, where useful data has been removed).