Hmm... I have Q103059 printed out and stuck to my wall (wish I had saved it
to a file!), which lists the "Description of Bug Codes for Windows NT". I
can't seem to find it on MS's site anymore, but if you do a google search,
there are tons of hits referencing the article. I would imagine that many
of these apply to Win2k still.
For KMODE_EXCEPTION_NOT_HANDLED (0x1E)
"This is a very common bug code. Usually the exception address pinpoints
the driver or function that caused the problem. Always note this address as
well as the link date of the driver or image that contains this address. A
common error is exception code 0x80000003. This error means a hard-coded
breakpoint or assertion was hit, but the system was booted with the /NODEBUG
switch. This problem should not occur very often. If it occurs repeatedly,
make sure a debugger is connected and the system is booted with the /DEBUG
switch.
On non-Intel systems, if the address of the exception is 0xbfc0304, the bug
code is the result of a cache-parity error on the CPU. If the problem
reoccurs frequently, contact the hardware manufacturer.
Parameters:
1 - The exception code that was not handled
2 - The address at which the exception occurred
3 - Parameter 0 of the exception
4 - Parameter 1 of the exception"
I know it's probably not much more info than you already have, but good
luck!
-Bonnie
-----Original Message-----
From: Gareth Campling [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 11, 2001 4:53 AM
To: NT System Admin Issues
Subject: win2k Blue Stop Screens
Hi
has anyone got a list of what the 2k blue stop screens actually mean,
got 1 machine that keeps erroing with KMODE_EXCEPTION_NOT_HANDELD
would like to know why this is and also have a list for reference
thanks in advance
--
Best regards,
Gareth, MCP mailto:[EMAIL PROTECTED]
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
