Hi,
I am running SBS 2003 Premium R2 with Backup Exec 12, I am experiencing BSOD's only during backup jobs. The jobs can be running on various drives and will have completed various amounts of data before the BSOD occurs so there is no pattern to it. Below is the latest CrashDump :
==========================
==========
==========
==========
==========
========
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini0
50108-02.d
mp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\windows\symbols*
http://msdl.microsoft.com/download/symbolsExecutable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs) Free x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS
Built by: 3790.srv03_sp2_gdr.070304-
2240
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Thu May 1 11:35:54.149 2008 (GMT+1)
System Uptime: 0 days 5:07:33.156
Loading Kernel Symbols
..........................
..........
..........
..........
..........
..........
..........
..........
..........
.........
.............
Loading User Symbols
Loading unloaded module list
........
**************************
**********
**********
**********
**********
**********
***
* *
* Bugcheck Analysis *
* *
**************************
**********
**********
**********
**********
**********
***
Use !analyze -v to get detailed debugging information.
BugCheck B8, {8b57e660, 8a29f9a0, f78ff000, 0}
Probably caused by : ntkrpamp.exe ( nt!ScPatchFxe+4c )
Followup: MachineOwner
---------
2: 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: 8b57e660, Original thread which is the cause of the failure
Arg2: 8a29f9a0, New thread
Arg3: f78ff000, Stack address of the original thread
Arg4: 00000000
Debugging Details:
------------------
FAULTING_THREAD: 8b57e660
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDU
MP
BUGCHECK_STR: 0xB8
PROCESS_NAME: lsass.exe
CURRENT_IRQL: 1b
LAST_CONTROL_TRANSFER: from 8088dd4d to 80827c63
STACK_TEXT:
b9817cec 8088dd4d 000000b8 8b57e660 8a29f9a0 nt!KeBugCheckEx+0x1b
b9817d18 80a5c1ae b9817d64 042eff00 00000002 nt!ScPatchFxe+0x4c
8ac87720 00000000 88f5db90 88f5db90 8ac87730 hal!HalpDispatchSoftwareIn
terrupt+0x
5e
STACK_COMMAND: .thread 0xffffffff8b57e660 ; kb
FOLLOWUP_IP:
nt!ScPatchFxe+4c
8088dd4d c3 ret
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ScPatchFxe+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:
45ec0a19
FAILURE_BUCKET_ID: 0xB8_nt!ScPatchFxe+4c
BUCKET_ID: 0xB8_nt!ScPatchFxe+4c
Followup: MachineOwner
---------
==========================
==========
==========
==========
==========
=====
I am struggling to find a solution so any light that can be shed on this will be greatly appreciated.
Thanks in advance.
Start Free Trial