BSODs; volsnap.sys identified

[Kaktussoft]

Is computer running in IDE or AHCI mode? http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html

If you don't know, goto device manager, expand branch IDE ATA/ATAPI-controller. Post screenshot. Do it in problem win7 instance and new win7 instance

I reviewed Device Manager in the context of the article but am not sure how to interpret the results so as to answer your question--so here are the screenshots. The two configurations look the same, FWIW.

Is it a SATA drive? If so dow what's described in http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html on good and bad win7. Do BIOS part as last

 

[cwaters]

vssadmin list shadows

Not sure if you are asking for the output from this command, but here goes. Note that there is no longer a HarddiskVolumeShadowCopy14 volume:

C:\Windows\system32>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Contents of shadow copy set ID: {518faa79-321d-4554-88b6-a6b28e352764}
Contained 1 shadow copies at creation time: 12/13/2012 10:38:19 PM
Shadow Copy ID: {488bf1e3-5b80-4729-9cc1-26949df514c1}
Original Volume: ( E: )\\?\Volume{88053144-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential

Contents of shadow copy set ID: {206020ed-b720-4231-92c5-3db54e54c6c6}
Contained 1 shadow copies at creation time: 12/13/2012 10:38:16 PM
Shadow Copy ID: {27ee0504-6cbe-4410-939e-20bb11952a85}
Original Volume: ( D: )\\?\Volume{88053145-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential

Contents of shadow copy set ID: {66464d4a-4497-4830-a84a-31a95b2da25d}
Contained 1 shadow copies at creation time: 12/24/2012 11:41:07 AM
Shadow Copy ID: {390423c0-72a2-48cd-94ab-a0cd1f92dff4}
Original Volume: ( D: )\\?\Volume{88053145-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: Backup
Attributes: Differential

Contents of shadow copy set ID: {b576fc15-09cc-4b64-ac1f-9e967be568de}
Contained 1 shadow copies at creation time: 12/24/2012 9:35:04 AM
Shadow Copy ID: {f8655ddd-4a05-4ec5-8144-2950fa5e00ef}
Original Volume: ( C: )\\?\Volume{88053147-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered

Contents of shadow copy set ID: {d7dc62f7-7b4a-4f98-8f1f-f7e08d603079}
Contained 1 shadow copies at creation time: 12/21/2012 1:16:47 PM
Shadow Copy ID: {50d40d4b-c338-4459-afd6-fe8cc54924e1}
Original Volume: ( M: )\\?\Volume{acee3657-4b2b-11e2-820d-0024e80cc47a}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13
Originating Machine: PC01A
Service Machine: PC01A
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered

Contents of shadow copy set ID: {4f0b5bd3-71a5-4e19-8cba-d2d76a40237e}
Contained 1 shadow copies at creation time: 12/24/2012 9:43:21 AM
Shadow Copy ID: {12059aaa-ecf0-4917-8c46-7160c8146a0f}
Original Volume: ( M: )\\?\Volume{acee3657-4b2b-11e2-820d-0024e80cc47a}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16
Originating Machine: PC01A
Service Machine: PC01A
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered
​

BTW, I've begun getting deluged with "Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider" error events again.

 

[Kaktussoft]

vssadmin list shadows

output please

 

[cwaters]

Is computer running in IDE or AHCI mode? http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html

If you don't know, goto device manager, expand branch IDE ATA/ATAPI-controller. Post screenshot. Do it in problem win7 instance and new win7 instance

I reviewed Device Manager in the context of the article but am not sure how to interpret the results so as to answer your question--so here are the screenshots. The two configurations look the same, FWIW.

Is it a SATA drive? If so dow what's described in http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html on good and bad win7. Do BIOS part as last

Yes, both Disk 0 and Disk 1 are SATA drives.

I will perform the steps in the article, on both Win7 instances. Can you clarify: Are you recommending that I just set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci to 0 (on both instances) but not update the BIOS? Or update both values and then enable AHCI? (BTW, the current value in the problem instance is 3.) And what should I do after I perform these steps?

 

[cwaters]

vssadmin list shadows

output please

Please see above.

 

[cwaters]

I reviewed Device Manager in the context of the article but am not sure how to interpret the results so as to answer your question--so here are the screenshots. The two configurations look the same, FWIW.

Is it a SATA drive? If so dow what's described in http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html on good and bad win7. Do BIOS part as last

Yes, both Disk 0 and Disk 1 are SATA drives.

I will perform the steps in the article, on both Win7 instances. Can you clarify: Are you recommending that I just set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci to 0 (on both instances) but not update the BIOS? Or update both values and then enable AHCI? (BTW, the current value in the problem instance is 3.) And what should I do after I perform these steps?

I changed HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci from 3 to 0, on the problem instance, and then rebooted. Next, I examined the BIOS. I don't see an option to enable AHCI; please see screenshots. I have the latest BIOS update from Dell.

How should I proceed? Is there any harm in my leaving the msahci setting set to 3 while I use the problem instance?

 

[Kaktussoft]

Is it a SATA drive? If so dow what's described in http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html on good and bad win7. Do BIOS part as last

Yes, both Disk 0 and Disk 1 are SATA drives.

I will perform the steps in the article, on both Win7 instances. Can you clarify: Are you recommending that I just set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci to 0 (on both instances) but not update the BIOS? Or update both values and then enable AHCI? (BTW, the current value in the problem instance is 3.) And what should I do after I perform these steps?

I changed HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci from 3 to 0, on the problem instance, and then rebooted. Next, I examined the BIOS. I don't see an option to enable AHCI; please see screenshots. I have the latest BIOS update from Dell.

How should I proceed? Is there any harm in my leaving the msahci setting set to 3 while I use the problem instance?

It most likely doesn't bott now.

change SATA MODE to RAID in BIOS

 

[cwaters]

Yes, both Disk 0 and Disk 1 are SATA drives.

I will perform the steps in the article, on both Win7 instances. Can you clarify: Are you recommending that I just set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci to 0 (on both instances) but not update the BIOS? Or update both values and then enable AHCI? (BTW, the current value in the problem instance is 3.) And what should I do after I perform these steps?

I changed HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci from 3 to 0, on the problem instance, and then rebooted. Next, I examined the BIOS. I don't see an option to enable AHCI; please see screenshots. I have the latest BIOS update from Dell.

How should I proceed? Is there any harm in my leaving the msahci setting set to 3 while I use the problem instance?

It most likely doesn't bott now.

change SATA MODE to RAID in BIOS

Did you mean to say that after changing the msahci setting to 3 but not changing the SATA mode to RAID, the old/problem instance likely won't boot? The old/problem instance's msahci setting is 3; it boots OK, even with the SATA mode still set to ATA. (I haven't changed the msahci setting in the the new/good instance yet, nor have I booted into it recently.)

As you instructed, I changed the SATA mode from ATA to RAID, saved the change, and rebooted. During boot, a RAID menu passed by quickly (listing the two SATA drives with a setting of "Non-RAID"; see attached) and then the standard Windows boot menu appeared; I selected the old/problem instance, saw a few seconds of Windows animation, and then a generic BSOD occurred (see attached). I rebooted and was presented with a message stating that a recent hardware or software change might be causing Windows to fail to load; a menu also appeared (see attached; I think the first option is 'Launch Windows repair (recommended)'). I chose 'Start Windows Normally' (wasn't sure what launching repair would lead to) and encountered the same generic BSOD.

I went into the BIOS and changed the SATA mode from RAID back to ATA and then rebooted; the old/problem instance booted. The msahci is still set to 3.

Appreciate your comments as to how to proceed.

 

[Kaktussoft]

Normally you have 3 sata modes: IDE, AHCI, RAID. RAID also uses same driver as AHCI as far as I know. Set SATA MODE back to ATA (you already did). STOP 7B means ... no valid disk driver. The RAID driver for your hard disk can't load (isn't installed). MSAHCI in registry can be set to 0 or 3. Only if value is 0 it is started!! Are you sure you changed it to 0???!!

 

[Kaktussoft]

vssadmin list shadows

Not sure if you are asking for the output from this command, but here goes. Note that there is no longer a HarddiskVolumeShadowCopy14 volume:

C:\Windows\system32>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Contents of shadow copy set ID: {518faa79-321d-4554-88b6-a6b28e352764}
Contained 1 shadow copies at creation time: 12/13/2012 10:38:19 PM
Shadow Copy ID: {488bf1e3-5b80-4729-9cc1-26949df514c1}
Original Volume: ( E: )\\?\Volume{88053144-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential

Contents of shadow copy set ID: {206020ed-b720-4231-92c5-3db54e54c6c6}
Contained 1 shadow copies at creation time: 12/13/2012 10:38:16 PM
Shadow Copy ID: {27ee0504-6cbe-4410-939e-20bb11952a85}
Original Volume: ( D: )\\?\Volume{88053145-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential

Contents of shadow copy set ID: {66464d4a-4497-4830-a84a-31a95b2da25d}
Contained 1 shadow copies at creation time: 12/24/2012 11:41:07 AM
Shadow Copy ID: {390423c0-72a2-48cd-94ab-a0cd1f92dff4}
Original Volume: ( D: )\\?\Volume{88053145-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: Backup
Attributes: Differential

Contents of shadow copy set ID: {b576fc15-09cc-4b64-ac1f-9e967be568de}
Contained 1 shadow copies at creation time: 12/24/2012 9:35:04 AM
Shadow Copy ID: {f8655ddd-4a05-4ec5-8144-2950fa5e00ef}
Original Volume: ( C: )\\?\Volume{88053147-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered

Contents of shadow copy set ID: {d7dc62f7-7b4a-4f98-8f1f-f7e08d603079}
Contained 1 shadow copies at creation time: 12/21/2012 1:16:47 PM
Shadow Copy ID: {50d40d4b-c338-4459-afd6-fe8cc54924e1}
Original Volume: ( M: )\\?\Volume{acee3657-4b2b-11e2-820d-0024e80cc47a}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13
Originating Machine: PC01A
Service Machine: PC01A
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered

Contents of shadow copy set ID: {4f0b5bd3-71a5-4e19-8cba-d2d76a40237e}
Contained 1 shadow copies at creation time: 12/24/2012 9:43:21 AM
Shadow Copy ID: {12059aaa-ecf0-4917-8c46-7160c8146a0f}
Original Volume: ( M: )\\?\Volume{acee3657-4b2b-11e2-820d-0024e80cc47a}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16
Originating Machine: PC01A
Service Machine: PC01A
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered
​

BTW, I've begun getting deluged with "Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider" error events again.

Contents of shadow copy set ID: {66464d4a-4497-4830-a84a-31a95b2da25d}
Contained 1 shadow copies at creation time: 12/24/2012 11:41:07 AM
Shadow Copy ID: {390423c0-72a2-48cd-94ab-a0cd1f92dff4}
Original Volume: ( D: )\\?\Volume{88053145-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: Backup
Attributes: Differential

What backup software is/was running?
"Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider"=>
The errors you are referring appears in a computer, when a program installed in the computer is not communicating with the volume shadow copy service properly.

 

[cwaters]

Normally you have 3 sata modes: IDE, AHCI, RAID. RAID also uses same driver as AHCI as far as I know. Set SATA MODE back to ATA (you already did). STOP 7B means ... no valid disk driver. The RAID driver for your hard disk can't load (isn't installed). MSAHCI in registry can be set to 0 or 3. Only if value is 0 it is started!! Are you sure you changed it to 0???!!

I just checked; it's still set to 0. I changed it from 3 to 0 a few days ago, as per your suggestion.

 

[cwaters]

vssadmin list shadows

Not sure if you are asking for the output from this command, but here goes. Note that there is no longer a HarddiskVolumeShadowCopy14 volume:

C:\Windows\system32>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Contents of shadow copy set ID: {518faa79-321d-4554-88b6-a6b28e352764}
Contained 1 shadow copies at creation time: 12/13/2012 10:38:19 PM
Shadow Copy ID: {488bf1e3-5b80-4729-9cc1-26949df514c1}
Original Volume: ( E: )\\?\Volume{88053144-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential

Contents of shadow copy set ID: {206020ed-b720-4231-92c5-3db54e54c6c6}
Contained 1 shadow copies at creation time: 12/13/2012 10:38:16 PM
Shadow Copy ID: {27ee0504-6cbe-4410-939e-20bb11952a85}
Original Volume: ( D: )\\?\Volume{88053145-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential

Contents of shadow copy set ID: {66464d4a-4497-4830-a84a-31a95b2da25d}
Contained 1 shadow copies at creation time: 12/24/2012 11:41:07 AM
Shadow Copy ID: {390423c0-72a2-48cd-94ab-a0cd1f92dff4}
Original Volume: ( D: )\\?\Volume{88053145-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: Backup
Attributes: Differential

Contents of shadow copy set ID: {b576fc15-09cc-4b64-ac1f-9e967be568de}
Contained 1 shadow copies at creation time: 12/24/2012 9:35:04 AM
Shadow Copy ID: {f8655ddd-4a05-4ec5-8144-2950fa5e00ef}
Original Volume: ( C: )\\?\Volume{88053147-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered

Contents of shadow copy set ID: {d7dc62f7-7b4a-4f98-8f1f-f7e08d603079}
Contained 1 shadow copies at creation time: 12/21/2012 1:16:47 PM
Shadow Copy ID: {50d40d4b-c338-4459-afd6-fe8cc54924e1}
Original Volume: ( M: )\\?\Volume{acee3657-4b2b-11e2-820d-0024e80cc47a}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13
Originating Machine: PC01A
Service Machine: PC01A
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered

Contents of shadow copy set ID: {4f0b5bd3-71a5-4e19-8cba-d2d76a40237e}
Contained 1 shadow copies at creation time: 12/24/2012 9:43:21 AM
Shadow Copy ID: {12059aaa-ecf0-4917-8c46-7160c8146a0f}
Original Volume: ( M: )\\?\Volume{acee3657-4b2b-11e2-820d-0024e80cc47a}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16
Originating Machine: PC01A
Service Machine: PC01A
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differentia
l, Auto recovered
​

BTW, I've begun getting deluged with "Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider" error events again.

Contents of shadow copy set ID: {66464d4a-4497-4830-a84a-31a95b2da25d}
Contained 1 shadow copies at creation time: 12/24/2012 11:41:07 AM
Shadow Copy ID: {390423c0-72a2-48cd-94ab-a0cd1f92dff4}
Original Volume: ( D: )\\?\Volume{88053145-047e-11e2-8c55-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20
Originating Machine: PC01
Service Machine: PC01
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: Backup
Attributes: Differential

What backup software is/was running?
"Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider"=>
The errors you are referring appears in a computer, when a program installed in the computer is not communicating with the volume shadow copy service properly.

I have a Windows Home Server on my network; (changes to) files on this PC get backed up to WHS every night, between 2am and 7am. In addition, the Carbonite service (used for offsite backups) is installed on this PC; I believe Carbonite backs up changed files whenever it senses inactivity. I just now checked the status of my WHS backup and of Carbonite; they show both backups as being complete (i.e., no failures).

I'm not currently seeing any volsnap-related errors in the System log; however, I'm still seeing many VSS errors in the Application log.

Could the backups' services -- or, rather, the presence of (potentially) conflicting backup services -- be causing my BSODs and lockups? I wouldn't think so; the BSOD have been occurring at all hours of the day; i.e., not during the 2am to 7am WHS backup window. I will stop the Carbonite service ... and disable WHS backups ... to see if the errors in the Application log stop.

I think it's important to mention that I haven't had a BSOD (other than the one from changing the SATA mode from ATA to RAID) or a lockup in a few days.