September 19, 2003

So here's yet another update on the pesky "NMI: Parity Check / Memory Parity Error" message, I've repeatedly written about (original article and first update).

Last week, Markus Franke sent me this email:

Hi,
just read your story about the NMI parity error.

I'd like to add some information. I see the error with Linux too, but the kernel boots, it's just a message in the logs.

Win2k crashes while trying to install.
WinXP never installs, the installer hangs.

After reading your hint with the new hardware, I removed my second network adapter and the ISDN card and now I can install Win2k on my IBM box.

Many thanks!!

Most interesting that the error occurs in Linux too, but that removing some hardware seemed to have fixed the problem for Marcus.

Any more feedback from readers is most welcome, and will be logged here for the greater good.

Oh - and did I mention that despite my best efforts in enganging the powerful Microsoft Evangelist Robert Scoble (Hi, Scoble. How's it going?), there hasn't been a peep from the vast internal bowels of the Redmond Godzilla since June in regards to fixing the NMI Parity error...