BSOD away from PC, stop 0x70000007e volsnap.sys

[lilnipsfatal]

Started receiving these BSOD's on 10/28/2020. Most recent occurrence was today 11/22/2020. A few days I ago, I modified my settings so the BSOD would stay up on the screen so I could capture the stop message and in this case the volsnap.sys reference. I did have an external hard drive connected via USB. I've also run system file checker and no issues were detected. I've attached the appropriate zip file. I'm up to date on all required windows updates (I have a couple optional ones). From what I can tell, my drivers appear to be up to date as well (I've manually clicked on quite a few of them and searched for updates). Any assistance would be greatly appreciated, thank you!

 

[wither 2]

Does this happen if the external drive is disconnected?

 

[lilnipsfatal]

Great question, I’ve since unplugged the external hard drive when I’m not using it and haven’t seen the BSOD since. Do you think that was the culprit?

 

[wither 2]

My suggestion is to backup any important files on that drive to some other drive. Then, in Windows Explorer, right click on the drive and select Format. Choose NFTS and run it. Hopefully, you won't get any BSODs afterwards.

 

[wither 2]

Deleted by me. Duplicate answer.

 

[lilnipsfatal]

You think there’s an issue with the external hard drive?

 

[wither 2]

Yes. Might be some problem with the formatting or perhaps some corrupt files on it.

 

[lilnipsfatal]

It happened again but this time without any attached external hard drive. Uploaded the files again. If anyone can please help, I'd really appreciate it.

 

[wither 2]

It's not volsnap this time but I don't have time this morning to pursue it. Talk to you later unless someone else resolves it for you.

 

[lilnipsfatal]

I’ll be backing up my files in the meantime and will wait for anyone to look at it. Thanks wither.

 

[wither 2]

Sorry to take so long to respond. Had to take my girl to the doctor in the morning and she decided she wanted to go shopping. Didn't know if would be all day and didn't have time to do all the catch up afterwards.

The Hal.dll error is so generic it's tough to evaluate.

Something that bothers me is that it appears your hard drive is severely limited in free space. How much free space do you have?

 

[wither 2]

Where I was going with in my last comment is you should go to Accessories, System Tools. Open Disk Cleanup and select your C:\ drive. After it runs, how much space can it retrieve? Then, make sure that Temporary Files and Recycle Bin are check marked. Let it run. Reboot. If you have a SSD, you should probably run the Trim function. Do you get any more BSODs?

 

[lilnipsfatal]

I had about 5 GB free and 227 GB used on my SSD and I am able to clear another 4-5 GB after disk cleanup. I included most items other than the dump files. Not sure i'm familiar with trim function. Anything else you can suggest? I'll update if i get any other bsod's.

 

[wither 2]

The Trim function is used to reset the NAND on the SSD which is identified as unused by the disk cleanup, similarly to defragging on a hard drive (you don't defrag a SSD). You should have the Samsung Magician somewhere on your computer. If not, you can download it This video looks to be most helpful to using it-

Samsung SSD 850 EVO 250G trim function - Bing video

With so little free space, you should go through you SSD and delete files that you really don't need or you can transfer to another drive or disc.

 

[lilnipsfatal]

I got volsnap again and I don’t know what to do :/

 

[wither 2]

I think the volsnap is tied to your lack of SDD space. I mean, it had to delete a dump file to get enough space to write a new one. It might have to do the same thing to do a shadow copy and can't. Did you do a thorough clean up?

 

[lilnipsfatal]

I've now cleared the C: drive to where I have 42 GB of space. Hopefully that should resolve the issues?

 

[wither 2]

If it doesn't, we'll have to do more chasing. Fingers crossed.