BSODs; volsnap.sys identified

Arc said:

Hello cwaters.
In this situation, I am suggesting you to scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline
  

One problematic element is still remained there, but apparently it is not a startup issue but a BIOS rootkit that is causing the issues.

Windows Defender Offline (default Quick Scan) did not find any problems. I'm now running a Full Scan.

As I mentioned earlier, the updated version of TDSSKiller, using the default parameters, did not find any threats.

I can free up the startup; however, the problem is so random and inconsistent, I'm not sure how effective that will be. Of course, with the VSC service now disabled, the PC is working great!
UPDATE: Would it be possible for me to overwrite volsnap.sys from another source? And would that help?

I'm a bit concerned by your comment about a possible BIOS rootkit. Are you suggesting that the BIOS has been compromised? If so, could that result in TDSSKiller and Windows Defender Offline returning a false negative. How do you suggest I proceed?

Arc said:

Try one more thing ... Malwarebytes : Malwarebytes Anti-Rootkit

If it also comes clean, your BIOS is OK.

Thanks! It came back clean. Are you sure it checks for BIOS rootkits?

So it seems this PC is free of viruses, malware, and (apparently) rootkits. Yet the problem with volsnap.sys still exists...and, based on the comments in this thread, there may still be other concerns.

What now? Would my performing a 'repair install' be a good next step?

I have since re-enabled the VSC service to see whether the BSODs and unexpected reboots start occurring again.

Arc said:

cwaters said:

I have since re-enabled the VSC service to see whether the BSODs and unexpected reboots start occurring again.

If you get the BSODs again, let us know .... we will have a look again.

It crashed again overnight. I was greeted this morning with a BSOD identifying volsnap.sys. Appreciate any guidance you can provide.

I will follow Kaktussoft's suggestion to install a fresh copy of volsnap.sys.

My system BSOD'd again, naming the (now hotfixed) volsnap.sys.

I will revert to the original SP1 volsnap.sys.

What next? Should I try a repair re-install?