Aller au contenu principal

BSOD Snapman.sys - Windows Server 2008R2 Enterprise

Thread needs solution

Hello!

we got some weird problems lately.
A BSOD on MS HyperV while Acronis is backing up the maschines.
It happens in combination with the Snapman.sys.

Analyzing the memory.dmp shows clearly that the snapman.sys is involved.

I just found some information about snapman errors, but nothing really fits with the actual version 11.5.
Some information out of the memory.dmp analysis:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffff80a37248, 1, fffff8800173d54d, 5}

*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : snapman.sys ( snapman+1254d )

Followup: MachineOwner
---------

17: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffff80a37248, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800173d54d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

17: kd> !irp fffffa80a5e04b10
Irp is active with 1 stacks 1 is current (= 0xfffffa80a5e04be0)
No Mdl Thread fffffa80550e5640: Irp stack trace.
cmd flg cl Device File Completion-Context
>[ e, 0] 5 0 fffffa8049860470 fffffa80a867eb50 00000000-00000000
\Driver\snapman
Args: 00000000 00000018 80212407 15e4e70c

0 Users found this helpful

which Build of BuR are you using at the moment...?

I didn't have any BSODs yet with the latest (Win2012 compatible) build..

Regards

Volker
Nadolski

I have the exact same problem, and the memory.dmp clearly shows Acronis Snapshot API is the issue:

I'm using build ABR11.5A_32308

Here's the error message detail:

Bug check name: DRIVER_CORRUPTED_EXPOOL
Bug check code: 0xC5
Bug check parm 1: 0x37E51618
Bug check parm 2: 0x2
Bug check parm 3: 0x1
Bug check parm 4: 0xFFFFF80001BAF147
Probably caused by: snapman.sys
Driver description: Acronis Snapshot API
Driver product: Acronis Snapshot API
Driver company: Acronis
OS build: Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Architecture: x64 (64 bit)
CPU count: 16
Page size: 4096

I'm going to try to upgrade to the latest version of ABR11.5 to see if it resolves the issue.

Hello Quan,

please let me know if the latest build could resolve the issue.

If you need additional assistance, feel free to contact me.

Thank you.

Hi All,

Last tuesday we have also had a BSOD 0x0000050 STOP on our HyperV (core) server.
Dump file also shows the same "Snapman.sys" as being the driver that caused the crash.
We are currently running version Acronis Backup and Recovery 11.5.

Is anybody from Acronis looking into this driver problem ?

Kind Regards,
Luke.

Hi Luke,

please create full memory dump and contact our support team.

Such issues should be investigated on case by case basis since they usually have system specific causes.

Thank you in advance!