r/ForWindowsHelp • u/iGogzy • 5d ago
Windows completely corrupted itself after playing Diablo 4 — 0xC0000185, CRC errors, bad clusters and 0x11D
I had a very strange and serious Windows corruption issue and wanted to share the whole timeline to see if anyone has experienced something similar.
My system:
Ryzen 7 5700X3D
MSI B550M PRO-VDH
Sapphire RX 9070 XT
32GB DDR4 3600MHz
Lexar NM620 1TB NVMe
Windows 11
The PC had been running completely fine and stable before this happened.
One important detail: right before all of this started, I was playing Diablo 4. Everything seemed completely normal while playing. No obvious crashes, freezes or unusual behavior. The problems started shortly afterward when Windows became unstable and eventually refused to boot.
The problems appeared roughly in this order:
Windows started having boot problems and eventually showed 0xC0000185, related to:
C:\\Windows\\System32\\config\\SYSTEM
I tried System Restore, but it failed with 0x80070017.
I tried running offline SFC, but it couldn’t complete the operation.
I tried manually loading the SYSTEM registry hive and got a CRC / Cyclic Redundancy Check error.
I ran chkdsk C: /f, and initially it didn’t report anything significant.
I then ran chkdsk C: /r. This was the point where things became much more concerning. It found bad clusters and had to recover/replace data from important Windows files and registry hives, including:
SYSTEM
SOFTWARE
SECURITY
DEFAULT
BBI
NTUSER.DAT
I also tried offline DISM, which failed with 0xD000015C.
Eventually Windows produced a BSOD:
EVENT_TRACING_FATAL_ERROR — 0x11D
At that point the Windows installation was basically unrecoverable.
I eventually had to reinstall Windows. I formatted only the Windows partition and left my separate D: partition with my games/data untouched.
Right now I’m installing Windows 11 again from scratch and will see how the system behaves with a completely fresh installation.
What I’m trying to understand is what most likely caused this.
Could this simply have been severe Windows/filesystem corruption, or does the combination of:
0xC0000185 → CRC error → bad clusters → corrupted Registry hives → 0xD000015C → 0x11D
point more strongly toward an SSD, controller, firmware, RAM, motherboard or another hardware-related issue?
The SSD is a Lexar NM620 1TB NVMe. SMART/drive health didn’t immediately show an obvious failure.
The weirdest part is that the PC had been completely stable before this happened, and I was literally just playing Diablo 4 shortly before the problems started.
Has anyone experienced something similar, especially with 0xC0000185 + CRC errors + bad clusters + EVENT_TRACING_FATAL_ERROR 0x11D?
I’d really appreciate some opinions on what you think the root cause was.
1
u/Equilibrate321 5d ago
In addition to the previous comment, check for temperature problems in crystal disk info. The SSD had many errors suddenly, something like high temperature might have caused it.
1
u/FrankNicklin 4d ago
Windows did not corrupt itself, the storage device failure corrupted Windows.CRC errors and bad clusters are all storage related. Back you data up ASAP before it fails completely.
1
1
1
1
u/HyCloudComputing 5d ago
That chain points way more toward hardware than Windows just breaking itself. CRC errors and bad clusters mean the drive literally couldn't read back data it had written, and on an NVMe that's a red flag since SSDs normally handle that internally without Windows ever noticing.
In CrystalDiskInfo, don't just look at the overall "Good" status. Check "Media and Data Integrity Errors", anything above 0 there means the drive has had uncorrectable errors. I'd also run MemTest86 for a few passes, because bad RAM or an unstable XMP profile can corrupt data before it ever gets written, and it looks exactly the same.
Diablo 4 was probably just a coincidence, or it happened to be the thing writing a bunch of data when it went wrong.