Consistent Clip.sys BSOD

I've been having the same BSOD for the past three weeks. Happens at least 5 times a week randomly. Sometimes I'm working on a word document with music playing, other times I am gaming.

Very frustrating as my system is mostly stable now. My build should be below and I have attached the most recent crash logs plus kernal log. I previously put up a post and checked the memory. Memory is not the issue. I have replaced the ram kit to be sure.

Additionally, WhoCrashed is unsure of the issue as well. I am running on Windows 10. Appreciate any help.

- - - Updated - - -

The kernal zip file seems to be too large to upload on here.

Ztruker said:

Please read and follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions

The tool is creating a file size of around 10 mb. Win10 forums is saying it is not allowing for uploads larger than 4mb when I try to upload

Then send these logs through some cloud such as Google Drive, MEGA.nz, Dropbox or OneDrive

Log File Upload: LAPTOP-D3L7AD20-(2021-05-14_13-05-37).zip - Google Drive

Ztruker said:

All dumps shows:

Code:

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: ffffb78b53440000, Chunk heap buffer whose hash didn't match.
Arg3: 000000004d1a787b, Expected buffer hash.
Arg4: 000000000065ba40, Page frame number of the corrupted page.

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.

To investigate if this bug check is caused by defective RAM hardware, run a Memory Diagnostics tool. I recommend memtest86.

===================================================
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.

You have 32GB of ram so this is going to take quite a while. Another method of testing would be to remove one of the memory modules and test for awhile and see if the problem occurs. If not, swap modules and test again.

If you find a scenario where it fails with one module but no the other replace the failing memory module.

Hey Ztrucker,

I had this issue a while back and someone told me to check my RAM. I ended up replacing the entire RAM kit. I do not believe there is a fault in the memory kit especially this new one. Which makes me believe it may be either problems 2 or 3.

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.

Theoretically lets say it is tested and all results come back nominal, how would I figure out what driver or device is causing the issues?

Ztruker said:

Probably not a RAM problem but it's worth testing if you have the time. New RAM has been known to be defective. Not often but it does happen.

For possible driver problems, run Driver Verifier:

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.

Ended up trying out Driver verifier and a driver for Valorant came up.... vgk.sys. Riot Games is notorious for making terrible software so I was not surprised. I restored to prior to driver verifier and removed the valorant which removed vgk.sys

However, a BSOD still occurs every now and then. I booted up Verifier and nothing came up, although the system failed to boot to windows regardless. So my theory is that something is causing a driver issue that cannot be detected by Verifier.