1 of 1 people found this helpful
1. Try another port.
2. Re-seat all cables and connectors.
2. Try another cable.
3. Edit BIOS settings so you can see where BIOS hangs.
You did mean the boot screen and not a system load screen, right? Come to think about it, I read about a Windows Update that Microsoft was recommending people uninstall on Win7. KB2823324 I think. Something about a platform update. Your symptoms are different but I would look at rolling the system back unless you have a better idea.
Try this link:
On the DC3217IYE system there is only one mSATA port (no cables) so no way to test if its the port or not (at least, not without another mSATA drive which I do not have available to me).
And yes, the Intel Boot Screen (I never see the Windows loading screen) is where the system hangs.
If I remove the drive, I can boot to USB, or to the BIOS, but once the drive is back in I cannot get anywhere.
Thanks for the suggestions though.
That is a good question. There are no codes to indicate where in the process it is hanging. All I can tell you is the Intel BIOS screen pops up, and nothing happens after that. (Unless, of course, I remove the drive) I have ordered a USB/mSATA adapter which should arrive in a couple of days. I will test the drive on another system to try to confirm the probably is the drive.
UPDATE: Interesting development...Removing the drive, disabling UEFI, and reinstalling the drive has allowed me to get back into Windows XP. This is very strange because it had worked fine before. (Legacy boot was always enabled.) I am now suspecting that there might be an issue with the board...I am getting a backup of the installation, then will try to install Windows 8 with UEFI and see what happens...
I think I know what you're talking about now. You see a splash screen and not the messages BIOS prints from POST. I was a little confused on that.
You would do yourself a favor to find out how to set BIOS to print POST messages so you can see where BIOS hangs.
Honestly, I don't know any better but it sounds like there's a problem with the Trusted Platform Module (TPM) and some update. I don't really remember XP anymore, but I don't think it supports TPM and that may explain why you can get back into XP.