Article ID: 273636
Article Last Modified on 3/1/2007
APPLIES TO
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Datacenter Server
This article was previously published under Q273636
SYMPTOMS
When you use Windows 2000, you may receive the following error message on a blue screen:
CAUSE
A Stop 0xE2 error message indicates that you manually initiated the crash. However, if the Driver Verifier Manager tool is enabled and there is an issue with either an enabled driver or one of the monitored settings, then a Stop 0x000000E2 error message is generated.
For more information on the cause of the Stop 0x000000E error, use the Kernel Debugger to open the Memory.dmp file, and then look at the functions that occurred before KeBugCheckEx, KiBugCheck, or KdpCauseBugCheck.
If the Stop 0x000000E2 error was initiated through a manual key sequence, you should see a stack in the Kernel Debugger similar to:
kd> kv
ChildEBP RetAddr Args to Child
8047130c 80466eca 817642c8 817eeba0 bffb0e02 i8042prt!I8042KeyboardInterruptService+0x327 (FPO: [Non-Fpo])
8047130c 80069f02 817642c8 817eeba0 bffb0e02 ntoskrnl!KiInterruptDispatch+0x2a (FPO: [0,2] TrapFrame @ 80471324)
80471394 804621b9 0000000e 00000000 00000000 halapic!HalProcessorIdle+0x2 (FPO: [0,0,0])
ffdff800 ffdff800 00000000 00000000 00018ca1 ntoskrnl!KiIdleLoop+0x10
MORE INFORMATION
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
244139 Windows 2000 Feature Allows a Memory.dmp File to Be Generated with Keyboard
216206 Blue Screen or STOP Error Message Troubleshooting Before You Call Microsoft Support
251233 Things to Consider Before You Enable Driver Verifier Manager on Production Servers
244617 How to Use Driver Verifier to Troubleshoot Device Drivers in Windows 2000
Keywords: kberrmsg kbprb KB273636
