Shibathedog Posted June 11, 2006 Posted June 11, 2006 i keep getting an error on my friends Dell (yeah....i know...) where the computer stops, turns blue and says something like System has haltedmemory parsity check failed im guessing his ram is flocked? he said he recently replaced the mobo so i dunno if thats it it seems to only do it if you let it sit there turned on and do nothing with it, it doesnt seem to do it if your actively using it Its also a fairly fresh install of XP, i did it myself a month or two ago and the system runs fine (other than halting) and is pretty clean
Shibathedog Posted June 11, 2006 Author Posted June 11, 2006 oh and another weird thing, if all 4 RAM bays arent being used, the computer just keeps beeping and refuses to boot or show anything onscreen
Weirdy Posted June 11, 2006 Posted June 11, 2006 ...he said he recently replaced the mobo so i dunno if thats it...He could be using the same RAM that was on the Dell mobo. Did you check to see if his RAM is supported by the mobo?
ken_cinder Posted June 11, 2006 Posted June 11, 2006 Memory Parity Check Error? Ewwww ECC memory in a desktop? Servers only dammit, WTF is Dell thinking putting ECC in a workstation in the first place? Probably only one module. Pull modules out one at a time till the error goes away. If needed in pairs, pull pairs out though it will take double the checks to figure out which module(s) are bad. I'd recommend to your friend, to purchase some NON parity RAM and sell the other stuff. It may also be possible for him to disable ECC in the bios. ECC = Error Checking and Correction. This checks the first bit of every page to the registers, and will correct any errors. If you have a bad module, you'll get errors that can cause serious problems. This isn't needed in a personal desktop, theres nothing "critical" about playing a video game, but in a server that does some serious business......there is. Dell sux balls btw, along with every other store bought POS.
Shibathedog Posted June 12, 2006 Author Posted June 12, 2006 yeah i know, he wants to sell it, but who would buy it? Yeah i tried pulling RAM, but as i said, unless all 4 bays are full, the computer refuses to boot, i tried pulling 1, 2, and 3 and it just beeps and refuses to start and show anything onscreen, ill try again when i get back from vacation though also hes already put a bunch of money into this computer, i dont think he wants to spend any more the BIOS thing, i havent tried, ill look for that, i did mess around in the BIOS alot and i dont remember seeing that but i could be wrong and yeah half the RAM is samsung and half is Dell so who knows, its all the same type though I also wanted to try and update his BIOS but his floppy drive is broken and he has no CD-Rs (and im out at the moment too >_< )
ken_cinder Posted June 12, 2006 Posted June 12, 2006 If you have a Win98 disc laying around, just put the bios update stuff in the C drive and boot the 98 disc to DOS.
Shibathedog Posted July 5, 2006 Author Posted July 5, 2006 Bad news The BIOS has no option to turn Error checking off Even worse news The BIOS reports it as NON-ECC RAM, So what do you suppose the problem is?
ken_cinder Posted July 5, 2006 Posted July 5, 2006 Parity error could also be a problem with incorrect voltage being applied to the DIMMs. Is this system overclocked in any way? Also given that the system refuses to even boot without all the DIMMs in place, it's possible theres damaged hardware on the motherboard itself. In your 2nd last post, you stated you tried pulling ram in slots 1, 2 and 3. If it's dual channel ram, you probably have to keep memory in combinations of 1+2/3+4 or 1+3/2+4, of equal sizing as well.
Shibathedog Posted July 7, 2006 Author Posted July 7, 2006 ahhh i forgot about trying the combinations 1+3 and 2+4, i did try everything else though, and it just does that beeping thing no its not overclocked, i dont think its a bad mobo because supposedley it was recently replaced. Im actually on it right now, it can stay up for anywhere between 15 minutes to 12 hours before crashing totally randomly (it used to not even boot anymore but after i made a new login it can boot, it seems to crash when the RAM is accessed alot, which would make sense)
Madman Posted July 8, 2006 Posted July 8, 2006 (edited) Test the memory itself, wether its bugged or not.Make a Selfboot CD with Memtest86, boot from CD and let memtest86 check the ramsticks. If everything worked so far, its prolly a bugged out stick. http://www.memtest86.com/ Edited July 8, 2006 by Madman
Shibathedog Posted July 8, 2006 Author Posted July 8, 2006 alright ill try that next, and its good that its a selfboot CD because the floppy drive is dead too (but who really cares)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now