What STORE_DATA_STRUCTURE_CORRUPTION means

The store component keeps its own data structures for memory compression and paging. This stop means it found them damaged. Drive problems, driver issues, damaged system files or a sudden power loss can contribute, so it is wise to check storage and system files first.

Common causes

  • A drive with errors or an unreliable controller connection
  • Outdated storage drivers or SSD firmware
  • Damaged system files after an interrupted update or power loss
  • Faulty RAM, less often

How to fix STORE_DATA_STRUCTURE_CORRUPTION

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

  1. Check the health of the drive. Read the SMART data with the drive maker's tool or CrystalDiskInfo and look for reallocated or pending sectors, media errors and a low remaining-life figure. Back up important files first if the drive reports any warning.
  2. Repair Windows system files. Open Terminal (Admin) and run sfc /scannow. If it reports damage it could not repair, run DISM /Online /Cleanup-Image /RestoreHealth, restart, and run sfc /scannow once more.
  3. Scan the file system. Open Terminal (Admin) and run chkdsk C: /scan. If it finds errors, back up first and then schedule a repair with chkdsk C: /f.
  4. Update storage drivers and firmware. Install the chipset and storage package from the PC or motherboard maker, and check the SSD maker's utility for new firmware.
  5. Test the memory. Run Windows Memory Diagnostic (search for it in Start) for a quick check, then MemTest86 for several passes if the crashes continue. Any error points to a faulty stick or slot, or to memory settings the hardware cannot run reliably.
When to stop and protect your data

Recurring corruption on a healthy-looking drive can mean a power-delivery or controller problem, so test with another drive if you can.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other storage and file system errors