Microsoft KB Archive/262686

= CPU Context Is Not Saved in the Memorydump File When NMI Occurs =

PSS ID Number: 262686

Article Last Modified on 11/14/2003

-

The information in this article applies to:


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional

-



This article was previously published under Q262686



SYMPTOMS
When you view the crashdump by using the kernel mode debugger, the processor registers for one more processor on a multiple-processor computer are all zero (0):

1: kd> r eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=00000000 eip=00000000 esp=00000000 ebp=00000000 iopl=0        nv up di pl nz na pe nc cs=0000  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00000000 0000:00000000 ??         ???



CAUSE
This problem can occur because CPU context is not saved in the memorydump file when a non-maskable interrupt (NMI) occurs on a multiple-processor computer. In the crashdump file with this problem, register information for most of the CPUs has all zeroes.

When you view the crashdump file, check if one of the processors is currently handling a NMI. The stack trace contains the following information:

0: kd> kv ChildEBP RetAddr Args to Child 8046dad0 804638d1 00000000 803ed000 00000000 halmps!HalHandleNMI+0x19d(FPO: [Non-Fpo] 8046dad0 80461a32 00000000 803ed000 00000000 ntkrnlmp!KiTrap02+0x41 (FPO: TaskGate 28:0) ffdff800 ffdff800 00000000 00000000 00014a7c ntkrnlmp!KiIdleLoop+0x4a(FPO: [Non-Fpo]



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbenv kbfix kbMemory KB262686

Technology: kbwin2000AdvServ kbwin2000AdvServSearch kbwin2000Pro kbwin2000ProSearch kbwin2000Search kbwin2000Serv kbwin2000ServSearch kbWinAdvServSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.