Acronis BSOD Issues


Joined
Oct 7, 2010
Messages
7
Reaction score
0
Can anyone help? After many years happily using Acronis suite, had to upgrade to Acronis 2011 for a new Windows 7 64 bit system. After a frustrating week, just uninstalled the software, issues solved. .

1/ Performance of the system was so severely degraded that I could hardly get anything done.

2/ multiple BSOD's per day due to snapman.sys:

Bug Check String: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code: 0x000000c4
Caused By Address: snapman.sys+2340d

Tried the Vista compatibility mode setting, no help. No other compatibility mode settings available.

I have summaries of the last BSOD if that will help any.
 
Ad

Advertisements

Kalario

Aquarius
VIP Member
Joined
Dec 15, 2009
Messages
590
Reaction score
68
Istmad, welcome to the forum.

If you can post a dump of your BSOD, out resident BSOD expert TorrentG will surely help you out.
 
Joined
Oct 7, 2010
Messages
7
Reaction score
0
Hi Kalario and TorrentG, many thanks. Attached is one of the dumps. BlueScreenView shows me they are all the same.
 

Attachments

Joined
Nov 30, 2009
Messages
1,752
Reaction score
396
Hey there...

Not really much to say about this as you already know what's going on:

Code:
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000001001, Verifier predicted potential deadlock.
Arg2: fffff98003ac6fc0, Lock address.
Arg3: fffffa8005221f30, Verifier internal data.
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_1001

DRIVER_DEADLOCK: Deadlock detection not initialized 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800037553dc to fffff800032cb740

STACK_TEXT:  
fffff880`03f8b7f8 fffff800`037553dc : 00000000`000000c4 00000000`00001001 fffff980`03ac6fc0 fffffa80`05221f30 : nt!KeBugCheckEx
fffff880`03f8b800 fffff800`037565c8 : fffff880`01a2340d fffff980`03ac6fc0 00000000`00000000 fffffa80`05221f30 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03f8b840 fffff800`0375ed43 : fffffa80`0153b000 fffffa80`052f21e8 fffff800`03754160 00000000`00000000 : nt!ViDeadlockReportIssue+0x38
fffff880`03f8b880 fffff800`03762d2b : fffff980`03ac6fc0 fffffa80`036c4f18 00000000`00000001 00000000`00000000 : nt!ViDeadlockAnalyze+0x203
fffff880`03f8b8e0 fffff800`037631be : fffff880`03f8baa0 fffffa80`02f5c600 00000000`00000000 00000000`00000000 : nt!VfDeadlockAcquireResource+0x3ab
fffff880`03f8b9e0 fffff800`03768737 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ViKeObjectAcquired+0x4e
fffff880`03f8ba20 fffff880`01a2340d : fffff980`03ac6fc0 00000000`00000000 fffff980`139a2ee0 fffff800`0326b967 : nt!VerifierKeWaitForSingleObject+0x177
fffff880`03f8baa0 fffff980`03ac6fc0 : 00000000`00000000 fffff980`139a2ee0 fffff800`0326b967 00000000`00000000 : snapman+0x2340d
fffff880`03f8baa8 00000000`00000000 : fffff980`139a2ee0 fffff800`0326b967 00000000`00000000 fffff880`00000008 : 0xfffff980`03ac6fc0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
snapman+2340d
fffff880`01a2340d ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  snapman+2340d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: snapman

IMAGE_NAME:  snapman.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c6126a9

FAILURE_BUCKET_ID:  X64_0xc4_1001_VRF_snapman+2340d

BUCKET_ID:  X64_0xc4_1001_VRF_snapman+2340d

Followup: MachineOwner
---------
snapman snapman.sys Tue Aug 10 06:15:05 2010

Find something else to use.

-----------------

You should really make your machine in a better position.

Delete the following driver in C:\Windows\System32\drivers:

PxHlpa64 PxHlpa64.sys Fri Feb 02 16:24:22 2007

Update the following drivers:

RimSerial_AMD64 RimSerial_AMD64.sys Tue Jan 09 11:50:11 2007
Tppwr64v Tppwr64v.sys Wed Oct 18 04:40:21 2006 <<< Lenovo Trackpoint driver
smiifx64 smiifx64.sys Mon May 12 05:01:13 2008
 
Ad

Advertisements

Joined
Oct 7, 2010
Messages
7
Reaction score
0
Hi there,your assistance and validation much appreciated. I am test driving other options. Got rid of that driver, The other three I have the latest updates from RIM and Lenovo. Is there another way to get more recent drivers?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top