none
SCDPM 2012 Volsnap.sys BSOD

    Question

  • We have one of our SCDPM 2012 that's BSOD whenever we ran Consistency Check on our backup. We have applied DPM 2012 Update Rollup as well as Hotfix 425598 from

    http://support.microsoft.com/kb/2460912/en-us?wa=wsignin1.0

    From minidump file, we are getting this error,

    FOLLOWUP_IP:
    volsnap!VspCompareMemoryWithCopyIrp+fe
    fffff880`01a814ee 483bc3          cmp     rax,rbx

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  volsnap!VspCompareMemoryWithCopyIrp+fe

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: volsnap

    IMAGE_NAME:  volsnap.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d0c4f58

    FAILURE_BUCKET_ID:  X64_0x50_volsnap!VspCompareMemoryWithCopyIrp+fe

    BUCKET_ID:  X64_0x50_volsnap!VspCompareMemoryWithCopyIrp+fe

    In our environment, we have 2 other SCDPM 2012 and only this particular server that's having this problem.

    Can someone point us to the right direction to resolve this issue?

    Wednesday, January 23, 2013 8:25 PM

Answers

  • We resolved this issue by a simply changing the advanced recovery option from minidump to kernel dump. Oddly, we haven't had BSOD for the last few weeks when we ran consistency check.

    At first, we intended to use the kernel dump to provide product support to take a look the debugger. However, we weren't able to reproduce the BSOD when the advanced recovery is set to kernel dump.

    Tuesday, March 05, 2013 7:53 PM

All replies

  • Hi,

    Volsnap.sys is a Windows component, please work with the Windows folks to find root cause / solution, most likely need to get the memory.dmp analyzed.

    Make sure you have the latest volsnap.sys driver installed.

    2727941 "0x00000050" Stop error when you create a volume snapshot in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2
    http://support.microsoft.com/kb/2727941/EN-US


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, January 23, 2013 10:46 PM
  • Hi,

    Volsnap.sys is a Windows component, please work with the Windows folks to find root cause / solution, most likely need to get the memory.dmp analyzed.

    Make sure you have the latest volsnap.sys driver installed.

    2727941 "0x00000050" Stop error when you create a volume snapshot in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2
    http://support.microsoft.com/kb/2727941/EN-US


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Thanks for the reply. We have applied your suggested hotfix in the past as well. This BSOD issue is only happened when we ran Consistency Check. Otherwise, the server is up and running without any issue at all. We're going to ask on the Windows forum, I am afraid they'll probably revert it back to DPM issue...
    Monday, January 28, 2013 8:18 PM
  • Hi,

    Volsnap.sys tracks block level file changes when a snapshot is active, so if you don't make snapshots outside of DPM, then I would not expect you to see the crash any other time.   It's like saying you only feel toothache when you eat candy, so it must be the bad candy, when in fact, it's a bad tooth.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, January 28, 2013 8:25 PM
  • We resolved this issue by a simply changing the advanced recovery option from minidump to kernel dump. Oddly, we haven't had BSOD for the last few weeks when we ran consistency check.

    At first, we intended to use the kernel dump to provide product support to take a look the debugger. However, we weren't able to reproduce the BSOD when the advanced recovery is set to kernel dump.

    Tuesday, March 05, 2013 7:53 PM