Random 0xB8 BSOD

seaves88 · 02 Jun 2014

Hello all! I just recently built a custom computer for my office to replace our old Compaq that kept locking up because the processor was going out. I cloned the HDD to a new SSD and ran sysprep before installing it in the newly built rig. I had also installed windows the SSD beforehand so I could make sure everything worked correctly before trying the clone.

Everything ran great for a couple of days and then it started suffering from random BSODs. I viewed all the dumps in bluescreen viewer and almost all seem to be being thrown by different drivers. I would wipe the computer and start from a fresh install except that we have older programs that we have to use that we no longer know where the product keys are.

I used DM Log Collector to make the zip file and have attached it. Any help I get would be much appreciated.

Thanks in advance

Arc · 03 Jun 2014

Hi seaves88.

Either update Acronis or uninstall it.

Let us know the result.
_________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000B8, {fffffa8006fbd660, fffffa8006f6a550, 0, 0}

*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : snapman.sys ( snapman+18e71 )

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

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

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffffa8006fbd660, Original thread which is the cause of the failure
Arg2: fffffa8006f6a550, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

FAULTING_THREAD:  fffffa8006fbd660

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xB8

PROCESS_NAME:  rundll32.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF80000BA2FB0

LAST_CONTROL_TRANSFER:  from fffff800034df992 to fffff800034dceda

STACK_TEXT:  
fffff800`00ba24d0 fffff800`034df992 : fffffa80`07be0d01 fffffa80`06fbd660 00000000`00000002 fffffa80`00000007 : nt!KiSwapContext+0x7a
fffff800`00ba2610 fffff800`034e21af : fffffa80`07c65aa8 00000000`00000001 fffff800`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff800`00ba26a0 fffff880`01915e71 : fffff880`01928100 fffff880`00000000 00000000`00000000 fffffa80`07c88b00 : nt!KeWaitForSingleObject+0x19f
fffff800`00ba2740 fffff880`01928100 : fffff880`00000000 00000000`00000000 fffffa80`07c88b00 fffff800`0364ce80 : snapman+0x18e71
fffff800`00ba2748 fffff880`00000000 : 00000000`00000000 fffffa80`07c88b00 fffff800`0364ce80 fffff880`01928140 : snapman+0x2b100
fffff800`00ba2750 00000000`00000000 : fffffa80`07c88b00 fffff800`0364ce80 fffff880`01928140 fffffa80`07e186f8 : 0xfffff880`00000000


STACK_COMMAND:  .thread 0xfffffa8006fbd660 ; kb

FOLLOWUP_IP: 
snapman+18e71
fffff880`01915e71 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  snapman+18e71

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: snapman

IMAGE_NAME:  snapman.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45265d99

FAILURE_BUCKET_ID:  X64_0xB8_snapman+18e71

BUCKET_ID:  X64_0xB8_snapman+18e71

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xb8_snapman+18e71

FAILURE_ID_HASH:  {89089437-cc69-08df-df5e-4415624b389b}

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

0: kd> lmvm snapman
start             end                 module name
fffff880`018fd000 fffff880`01930000   snapman  T (no symbols)           
    Loaded symbol image file: snapman.sys
    Image path: \SystemRoot\system32\DRIVERS\snapman.sys
    Image name: snapman.sys
    Timestamp:        Fri Oct 06 19:13:53 2006 (45265D99)
    CheckSum:         000375F1
    ImageSize:        00033000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

seaves88 · 04 Jun 2014

Hey Arc,
I tried uninstalling it and it makes the computer crash every time I restart it until I restore it to before the uninstall.

Arc · 04 Jun 2014

Try in safe mode?

seaves88 · 06 Jun 2014

I tried safe mode and it wouldn't let me uninstall. I finally got it to uninstall during normal boot and was able to go through the registry and delete the leftover keys that evidently cause it to not be able to boot after uninstalling Acronis. It has been running for about 5 hours without a crash so hopefully that fixed it. Thank you for your help Arc! I will be letting it run all weekend and check on Monday to see if it crashed

Arc · 07 Jun 2014

Good news. :)

Let us know how the computer is running. And let us know about any further issue.

seaves88 · 09 Jun 2014

Ok I left it running all weekend and when I got in to work this morning it was still going with no crashes so looks like that fixed it! Thank you so much for your help Arc!

Arc · 09 Jun 2014

You are welcome mate. :)

Let us know for any further issue.