I’ve gotten the following blue screen multiple times on two Windows NT
systems. We both design / build the hardware and write the drivers , so I
suspect something we control, not the RAM or some third-party component.
NMI: Parity Check / Memory Parity Error
*** The system has halted ***
*** STOP: 0x00000080 (0x004F4454,0x00000000,0x00000000,0x00000000)
Hardware malfunction.
I know that 0x00000080 is an NMI_HARDWARE_ERROR, but that’s all the
information that I can find.
The big question is “What does the first parameter mean?” That parameter
is the same on both machines and every blue screen. If it were a memory
address (indicating the bad RAM address), I certainly wouldn’t expect it
to be the same on both machines!
This is particularly bothersome because we now have about 2000 of these
machines out there, but we’ve only seen this (identical) problem on 2 of
them that I know of.
Thanks in advance for any pointers!
‘ODT’, its ascii. I don’t think it means much at all, other than that
this was a real NMI failure. The NMI handler reads motherboard status
port 0x33. The bugcheck string displayed (Parity Check / Memory Parity
Error) is the result of this status port read. Your hardware is somehow
causing the memory system to fail.
=====================
Mark Roddy
Windows XP/2000/NT Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
xxxxx@hollistech.com
For Windows Device Driver Training: see www.azius.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@vertical.com
Sent: Thursday, April 04, 2002 2:34 AM
To: NT Developers Interest List
Subject: [ntdev] How to interpret a stop code 0x00000080?
I’ve gotten the following blue screen multiple times on two
Windows NT systems. We both design / build the hardware and
write the drivers , so I suspect something we control, not
the RAM or some third-party component.
NMI: Parity Check / Memory Parity Error
*** The system has halted ***
*** STOP: 0x00000080 (0x004F4454,0x00000000,0x00000000,0x00000000)
Hardware malfunction.
I know that 0x00000080 is an NMI_HARDWARE_ERROR, but that’s
all the information that I can find.
The big question is “What does the first parameter mean?”
That parameter is the same on both machines and every blue
screen. If it were a memory address (indicating the bad RAM
address), I certainly wouldn’t expect it to be the same on
both machines!
This is particularly bothersome because we now have about
2000 of these machines out there, but we’ve only seen this
(identical) problem on 2 of them that I know of.
Thanks in advance for any pointers!
You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
%%email.unsub%%
> I’ve gotten the following blue screen multiple times on two Windows NT
systems. We both design / build the hardware and write the drivers , so I
suspect something we control, not the RAM or some third-party component.
NMI: Parity Check / Memory Parity Error
*** The system has halted ***
*** STOP: 0x00000080 (0x004F4454,0x00000000,0x00000000,0x00000000)
Hardware malfunction.
Maybe some PCI bus hardware error? They are mapped to NMI too.
Max
> ‘ODT’, its ascii. I don’t think it means much at all, other than that
this was a real NMI failure. The NMI handler reads motherboard status
port 0x33. The bugcheck string displayed (Parity Check / Memory Parity
Error) is the result of this status port read. Your hardware is somehow
causing the memory system to fail.
Well, that brings up a few more questions:
– Do you know that “ODT” (or maybe “TDO”) has some meaning or did you just
happen to notice the ASCII pattern?
– By “real NMI failure”, do you mean a real NMI versus something like PERR
/ SERR / IOCHCHK signals which get routed to NMI?
– What is port 0x33? It’s not listed in any Intel chip / motherboard
manual that I could find. (Although I found a bit of source code that reads
it and decodes NMI_PARITY from it.) If you know the name or a document, I
can look that up.
Thanks for any assistance!