BSOD loop at BOOT, useless laptop

sebastianrhrh · 14 Jan 2011

DONE. Im writing this from Ubuntu on my Gateway. I thought the BSOD will appear again, but thankfully it didnt. So right now im backin up all of music and files. IM SAVED! Thanks a lot!

So backin up is done. Now, I just realised that early in the morning I entered the Recovery Options and clicked on the Gateway Recovery Options and then I went on one that said, it would get back to factory settings without erasing any of my documents. I completely forgot about that. So what happened was it finished backin up all the documents and then it started to reinstall windows. At some point it said it needed to restart and automatically did that. Then boot up and the screen showed that windows was installing services, something like that. And then, it said that services couldnt be configured to THIS MACHINE. After that, it rebooted and it said: windows is initialising services and then a popup window apperaed saying windows couldnt install and that it will reboot. I clicked OK, and then it said windows will continue installing after it reboots. So it turned off and on back again, and the same process was repeated. Windows cant install, windows will continue installing after reboot, and infinite loop.

Thing is, while im here in Ubuntu, I can see all of my HDD files, and it doesnt seem like anything has uninstalled, all my programs are still there, all the windows files are still there, so im confused. IDEA: ill search for that famous minidump folder!

sebastianrhrh · 14 Jan 2011

I just read your last post... I cant enter windows, BSOD screen shows right after XP Loading Logo, the same as with Windows 7. Well, not anymore cause apparently its uninstalled.

But i found the minidump folder, and theres only one file in it. Ill attach it.

Jonathan_King · 14 Jan 2011

Either the problem is with hardware, or some nasty virus hiding in the MBR.

Run those bootrec commands I posted earlier; hopefully that will cure any MBR virus.

For hardware tests, start with RAM. Run Memtest86, according to this guide: RAM - Test with Memtest86+

A hard drive test would be a good idea too; use the DOS version of SeaTools.

...Summary of the dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Jan 13 19:40:06.643 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:48.406
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_36B1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xF4_36B1_IMAGE_wininit.exe
SystemManufacturer = Gateway
SystemProductName = NV55C
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

sebastianrhrh · 14 Jan 2011

I'm sorry jonathan, id didnt understand well your instructions.
1. What is the MBR?
2. Where should I run those bootrec commands? In Ubuntu or from the Recovery CD?
3. Where should I run the RAM test and HDD test? In Ubuntu? Or where?

Thanks for your help.

Jonathan_King · 14 Jan 2011

MBR - Master Boot Record. Master boot record - Wikipedia, the free encyclopedia

Run the bootrec commands from the recovery CD.

The RAM and HDD tests are in their own custom environment. Download them, burn them to their CDs or USB drive, boot from it, and you'll enter a mini-OS. It is all explained in their respective links, if you have any questions.

sebastianrhrh · 14 Jan 2011

bootrec /fixboot
operation completed succesfully

bootrec /fixmbr
operation completed succesfully

bootrec /rebuildbcd
scanning all disks for windows installations
may take a while...

succesfully scanned windows installations.
total identified windows installations: 0 >>>>>>>> 0 INSTALATIONS? IS THIS OK?
operation completed succesfully.

First part done.

Jonathan_King · 14 Jan 2011

Can you boot into Windows? If not, mark the Windows 7 partition as active, and then startup repair on it:

Partition - Mark as Active

sebastianrhrh · 14 Jan 2011

No, I cant. It says the same thing:

Windows cant install, to install reboot. When I reboot, same message. Right now I'm checkin the HDD with SeaTools for DOS "Long Test". I read the post about memtest, and apparently it takes a lot of time. So I was thinking, if this test is about checkin RAM, couldnt I just swap RAM with my previous laptop and try? Wouldnt that determine if the problem is RAM?

Thanks.

P.D.: Formatting the HDD and reinstalling Windows would solve the problem? I have all of my files backed up so I was guesing...

Jonathan_King · 14 Jan 2011

If you have everything backed up, a clean install is a good idea. Don't just format though, as that may leave traces of possible viruses behind. In your case, I'll have to recommend a complete wipe.

Boot to a command prompt, and enter the following:

Code:

diskpart
list disk
select disk n // where n is the number of your Windows drive
clean all

When that is finished, install Windows again.

If that does not solve the problem, send the computer back; it is a hardware problem.

sebastianrhrh · 14 Jan 2011

Illl try to do that... thing is... i dont have a copy of windows. The laptop came like that, wit Windows Home Basic x64. So should I send it back now? Should say Ive run all of these tests?

Thanks for all your time Jonathan.