BSOD with bunch of errors

[zoheb]

Hi, I am new here, and I'm not too technical. So please bare with me......

My computer specs:
*Toshiba Satellite A105 Series
*Processor - Intel Pentium M Processor 760
*Processor Speed - 2.0 GHz, 2MB L2 cache, 533 MHz FSB
*Memory (RAM) - 1024 MB (2 x 512 MB)
*Operating System - Windows XP Home Edition SP2

--------------------------------------------------------------------------------------------------------


So basically my problem is that I got this BSOD today all of a sudden, after running my laptop for 4-5 hours. It showed the following error message.

=> 0x0000007F (0x00000008, 0x8004200, 0x00000000, 0x00000000)

I googled it and figured that this might be due to memory issues. So, I tried testing my memory using MemTest in Safe Mode (I obviously cannot run Windows in normal mode). As soon as the test reaches 26%-27% the computer restarts automatically and reaches the BSOD with a new error message. It stays there for about 30 seconds and restarts again with the BSOD back again with a different error message this time. And it keeps doing that constantly. and I keep getting new error messages everytime.. (unless I turn off the pc manually and start it back again, which takes me back to the BSOD with the error message I mentioned first....the "0x0000007F" message....[I'm still able to access Safe Mode though])

So, when it was restarting automatically over and over again during the MemTest.....these are all the error messages I was getting

=> NO_MORE_IRP_STACK_LOCATION
=> IRQL_NOT_LESS_OR_EQUAL
=> BOGUS_DRIVER
=> PAGE_FAULT_IN_NONPAGED_AREA
=> BAD_POOL_HEADER
=> MAXIMUM_WAIT_OBJECTS_EXCEEDED
=> SYSINTERNALS_GREAT_SITE
=> UNEXPECTED_KERNEL_MODE_TRAP
=> PANIC_STACK_SWITCH
=> KMODE_EXCEPTION_NOT_HANDLED

So, I turned off everything, took apart my laptop, and checked my memory (2 x 512 MB) manually by testing each of the memories individually, and they both seem to be working just fine. So, there are probably no issues with my memory.....and I don't use Norton or any other software from Symantec. .....and I also edited my Registry Key for the BAD_POOL_HEADER, but it didn't help at all, and I am clueless at the moment.

I really don't know what to do with all those error messages. Someone please help me out. I'm in pretty bad shape now, and I've been working on this for 4 hours now and already frustrated. Any kind of help would be highly appreciated. Thanks a lot!

 

[AlbertLionheart]

I think that to be sure you have good RAM you need to test the system with just one of the memory modules installed - try one after the other and if the problem exists with both of them then it is unlikely that the memory is the problem,
I have worked on Tosh laptops before and found motherboard and CPU related problems sich as this - it may have to go to a specialist for repair. If you are in the UK I can offer a contact for you,

 

[Darth_Terra1]

How long did you run Memtest on each stick, you should do 7 passes minimum which can take upto 3 hours for each stick, if each stick passes after that then it could be a problem with the second ram slot.

 

[zoheb]

I think that to be sure you have good RAM you need to test the system with just one of the memory modules installed - try one after the other and if the problem exists with both of them then it is unlikely that the memory is the problem,
I have worked on Tosh laptops before and found motherboard and CPU related problems sich as this - it may have to go to a specialist for repair. If you are in the UK I can offer a contact for you,

How long did you run Memtest on each stick, you should do 7 passes minimum which can take upto 3 hours for each stick, if each stick passes after that then it could be a problem with the second ram slot.

So, you guys mean I have to run Memtest on each memory module seperately? I never thought of that. I tested them manually by taking apart each of them at a time, but did not run memtest for each of them individually...... thanks for the advice. I'll try it out and let you guys know.

 

[zoheb]

ran the Memtest for each of the memory modules seperately, and no errors were found. Any other suggestions? Do you guys think that the hard disk might have crashed? If so, then is it possible to run Windows in safe mode with a crashed HD?

 

[AlbertLionheart]

From the symptoms I would have thought the HDD was OK but you may be right - boot into safe mode, open my computer and right click on the HDD - go to properties and select tools, Select check for errors and then tick both boxes - the system will then prompt for a restart - do it and let the test run at boot. At the very end (and for a few secs only) there is an error report - if you see any bad sectors, plan to get a new drive.

 

[woody1191]

I'll try to help a bit

=> 0x0000007F (0x00000008, 0x8004200, 0x00000000, 0x00000000)

That first parameter that I have coloured in Red indicates a Double Fault.

Here is a Extract from a Microsoft Article - http://support.microsoft.com/?kbid=137539&sd=RMVP
Double fault
A double fault occurs when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially, however there are several exceptions that cannot be handled serially and in this situation the processor signals a double fault. The two primary causes for this are hardware and kernel stack overflows. Hardware problems are usually related to CPU, RAM, or bus. Kernel stack overflows are almost always caused by faulty kernel-mode drivers.

I would suspect a CPU fault at this time without looking at the MiniDumps to confirm so try running Prime95 on the tests "Small FFT's" and "Large FFT's".
And post back with the results.

Prime95
32bit OS Version - http://files.extremeoverclocking.com/file.php?f=103
64bit OS Version - http://files.extremeoverclocking.com/file.php?f=205

I googled it and figured that this might be due to memory issues.

0x7F errors are caused by Hardware or Software most notably Memory Issues, so you are correct with that

 

[zoheb]

thanks for all the help, but my computer stopped running on safe mode as well.....now i am out of luck......any more ideas?

 

[AlbertLionheart]

I stick by my suggestion to make sure the HDD is OK before doing anything else - besides, it might be the cheapest option!

 

[woody1191]

I've changed my mind now you can't access the OS even in Safe Mode, I have to agree with AlbertLionheart now and say the HDD looks bad.

Try reformatting the HDD and installing the OS again otherwise you may be looking at getting a new HDD.

How old is the Laptop?
What HDD do you have?

 

[AlbertLionheart]

If you decide to reinstall windows, make sure you select the format option and when you get to the next box select the normal format - this will mark any bad sectors against future use and give the installation a fighting chance!

 

[Micromancer]

www enigmasoftware com/support/cnncomdailytop10-removal

Don't format, it's a pest not a hardware issue. I was running a scan with Malwarebyte's Anti-Malware in an attempt to remove Anti-Virus XP 2008 from a machine here at work. The BSOD's began after about 15 minutes and while it was sitting at the BSOD, I looked up the first one it displayed which was SYSINTERNALS_GREAT_SITE which I knew had to be bogus.

Then is starts a loop of restarting and displaying various other problems. After reading the link above - it mentioned it was a screensaver. So I moved my mouse and wouldn't you know the scan is still running. It hasn't crashed at all.

Your hardware is fine, you have a pest. Sure, a format will take care of it, but I would try removing the pest before going through all of that.

 

[AlbertLionheart]

You can always download the HDD maker's diagnostics and run them to check the condition of a hard drive.