Windows XP will not load in any mode. BSOD.

June 27, 2011 at 23:11:37
Specs: Windows Xp 3, Intel Quad Core Q6600 / 4gb Ram
Hi Guys,
My windows xp with sp3 suddenly wouldn't boot, I keep getting the blue screen, it will not even let me install windows, as soon as the cd finishes loading the drivers I get the blue screen. I dont't get a specific error I just get: stop: 0x0000007F (0x00000000, 0x00000000, 0x00000000, 0x00000000) I downloaded Ubuntu and had no problem with it and was able to backup my info. I need the computer work and not sure what the problem is. I have Kaspersky installed and updates so I kinda ruled out that the cause is virus, but you never know. My guess is that its hardware related, I just can't pinpoint what it is. I would greatly appreciate any help. Thanks so much.

See More: Windows XP will not load in any mode. BSOD.

Report •

#1
June 28, 2011 at 00:23:06
Sounds like a memory issue. Can you test the memory with MemTest? Also try and remove one stick if you have more than 1.

Google is your friend

www.google.com

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

Keyboard not present,press F1 to continue...


Report •

#2
June 28, 2011 at 12:16:17
Sometimes cleaning the RAM edge connectors with a pencil rubber can do the trick. Pop the sticks in and out a few times too, to clear any oxide off the sockets.


Report •

#3
June 28, 2011 at 15:46:19
Hi Guys,

First of all, thanks for the replies. I did some memory checking with ubuntu and it didn't throw any errors, I'm still running memTest86+ and its 66% complete without any issues. I still have to do the memory swapping and cleaning. I'll let you know what happens then.

Thanks


Report •

Related Solutions

#4
June 28, 2011 at 19:23:37
Hi Guys,

So far I tested the memory with memtest and ubuntu memory test, in both cases I didn't get errors. Later, I cleaned the memory and also tried one stick at a time, with no positive results, the computer is still behaving the same way. I wonder if this could be a motherboard issue? Any ideas.

Thanks


Report •

#5
June 29, 2011 at 09:06:15
Like you, I originally thought it was a hardware issue. Now that you've eliminated RAM and as Ubuntu was OK it seems it is Windows software.

Is there any file mentioned in that BSOD, if so it might help?

Do you use registry cleaners? The reason I ask is that they can get things wrong and cause issues. It rather looks like you are heading for a repair install but see what others think.


Report •

#6
June 29, 2011 at 09:10:57
The BSOD appears when the OP boots from the CD too. Anyway, it might be caused by some Windows driver/software. I found antivirus as one of possible causes.

Google is your friend

www.google.com

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

Keyboard not present,press F1 to continue...


Report •

#7
June 29, 2011 at 11:16:18
Re #6
Sorry, I missed the bit about the CD.

gamesbond
I assume you've seen this:
http://support.microsoft.com/kb/137539
Not that it helps too much. Seems strange for it to be a mobo issue if Ubuntu runs OK.

Do you get the BSOD if you start in Safe Mode too?

You might be able to disable the AV in Ubuntu by renaming its main .exe file to .old


Report •

#8
June 29, 2011 at 11:35:36
Thanks Derek,

There is no file mentioned in the BSOD and my main problem is that I can't run windows in any mode, not even install it! I get the screen whatever XP I try. a friend even lent me a windows live boot cd (windows that runs directly from cd without the need to install it) and its the same thing. I don't know how long should Ubuntu take to load but it feels it takes longer than windows XP. I'm now even considering upgrading my computer, may this is what I needed to make this decision.


Report •

#9
June 29, 2011 at 12:50:51
You might be able to disable the AV in Ubuntu by renaming its main .exe file to .old

Do this.

Google is your friend

www.google.com

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

Keyboard not present,press F1 to continue...


Report •

#10
July 5, 2011 at 10:22:26
Hi Guys,

After a few further tests I found out what the problem was and it was one of my secondary hard drives the one that was causing all the havoc. It seems the electronics on the hard drive are not working properly.


Report •

#11
July 5, 2011 at 11:04:14
Well, it usually is hardware (but not always). Glad to hear you fixed it and thanks for popping back to let us know what it was.

Report •

Ask Question