Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account

Windows 2000 Server Crashing (ntkrnlmp.exe)

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 1 posts
I've noticed a few postings regarding these types of BSOD issues and mine unfortunately hasn't turned up any 'helpful' information when reading the crash dumps. I apologize in advance if this information is someplace else, but please advise if you have any suggestions.....

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 *
* *

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
.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)
kb will then show the corrected stack.
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:


TSS: 00000000 -- (.tss 0)



LAST_CONTROL_TRANSFER: from 00000000 to 80468ecf

00000000 00000000 00000000 00000000 00000000 nt!KiTrap08+0x41

80468ecf ebef jmp nt!KiTrap08+0x32 (80468ec0)



SYMBOL_NAME: nt!KiTrap08+41


IMAGE_NAME: ntkrnlmp.exe


STACK_COMMAND: .tss 0 ; kb

FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+41

BUCKET_ID: 0x7f_8_nt!KiTrap08+41

Followup: MachineOwner
  • 0




    Retired Staff

  • Retired Staff
  • 11,365 posts
an unexpected kernel mode trap means that the kernel has caught an error, perhaps by looking in memory for something and not finding it, or it tried to write and could not.

often driver related or bad ram
  • 0

Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP