BSODs; volsnap.sys identified

Page 6 of 6 FirstFirst ... 456

  1. Posts : 51
    Windows 7 Ultimate x64 w/SP1
    Thread Starter
       #51

    Kaktussoft said:
    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. :)
      My Computer


  2. Posts : 51
    Windows 7 Ultimate x64 w/SP1
    Thread Starter
       #52

    Kaktussoft said:
    cwaters said:
    Kaktussoft said:
    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.
      My Computer


 
Page 6 of 6 FirstFirst ... 456

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:25.
Find Us