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 = 0x8183f000 PsLoadedModuleList = 0x81987810
Debug session time: Sat Mar 5 00:49:28.905 2011 (UTC + 0:00)
System Uptime: 0 days 0:02:16.092
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000B8, {858bf030, 807eb800, 9b61bfd0, 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: 858bf030, Original thread which is the cause of the failure
Arg2: 807eb800, New thread
Arg3: 9b61bfd0, Stack address of the original thread
Arg4: 00000000
Debugging Details:
------------------
FAULTING_THREAD: 858bf030
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xB8
PROCESS_NAME: SearchIndexer.
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 818adb15 to 818a6966
STACK_TEXT:
87207bf0 818adb15 858bf030 00000000 807e6120 nt!KiSwapContext+0x26
87207c28 818ac403 858bf0f0 858bf030 84663ca0 nt!KiSwapThread+0x266
87207c50 818a62cf 858bf030 858bf0f0 00000000 nt!KiCommitThreadWait+0x1df
87207ccc 8660fd6b 84663ca0 00000000 00000000 nt!KeWaitForSingleObject+0x393
WARNING: Stack unwind information not available. Following frames may be wrong.
87207d38 8187b4bc 843672c0 833291a8 8332935c snapman+0xfd6b
87207d50 867c3bed 00004000 843bb408 846a5000 nt!IofCallDriver+0x63
87207d64 867d10f7 833291a8 843672c0 00000004 volsnap!VspAsynchronousIo+0x10f
87207db0 867d12e8 843bfc84 843bfc78 00000000 volsnap!VspWriteTableUpdates+0x27d
87207de0 867d140e 007f3950 8436b388 835524c8 volsnap!VspWriteVolumePhase32+0x12c
87207dfc 867c3ac4 00000000 84d1e6d8 00000000 volsnap!VspWriteVolumePhase3+0xc0
87207e1c 818a7b33 00000000 84d1e6d8 835524c8 volsnap!VspPerformanceWrapperCompletionRoutine+0x3c
87207e60 865ac498 87207e94 865acabd 843474f0 nt!IopfCompleteRequest+0x128
87207e68 865acabd 843474f0 84d1e6d8 00000001 CLASSPNP!ClassCompleteRequest+0x11
87207e94 818a7b33 00000000 83c56b80 00c56c88 CLASSPNP!TransferPktComplete+0x2e4
87207edc 861209a5 840479b0 87207f20 8612fa10 nt!IopfCompleteRequest+0x128
87207ee8 8612fa10 83c56b80 00000001 00000000 storport!RaidCompleteRequestEx+0x1c
87207f20 861211d9 840479b0 840343b4 858bf0b4 storport!RaidUnitCompleteRequest+0xac
87207f48 818a73b5 840343b4 84034340 00000000 storport!RaidpAdapterDpcRoutine+0x51
87207fa4 818a7218 807e6120 858bf030 00000000 nt!KiExecuteAllDpcs+0xf9
87207ff4 818a69dc 9b61bce4 00000000 00000000 nt!KiRetireDpcList+0xd5
87207ff8 9b61bce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
818a69dc 00000000 0000001a 00d6850f bb830000 0x9b61bce4
STACK_COMMAND: .thread 0xffffffff858bf030 ; kb
FOLLOWUP_IP:
snapman+fd6b
8660fd6b ?? ???
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