Question Locked

NMI error following installation of SP3 (WinXP Pro)

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
My pc, Lenovo M55e, breaksdown with the following blue screen error message:

*** Hardware Malfunction
Call your hardware vendor for support
NMI: Parity check / Memory parity error
*The system has halted*

The error occurs o n l y in when I try to connect some USB items, an LG external DVD drive or an external WD HD packed in an external enclosure.

I checked my memory cards by replacing them, and they are flawless.

In addition, I have ran a "Repair" installation of a clean streamlined SP3 disk. The disk was prepared by integrating an MS final version SP3 file with my original SP2 disk.

I can connect successfully some USB items, my Nokia cellular or my Brother printer, for example.

The final version SP3 was installed above some beta versions of SP3, which caused no problems. Since SP3 has been installed on my system for quite a long time, whether as beta or final, removal of it and returning to SP2 would be costful.

What can be done to solve this problem.

7 replies

by oh smeg

With SP2?

http://tinyurl.com/g4bv8

The only guess that I can think of is that the USB Devices that are producing a problem are not compatible with SP3. This happened quite a lot with some of the SP3 Beta's.

Col

by rancherm

For the last few months, my system was in a beta SP3 state with no discernible problems. ONLY when MS reached the final version state, only with the installation of final SP3, my problems started.
As to your suggestion to try and apply repair installation of SP2, I'm quite worried that this mixup of SP2 and SP3 may even more harmful than the current.

by oh smeg

M$ has just rereleased SP2 recently to prevent problems that have occurred with SP3 so there must be some major things occurring.

Doing a Repair Install of XP SP2 following the directions listed above will totally remove all trace of SP3 from the system but you will need to add the M$ SP Blocking Took Kit available here.

http://tinyurl.com/48oojp

M$ Notification of SP2 being rereleased is here

http://tinyurl.com/yvudk

Col

by pc-guru

go into BIOS and turn off USB legecy support or usb emulation this should prevent the BSODs ive seen this alot

by rancherm

I checked my BIOS configuration and the only USB related choice was betwen "Enable" and "Disable" USB.
Tough luck.

by Former member

Explanation: A parity error is occurring on a PC as it boots up. The parity error will typically occur as soon as the system completes the power-on self test; the memory count that is performed will typically pass without any problems being recognized. In some cases, when booting up Windows 95 or Windows NT for example, the parity error will not appear until the graphical user interface of the Windows operating system itself comes up on the screen.

Diagnosis: The most common cause of parity errors when first booting up the PC are incorrect configuration or using the wrong type of memory. It is unusual for an actual memory failure, of the type that parity checks for (meaning, you wrote one value into memory and read back another value with a bit changed) to be encountered at the start of booting, although it is possible.

Recommendation: Look on the screen to see if the system is giving you any sort of memory address that indicates where the parity error is occurring. Reboot the system and see if the same address comes up again, and then reboot a third time. Take note of whether or not the memory location changes, and then continue below:

* If the parity error is coming up as soon as the BIOS tries to boot, and especially if it fails at memory address "0000" consistently, this is a dead giveaway of trying to use non-parity memory in a parity system. Make sure that you have used real parity memory if you have parity checking enabled.
* If you are or were running with parity checking disabled, double-check the BIOS setting to make sure that it is still set as disabled. If it is enabled accidentally, parity errors will result.
* I have encountered a defect in the Abit IT5H motherboard, version 1.5, which will cause it to fail when using parity memory--it just does not work in this board due to a design flaw. Every time parity is enabled a parity error is generated immediately at boot time. It is possible that other motherboards may have similar problems. The only solution is to replace the motherboard or run with parity checking disabled.
* If you are trying to run with ECC enabled on a motherboard that supports both parity and ECC, change the ECC/parity BIOS setting to straight parity and try to reboot. If the parity error goes away, and returns when ECC is re-enabled, the chances are high that you have false parity memory in your PC. False or "logic" parity memory is designed to fool the standard motherboard parity circuits but will not work if you set the machine to run with ECC. The only good solution is to replace the memory.
* Make sure that the modules you are using are appropriate for your board. In particular, there are some motherboards that will not support the newer ECC-only modules. See this section for more in the differences.
* On a new PC, it is possible that you have an actual hardware failure. If the parity error address remains the same or is in the same general vicinity each time it is encountered, this implies a failure of the memory itself. Troubleshoot the memory itself here.
* Look in the section on parity errors encountered during operation. It is possible that one of the causes there could be responsible for a parity error encountered during the boot (just less likely than the causes listed above).

Please post back if you have any more problems or questions.

This discussion is closed to new replies.