XP Startup Loop - Secondary Hard Drive

smlie4

Member
Reaction score
3
Location
Perth, Australia
I went out to customers house couple of days ago with complaint that Windows XP was getting stuck on the Black XP Startup Loader screen.

First things first I tried safe mode and it was hanging at MUP. I used Hirens boot CD which loaded find and I could browse all 3 of the attached hard drives.

I ran memtest and it came out ok. I ran quick virus check in hirens boot cd and nothing came up. I told customer I would need to take computer away to carry out further checks including deep virus scan and full hard drive tests if all came up good I would have to re-install windows as it would most likely be a registry error if all other test showed good.

The customer decided they were thinking of upgrading anyway and would rather I quoted them on new computer with Win7. Did up quote which customer gave go ahead.

After I had setup new system, I pulled out a 1TB WD Caviar (Green) drive which had been running as slave out in customers old system with the intention of using again as slave in the system.

As soon as I boot new system up with slaved Caviar drive from old system windows 7 hung at Windows loader screen. I shut down computer and pulled sata cable off and windows startup up no problems!

I booted with WD diagnostics to test drive and it said "no drives" found. I swapped sata cables and ports and still no drives found. I checked BIOS and drive was there. I used hiren's boot CD and it would not load the desktop just hung in the rainbow coloured screen.

I tried UBCD4WIN and I got BSOD error.

I was thinking of maybe trying to load recovery console and seeing if I could run chkdsk on the troubled drive providing it showed up in recovery console.

I have spent long enough on it now and just going to condemn drive and go through process of informing customer about importance of backing regularly.

Comments welcome on what else I should've/could've done.
 
So are you asking about recovering data from it or something else?

I don't see what else you could have done. It's clearly a drive with problems and sometimes problems are not consistent or they progress. You acted according to the testing results you had at each state.
 
Back
Top