Ntkrnlmp.exe BSOD
My windows server 2003 SP2 machine continues to crash. The dump file is pointing to the Ntkrnlmp.exe. I have the latest service pack and the version of the Ntkrnlmp.exe is 5.2.3790.4566. I found several Ntkrnlmp.exe files, so I am not sure which folder actually contains the correct version. I found a folder under the c:\WINNT\system32\dllcache. Any advice is much appreciate.Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+dc ) Followup: MachineOwner--------- 2: 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 kindthat the kernel isn't allowed to have/catch (bound trap) or thatis always instant death (double fault). The first number in thebugcheck params is the number of the trap (8 = double fault, etc)Consult an Intel x86 family manual to learn more about what thesetraps 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 valueElse .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)Endifkb will then show the corrected stack.Arguments:Arg1: 00000008, EXCEPTION_DOUBLE_FAULTArg2: f772fff0Arg3: 00000000Arg4: 00000000 Debugging Details:------------------ **************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: kernel32!pNlsUserInfo ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command to work properly, your symbol path ****** must point to .pdb files that have full type information. ****** ****** Certain .pdb files (such as the public OS symbols) do not ****** contain the required information. Contact the group that ****** provided you with these symbols if you need this command to ****** work. ****** ****** Type referenced: kernel32!pNlsUserInfo ****** **************************************************************************** BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28)eax=b76e002c ebx=c0000000 ecx=8a074ba0 edx=00000000 esi=c0300000 edi=89392660eip=8084708f esp=b76e0000 ebp=b76e003c iopl=0 nv up ei pl zr na pe nccs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246nt!MmAccessFault+0xad7:8084708f ff750c push dword ptr [ebp+0Ch] ss:0010:b76e0048=00000000Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: b76e1098 -- (.trap 0xffffffffb76e1098)ErrCode = 00000000eax=00000000 ebx=00000000 ecx=00000000 edx=8083a148 esi=00000000 edi=00000000eip=00000000 esp=b76e110c ebp=b76e112c iopl=0 nv up ei pl zr na pe nccs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=0001024600000000 ?? ???Resetting default scope EXCEPTION_RECORD: b76e15b0 -- (.exr 0xffffffffb76e15b0)ExceptionAddress: 00000000 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000010NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000000Attempt to read from address 00000000 LAST_CONTROL_TRANSFER: from 808368c2 to 8084708f STACK_TEXT: b76e003c 808368c2 00000000 00000000 00000000 nt!MmAccessFault+0xad7b76e003c 00000000 00000000 00000000 00000000 nt!KiTrap0E+0xdcWARNING: Frame IP not in any known module. Following frames may be wrong.b76e00c4 8083a134 b76e056c b76e3c24 b76e0268 0x0b76e00e8 8083a106 b76e056c b76e3c24 b76e0268 nt!ExecuteHandler2+0x26b76e0198 808162f9 b76e056c b76e0268 00000000 nt!ExecuteHandler+0x24b76e0550 8083435c b76e056c 00000000 b76e05c0 nt!KiDispatchException+0x131b76e05b8 80834310 b76e0654 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e0630 8083a134 b76e0ad8 b76e3c24 b76e07d4 nt!Kei386EoiHelper+0x186b76e0654 8083a106 b76e0ad8 b76e3c24 b76e07d4 nt!ExecuteHandler2+0x26b76e0704 808162f9 b76e0ad8 b76e07d4 00000000 nt!ExecuteHandler+0x24b76e0abc 8083435c b76e0ad8 00000000 b76e0b2c nt!KiDispatchException+0x131b76e0b24 80834310 b76e0bc0 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e0b9c 8083a134 b76e1044 b76e3c24 b76e0d40 nt!Kei386EoiHelper+0x186b76e0bc0 8083a106 b76e1044 b76e3c24 b76e0d40 nt!ExecuteHandler2+0x26b76e0c70 808162f9 b76e1044 b76e0d40 00000000 nt!ExecuteHandler+0x24b76e1028 8083435c b76e1044 00000000 b76e1098 nt!KiDispatchException+0x131b76e1090 80834310 b76e112c 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e1108 8083a134 b76e15b0 b76e3c24 b76e12ac nt!Kei386EoiHelper+0x186b76e112c 8083a106 b76e15b0 b76e3c24 b76e12ac nt!ExecuteHandler2+0x26b76e11dc 808162f9 b76e15b0 b76e12ac 00000000 nt!ExecuteHandler+0x24b76e1594 8083435c b76e15b0 00000000 b76e1604 nt!KiDispatchException+0x131b76e15fc 80834310 b76e1698 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e1674 8083a134 b76e1b1c b76e3c24 b76e1818 nt!Kei386EoiHelper+0x186b76e1698 8083a106 b76e1b1c b76e3c24 b76e1818 nt!ExecuteHandler2+0x26b76e1748 808162f9 b76e1b1c b76e1818 00000000 nt!ExecuteHandler+0x24b76e1b00 8083435c b76e1b1c 00000000 b76e1b70 nt!KiDispatchException+0x131b76e1b68 80834310 b76e1c04 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e1be0 8083a134 b76e2088 b76e3c24 b76e1d84 nt!Kei386EoiHelper+0x186b76e1c04 8083a106 b76e2088 b76e3c24 b76e1d84 nt!ExecuteHandler2+0x26b76e1cb4 808162f9 b76e2088 b76e1d84 00000000 nt!ExecuteHandler+0x24b76e206c 8083435c b76e2088 00000000 b76e20dc nt!KiDispatchException+0x131b76e20d4 80834310 b76e2170 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e214c 8083a134 b76e25f4 b76e3c24 b76e22f0 nt!Kei386EoiHelper+0x186b76e2170 8083a106 b76e25f4 b76e3c24 b76e22f0 nt!ExecuteHandler2+0x26b76e2220 808162f9 b76e25f4 b76e22f0 00000000 nt!ExecuteHandler+0x24b76e25d8 8083435c b76e25f4 00000000 b76e2648 nt!KiDispatchException+0x131b76e2640 80834310 b76e26dc 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e26b8 8083a134 b76e2b60 b76e3c24 b76e285c nt!Kei386EoiHelper+0x186b76e26dc 8083a106 b76e2b60 b76e3c24 b76e285c nt!ExecuteHandler2+0x26b76e278c 808162f9 b76e2b60 b76e285c 00000000 nt!ExecuteHandler+0x24b76e2b44 8083435c b76e2b60 00000000 b76e2bb4 nt!KiDispatchException+0x131b76e2bac 80834310 b76e2c48 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e2c24 8083a134 b76e30cc b76e3c24 b76e2dc8 nt!Kei386EoiHelper+0x186b76e2c48 8083a106 b76e30cc b76e3c24 b76e2dc8 nt!ExecuteHandler2+0x26b76e2cf8 808162f9 b76e30cc b76e2dc8 00000000 nt!ExecuteHandler+0x24b76e30b0 8083435c b76e30cc 00000000 b76e3120 nt!KiDispatchException+0x131b76e3118 80834310 b76e31b4 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e313c 80842b32 d6ca5000 c0300d6c 00000000 nt!Kei386EoiHelper+0x186b76e31b4 8083a106 b76e3638 b76e3c24 b76e3334 nt!MmCheckCachedPageState+0x309b76e3264 808162f9 b76e3638 b76e3334 00000000 nt!ExecuteHandler+0x24b76e361c 8083435c b76e3638 00000000 b76e368c nt!KiDispatchException+0x131b76e3684 80834310 b76e3720 00000000 badb0d00 nt!CommonDispatchException+0x4ab76e36fc 8083a134 b76e3ba4 b76e3c24 b76e38a0 nt!Kei386EoiHelper+0x186b76e3720 8083a106 b76e3ba4 b76e3c24 b76e38a0 nt!ExecuteHandler2+0x26b76e37d0 808162f9 b76e3ba4 b76e38a0 00000000 nt!ExecuteHandler+0x24b76e3b88 8083435c b76e3ba4 00000000 b76e3bf8 nt!KiDispatchException+0x131b76e3bf0 80834310 80923d83 e18f37d8 badb0d00 nt!CommonDispatchException+0x4ab76e3c0c 8093707b e18f37d0 e18f37d0 b76e3c30 nt!Kei386EoiHelper+0x186b76e3c54 80923d83 00000002 e18f37d8 00000008 nt!RtlValidSid+0x41b76e3c68 80928169 e18f37d0 00000002 000f01ff nt!RtlAddAccessAllowedAce+0x1ab76e3c90 80928039 e429db50 e1e47de0 b76e3d10 nt!SepCreateImpersonationTokenDacl+0x95b76e3d30 80941508 fffffffe 00020008 00000001 nt!NtOpenThreadTokenEx+0xc4b76e3d4c 8083387f fffffffe 00020008 00000001 nt!NtOpenThreadToken+0x18b76e3d4c 7c82860c fffffffe 00020008 00000001 nt!KiFastCallEntry+0xfc022bfcc8 7c827409 7d206d05 fffffffe 00020008 ntdll!KiFastSystemCallRet022bfccc 7d206d05 fffffffe 00020008 00000001 ntdll!ZwOpenThreadToken+0xc022bfce4 776c152c fffffffe 00020008 00000001 ADVAPI32!OpenThreadToken+0x17022bfd14 776c1498 00172118 00000001 022bfd94 ole32!GetTokenForRpcClient+0xd7022bfd5c 77c7c42a 022bfd84 00172118 001083d8 ole32!ORPCInterfaceSecCallback+0x148022bfdb4 77c7c4b0 00172118 0667ee48 064cd418 RPCRT4!RPC_INTERFACE::CheckSecurityIfNecessary+0x6f022bfdcc 77c7c46c 00172118 00172118 00094198 RPCRT4!LRPC_SBINDING::CheckSecurity+0x4f022bfdfc 77c812f0 061393d8 00094198 000dd210 RPCRT4!LRPC_SCALL::DealWithRequestMessage+0x2bb022bfe20 77c88678 000941d0 022bfe38 061393d8 RPCRT4!LRPC_ADDRESS::DealWithLRPCRequest+0x127022bff84 77c88792 022bffac 77c8872d 00094198 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x430022bff8c 77c8872d 00094198 00000000 00000000 RPCRT4!RecvLotsaCallsWrapper+0xd STACK_COMMAND: .tss 0x28 ; kb MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe FOLLOWUP_NAME: MachineOwner DEBUG_FLR_IMAGE_TIMESTAMP: 4a79a315 FOLLOWUP_IP: nt!KiTrap0E+dc808368c2 85c0 test eax,eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiTrap0E+dc FAILURE_BUCKET_ID: TRAP_FRAME_RECURSION BUCKET_ID: TRAP_FRAME_RECURSION Followup: MachineOwner---------
January 4th, 2010 8:09pm

You may want to verify that a processor is not defective.Stop 7F, 0x00000008 (double-fault) error occurs because of a single-bit error in the ESP registerhttp://support.microsoft.com/kb/842465Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]
Free Windows Admin Tool Kit Click here and download it now
January 4th, 2010 8:21pm

Thanks for the response. It appears the processor on my RILO board is bad. I updated the firmware, however, it was still reporting a problem. I have removed the hardware and will be monitoring the server. If it doesn't reboot after a few days, then we can assume it may have been faulty hardware. Thanks again for the information which pointed me in the processor direction.Tina.
January 5th, 2010 3:50am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics