Repeated BSOD

I'm trying to troubleshoot a problem with a computer that repeatedly has stop errors. I've managed to clean the system of malware. The BSOD's vary the latest is the one that begins with 0X0000007F. This is an HP running Win XP home. It is probably three years old and has all of the original equipment, in other words no recent hardware has been added. I'm not well versed on getting or reading a dump log, so help would be greatly appreciated.

 

This is what MS has to say about it: General causes of "STOP 0x0000007F" errors. Based on that, try taking a stick or ram out and see if you still get the BSOD. If you do, then replace that one and remove another. Also need to make sure the ram sticks are securely seated.

Might also want to take a look at HOW TO: Debug Memory Dumps (Figure out what is causing a BSOD) by Adrynalyne.

You can also run "Memtest86+". I'd post a link but having trouble accessing the page at the moment.

 

Drat, didn't get back in time to edit. Anyway, Memtest86+.

 

Okay, finally got back to work here, ran Memtest86+ and found a bad stick of RAM. I pulled it and replaced it with a stick that tested good. I put the machine though some paces and got another blue screen. I've attached the dump.txt file.

 

Well I'm pretty sure this machine is going to live to fight another day. I've been doing one thing and another with it for the balance of the day since replacing the faulty stick of RAM and no more instances of stop screens. .

 

When you have/had bad ram, corrupted data may have been written to the hard drive. Just to be sure though, you should go to the web site of the manufacturer of your hard drive, download and run the diagnostic tools for the drive.

You should also run a chkdsk /r. This can be done one of two(2) ways.

Click on Start > Run, in the "open" box type cmd and click the "OK" button.

In the command console window type chkdsk /r(note the space between the word "chkdsk" and the "/r"). You will be told that it can't run now and would you like to schedule it for next boot, answer yes.

Or you can right click on "My Computer", from the context menu select "Properties", select the "Tools" tab.

In the "Error-checking" box, click on the "Check Now..." button. A "Check Disk Local Disk" window will open. In the "Check disk options" box, make sure there is a check mark in both of the check boxes;
"Automatically fix file system errors" and
"Scan for and attempt recovery of bad sectors"

Click the "Start" button.

Again you will be told that it can't run now and would you like to schedule it for the next boot, answer yes.

In either case, when you reboot the computer it will take time for the check disk operation to run.

 

Okay ran chkdsk /f and it came up clean. Then I downloaded Seatools form Seagate and ran the long diagnostic test; got a passing grade there as well. Things are looking good on this front. Thanks for the very detailed and concise answer, it gave me confidence that I'm on the right track.

 

Looks like I still have a concern, BSOD this morning.

 

Kirk,

The file referred to in your last dump file was IDSxpx86.sys.

This is a Norton anti-virus program file. Are you using Symantec's Norton for virus protection? If not, has Norton been uninstalled in your add/remove programs? If it has, then fun the Norton removal tool to finish the job;
http://www.majorgeeks.com/Norton_Removal_Tool_SymNRT_d4749.html

If you are using Norton, it seems to have a problem. :wave:wave:wave

 

I was fearful that Norton 360 would cause concerns for this system. This computer actually belongs to a school teacher in whose classroom I volunteer as a tutor. I fiddled with it off and on all weekend, as you can see from the posts. I got it back to her yesterday as she needs it for her school work. She purchased Norton 360 about a week ago. I had her send me the latest dump as a email attatchment and then posted it here. I assume I should tell her to check with Norton Support since she owns the software and is stuck with it. Or does someone have an alternate solution?

 

And what antivirus did she have previously? Many, if not most, require a special uninstaller to fully erase it.

 

I understand exactly what you are saying. I don't know what she was doing for Antivirus before Norton 360, (didn't think to ask) but as for firewalls and other security she has stuff as recomended by Major Geeks to help prevent infections. I'll get back with her and ask what she was using before Norton so I can be certain it was unistalled the right way. I may have to get my hands on the computer again in order to get the other instructions completed. One of her sons is pretty handy with computers but he is not around and I think she would be intimidated with the instructions regarding Norton repair.

 

I've got this computer again. The owner said she got a message saying that Norton has some kind of problem and gave a solution to download a patch. She formerly used Panda anti-virus and tried to uninstall it by using add/remove programs, (the tech at Staples told her she could do it that way) but I assume that is not sufficient. Would it be a good idea to make sure Panda is completely removed before I do the the steps that were previously suggested?

 

Okay, ran the Panda uninstall program, she had tried to unistall Norton, but hadn't used the removal tool so it was still haging around. I ran the removal tool and scoured the registry with CCleaner. So, I should now unistall the other security software? This unit has Superantispyware, Malware Bytes and Spywareblaster. I didn't know there was a problem with keeping these programs, but if there is I'll blow them out.

 

I took out Norton and all of the other stuff. No BSOD for a day and night. Put Norton back, no BSOD of a day and night. Gave computer back to my teacher friend, she called this morning with BSOD. I had her send me the dump.txt.

 

From what I've stumbled across so far, this looks like it is a ram timing problem. While Norton's isn't at fault here, it very well could be aggravating the issue as might any program that pushes the system enough. Maybe start a new thread in the Hardware forum with a link to this thread to give a history?

 

Alright, I've considered asking her to uninstall Norton once again and perhaps install a free program temporarily to see if that makes a difference. But she paid for the Norton 360 so eventually she will need to reinstall it and another Anti virus might just cause more problems. Trying the hardware forum is a good idea, but I'm not sure how to do a link back to this one. Can you tell me how that works?

 

The simplest way:

While viewing this thread, right click on the address bar of your browser. The url should become highlighted and a context menu should pop up.

Select Copy from the context menu.

Go to the Hardware forum and start your new thread explaining your problem.

While still in the editor box(before you Submit your post), place the cursor at the position where you want the link to be placed in your post, right click and select Paste from the context menu.

The link you post should look like: http://forums.majorgeeks.com/showthread.php?t=214038
which is the link to this thread.

If you look in your address bar at this moment, that is what you should see.

As far as removing Norton's, don't think that would solve the problem. Think it's just causing the real problem to manifest itself. From the bits and pieces I've picked up and what little sense I could make of the dump, it looks like a timing problem, which is over my head(like everything else). There was also a mention of possible file corruption and a slim chance of rootkits, but don't think that's the problem in this case. Probably has more to do with that replacement stick of ram.

Suppose it could be a video card problem or a video card driver problem too.

When you start your new thread, try to include as much information as you can about the machine.

Make, model, how much ram, which version of Windows and service pack(i.e. XP Home Sp?).

Don't know if this would help or not but you could try going to Crucial.com and scan the computer for the type of ram it can use and then compare that to the replacement stick you used.