NotebookForums.com › Forums › Notebook Manufacturers › Dell Forums › Dell Home (Inspiron, XPS, Studio) › IM keep having a memory parity error
New Posts  All Forums:Forum Nav:

IM keep having a memory parity error

post #1 of 9
Thread Starter 
ok if i leave my computer idle for any amount of time i get this error
hardware malfunction
MMI parity check/memory parity error
the system has halted
weve replaced the ram and that still hasnt fixed it im kinda at a lossif any one knows what the hell to do let me know thanks i do apologize the computer is a dell XPS M1710
post #2 of 9
What laptop? Model? Hardware configuration? Software configuration?

Off-hand, I was getting these errors on my current laptop because I had Powermizer enabled. Turning this off completely fixed the problem.

Regards,

zakaluka2.
post #3 of 9
As the prior poster asked whats your complete configuration? It would help knowing more. Also, many people have replaced their RAM modules with others only to have errors with the new modules aswell. That said... where did you get the replacement modules from? Did Dell replace them? Almost all replacement modules shipped from Dell are refurbished from past systems. Did you buy them yourself elsewhere?

Personally I've always recommended buying the least amount of RAM with the system and replacing it with QUALITY RAM modules from a company like Crucial. Crucial has the undisputed highest Quality Control in the industry. Every single module is fully tested before they leave their factories. Something no other manufacturer can say. I've been using Crucial RAM modules for well over a decade and have never had an issue with their RAM.
post #4 of 9
i had this error on my xps m1710. resolved it by updating my gfx drivers to x-treme g mobileforce drivers.. find them here http://www.notebookforums.com/thread180603.html these are newer than the ones i used, haven't gotten around to updating them yet. i also updated the broadcom gigabit nic with these http://www.opendrivers.com/downloado...php?href=42444

i have never had the parity error since. so it wasnt my ram. hope this can help
post #5 of 9
Quote:
i had this error on my xps m1710. resolved it by updating my gfx drivers to x-treme g mobileforce drivers.. find them here http://www.notebookforums.com/thread180603.html these are newer than the ones i used, haven't gotten around to updating them yet. i also updated the broadcom gigabit nic with these http://www.opendrivers.com/downloado...php?href=42444 i have never had the parity error since. so it wasnt my ram. hope this can help
What driver must i use for the broadcom driver? i open the list of avaible dirvers on the file and there are a lot of them..
post #6 of 9
I'm having the same problem. I've reseated all cards with no effect. I went through my logs this morning and found out I was getting errors in my System log every time it locked up with an Event ID of 4226. I did a search on this and found this page: http://www.lvllord.de/?lang=en&url=4226patch/faq
I downloaded the patch and set my concurrent TCP connection attempts from 10 to 100. Everything seems to be working now. I'll update in a couple days if this solves the memory parity lockups.
post #7 of 9
You've missed the obvious step... Download and run Memtest86+ (http://www.memtest.org/) and run it. Do at least one full iteration, leave it running overnight for most accurate results. If you wake up in the morning and it reports zero problems, then your memory is fine. If it reports anything at all, your memory is bad and needs replacing.

This will tell you without a doubt if the memory is bad, independent of drivers (memtest runs as a boot CD).
post #8 of 9
That's what I did after reseating everything, Guspaz. Overnight 9-hour run with zero errors. Sorry I didn't mention it.
post #9 of 9
I've had 3 replacements from Dell all 3 have those BSOD. I've asked, look, find some info about those BSOD, many people are experience this error.

Well , based from personal experience, there's no way to fix for me its just luck. I 've had 3 BSODs on my 3rd replacement. then I haven't seen one till now. I should have let my computer running 24/7 cause sometimes I brought my laptop to school , so it's not fully run 24/7.

There're many solutions like other members suggested, such as reseat memory, run memtest, update drivers. blah blah... it's not gonna help though. This error is probably either motherboard or videocard error. Sometimes drivers did this too (???).

Well, I haven't had any BSODs for a week now I'm waiting for the next one.

I just firgure out that you should do a clean up of junks processes and programs runinng on ur computer.

After reformat windows.
- Run windows Updates , if ur're having problem with WGA, download the patches from some websites in stead (google).
- Install the following nescessary drivers , there's no need to install Dell's software crap.(quick set , touch pad etc)

- Video
- Audio
-Ethernet LAN (broadcom)
- modem
-Intel Wireless
- Bluetooth
-Card reader


Turn off those processes in ur computer by go to msconfig
- I turn off mostly Registry, windows firewall, windows updates, Messenger , help support.. mostly softwares that you'll not gonna use
- Some start up Items too.

- I found out that when I disable The INTEL WIRELESS SOFTWARE and use windows to config my wireless, it's connects so much faster when i start my computer. Also, it saves 3 processes or so. And no more BSOD since then, but I'm still testing if it works that way.

Run TuneXP, Regscrub after you reinstall everything back on computer for a final clean up.

This is a good thread clean up malicious programs in back ground http://forum.notebookreview.com/showthread.php?t=5787


I ran 3 process of Yahoo Widgets, 2 kaspersky antivirus, and windows blinds, wind log on , Cursor XP.. ,the total processes that are running is about 29 .. With TOshiba blue tooth, it takes up 4 more processes.

I'll give Dell a hard time if i have a another BSOD.
New Posts  All Forums:Forum Nav:
  Return Home
NotebookForums.com › Forums › Notebook Manufacturers › Dell Forums › Dell Home (Inspiron, XPS, Studio) › IM keep having a memory parity error