Computer freezes on "Starting Windows" at bootup

iamc3k · 21 Jun 2015

Folks,

I just started the computer, and as the title says, it freezes at "Starting Windows".

I cannot get it to the boot menu (to select "Safe Mode"). My options during bootup (by pressing the reset switch) are "Delete" or "F8". F8 gives me a boot menu which means I can choose which device to use for booting (SSD, HD, or bluray. The OS was installed on the SSD about 6 months ago with the HD disconnected.)

Using Delete just gets me to the BIOS screen.

Reset switch offers those two options, looks normal, then the MS "flag" icon appears from glowing specks, and "Starting Windows" appears.

My last /scannow scan was about 2 months ago.

I am at a loss as to how to repair/diagnose what to do next?

Any thoughts?

Thanks,
Ken

iamc3k · 21 Jun 2015

I've found that repeatedly pressing the reset switch gives me two options to boot: "Start up repair" or "Windows Normally"

"Windows Normally" led to the same hang/freeze.

"Start up repair" at least gave me a cursor and a sky-blue backdrop with artsy swirls. (A windows backdrop of some sort.) And then IT froze. For 45 minutes without a flicker from my SSD status light.

I quit, restarted (hard power cut), no change.

It would be nice to have a boot menu option to toggle "Safe mode". I don't know how to get that to appear.

Meanwhile, I disconnected the hard-drive ( D drive) and tried to reboot. Presto, magicko: it booted right up.

Now, I'm in the midst of a sfc/scannow check...

If that passes, I'll reconnect the D drive and see what happens.

+ Corrupted files were found: how do I find out how to fix them?
+ Re-running sfc /scannow: I'll do that 3x, reboot, do it another 3x.

(If, somehow, system files ended up on the D drive, how do I find them and delete them?)

Thanks,
Ken

**Pauly** · 21 Jun 2015

Reboot after each sfc scan up to three times to complete repairs, if errors are still found after three runs post the sfc log

Quite often sfc errors are not the cause of the fail to boot, in your situation it sounds like it may be a problem with your second drive, if after reconnecting the D drive your system fails to boot again then that is highly likely and some hdd checks may be the next step

Please fill in your system specs properly so we can see what kit you have

System Info - See Your System Specs

iamc3k · 21 Jun 2015

Pauly,

Thanks.

I've updated the system specs for the problem machine. I've also attached my CBS log file.

I only have my C: drive (Samsung SSD) and my bluray connected.

3x sfc /scannow and reboots... Still get a scannow error.
I scheduled, and ran, a chkdsk at reboot: no errors.
Samsung's Magician says my C drive is okay.

Still... I get the scannow errors.

Also, I reconnected the D drive (A WD 1TB Black), and got the same hang.
I disconnected D drive, and booted normally.
I reconnected D drive to a DIFFERENT Sata plug on the mobo...same hang.
I disconnected D drive, and booted normally.

So... D drive hangs the boot. I need/want to get the data off it. (I could toss it into an external enclosure and see what I can get via USB3 to the external enclosure. But I should be able to boot and run some diagnoses on it since my C drive should work.)

My w7 disk is an oem, so I have a thumb drive with a w7 iso image. (I think! LOL.)

First steps: how do I fix my scannow errors?

Thanks,
Ken

**Pauly** · 21 Jun 2015

SFC errors are your 2nd problem at the moment, primary job is to look at the D drive unit
I would start by downloading WD data lifeguard utility for DOS or windows then connect drive either internally and boot to dos version or connect externally and access via windows version and run tests on the drive

In the meantime I will see if I can get one of our SFC gurus to have a look at your scan results as there are far too many entries for me to even try to understand whats going on there

http://www.wdc.com/wdsearch/?sq=data+lifeguard&sl=en

iamc3k · 21 Jun 2015

Wow. Thank you.

I'll grab the latest WD utility and run the tests, as you've advised.

There is a "history" to this computer: I had a failing HD so I swapped from the HD to the SSD. I then performed a Repair Install on that SSD, due to issues. The current WD hard-drive is new (meaning, it was never installed before I had this machine running with the SSD.). I mention this in case I somehow messed up the repair install. (FWIW, after the repair install, with JUST the SSD installed, the sfc /scannow ran with no errors.)

Thanks!

Ken

iamc3k · 21 Jun 2015

WD DataLifeguard (5?) and Rufus made a bootable usb drive...
WD Quick Check found a Read Error. It recommended a more thorough check. That took ~2 hours. It finished and said it had repaired the disk.
My machine booted. Windows wanted to do a startup repair...but failed.
A reboot into my desktop, and now I've dismounted the D drive and am running a chkdsk (with repair) just to be sure.

That -may- leave just the sfc /scannow issues...

I'll post more later.

Thank you very much.

Ken

NoelDP · 22 Jun 2015

Here's the error from the SFC log

Code:

 Line 37330: 2015-06-21 15:26:37, Info                  CSI    0000031f [SR] Repairing 1 components
 Line 37331: 2015-06-21 15:26:37, Info                  CSI    00000320 [SR] Beginning Verify and Repair transaction
 Line 37334: 2015-06-21 15:26:37, Info                  CSI    00000322 [SR] Cannot repair member file [l:54{27}]"TaskScheduler.resources.dll" of TaskScheduler.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol later.

NoelDP · 22 Jun 2015

I've uploaded a file - i3kaa.zip - to my OneDrive at Noel'sOneDrive

Please downloadand save it.

Right-click on the saved file and select Extract all...

Change the target to C:\ and click on Extract

Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'

Pick that

You'll have to log in with your username and password.

Pick the option to use a Command Prompt

At the prompt type

DIR C:\i3kaa

hit the enter key - if you get a 'Not Found' error try

DIR D:\i3kaa

or

DIR E:\i3kaa

The drive letter in use when you find the folder will need to be substituted (for<drive>)into the following command...

XCOPY <drive>:\i3kaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type

EXIT

and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt

then reboot and upload the new CBS.log file to your reply

iamc3k · 22 Jun 2015

NoelDP,

I've tried to do exactly as you suggested.
I extracted the i3kaa folder onto the root directory of my C drive. (C:\i3kaa)
Rebooting into Safe Mode with Command Prompt got me into the elevated DOS window (at least, that's what it looked like).

+ I did NOT have to log in with a username or password. (In fact, I never have to do so with this computer)

Upon running the command you listed (xcopy from the i3kaa folder to the winsxs folder) I was told that "access denied - unable to create directory winsxs".

I then exited, rebooted, and with Windows 7 running, checked my C:\Windows folder and, sure enough, there is a winsxs folder.

I had double checked my typing. I did not make an error.

I then tried again. I got the same error. Within the elevated command prompt from the safe mode, I then checked: yes, my c:\windows\winsxs folder exists, and I could change directory (cd) and get a command prompt from there. (I tried the xcopy from "within" the windows\winsxs directory but got the same "access denied - unable to create" error.

This sounds like a permissions issue?

Thanks,
Ken

Edited for clarity.