PC takes 5 mins to boot then runs fine

[Hamgray]

Hi guys,
I have just upgraded a friends pc to two new WD hard drives. A 1TB black for C drive and 2TB green for storage. Previously 80 + 320GB.
Using W7 Pro on a AMD x3 3Ghz CPU and 2 x 2GB (4GB) DDR2 RAM.
Cloned the old drives to new (via my pc) and it was booting up in just over 1 min. Very impressed.
Delivered to friends house and now takes 5 mins to boot, but after that all is very quick.
Checked inside for loose wires (disconnect & reconnect SATA cables) and reseated RAM.

Now here's what I have noticed, the hard drive light is nearly solid from switch on until about 6 fades of the 4 colored lights thing, then the HDD lamp blinks very slowly. Just before the desktop (nearly 5 mins later) it speeds up again and the desktop is virtually instant.
Tried defrag, HDD scandisk for errors & restore to a previous point. All no change to the problem.

CBS and NTBTLOG files attached if anyone can understand them (beyond me I'm afraid and I though I was a pc wizard!)

Only other changes to note are:
At my place I used different KB & mouse (both USB). At his house the mouse is PS2 (KB USB but a different one).
For Internet I was using an WiFi box connected by ethernet to the pc (actually a Sky WiFi box) and at his house a BT Hub 4 directly connected by ethernet. When finally booted Internet speed is good.
At my place no printer was connected at his a Canon connected but not switched on (also tried switched on but no different)
Tried booting with only monitor connected - still slow boot.
CBS file had to be divided in two to get over the size limits.
Hope some kind soul can give me some hope?

 

[GokAy]

Try loading defaults in BIOS and if no go, take out the 2TB green to test OS drive alone.

 

[Hamgray]

Thanks. Tried both those ideas and still a slow boot.
Forgot to mention before that Safe Mode is ALSO as slow to start.
Is there any indication in the log files attached? All a bit too deep for me!

 

[MilesAhead]

Take a look on this page about 70% of the way down:
Delay on boot due to multiple attempts to install NDProxy.sys, - Microsoft Community

Edit: I found that page because of these entries in your boot log

Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS


Edit2: My gut feeling, as they say on the police detective shows, is that the green drive is not spun up when the system is trying to load drivers. I always run WD black. That spin up spin down stuff is asking for headaches.

 

[Hamgray]

Thanks MilesAhead, I had seen that article but apart from a 20 mile journey to my friends house nothing changed from when I had a1 minute boot not 5 mins ! Other articles say the multiple driver attempt is not a problem, just that Windows found 1 so that's ok.
I'm not in a position to do any repairs or clean install yet, but the two drives are brand new. In fact I always use WD as I have seen less failures with them.
I'm warming to the network connection which some reports have mentioned, or the USB card reader (?).
Any thoughts on the network idea??

 

[GokAy]

But already tried with green disconnected?

Edit: Bit late

 

[UsernameIssues]

Windows event logs should show something during that 5 minute wait.

The CBS logs seem to indicate repairs are being done (and failing?).

What does SFC/SCANNOW show from an admin command prompt?

Hopefully, you can gather this info via TeamViewer or the like.

 

[MilesAhead]

Thanks MilesAhead, I had seen that article but apart from a 20 mile journey to my friends house nothing changed from when I had a1 minute boot not 5 mins ! Other articles say the multiple driver attempt is not a problem, just that Windows found 1 so that's ok.
I'm not in a position to do any repairs or clean install yet, but the two drives are brand new. In fact I always use WD as I have seen less failures with them.
I'm warming to the network connection which some reports have mentioned, or the USB card reader (?).
Any thoughts on the network idea??

It tried to load the same driver 4 times. I doubt the time out is less than 15 seconds. That should account for 1 minute by itself. The fact that you talk about funny access light action makes me suspect the green drive. Perhaps your friend's AC voltage is a tad low or some other factor.

I don't even use hybernate or sleep. It may work OK for the annointed but for a regulation lunchbox toting guy like me it is another excuse for lame stuff to happen. I like my systems up and running.. not looking to doze off when I need 'em.

 

[Hamgray]

Yes, I saw the 4 failed driver notices. Thanks for your confirmation is shouldn't take very long.
What is the BIG puzzle for me, it was working fine and fast at my place. I reread your comment and see its about mains voltage.
Here in the UK that's not usually a problem now - was about 50 years ago (I recall!) and his house is fairly new.
I'm hoping to do a Team View session tomorrow and will be firstly looking at the networks listed.
Was there no other mention of a 5 minute wait??

 

[MilesAhead]

That was what stuck out on the boot log. I didn't go through all the logs as drivers never loading in the boot log tends to indicate a problem. One that happened to me, I uninstalled Norton anti-virus on my Vista machine, but it kept trying to install drivers for it during boot. I had to run the Norton Removal Tool a bunch of times and clean the registry to get rid of the driver load attempts.

You could have your friend try the Registry Cleaner in CCleaner. It is one of the safer ones and has a backup. Before it does erase of registry issues it offers to save the old values just have the friend click Yes and it will save a .reg file in Documents.

I have never owned a Green drive. Is there a "performance" setting where it never spins down even if only for diagnostics? Hanging for 5 minutes is not usually software unless things are really scrambled.

 

[GokAy]

Unlikely, but you can check Advanced Acoustics Management (AAM) setting of your drives with CrystalDiskInfo (Function - Advanced Feature - AAM/APM Control). Slide to rightmost (performance) if not already.

I would not fix on the green drive since this happens when it is disconnected too.

 

[Hamgray]

Is this where it's going wrong?
Anyone make sense of it??
Package_for_KB2862152~31bf3856ad364e35~amd64~~6.1.1.1, ApplicableState: 112, CurrentState:112
2015-07-27 12:10:38, Info CBS Session: 30459996_3726590043 initialized by client WindowsUpdateAgent.
2015-07-27 12:10:38, Info CBS Read out cached package applicability for package: Package_for_KB2852386~31bf3856ad364e35~amd64~~6.1.1.3, ApplicableState: 112, CurrentState:112
2015-07-27 12:10:38, Info CBS Session: 30459996_3726902543 initialized by client WindowsUpdateAgent.
2015-07-27 12:10:38, Info CBS Read out cached package applicability for package: Package_for_KB2647753~31bf3856ad364e35~amd64~~6.1.4.0, ApplicableState: 112, CurrentState:112
2015-07-27 12:10:38, Info CBS Session: 30459996_3727058793 initialized by client WindowsUpdateAgent.
2015-07-27 12:10:38, Info CBS Read out cached package applicability for package: Package_for_KB3064209~31bf3856ad364e35~amd64~~6.1.1.1, ApplicableState: 112, CurrentState:112
2015-07-27 12:14:50, Info CBS Trusted Installer signaled for shutdown, going to exit.
2015-07-27 12:14:50, Info CBS Ending the TrustedInstaller main loop.
2015-07-27 12:14:50, Info CBS Starting TrustedInstaller finalization.
2015-07-27 12:14:51, Info CBS Ending TrustedInstaller finalization.
2015-07-27 12:22:18, Info CBS Starting TrustedInstaller initialization.
2015-07-27 12:22:18, Info CBS Loaded Servicing Stack v6.1.7601.18766 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7\cbscore.dll

 

[Hamgray]

Got my friend to disconnect the green 2TB drive and it booted normally!
Did a WD diagnostics test (quick test) on the drive and nothing found.
Question for the experts:
I cloned his old spare drive to the 2TB and was given the choice of MBR or (something else) non bootable structure (ACHI??)
I went for the MBR, was this right?
Wondering if I format the drive (which settings please?) and next time COPY his files over, will that perhaps solve the problem?
Still a puzzle though why it WAS working fine before I took it back to him!
Thanks for any advice.

 

[GokAy]

You did say you tried without green drive in post#3, after I asked you to in post #2

It possibly asked for MBR or GPT. Since this is 2TB, either is alright. GPT is bootable too though, maybe that motherboard doesn't support it (has legacy BIOS instead of UEFI). They are alright as data drives.

 

[Hamgray]

Sorry about that, in the frustration of trying to get it sorted thought I tried that myself when I took it back to him
The BIOS is Legacy (not UEFI).
Yes, I think you are right it probably was GPT.
What are your views on my reformat & copying idea. What settings for format should I choose as I know there are different cluster sizes etc. now.
I'm really hoping that it just got corrupted in the move and a format will solve?
There's no problem with 2TB on W7 is there? Getting paranoid now, but still can't get over the 'was working fine' previously.

 

[GokAy]

No hard feelings

You can use MBR for 2TB. Use default options and quick format if you wish to redo the drive (the worst is to re-copy all back :/). I use a 3TB drive with no issues (it is GPT of course since larger than 2.2TB) on Windows 7. It has burnt a chip 2 weeks back, got a new one yesterday from the seller and been copying back for 12 hours now (%95 finished).

I would try the re-format myself.

 

[Hamgray]

A BIG thank you to all who posted here.
I formatted the 2TB hard drive, ran some tests including a WD Alignment tool and all looked good.
Copied the files back and it seems to have cured the problem. Boots in normal time.
So, for anyone who reads these posts later - problem solved.

 

[GokAy]

 

[UsernameIssues]

Thanks for posting the solution