Skip to comments.Blue Screen of Death on WinXP computer (img) -- Is it a terminal disease? (vanity)
Posted on 02/25/2011 10:50:08 AM PST by webschooner
We have two desktops in our household. Just a couple of weeks ago, my wife's WinXP desktop, at that time just under 3 years old (not on warranty), started going blue screen every day at least once, always when she was using it, but you could always reboot it. I took a pic of the BSOD and emailed it to a computer service guy friend, and he said that machine was on the way out, and not worth repairing. We turned off the machine, bought a new computer, then I transferred my wife's data to the new machine.
I wanted to see what her old machine was up to, so I then kept it booted up and web surfed on it regularly. It didn't blue screen even once, but after a few days, it went belly up -- monitor went dark, and I checked the monitor -- monitor is fine, so the computer is a dead soldier. Anyway, issue is solved, wife has new computer, all is well.
Below is pic of BSOD of wife's computer before it passed away, may it rest in peace:
That is just background history which I thought possibly might help with analysis of the issue at hand with my desktop. My desktop, also a Dell WinXP machine, just over 3 years old, has been blue screening off and on for awhile, but nowhere near as frequently as my wife's machine was. When it does, mine only blue screens overnight, when it is idle (I usually leave it on), not when I am using it during the day. It blue screened say once a week for about three weeks, then worked fine for about a month, then last night, blue screened again (I can always reboot after a blue screen). I presume most of the BSOD message is kind of boiler plate, but regarding the error message specific to the machine and the incident -- I notice the message for my machine is very similar to the message for my wife's machine, although some of the numbers are a little bit different.
Pic of BSOD on my machine last night:
My question is this to Windows tech savvy people: does it look like my machine is on the way out and not worth fixing as was my wife's machine? For years I have purchased our computers refurbished on Dell Outlet with same warranty as new. My wife's new replacement machine I bought a week ago was $350 delivered (sans monitor), well equipped, with a dual core Intel chip. Therefore I won't put a lot of money into repairs. Usually we run our machines 5-6 years and upgrade, and they are still running fine at that time, but trouble happened to hit early this time. I don't buy warranties on desktops beyond the 1 year factory warranty that comes with them, so no recourse there.
Any advice on what this specific BSOD (2nd pic) on my machine means would be appreciated. Apple guys who are thinking of telling me to buy a Mac, or Linux guys who want to tell me to load Linux, thanks anyway for the advice, but you will all be ignored by myself. I'm not interested, just as you're not interested in the OS I use. To each his own OS.
Thanks in advance.
Thanks. That Windows Debugger looks worthwhile.
I’ve got to run an errand now. Back in awhile and will respond to additional posts then. Thanks to all who have posted so far. Much appreciated!
Your motherboard or CPU is fried.
Memory Chips are very sensitive to static electricity.
Unless you are properly ESD grounded, you may destroy your RAM. About the only physical thing you can see, anyway; is if the RAM sticks are properly installed.
Run chkdsk /p from command prompt. If you see errors, run chkdsk /r. This takes a while to run since it is seeking and repairing problems with hard drive concurrently. As it happens I fixed grandaughters BSOD problem last night.
I am reasonably technically savvy but don’t know how to access the system event log, but I’m sure I can research it and figure it out. Thanks much!
Allright thanks, I’ll try that too.
Restart your computer and press the F8 on start. If you hear a clicking sound, release the key and immediately press it down again.
You'll get to a screen with some options. pick the one that says command prompt.
Type in the following command "chkdsk /r" (minus the quotes and a space between the word and the slash) and then hit the return key. You may have to restart to have the process begin.
This will check your drive and fix any problems and recover any data. If this doesn't work, we are on to other tests.
Allright thanks. I cleaned out the box, reset the Ram, and pushed all the connections in. Now I’m running Disk Defragmenter. As soon as that is finished, I’ll run Chkdsk.
Appreciate the help!
It was my mouse that caused my problem.
“It is a Pentium 3 from 2000 that still works great.”
As an aside, I found the manual for my MOTU 2408mk3 sound card and was looking thru it. It said that an 800mkhz Pentium processor would do but a Pentium III would be better.(Sigh.) My rig is 6 yrs old but I upgrade when it dies and I am out of choices. And since I have a spare MOBO with Processor, that won’t be for a while!
I think this issue can be caused by the 2011 free version of AVG...
I doubt it. Mine occurred prior to that. No problems since.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.