- STOP 0x0000000A
- Posted by Michel G on October 16th, 2003
W2K SP-4 Built 5.00.2195 reported following stop message
when failling to reboot following the installation of the
5 fixes released yesterday (October 15).
STOP 0x0000000A(0x0000015A, 0x00000002, 0x00000000,
0x8042EA48)IRQL_NOT_LESS_OR_EQUAL
** Address 0x8042EA048 has base at <80400000>-ntoskrnl.exe
Have not been able to reboot since, or fix the problem
through safe mode, booting from CD-ROM or reinstalling
W2K. No HW or SW added to the system for months.
Any useful hint and/or KB on this problem? How do we
identify the device/service/app through Recovery Console?
TIA
- Posted by Jimmy Andersson [MVP] on October 16th, 2003
Possible Resolutions to Stop 0x0a, 0x01e and 0x50 Errors:
http://support.microsoft.com/default...;EN-US;Q183169
Regards,
/Jimmy
--
Jimmy Andersson, Q Advice AB
Microsoft MVP - Active Directory
---------- www.qadvice.com ----------
"Michel G" <anonymous@discussions.microsoft.com> wrote in message
news:02b401c39421$1ad40500$a401280a@phx.gbl...
- Posted by Doug Allen [MSFT] on October 16th, 2003
Michael,
The BEST way would be for us to look at the memory dump file from one of the
crashes. However since the machine won't boot, there are a few things to
try. Do you know which fixes were installed?
1) Boot the server with the Last Known Good configuration.
2) From the recovery console, we can run an uninstall of the patches that
were installed (usually), but it can be very cryptic.
You can contact Microsoft Support and open a free incident to get assistance
with this appears to have been caused by a patch that was installed. One of
us will then be glad to work with you until we get your issue resolved. The
number is 866-PCSAFETY.
Good luck!
--
Doug Allen
Windows 2000 MCSE
Microsoft Enterprise Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jimmy Andersson [MVP]" <jimmy_NO_SPAM@mvps.org> wrote in message
news:OdzVMTClDHA.2060@tk2msftngp13.phx.gbl...