Question Blue screen - volsnap.sys - dump file included

[firestarhero]

Any help or ideas would be really appreciated

random blue screens started in the last few days
STOP: 0x0000007e 0x0000007E 0xffffffffc0000005, 0xfffff88001369d6e, 0xfffff880127f97c8,
0xfffff880127f9030

volsnap.sys address FFFFF88001369d6e base at fffff8800135000


dump file, spec and blue screen can be found here
https://www.dropbox.com/sh/7bflkju688iqykv/AACaRAVsBChkS_NR99rgZCENa?dl=0

win 7 / 64
i5-2500k
32GB ram

 

[PC Tailor]

Welcome to the forums my friend! Thank you for the dump files.

I have just run the latest 3 dump files (as this should be enough to begin with) and you can see the reports here:
Dump 1: https://pste.eu/p/obuv.html SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Dump 2: https://pste.eu/p/BeJK.html SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Dump 3: https://pste.eu/p/VF8f.html SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Summary of findings:

BugCheck 7E
Probably caused by : volsnap.sys ( volsnap!VspCollectLazyOffsetsPass+1be )

Bugcheck Description:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
"This bug check indicates that a system thread generated an exception that the error handler did not catch. To interpret it, you must identify which exception was generated.

Common exception codes include the following:
0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered.
0x80000003: STATUS_BREAKPOINT indicates a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
Ntstatus.h file that is located in the inc directory of the MWDK contains all references"

About your bugcheck:
This is typically driver based and therefore you should reference the third party modules loaded to check which ones may be misbehaving.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.

Check with your hardware vendor for any ACPI or other firmware updates. Hardware issues, such as system incompatibilities, memory conflicts, and IRQ conflicts can also generate this error. Confirm that any new hardware that is installed is compatible with the installed version of Windows.

You can also disable memory caching/shadowing of the BIOS to try to resolve the error. You should also run hardware diagnostics, that the system manufacturer supplies.

Some things to consider:

• I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.
• I could not deduce system information, can you post your entire system spec including PSU make and model? Do you have latest BIOS installed?

- Being as the bugchecks have started appearing suddenly, what software or hardware have you changed recently as first port of call? Even if this is peripheral devices, I'd like to understand what changed before digging into all the third party modules on the reports.

 

[firestarhero]

Hi -
There's a html spec list in the folder.
Every driver and the bios I can think of has been updated and no new programs or devices were installed prior to the blue screens? System has been running perfectly for 7 years.
The only significant change was the memory upgrade about 6 months ago to 32gb

sorry, not an expert so was really looking for an obvious answer from the dump files that points to a device or software causing the issue.

seems really random - can go a whole day then twice in 10 mins?

 

[PC Tailor]

Every driver and the bios I can think of has been updated and no new programs or devices were installed prior to the blue screens?

Well this is the part I'm wondering about, by software I also mean drivers, have you updated any specific drivers recently just prior to the stop errors? Or the BIOS even? as it could be a conflict with the OS.

Also are you using any third party software to update drivers?

How long ago have the bugchecks started? Did you mix RAM modules or did you buy a whole new pack entirely?

sorry, not an expert so was really looking for an obvious answer from the dump files that points to a device or software causing the issue.

Unfortunately it very rarely is, it's just a science of identifying the potential causes and the scoping down. Which the reports I have attached will help with, as you have a lot of modules running at the times of the crash.

 

[firestarhero]

re memory - I have two pairs of 8GB
https://www.amazon.co.uk/gp/product/B008E3M4QS
https://www.amazon.co.uk/gp/product/B00J8E90WS

I've just taken out the corsair to run at 16GB with the Fury matching pair to test.

I updated the bios yesterday but it didn't stop the BSOD x2 today
Not using any driver update software so I know none have been updated unless via a windows update?

Is it worth a system restore back a couple of weeks?

 

[PC Tailor]

re memory - I have two pairs of 8GB
https://www.amazon.co.uk/gp/product/B008E3M4QS
https://www.amazon.co.uk/gp/product/B00J8E90WS

I've just taken out the corsair to run at 16GB with the Fury matching pair to test.

I updated the bios yesterday but it didn't stop the BSOD x2 today
Not using any driver update software so I know none have been updated unless via a windows update?

Is it worth a system restore back a couple of weeks?

A system restore would be an easy way to see if it was a driver, obviously just have to make sure it predates the crashes.

Does the BSOD still occur in safe mode?