SSD slow bootup & WEI only 5.9 ??

[windzstriker]

Hi Guys...

My SSD is ADATA S501. 120GB.

Everytime I boot up my PC, it is definitely not the speed of a SSD I would say.

It stops at the Gigabyte boot screen for a good 18secs ----> Black W7 for 4 secs ----> Welcome screen for 10 secs ---->
(Then while loading the desktop, it is a black screen for a good 16secs again)


I would say the Gigabyte screen & black screen as mention above is not satisfactory.

Any thing wrong here ? Caus I remember when my computer just got fixed up, the startup isn't this slow, this happen only after like a few weeks later.

And my Windows Experience Index for the Primary HDD is only 5.9 .

 

[SkyWalker1726]

are u sure u installed the win on ur SSD ?

 

[windzstriker]

are u sure u installed the win on ur SSD ?

Ya.................My C drive primary drive is the SSD.

 

[Deleted member 217926]

What is the rest of your hardware?

When people get a 5.9 it usually means they have installed the SSD in IDE mode and not AHCI like you are supposed to. Post number 7 in the link explains how to fix this without reinstalling Windows.

http://www.sevenforums.com/installation-setup/29089-change-ide-ahci-bios-much-better-performance.html

 

[windzstriker]

What is the rest of your hardware?

When people get a 5.9 it usually means they have installed the SSD in IDE mode and not AHCI like you are supposed to. Post number 7 in the link explains how to fix this without reinstalling Windows.

http://www.sevenforums.com/installation-setup/29089-change-ide-ahci-bios-much-better-performance.html

Hi,

I went to the website and stuck at the modifying data value step.

i right click and the "modify" option was not available for clicking.


I went to Gigabyte Intergrated Touch Bios and under the "PCH Sata Control Mode", it was set to IDE, does this mean my SSD is in IDE mode ? or how can I check if my SSD is in IDE mode ?

 

[Deleted member 217926]

Yes your SATA ports are in IDE mode. They should be in AHCI mode for an SSD.

Here is a more detailed fix.

http://support.microsoft.com/kb/922976