New Posts  All Forums:Forum Nav:

Memory Parity Error - Page 2

post #21 of 34
Also got this BSOD with the parity error two times and it's really funny since I switched from Dell's video drivers to XG drivers it never happened again...and also nic eto see is that with the XG drivers my card isn't running that hot, with stock drivers I had 62° C and with the XG I have 56° C on idle...
post #22 of 34
post #23 of 34
I had this memory parity error last night first while playing C&C3. Since then, it happened twice more. Is it certain that this is a video card issue related to overheating?

E1705/CoreDuo2.0/1.5Gb553/7900GS
post #24 of 34
i used to get it frequently when playing HL2 under XP. I suspect the problem was driver related. I haven't encountered it yet under Vista 64.
post #25 of 34
I used to get this all the time due to my Atheros wireless card until I found a good set of drivers and it stopped.
post #26 of 34
I upgraded my e1705 to 2gb from Dell last week, ever since then whenever I ran bf2 it would give me the parity error after 30min of playing, which I've never had before. Ran diagnostics and both sticks passed, so I tried with just one stick installed. One of the sticks worked fine, the other gave me the error so they're sending me a replacement. I'm just wondering if I should get a warranty now since it's expired, I'm a little worried now. Hopefully the replacement will fix this for me.
post #27 of 34
Quote:
Originally Posted by Abadee View Post
I used to get this all the time due to my Atheros wireless card until I found a good set of drivers and it stopped.

What card and driver set are you running? I'm on a GIGABYTE GN-WI01GT and am getting these errors as well. I'm also using i8kfangui, a modded bios, and have passed an overnight run of memtest86+.
post #28 of 34
chances are the issue is driver related. try a different video driver and it will most likely fix the problem.
post #29 of 34
I wouldn't call memtest the end all be all. If you only get the errors with one of the sticks of RAM then thats pretty definitive. I'm assuming you have kept all other variables constant.
post #30 of 34
I too have been plagued with the NMI memory error. I found that the reason for the crashing was the USB drivers. I installed the latest chipset drivers and so far the errors have stopped.
post #31 of 34
I fell sympathy for all ppl who get NMI Parity Errors becasue I have cried myself to sleep over this problem for like a month. But w/ constant help from the wonderful guys/gals at NBF their experience helped greatly in rooting out some problems. I did research of Parity errors for a good solid 2 weeks. From reading 100's of posts and 'tech' guides I have come to find a few things.

Lots of people have different experiences w/ these errors and by reading their cause and effect stories I was able to play w/ many things.

From MY experiences I have come to see that-
It Could very well be a Hardware issue, but my natural human instinct points my attention to those Dell Drivers. I was running Dell stock driver 84.69 and had a whole slew of problems w/ my system while using it. When I came across a thread and there were people 'bashing' stock Dell drivers(note- im not bashing anything here, im trying to give an unbiased response). So i decided to uninstall 84.69 and a buddy of mine told me to use a 'genuine Nvidia driver, as they are the most stable.' He is a big computer dude and is pretty knowledgeable so I gave nvidia.com a look. I downloaded driver 84.63 and installed it(removed dell video stock driver 1st). I am now currently using 84.63 on my 1705 and I havent seen the error in over 4 months now. So it I now have a special place in my heart for driver 84.63

I should also mention. I did have my video card replaced but heres the rundown.

I used my 1705 and the 84.63 driver from Nvidia happily w/ no errors for about 2-3 weeks BEFORE i sent the laptop in to get its card replaced. However, I am convinced that it wasnt my card to blame, but the Dell driver. As I had stated above, I was was parity error free for about 2-3 weeks while using the nvidia driver. The laptop was sent in later to have the LCD replaced(dead pixels) and they replaced the video card (fools)

So while only God may know what the problem was, Im convinced that it was a bad driver at fault, not necessarily my 7900GS mainly beacsue it ran w/ no problems for almost a month using a different video driver.

Hope this helps, GL man I hate parity erros w/ a passion.

Ps- FEED ME
post #32 of 34
Is there any way to look into something like a crash log to figure out what device's driver is causing this problem?
post #33 of 34
I just had my first NMI memory parity error on the M1710 and it just so happened after I reinstalled the audio drivers because the microphone wasn't working.

maybe this isn't just video related but other drivers as well...
post #34 of 34
Quote:
Originally Posted by mmk1125 View Post
I just had my first NMI memory parity error on the M1710 and it just so happened after I reinstalled the audio drivers because the microphone wasn't working. maybe this isn't just video related but other drivers as well...
Problem: The parity error message can mean 2 things. It's either your ram that is bad or your video card is fried. Solution: Run memtest86 to find out if its the ram. If its the ram, keep complaining to Dell to replace your ram until you get sticks that will not even give one error in memtest86 overnight. If its not your ram, try setting your graphics performance level to Balanced. If there errors go away, it is your video card. Complain to Dell saying your computer gives that error when you play games and get them to replace your card. thewird
New Posts  All Forums:Forum Nav:
  Return Home