sporadic blue screen shutdown

BDrums1971 · Jun 1, 2010

Hi, I have had an on/off problem with intermittent blue screen of death problems. It seems like every 2 to 3 weeks, sometime during the night, this will happen. I then chkdsk, run fresh anti spy, and everything seems fine for another 2 to 3 weeks or so. Very frustrating. This has been happening for over 6 months, and I am tired of it, as it just happened yesterday. Question...the next time this happens, can I copy the error file to you to see if you can help me with this? And secondly, HOW and where can I find the error log file. Thanks so much for any help!! Oh, I'm running Win XP.

TimW · Jun 1, 2010

Right click My Comuter / properties / Advanced / under startup and recovery, uncheck the box to restart on errors. That will give you the error message the next time you have a BSOD.

BDrums1971 · Jun 6, 2010

Well, it happened again. Here is the Blue screen info. IRQL_NOT_LESS_OR_EQUAL. Then down below: Technical Information: STOP: 0x0000000A (0x00000000, 0x00000002, 0x00000000, 0x8051B8C2). Does this mean anything to you? Please let me know if you need more data, and thanks in advance for your help!

plodr · Jun 6, 2010

Stop error 0A
http://www.aumha.org/a/stop.htm
scroll down until you get to the list of links.
there are 15 links and I've gone through the ones that possibly could apply and have not found anything useful. 1st link gives me a 404, 2nd and 4th links about upgrading to XP, 3rd link does not list XP in the list of Oses it applies to.
Even the top link to an MSDN article led me to a page that said Content Removed.

BDrums1971 · Jun 7, 2010

plodr said: ↑

Stop error 0A
http://www.aumha.org/a/stop.htm
scroll down until you get to the list of links.
there are 15 links and I've gone through the ones that possibly could apply and have not found anything useful. 1st link gives me a 404, 2nd and 4th links about upgrading to XP, 3rd link does not list XP in the list of Oses it applies to.
Even the top link to an MSDN article led me to a page that said Content Removed.
Click to expand...

plodr, thanks so much for taking the time to check this out for me. Too bad you couldn't come up with something. If anyone else has any ideas, I would appreciate the help. Thanks!

plodr · Jun 7, 2010

I searched a bit more and found this:
Causes : This error occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software.
Solution : Look for other hardware issues. Remove any newly installed Hardware. Remove all adapters and disconnect all hardware devices that are not required to start the computer.
Perform a Driver Rollback in case a driver has been updated for a particular component.
Examine third-party software or drivers.
Use the Last Known Good configuration.
Use the Windows XP System Restore.
Repair the Windows XP installation.

I doubt it is hardware because the BSOD would occur more often than every 2 to 3 weeks. It seems like something is getting corrupted.
List the software you have checking for updates, aside from antivirus (that would update oftener than every 2 - 3 weeks) and maybe we can see if some software checking for an update over night might be causing the problem.

BDrums1971 · Jun 9, 2010

Plodr, thanks again for your help. I have had several BSOD shutdowns in the last few days, a couple of them during the day. I get a new error message every time. A couple of the new error messages are 0x00000008E, 0x00000001A, and 0x00000007E (with a memory_management notification). Obviously, there is some hardware/software problems. Do you have any suggestion as to where to start to track down the problem? thanks again for your help!

plodr · Jun 9, 2010

random BSOD with errors all over the place, usually is caused by a stick of RAM going bad.

If you have two sticks and do not need them installed in pairs, remove one of the sticks and work with computer. It will be slower with less RAM but if you get no errors, then you know the stick you have removed is the bad one.
If you do get errors, then swap sticks and see if the computer works with the stick you just put in.

An optional method: run a memory test like this
http://majorgeeks.com/Memtest86_d4226.html
if you get any error, stop the test and replace the stick of RAM.

itmortiz · Jun 9, 2010

It maybe is a memory problem, my two solutions for you.

1. Shutdown CPU, Extract your RAM modules, don't touch the golden pins, clean golden pins with a Rubber Eraser, blow slots don't touch there if you don't know how.

Put back your RAM modules.

2.Try using just one module of RAM (if you have two) and look if the problem persist change each other and wait if the problem appears (to test each module separated one by one)

Good luck tell us results!

PopaSmerf · Jun 10, 2010

I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to c:\windows\minidump and copy the last 2 or 3 minidump files to that folder. They are numbered by date.
3 > close the folder and right click on it and select "Send to (folder name).zip"
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.

This might point us to a 3rd party driver causing the error, if one exists for it.

Log in or Sign up

sporadic blue screen shutdown

BDrums1971 Private E-2

TimW MajorGeeks Administrator - Jedi Malware Expert Staff Member

BDrums1971 Private E-2

plodr MajorGeek Super Extraordinaire Moderator Staff Member

BDrums1971 Private E-2

plodr MajorGeek Super Extraordinaire Moderator Staff Member

BDrums1971 Private E-2

plodr MajorGeek Super Extraordinaire Moderator Staff Member

itmortiz Corporal

PopaSmerf Private E-2