BSOD: Store data structure corruption

The last dump, dated 8/21 1:17PM is STORE_DATA_STRUCTURE_CORRUPTION (1c7)
This is what Microsoft has to say about that error:

Code:

Bug Check 0x1C7: 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

 
Parameter
Description

1
Corruption ID. See values below.

2
See values below.

3
See values below.

4
See values below.



 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:
 
Defective RAM hardware
A driver or device incorrectly modifying physical pages via an incorrect DMA operation or associated MDL.
Corruption caused by a hardware device or firmware corrupting  memory, such as firmware illegally modifying physical pages across a  power transition. 

Start by setting all tweaks to nominal, clocks and voltages, see if that removes the problem. If it does then you can start reapplying your tweaks a little at a time until you find what is causing the error. If you are not doing any tweaking then test your ram as follows:

===================================================
Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

What about frequency/voltage tweaks? Are you doing any?

Also, How to fill out System Specs for tenforums.

See here: System Specs - Fill in at Ten Forums

Fill out as much as you can, look at mine for an example of what can be included. The more information the better.

Give Driver Verifier a try, see if it shows up and driver problems:

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.