BSODs accompanied by "Corrupted" DMP files
BSODs accompanied by "Corrupted" DMP files
I've been experiencing unpredictable BSODs since setting up my PC a year ago. They appear as sudden crashes with black screens, random audio spikes, and eventual restarts. These events happen during gameplay, sometimes every hour (Blue Prince and Helldivers 2 are most affected), occasionally even when the system is idle—especially after leaving it on for a while. In the Event Viewer, they’re logged as WHEA error 46.
My research suggests a range of possible causes: CPU problems, RAM failures, VRAM issues, or even the SSD itself. I’ve tried disabling XMP settings and updating the BIOS, which reduced crashes temporarily until Blue Prince was played again. Running thermal tests with Prime95 and Furmark didn’t trigger any issues, though GPU temperatures stay in the high 70s—CPU temps are normal. Memory tests using memtest86 passed without errors, and CrystalDiskInfo shows a healthy SSD.
I’ve examined DMP files via WhoCrashed, which only indicated hardware faults or overheating. Recently, after updating Windows, it reported my hardware as unsupported, pointing to a firmware problem on the SSD. I updated the firmware and avoided crashes for a week (playing Blue Prince). However, after a week, another BSOD occurred with a corrupted DMP file.
I’m now unsure what to do next. Any advice would be invaluable. Thanks in advance.
There were problems with SSDs lacking DRAM and using HMB, such as the SN770, which seemed limited to Windows 11 24H2. Are you experiencing WHEA uncorrectable issues? With Ryzen processors, these are often linked to unstable CPU settings. Do you employ PBO or curve optimizer? What type of RAM are you using? It would be wise to check, as these concerns could lead to data loss affecting your Windows setup or drivers.
I'm using the SN770. Yes, WHEA uncorrectable. I haven't manually enabled PBO and think I restored my BIOS settings back to defaults at some point. I'll verify later. Let me check my order history... T-FORCE VULCAN Z 32GB (2 x 16GB) 288-Pin PC RAM DDR4 3600 (PC4 28800). I plan to attempt that next weekend.
It seems uncertain at first, but it looks like a new setup was done on Sunday. The system just stopped working again, so likely the problem isn’t with the installation.
WhoCrashed processed this case. I can recheck the temperatures, though I’m sure they’re normal. Here’s the info from the viewer:
- Event ID: 46
- Timestamp: 2025-06-10T17:00:54.8978196Z
- Device: BeanMachine
- User: S-1-5-19
Details inside show an error code, but the data itself appears intact.
I've added a 3400g to check if the problem lies with the CPU. So far, I haven't experienced any crashes for several days. I'm optimistic, though since I've been stable before, it's tough to confirm the CPU is the cause.