01-11-2010 07:05 AM
I updated the firmware on my 160gig x25-m G2 drive to the latest. I then installed windows 7 x 64 from scratch on an intel DP55kg motherboard.
When I run the toolkit 1.2 and scan the drive everything is OK. When I go to the tools to optimize the drive it gives me "Intel SSD Optimizer Error" with no other explanation.
I have tried chaning the ACHI drivers from Intels to Windows but that did not fix the issue. I have also turned off the scheduled defrag (which you should always do for SSD drives) and I turned off windows restore. It still does not fix the issue.
01-11-2010 11:29 AM
Check that the drive is connected to one of the chipset SATA ports. Looks like these are supposed to be colored black on your board. According to some, connecting to port 0 or 1 may be preferable.
01-11-2010 11:42 AM
The drive is in SATA port 0.
Does Intel have a debug option or dump file for it's toolkit so you can figure out what is causing it to give an error?
01-12-2010 12:28 AM
SSD Toolbox has an Export button option to export log files.
01-12-2010 07:39 AM
The export option creates a CSV file with the drive's information. It does not contain any errors from the management tool.
Of interest I find that when I go to run the management tool for my drive it gets to 7% before it gives me the dreaded Intel SSD Optimizer Error
01-15-2010 11:30 AM
I had very similar problem:
SSD: 80GB x25-m with the latest 02HD firmware
OS: Windows 7 Home Premium 64bit
MB: Gigabyte GA-P35-DS4
SSD connected to channel 0 SATA port
SATA running in AHCI mode using msahci.sys
When I ran Intel SSD Optimizer, it immediately failed with "Intel SSD Optimizer Error" message.
Solution:
I've found that the problem was caused by TrueCrypt (using the latest version 6.3a). I don't have any part of SSD encrypted, but I had mounted 1TB encrypted partition. After I dismounted this encrypted drive and shut down TrueCrypt completely, SSD Optimizer started working like a charm (I know that it is not necessary to use SSD Toolbox to trim the drive when using msahci.sys, but I wanted to try it).