BSOD last few days.

Hi.

I am getting the BSOD more frequently in a random way. I did my homework as stated here in some posts:

I verified for malware (2 different software and not my own one)
I verified for Disk
I verified for Memory.

All seems OK.

This the story:

Last January 1st I installed a fresh windows7 in my laptop and started to install all the software I have. Many was new versions, the rest the one I had.

Previously I was using vista home premium and got the bsod like 3 times in 2.5 years. Now I got 9 in this month. So I think there is something wrong here.

My PC is up to date (windows update). Drivers as well (as far I can tell).

Attached are the last 2 files (minidump and the sysdata xml file related to each one)

Everything point to a driver failure (from the 100000b8 error) but I cannot update more now.

Here is the last report from the bsod:

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.48
  Locale ID:    2058

Additional information about the problem:
  BCCode:    100000b8
  BCP1:    8946D020
  BCP2:    8D0A7D48
  BCP3:    AF477FD0
  BCP4:    00000000
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

I hope somebody can help me to debug this.

Thanks in advance for your time and Best regards

If you need more info, please let me know.

notuo said:

Hi.

I am getting the BSOD more frequently in a random way. I did my homework as stated here in some posts:

I verified for malware (2 different software and not my own one)
I verified for Disk
I verified for Memory.

All seems OK.

This the story:

Last January 1st I installed a fresh windows7 in my laptop and started to install all the software I have. Many was new versions, the rest the one I had.

Previously I was using vista home premium and got the bsod like 3 times in 2.5 years. Now I got 9 in this month. So I think there is something wrong here.

My PC is up to date (windows update). Drivers as well (as far I can tell).

Attached are the last 2 files (minidump and the sysdata xml file related to each one)

Everything point to a driver failure (from the 100000b8 error) but I cannot update more now.

Here is the last report from the bsod:

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.48
  Locale ID:    2058

Additional information about the problem:
  BCCode:    100000b8
  BCP1:    8946D020
  BCP2:    8D0A7D48
  BCP3:    AF477FD0
  BCP4:    00000000
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

I hope somebody can help me to debug this.

Thanks in advance for your time and Best regards

If you need more info, please let me know.

First one probably caused by snapman.sys, which is part of the Acronis app. I would uninstall to test and if the problem goes away re-install a fresh copy

Ken J+
EDIT: second was also caused by Acronis.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\012810-27487-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8683a000 PsLoadedModuleList = 0x86982810
Debug session time: Thu Jan 28 14:01:17.953 2010 (GMT-5)
System Uptime: 0 days 0:09:08.044
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000B8, {8946d020, 8d0a7d48, af477fd0, 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+fd6b )

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

1: 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: 8946d020, Original thread which is the cause of the failure
Arg2: 8d0a7d48, New thread
Arg3: af477fd0, Stack address of the original thread
Arg4: 00000000

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


FAULTING_THREAD:  8946d020

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xB8

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 868a8b15 to 868a1966

STACK_TEXT:  
807e4b48 868a8b15 8946d020 00000000 807c4120 nt!KiSwapContext+0x26
807e4b80 868a7403 8946d0e0 8946d020 89d0a808 nt!KiSwapThread+0x266
807e4ba8 868a12cf 8946d020 8946d0e0 00000000 nt!KiCommitThreadWait+0x1df
807e4c24 902f4d6b 89d0a808 00000000 00000000 nt!KeWaitForSingleObject+0x393
WARNING: Stack unwind information not available. Following frames may be wrong.
807e4c90 868764bc 8a223a50 898ed008 898ed228 snapman+0xfd6b
807e4ca8 901b8bed 00004000 8d017eb0 898fe000 nt!IofCallDriver+0x63
807e4cbc 901c60f7 898ed008 8a223a50 00000004 volsnap!VspAsynchronousIo+0x10f
807e4d08 901c62e8 89851c84 89851c78 00000000 volsnap!VspWriteTableUpdates+0x27d
807e4d38 901c640e 0086de58 8a2245b8 898bbcc0 volsnap!VspWriteVolumePhase32+0x12c
807e4d54 901b8ac4 00000000 89829008 00000000 volsnap!VspWriteVolumePhase3+0xc0
807e4d74 868a2b33 00000000 89829008 898bbcc0 volsnap!VspPerformanceWrapperCompletionRoutine+0x3c
807e4db8 9038c498 807e4dec 9038cabd 8a211030 nt!IopfCompleteRequest+0x128
807e4dc0 9038cabd 8a211030 89829008 00000001 CLASSPNP!ClassCompleteRequest+0x11
807e4dec 868a2b33 00000000 8a700168 00700270 CLASSPNP!TransferPktComplete+0x2e4
807e4e30 8fb27d97 8a70031c 89527008 807e4e60 nt!IopfCompleteRequest+0x128
807e4e40 8fb28636 8945e9c0 8a700168 8a70031c ataport!IdeCompleteScsiIrp+0x31
807e4e60 8fb254bd 8945e9c0 89527008 893e50e0 ataport!IdeCommonCrbCompletion+0x44
807e4e7c 8fb2b468 893e50e0 89527008 89527008 ataport!IdeTranslateCompletedRequest+0x161
807e4ef4 8fb2b66b 893e50e0 89527008 893e509c ataport!IdeProcessCompletedRequests+0x2a0
807e4f48 868a23b5 893e509c 893e5028 00000000 ataport!IdePortCompletionDpc+0xab
807e4fa4 868a2218 807c4120 8946d020 00000000 nt!KiExecuteAllDpcs+0xf9
807e4ff4 868a19dc af477b9c 00000000 00000000 nt!KiRetireDpcList+0xd5
807e4ff8 af477b9c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
868a19dc 00000000 0000001a 00d6850f bb830000 0xaf477b9c


STACK_COMMAND:  .thread 0xffffffff8946d020 ; kb

FOLLOWUP_IP: 
snapman+fd6b
902f4d6b ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  snapman+fd6b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: snapman

IMAGE_NAME:  snapman.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45265dbe

FAILURE_BUCKET_ID:  0xB8_snapman+fd6b

BUCKET_ID:  0xB8_snapman+fd6b

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

Wow zigzag that was fast.

I am on it right now. I'll post any results here later.

Thank you so much

Captain, at your command.
Thanks

Just to close this.

Acronis released a new version of Acronis Snapshot AP.

Now is working fine.Thank you all.