I will copy the minidump anaylze here and hopefully someone can help point me in the right direction. This has been occuring over a few weeks, but doesnt happen 'every day', and sometimes will come back up from the dump and be ok. When it BSOD and its going to be a 'bad day', it will loop and the only way I can recover and get back to business again is to restart in safe mode..... disable the NICs, and load back in normal mode and then re-enable them again. That seems to 'get us going' when i'm in the loop. By doing that I assumed that there may be a physical problem or drivers.. I have updated the drivers and it was ok for about 4 days and then it started again. I'm not sure what to do next honestly.
Thanks again for anyone's help on this.
-----------------------------
Microsoft ® Windows Debugger Version 6.4.0007.2
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINNT\Minidump\Mini052505-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x80484b80
Debug session time: Wed May 25 09:26:48.273 2005 (GMT-10)
System Uptime: not available
Loading Kernel Symbols
........................................................................................................
Loading unloaded module list
.....
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiTrap08+41 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
TSS: 00000000 -- (.tss 0)
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 00000000 to 80468ecf
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nt!KiTrap08+0x41
FOLLOWUP_IP:
nt!KiTrap08+41
80468ecf ebef jmp nt!KiTrap08+0x32 (80468ec0)
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiTrap08+41
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41773335
STACK_COMMAND: .tss 0 ; kb
FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+41
BUCKET_ID: 0x7f_8_nt!KiTrap08+41
Followup: MachineOwner
---------
Sign In
Create Account
