[Randy22]

Hello, I have been getting nonstop recovery messages since startup heres a couple of them:

BCCode : 3b BCP1 : 00000000C0000005 BCP2 : FFFFF80001298026
BCP3 : FFFFFADF90518CD0 BCP4 : 0000000000000000 OSVer : 5_2_3790
SP : 2_0 Product : 256_1

C:\DOCUME~1\Destanie\LOCALS~1\Temp\WER90d2.dir00\Mini021911-02.dmp
C:\DOCUME~1\Destanie\LOCALS~1\Temp\WER90d2.dir00\sysdata.xml


BCCode : 109 BCP1 : A3A03A382B23C8CC BCP2 : B3B746BE7DA08528
BCP3 : FFFFF8000110F530 BCP4 : 0000000000000001 OSVer : 5_2_3790
SP : 2_0 Product : 256_1

C:\DOCUME~1\Destanie\LOCALS~1\Temp\WER0a94.dir00\Mini022011-01.dmp
C:\DOCUME~1\Destanie\LOCALS~1\Temp\WER0a94.dir00\sysdata.xml

BCCode : 3b BCP1 : 00000000C0000005 BCP2 : FFFFF97FFD7F517D
BCP3 : FFFFFADF90434610 BCP4 : 0000000000000000 OSVer : 5_2_3790
SP : 2_0 Product : 256_1

C:\DOCUME~1\Destanie\LOCALS~1\Temp\WERa320.dir00\Mini022011-02.dmp
C:\DOCUME~1\Destanie\LOCALS~1\Temp\WERa320.dir00\sysdata.xml

BCCode : 1a BCP1 : 0000000000000782 BCP2 : FFFFFADF7EF462C0
BCP3 : FFFFF98106E00000 BCP4 : FFFFFA80002AB3E0 OSVer : 5_2_3790
SP : 2_0 Product : 256_1

C:\DOCUME~1\Destanie\LOCALS~1\Temp\WERfa65.dir00\Mini022011-03.dmp
C:\DOCUME~1\Destanie\LOCALS~1\Temp\WERfa65.dir00\sysdata.xml


BCCode : d1 BCP1 : 0000000000003000 BCP2 : 0000000000000002
BCP3 : 0000000000000000 BCP4 : FFFFFADF80B9AE02 OSVer : 5_2_3790
SP : 2_0 Product : 256_1


C:\DOCUME~1\Destanie\LOCALS~1\Temp\WER5e4f.dir00\Mini022011-04.dmp
C:\DOCUME~1\Destanie\LOCALS~1\Temp\WER5e4f.dir00\sysdata.xml


My system specs are:
Windows XP x64 service pack 2
AMD athlon dual core 5200+ 2.6 GHZ
Nvidia 260 gtx
4 GB ram
nforce 570 SLI motherboard

I assumed that it was a glitch and that it would probably be endless so i just clicked dont send after these five. but it ended after about five more reports for a total of ten

Im not sure what is causing this but my computer shut off for no apparent reason the other day and my fiance was unable to turn it or my monitor back on. My only guess is that the power bar was going although i could get the computer to run on it at a later time. I have now changed the power bar to a high quality(I think) monster power brand bar and its running fine for now.

I should also add on startup since the abrupt shutdown it always says "cmos checksum error" and i am required to press F1 to continue.

Let me know what to do thanks!!ray:

 

[cluberti]

Your system is crashing, and should be generating .dmp files signifying each crash on the hard disk. You might want to post this in the section for these sorts of problems, here.

Given that these are all over the board though, it would be worth checking your hardware, especially RAM, before doing too much more with your machine. The more random the BSOD codes, the more likely hardware is at play, in most situations. The most likely hardware to die a slow, horrible death in a PC over time after the HDD is RAM :wink:, so checking that out first before investigating software is a good first step.

 

[Randy22]

So now it won't boot now. whenever I turn it on it just beeps in long repeating beeps with 3 second pauses in between.

 

[cluberti]

The nForce 570 is almost always paired with an Award BIOS (given it's an nForce chipset and AMD processor), and the Award BIOS beep codes indicate endlessly looping beeps are the motherboard indicating failed RAM.

Like I said before, what's most likely to fail after a time in a PC after the HDD? RAM. Bugcheck codes all over the place and not consistent, happening "at random" (especially after the system has worked fine for a time)? Bad RAM.

Sorry about your bad luck, but at least your situation is not a nebulous one - you need to replace your RAM to get your system running right again. Beware though - bad power (if the PSU is not of superior quality) could mean other parts of your PC are now worse for wear. Keep this in the back of your mind if other odd things start happening in the future...

 

[Randy22]

My bios is Phoenix actually which does not seem to have a beep code that matches what I'm hearing.

I should say my psu is a relatively new, maybe 6month old 850 watt corsair and my computer used to run on 650 so I think it's ok.

 

[wadmancpu]

remove all your cards and all your ram but 1 stick and see if you get it to boot. If not, swap your stick out for one of the other ones. If its your ram its not likely to be all of it. You need to do some component swapping to pin down the actual cause. Strip it down to bare bones first and then start adding components back if you get it to boot. Does sound like ram though.

 

[spunk.funk]

Boot off of the XP CD and get to the Recovery Console and type chkdsk /R and hit enter. The check disk utility will try and fix any errors.

 

[mcorton]

If you're getting 3 beeps it means a RAM problem.

 

[Randy22]

It was a long beep approximately 2 seconds with about a 3 second pause before the next beep then this repeated indefinitely.

 

[spunk.funk]

Shut down the computer and make sure the RAM sticks are seated properly. If you still have problems pull all but one stick out. Switch them around.

 

[Randy22]

When I just turned it on right now w/ all rams in place it started up fine. I think this might be like the earlier poster said and that the ram is nearing death.

 

[Randy22]

Since for the moment it is booting is there any way to determine if the ram is failing without the trial and error method and If so which chip(s)?

 

[spunk.funk]

download the ISO image for memtest and burn it to a CD using IMGBurn. Boot off of the newly created CD and run the tests with one stick of RAM in at a time. If you see red then that stick is bad.

 

[Randy22]

Spunkfunk, I was having problems with BSOD awhile ago. You actually responded to my thread "BSOD XP 64" about 2-3 weeks ago. I ran memtest back then as instructed and no problems came up but I will try it with the individual chips in place. One thing I never did was run my HDD tool as I didnt have an old school mouse/keyboard and the menu in the seatools hdd tool wouldnt work with the usb keyboard/mouse I have. I just found a ps/2 styles mouse so I will after backing up my old files using ubuntu live cd attempt to run the tool. I should also say that since running chkdsk /r twice I haven't had any BSOD

 

[spunk.funk]

That might have fixed it. You certainly can run Seatools to put your mind at ease, but I think your problems were more about correct drivers then anything else.

 

[Randy22]

I was reading about memtest and found that there are 11 possible tests that can be performed. Mine is only performing 8 by default should this be sufficient? Either way I can't change it right now since my USB keyboard doesn't work in memtest.

 

[Randy22]

So upon inserting my fourth ram chip for memtesting I booted and it beeped three times in a row and then didn't boot(comp running but no video). This happened no matter how many times j manually restarted(6). The first beep was slightly longer then the second two but they were all in rapid succession and non repeating. I don't understand the beep code notation so I'm not even going to attempt to determine what what means. Nevertheless I'm certain that that ram chip is junk.

 

[Randy22]

I just decided to try them all out again one by one and it's doing it for everyone now. I couldn't find a match in phoenix bios beep codes but my beeps did match that of the award bios codes 1 long 2 short indicating a possible problem with the video card.

 

[Randy22]

I reseated the video card and it's booting normally now. Phew!

 

[Randy22]

Okay so I ran memtest on my fourth chip for two passes without any errors. I then reinserted my other three chips and attempted startup. Beep...beep...beep... I knew it was running on all the individual chips so I decided to try removing them one by one while keeping three in at a time. After removing my fourth chip everything started up fine so I reinserted to double check... Same beeping so I took it out again and it starts up fine. Looks like my bad ram was the fourth chip after all. I hope this solves the odd problems I've been having lately. Thanks a lot for everyone's help I've learned much about troubleshooting from this experience.