BSOD volsnap,sys, errors in sfc -scannow (cbs.log)

[cinder]

Hi there,
Received a BSOD earlier relating to volsnap.sys. Did not get the chance to grab the error code. Have now changed settings so that system doesn't automatically restart.

Read a few existing threads and followed advice with running the scan. Have amended cbs.log to only show relevant errors as advised.

(see attached).

The problems seems to relate to IE 10. Any recommendations please?

Just realised there's a BSOD section, should have posted it there - unsure how to move.

 

[koolkat77]

Requested a friend to take a look at the CBS.

In the meantime, please Please 'Grab all' and post your files following -

Blue Screen of Death Posting Instructions​

 

[cinder]

Thanks, & done.

 

[koolkat77]

Is the firmware of your SSD up to date?

Upload a screenshot using:

CrystalDiskInfo​

:tip: For how to upload a screenshot or file, read here

Test your Hard Drive by running:

Hard Drive Diagnostic Procedure​

Run Disk Check:

Run Disk Check in Windows 7 for Bad Sectors & Errors​

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7
​

Antivirus software is basically whats just needed there.

Follow this -

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Drivers - You need to either update them to the latest version available, or uninstall/temporarily disable and see if BSOD's continue.

LHidFilt.Sys Fri Sep 21 17:05:39 2007
Logitech SetPoint HID Filter Driver
Driver Reference Table - LHidFilt.Sys

LMouFilt.Sys Fri Sep 21 17:05:43 2007
Logitech SetPoint HID Filter Driver
Driver Reference Table - LMouFilt.Sys

wdcsam64.sys Wed Apr 16 14:39:08 2008
Western Digital SCSI Arcitecture Model (SAM) WDM driver [br] 2008 driver version has known BSOD issues in Windows
Driver Reference Table - wdcsam64.sys

000.fcl Fri Sep 26 19:11:22 2008
CyberLink FCL Driver
Driver Reference Table - 000.fcl

BSOD BUGCHECK SUMMARY:

[FONT="Lucida Console"]Debug session time: Tue Jul 30 06:26:00.146 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:11:55.974
*** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
Probably caused by : volsnap.sys ( volsnap+19eae )
BugCheck 1000007E, {ffffffffc0000005, fffff88001e19eae, fffff880132247c8, fffff88013224020}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Bugcheck code 1000007E
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x7E_volsnap+19eae
MaxSpeed:     3400
CurrentSpeed: 3411
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[cinder]

Looks like there is an update to my SSD (see screen shot).

Release Date: 04/02/2013
Firmware 070H is recommended for anyone currently running 040H or previous firmware releases. It includes incremental improvements and refinements over these versions which may improve the overall user experience.

So, update you think?

 

[essenbe]

I would update it, or rather I should say I did update mine. I have 3 Crucial's and updated all 3 and have had no problems at all. The update is quick and simple and is not destructive at all, although I would back up, just in case. If you try the update and the disk can't recognize your SSD, put you sata controller in IDE mode and it will find it with no problem. Then put it back in AHCI mode after the update.

 

[cinder]

Ok thanks. I've updated it successfully so I'll keep an eye on the PC over the next few days to see if that's helped.

I'll also look into updating the drivers mentioned:

LHidFilt.Sys Fri Sep 21 17:05:39 2007
Logitech SetPoint HID Filter Driver
Driver Reference Table - LHidFilt.Sys

LMouFilt.Sys Fri Sep 21 17:05:43 2007
Logitech SetPoint HID Filter Driver
Driver Reference Table - LMouFilt.Sys

wdcsam64.sys Wed Apr 16 14:39:08 2008
Western Digital SCSI Arcitecture Model (SAM) WDM driver [br] 2008 driver version has known BSOD issues in Windows
Driver Reference Table - wdcsam64.sys

000.fcl Fri Sep 26 19:11:22 2008
CyberLink FCL Driver
Driver Reference Table - 000.fcl

If I can work out where/how.

 

[cinder]

I have updated LMouFilt.Sys Fri Sep 21 17:05:43 2007 to the 2013 version but I can't seem to get LHidFilt.Sys which is still showing 2007, I thought they'd both be done as part of the Logitech Set Point Update. I did however have to cancel the upgrade of the USB bluetooth dongle firmware as it stopped progressing, perhaps that's why.

Also, on the WD support page there's only the option to upgrade the firmware of the external WD drive, and this doesn't affect any of the Windows drivers so therefore wdcsam64.sys doesn't get updated.

 

[NoelDP]

The SFC scan shows the following problems...

2013-07-30 10:47:33, Info                  CSI    00000321 [SR] Repairing 3 components
2013-07-30 10:47:33, Info                  CSI    00000322 [SR] Beginning Verify and Repair transaction
2013-07-30 10:47:33, Info                  CSI    00000323 [SR] Cannot repair member file [l:54{27}]"Windows Feed Discovered.wav" of Microsoft-Windows-IE-InternetExplorer, Version = 10.2.9200.16521, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-07-30 10:47:33, Info                  CSI    00000324 [SR] Cannot repair member file [l:56{28}]"Windows Navigation Start.wav" of Microsoft-Windows-IE-InternetExplorer, Version = 10.2.9200.16521, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-07-30 10:47:33, Info                  CSI    00000325 [SR] Cannot repair member file [l:52{26}]"Windows Pop-up Blocked.wav" of Microsoft-Windows-IE-InternetExplorer, Version = 10.2.9200.16521, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-07-30 10:47:33, Info                  CSI    00000326 [SR] Cannot repair member file [l:54{27}]"Windows Information Bar.wav" of Microsoft-Windows-IE-InternetExplorer, Version = 10.2.9200.16521, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

... as well as two other files which it managed to fix.
I'll post a fix protocol for these a bit later.

 

[NoelDP]

I've uploaded a file - cdraa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\cdraa
hit the enter key - if you get a 'Not Found' error try
DIR D:\cdraa
or
DIR E:\cdraa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\cdraa <drive>:\windows\winsxs /y /i /s /v /h

(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply
Also run a new MGADiag report, and post the result.