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.
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
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.
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.
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.
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.
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.
Thanks for posting the solution
Quote
