Help - Strange Win7 Install issue with SSD

Associate
Joined
7 Feb 2011
Posts
353
Hi,

Been googling this for a while now, but since this isn't a newbie issue, I'm struggling to find an answer.

Just put my new M4 SSD in my PC - its the only HDD installed (as I'm short of a sata cable I had to completed remove the other HDD!!)

1st off, went to BIOS and switched to AHCI mode. Oddly, noticed that my BIOS no longer detects the disk.
But stuck the Win7 DVD in, and booted. Found the drive no problem and installed.

Couple of reboots went fine, but now it won't boot. If I change to IDE mode, it works fine???

Any ideas?
 
How odd.

Put the Win7 disk in to try a system repair (or reinstall if no luck). Couldn't fix it. So shut down, and restarted.

Lo and behold, worked fine. Rebooted, checked the BIOS, yet AHCI mode is enabled, and can't see any Sata devices. Buts its booting fine.


Now I come to think of it, the laptop I'm using to type this had the EXACT same issue when I installed an SSD in it. And I never got to the bottom of it.

(Original Win 7 64bit DVD if it makes any difference)
 
Generally, if you install in AHCI mode, then switching to IDE mode won't cause a boot fail, its when you install in IDE mode you have to do some reg tweaks to get AHCI going.
 
Ah, knew you "can't" move to AHCI if you accidentally install in IDE, thought it went both ways.

Still, any idea why I got this problem on TWO totally different machines?
 
What SSDs? Sandforce based by any chance? Also what firmware version are they running? Have you updated the BIOSes on the machines in question?
 
I'd update the BIOS. Also turn off hot swap (or whatever it might be called in your BIOS) function, sometimes helps with that issue, usually for Sandforce only but its worth a shot.
 
Hot swap? I don't recall seeing any settings for this. Just a note, I don't have any RAID setup.


Its working now. I'm just curious why its done this on a PC desktop AND on a netbook. Its odd.


Couldn't be because the Win7 Disk is a upgrade only disk could it? And so doesn't correctly set boot options as it expects them to already be setup? (I hacked reg to get it to work with a clean install)
 
Last edited:
Back
Top Bottom