BSOD - STORE_DATA_STRUCTURE_CORRUPTION

Question

Been having this lately, I had faulty ram that would pass Windows Memory diagnostic without any issues but failed on MemTest quite spectacularly. I sent that RAM away and using a different single RAM stick since then. I used to get MEMORY_MANAGEMENT BSOD on the daily a couple times with the other RAM, with this single stick it seems to be more irregular but still frequent enough for me to try and fix it.
Here is the latest minidump output after analyze as I am unable to get to a next step after this.
******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

STORE_DATA_STRUCTURE_CORRUPTION (1c7) The store component detected a corruption in its data structures. Arguments: Arg1: 0000000000000000, A chunk heap buffer's hash doesn't match. Arg2: ffffb90b39a9c000, Chunk heap buffer whose hash didn't match. Arg3: 00000000351ece57, Expected buffer hash. Arg4: 000000000023fe9c, Page frame number of the corrupted page.

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1343

Key  : Analysis.Elapsed.mSec
Value: 9672

Key  : Analysis.IO.Other.Mb
Value: 1

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 8

Key  : Analysis.Init.CPU.mSec
Value: 265

Key  : Analysis.Init.Elapsed.mSec
Value: 15623

Key  : Analysis.Memory.CommitPeak.Mb
Value: 99

Key  : Bugcheck.Code.LegacyAPI
Value: 0x1c7

Key  : Bugcheck.Code.TargetModel
Value: 0x1c7

Key  : Dump.Attributes.AsUlong
Value: 1808

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 0

Key  : Failure.Bucket
Value: 0x1C7\_0\_nt!SmHpBufferProtectEx

Key  : Failure.Hash
Value: {677f42d4-ea31-d924-1621-3373689c0a0a}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 1417cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key  : Hypervisor.Flags.ApicEnlightened
Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key  : Hypervisor.Flags.Phase0InitDone
Value: 1

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 1

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 4853999

Key  : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key  : Hypervisor.Flags.VpAssistPage
Value: 1

Key  : Hypervisor.Flags.VsmAvailable
Value: 1

Key  : Hypervisor.RootFlags.AccessStats
Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key  : Hypervisor.RootFlags.Value
Value: 1015

Key  : Hypervisor.RootFlags.ValueHex
Value: 3f7

BUGCHECK_CODE: 1c7

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb90b39a9c000

BUGCHECK_P3: 351ece57

BUGCHECK_P4: 23fe9c

FILE_IN_CAB: 080724-10421-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MemCompression

STACK_TEXT:
fffffb0731c57858 fffff80009fc7c00 : 00000000000001c7 0000000000000000 ffffb90b39a9c000 00000000351ece57 : nt!KeBugCheckEx fffffb0731c57860 fffff80009fc7ed1 : 4d04f187503ff2ef 000000000023fe9c 00000000000000bd fffffb0731c57998 : nt!SmHpBufferProtectEx+0xfc fffffb0731c578c0 fffff80009fc4294 : 0000000000000000 ffff85fc97a50ddb ffffb90b3333d050 0000000000000000 : nt!SmHpChunkUnprotect+0x2d fffffb0731c578f0 fffff80009fc443a : ffffffff00000000 ffffffffffffffff fffffb0731c57998 0000000000000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRecordUnprotect+0x1c fffffb0731c57920 fffff80009fc7279 : ffffb90b00000000 ffffb90b3b34d290 0000000000000000 fffff80020082173 : nt!ST_STORE<SM_TRAITS>::StDmPageRemove+0x17a fffffb0731c579e0 fffff80009ecdcaa : ffffb90b3333d000 fffffb0731c57a88 0000000000000001 ffffb90b3b34d2d0 : nt!ST_STORE<SM_TRAITS>::StWorkItemProcess+0x375 fffffb0731c57a30 fffff80009d563d1 : ffffb90b00000000 ffffb90b00000000 ffffb90b3342f340 ffffb90b00000002 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x177516 fffffb0731c57ac0 fffff80009d54d17 : ffffb90b3333d000 fffff80009d563c0 fffffb0731b6f038 004fa46fb19bbfff : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x11 fffffb0731c57af0 fffff80009e1a994 : ffffce8079557180 ffffb90b3342f340 fffff80009d54cc0 0000000000000000 : nt!PspSystemThreadStartup+0x57 fffffb0731c57b40 0000000000000000 : fffffb0731c58000 fffffb0731c51000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nt!SmHpBufferProtectEx+fc

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3958

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: fc

FAILURE_BUCKET_ID: 0x1C7_0_nt!SmHpBufferProtectEx

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {677f42d4-ea31-d924-1621-3373689c0a0a}

Followup: MachineOwner

Answer 1

Absolutely. At this stage, I would suspect issues like overheating, GPU power problems, or faulty connections. However, since you've already ruled out those hardware troubleshooting options, the next step would be a more drastic measure—reinstalling Windows. It might also be useful to test the system with just the new RAM you installed to see if the problem continues. If it does, we can then consider a potential motherboard issue.

Answer 2

Hi,

Yes I have run benchmarks that all comes back as fine. I used Unigine Heaven and UserBenchmark that both ran till completion without fail.

Yeah I plan on reinstalling windows once my ram gets back. Just figured I'd check this failing out in case it points to something different

Answer 3

Thanks for the info, Christo. Perform a stress test on your CPU and GPU using software like Prime95 and FurMark. These tests can help reveal instability under heavy load, which might not be apparent during regular use. If the BSOD occurs during stress testing, it might indicate a hardware issue with either the CPU or GPU.

At the end the nuclear option would be to reinstall Windows, but if it's a hardware issue it will keep happening.

Answer 4

Hi,

Sure sys details:
Desktop PC

Motherboard: Asus Strix Z390-e
CPU: i7 9700k

RAM: 8gb single card

Storage: 250gb m.2for OS and extra 1tb m.2 for extra storage

GPU: Asus Strix 1660 Super 6gb

I have switched RAM slots and it occurs at the same frequency.
I have completely removed all drivers and reinstalled the same/newer version from motherboard to GPU
I am not running any XMP profiles.

Answer 5

Hello, thank you for reaching out to the Microsoft Community. I'm here to help with your questions or issues. Just note – this is a place where passionate Microsoft users help each other, we don't work directly for Microsoft.

As for your issue, based on the BSOD details you provided, Christo, the minidump analysis suggests a STORE_DATA_STRUCTURE_CORRUPTION (1c7) error, usually related to memory corruption. Given that you've already swapped out the faulty RAM and are still encountering the problem, it might be useful to consider other potential causes.

Have you tried installing the RAM in a different slot? Is this the only RAM stick you have currently installed?

Additionally, could you provide details about your system, particularly the motherboard and GPU? If it's a laptop, the specific model would be helpful.