Parity Error BSOD

[ynbniar]

Got the BSOD a few weeks ago playing Call of Jaurez. First time in 3 years, thought it was Call of Jaurez's fault.

Then the other night playing Civilization IV, got it a couple of times.

More importantly and more worryingly I ran DefCon tonight and got BSOD before DefCon even started

Same BSOD every time...

NMI Parity Check/Memory Parity Error

Ran Windows Memory Diagnostic and it found no errors.

P4 3.2
2GB Ram
Windows XP
7800GTX

NVidia drivers are up to date.
Soundblaster drivers are up to date.
All clean installs.

Could it be a problem with soundcard or graphics card memory...only happens randomly when I play/run games?

Cheers

EDIT
Got it again tonight while surfing (Firefox)???

Found an error with Nvidia Port IO Driver so disabled it...we will see if that does anything...

[frenchfrog]

Smell like bad RAM, try MemTest86? Or the Microsoft equivalent??? (link from google)



BSOD generic answer

If it is instantly resetting, then thats XP doing a blue screen of death, and then restarting before you can read it. Handy.

If you could right click on 'My Computer', and select Properties, then select the Advanced tab, and where it says 'Startup and Recovery', click 'settings'.

There'll be a box that says 'System failure', and in that, a checkbox labled 'Automatically restart'. If you uncheck that box, and click Ok, Apply and then OK, you'll be ready

Now grab a pen and some paper. Start Uplink. Play for as long as you can before the system crashes. If you get a blue screen, record down the STOP reason and it's code

Next take that STOP reason and go to TROUBLESHOOTING WINDOWS STOP MESSAGES

[ynbniar]

Smell like bad RAM, try MemTest86? Or the Microsoft equivalent??? (link from google)

Thank you for taking the time to reply frenchfrog…I know it was a bit cheeky of me asking about BSOD problems here but when it starts affecting DefCon I get upset...

Anyway I already tried Windows memory check and it didn’t find any problems…I’ll try the other test for confirmation.

Cheers

[frenchfrog]

Have you check the exact stop reason?

[ynbniar]

Have you check the exact stop reason?

All the BSOD says is "NMI Parity Check/Memory Parity Error."

...there is loads on this on the internet but it boils down to...it's either a problem with RAM or a problem with something else...anything else!!!

After running Memtest86 and windows memory test and getting no errors I suppose it must be "something else".

However, there was a development tonight...got an entirely new BSOD every time I rebooted...

Problem with "nv4_disp" (NVidia driver).

Message went on about "...the device driver got stuck in an infinite loop...indicates problem with device itself or with the device driver...".

So it would dappear I have a problem with either my 7800 graphics card or the driver. Now I keep my drivers up to date and thinking back, the BSOD problems started not long after I installed the very latest Forceware drivers.

So I've done a clean install of some older drivers to see if the BSOD thing goes away...so far so good.

Cheers

[IactoSophos]

Yeah, that sounds like a corruption error, most likely in your hard drive. I had a good one whenever I booted up windows after my HDD started to... well, the only way I can describe it is 'click'. Had to do a complete reinstall of XP *cries*

[shinygerbil]

[xander]

xander

[shinygerbil]

Sorry, I couldn't help it.

[xander]

Ah lurves you, shineh-gerbil!

xander