Solved Windows 7 won't boot/come on

[dazzlenet]

I have a Windows Repair Disk and I have tried system restore, system repair, and every other option several times. When I run DISKPART > list volume, it shows all my drives with the status being healthy. I did get one message that I was missing a driver, but I can't find where I wrote it down. I do remember that it had Locale ID: 1033 at the bottom.

I have also run chkdsk and there are no problems. The message at the bottom is:
Failed to transfer logged messages to the event log with status 50.

 

[cottonball]

Please try the following:

You may want to print these instructions so you can have access to them.
Also, you may want to read them once before you apply them.

Please plug in a USB pen drive into a working computer.

Go to the Farbar Recovery Scan Tool Download
Select the download that applies to your system.
Save the program to the >> USB pen drive.
Remove USB pen drive when done.

Now, go to the problem computer.
Plug in the USB pen drive which has FRST.

Start the computer, and tap the F8 key until you get to the Advanced Boot Options
Use the arrow keys to select the Repair your computer menu item

From there...
Select your language settings, and click: Next
Select your User account and click: OK (If you did not set a password, leave blank.)

On the System Recovery Options you get the following options:
Startup Repair
System Restore
Windows Complete PC Restore
Windows Memory Diagnostic Tool
Scan your computer's memory for errors
Command Prompt

Select: Command Prompt

In the Command Prompt window, at the blinking cursor type notepad and press: Enter
In Notepad, under the File menu select: Open
Double-click the Computer icon on the left.
Find the pen drive letter, remember what letter it is, click on it, and press: Open
Close out of Notepad.

Click the Command Prompt window
Type x:\frst.exe, or x:\frst64.exe (depending on your system 32-bit or 64-bit), and press: Enter
Note: Replace the drive letter x with the drive letter of your pen drive!

FRST starts, and prepares to run. Follow the prompts.
Click Yes to the Disclaimer.

Press the Scan button.

The scan runs, and, the program saves the FRST.txt, on the pen drive.

When done, click the Command Prompt window, type exit, and press: Enter

Back at the System Recovery Options, press: Shutdown
Remove the USB pen drive.

:ar: Plug the USB pen drive in the working computer, and please provide the FRST.txt in your reply.

 

[dazzlenet]

I hope I attached the file correctly.

 

[cottonball]

Please do the following:

Open notepad (Start > All Programs > Accessories > Notepad)
Copy the entire contents of the code box below (Do not copy the word 'code');
Save it on the flash drive that has FRST and name it: fixlist.txt

start
HKLM-x32\...\Runonce: [Del20710677] - cmd.exe /Q /D /c del "C:\Users\Buddy\AppData\Local\Temp\0.del" [x]
HKU\Buddy\...\RunOnce: [Del20710677] - cmd.exe /Q /D /c del "C:\Users\Buddy\AppData\Local\Temp\0.del"
C:\Users\Buddy\cnmss Canon MG3100 series Printer (Local).dll
LastRegBack: 2013-10-21 00:43
end

NOTICE: This script is written specifically for this computer.
Running this on another computer may cause damage to the Operating System.

Now, please enter System Recovery Options and select the Command Prompt as done before.
Run FRST64, and press the Fix button, just once, and wait.
The tool creates a report on the pendrive called: Fixlog.txt

:ar: Please post the Fixlog.txt in your reply.

 

[dazzlenet]

File Attached

 

[cottonball]

The big question is, did the computer boot into Windows?

 

[cottonball]

The big question is, did the computer boot into Windows?

Do reboot, if you haven't done so.

 

[dazzlenet]

It still goes to the same screen ...repair, etc. Should I go in and change it to boot from the hard first and not the CD Drive? I don't think this will help, but I can try it.

Changed it to boot from hard drive & it goes to Windows Error Recovery screen as usual.

 

[dazzlenet]

The problem details are:

Problem Signature 01 & 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21200384
05: AutoFailover
06: 18
07: BadDriver
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

 

[cottonball]

Saw where someone went into the BIOS and switched the HDD controller from AHCI to IDE to solve this problem.

However, this issue is not within my area of knowledge or comfort zone, since I deal with malware.

 

[cottonball]

dazzlenet,

Sometimes the inability to know/understand why this machine will not boot normally after the fixes might be caused by too much staggerweed.

The action undertaken here was meant to rule out malware as a cause of the issue, and reconstruct the Registry, since damaged Registry files, malware, and corrupted data, can result in Windows Error Reporting.

Attempts to manually repair the Windows 7 Boot Loader (bootrec /fixmbr and bootrec /fixboot) have failed in every case seen so far with this problem.

Root cause found: Boot status indicates that the OS bo - there is nothing else after the "bo" - just the Close button.

It should read:
Root cause found: Boot status indicates that the OS booted successfully.

It may or may not help to see the Addition.txt that was produced when you initially ran FRST. It identifies application and system errors.

If not available on you pen drive, run FRST again, check Addition.txt, and post both reports (FRST.txt and Addition.txt) in your reply.

Also, perhaps someone with expertise in analyzing dump files or the like will jump in to assist.

 

[x BlueRobot]

The problem details are:

Problem Signature 01 & 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21200384
05: AutoFailover
06: 18
07: BadDriver
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

The problem signature 7 indicates a bad driver, most likely the missing driver which you said about.

The Locale ID simply shows your timezone and location settings for your computer.

Have you tried booting into Command Prompt from the Recovery disc, and then entering this command:

SFC /SCANNOW

 

[cottonball]

Thanks, x BlueRobot!

That is a good option.


@dazzlenet:
Another thought...

Tap on F8 until the Advanced Boot Options Menu appears.

Is there an option to Disable Driver Signature Enforcement ?

If so, please select, and allow the computer to start.
You may need to restart a second time...

 

[dazzlenet]

Thanks, x BlueRobot!

That is a good option.


@dazzlenet:
Another thought...

Tap on F8 until the Advanced Boot Options Menu appears.

Is there an option to Disable Driver Signature Enforcement ?

If so, please select, and allow the computer to start.
You may need to restart a second time...

Yes, I tried starting it twice this way and it still goes to Windows Error Recovery Screen

 

[dazzlenet]

dazzlenet,

Sometimes the inability to know/understand why this machine will not boot normally after the fixes might be caused by too much staggerweed.

The action undertaken here was meant to rule out malware as a cause of the issue, and reconstruct the Registry, since damaged Registry files, malware, and corrupted data, can result in Windows Error Reporting.

Attempts to manually repair the Windows 7 Boot Loader (bootrec /fixmbr and bootrec /fixboot) have failed in every case seen so far with this problem.

Root cause found: Boot status indicates that the OS bo - there is nothing else after the "bo" - just the Close button.

It should read:
Root cause found: Boot status indicates that the OS booted successfully.

It may or may not help to see the Addition.txt that was produced when you initially ran FRST. It identifies application and system errors.

If not available on you pen drive, run FRST again, check Addition.txt, and post both reports (FRST.txt and Addition.txt) in your reply.

Also, perhaps someone with expertise in analyzing dump files or the like will jump in to assist.

At this point, under Startup Repair, it reads:

Root cause found:
Startup Repair has tried several times but still cannot determine the cause of the problem

I will run FRST again and see if it helps.

 

[dazzlenet]

Thanks for all you help. I have worked on this computer for days....running everything so many times that I have decided to give up and take it to a computer store to see if they can repair it.

 

[cottonball]

Did you try SFC /SCANNOW also?

Most cases with this issue ended up reinstalling the OS.

 

[dazzlenet]

Yes, but it won't scan b/c of message that there is a repair pending.

It is going thru system image restore right now, which I have tried before. I have an old computer that hasn't been run in years. Wonder if I could take the hard drive out of it and get my data off this computer I'm trying to repair?

 

[x BlueRobot]

The missing driver is going to be a Windows driver, you could try booting with a Linux LiveCD and gathering your data, and then performing a clean install - http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

 

[cottonball]

Anothe thought...

Get to the Command Prompt, and use the following command:

dism.exe /image:C:\ /cleanup-image /revertpendingactions

Press: Enter


You should see something like:
Reverting pending actions from the image.... The operation completed.
Any revert of pending actions will be attempted after reboot.

Reboot the computer.

Any luck?

If no luck, would follow X BlueRobot's suggestion, and save yourself a hefty repair bill...