What does BSOD 0x1C7 (STORE_DATA_STRUCTURE_CORRUPTION) mean?

STORE_DATA_STRUCTURE_CORRUPTION

The STORE_DATA_STRUCTURE_CORRUPTION bug check has a value of 0x000001C7. It indicates that the store component detected a corruption in its data structures.

STORE_DATA_STRUCTURE_CORRUPTION Parameters

Corruption ID

 0x0 : A chunk heap buffer's hash doesn't match.
    2 - Chunk heap buffer whose hash didn't match.
    3 - Expected buffer hash.
    4 - Page frame number of the corrupted page.

 0x1 : An unhandled exception occurred on the store thread and a chunk heap buffer's hash doesn't match, which is likely the source of the exception.
    2 - Chunk heap buffer whose hash didn't match.
    3 - Expected buffer hash.
    4 - Page frame number of the corrupted page.

 0x2 : Page data appears corrupt during a read and the corresponding page record's heap buffer hash doesn't match.
    2 - Chunk heap buffer whose hash didn't match containing the page record of the data being read.
    3 - Expected buffer hash.
    4 - Page frame number of the corrupted page.
 
 0x3 : Page data appears corrupt during a read and the corresponding page record has changed since the start of the read operation.
    2 - Pointer to the page location information snapped from the page record that was found when the read was initiated.
    3 - Pointer to the page record currently in the page tree for the same page key.
    4 - Reserved.

Cause

The store component detected a corruption in its data structures.

This bugcheck can occur by memory corruption due to physical memory access. The causes for physical memory corruption include:

1. Defective RAM hardware
2. A driver or device incorrectly modifying physical pages via an incorrect DMA operation or associated MDL.
3. Corruption caused by a hardware device or firmware corrupting memory, such as firmware illegally modifying physical pages across a power transition.

For more information on Windows memory manager, see Windows Internals 7th Edition Part 1 by Pavel Yosifovich, Mark E. Russinovich, David A. Solomon and Alex Ionescu.

Resolution

Start with the corruption ID and the three remaining bug-check parameters. They identify whether the store detected a buffer-hash mismatch, page-record mutation, or another store-structure inconsistency, and they preserve the affected buffer or page-frame context.

When physical-memory corruption is suspected, correlate the reported page frame with hardware-error telemetry and DMA activity before attributing the failure to RAM. A driver or device writing the wrong physical page can produce the same store hash failure.

See Also

Bug Check Code Reference

Windows Kernel-Mode Memory Manager