Community
cancel
Showing results for 
Search instead for 
Did you mean: 
idata
Community Manager
2,225 Views

Intel SSD 330 120GB often freezes for 60 seconds

Jump to solution

Hello,

I have a problem with my SSD. The symptoms are exactly as decribed in this Microsoft article:

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

The problem is that I have already installed Windows 7 SP1 and available hotfix is already included in SP1. So the problem should be gone, but it's not in my case. It happens quite often and is very annoying. I think it may be the SSD firmware issue, because I have already tried almost everything and nothing helps. So I decided to post here on Intel's support community for help. I have Windows 7 Home Premium x86 SP1 installed in AHCI mode with msahci driver. My motherboard is Intel D915PBL with 4 SATA I ports. The OS often freezes for exactly 60 seconds and after that time, simply returns to the normal operation. Please help me solve this problem.

1 Solution
idata
Community Manager
216 Views

Please be aware that you are using a system with a SATA controller two generations behind, because of this reason you might experience slow performance and hardware compatibility issues, on this case the recommendation will be to use a SATA II port for better performance.

it is not recommended to use Solid State Drives with legacy systems (more than 4 years old computers) since the SATA controller was not designed to manage the high speed of Solid State Drives.

View solution in original post

28 Replies
idata
Community Manager
212 Views

Thank you for your answer, but I've already read this and the provided solution is not for me. I'm using ahci driver from Microsoft and I can't switch to a different driver, because my integrated SATA controller (ICH6R) is not supported by Intel in Windows 7.

idata
Community Manager
212 Views

trance,

Sorry, I wasn't very clear. It was the registry changes I was suggesting. I too am using the MS AHCI driver (with an Intel 335) and was running into the problems you describe. In fact, I came across your post while researching the issue.

I tried the registry changes mentioned in the article and my problem "appears" to have vanished. What it does is disable low power mode for the device.

1. Set a restore point.

2. Take the text at the bottom of this message and copy it into a file with a ".reg" extension.

3. Double click on the file and it will prompt you for permission, allow permission.

4. Reboot.

That should be it. It does assume you don't have more than six SATA ports. If you do, you can add additional ports to the file.

Text below:

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port0]

"LPM"=dword:00000000

 

"LPMDSTATE"=dword:00000000

 

"DIPM"=dword:00000000

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port1]

"LPM"=dword:00000000

 

"LPMDSTATE"=dword:00000000

 

"DIPM"=dword:00000000

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port2]

"LPM"=dword:00000000

 

"LPMDSTATE"=dword:00000000

 

"DIPM"=dword:00000000

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port3]

"LPM"=dword:00000000

 

"LPMDSTATE"=dword:00000000

 

"DIPM"=dword:00000000

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port4]

"LPM"=dword:00000000

 

"LPMDSTATE"=dword:00000000

 

"DIPM"=dword:00000000

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor\Parameters\Port5]

"LPM"=dword:00000000

"LPMDSTATE"=dword:00000000

"DIPM"=dword:00000000

idata
Community Manager
212 Views

I have no iaStor, but iaStorV registry entries. Should I create the iaStor too and add those mentioned registry entries or just add the registry changes only under iaStorV? Will it work even if the driver is not installed (iaStor) or is turned off (iaStorV) on my pc?

idata
Community Manager
212 Views

I believe it is iaStor and not IaStorV that you are interested in. I did not have an iaStor either and from what I read, most people didn't.

Creating via the .reg file was the one modification I made to the initial suggestion. It's a lot less work and automatically creates the entries.

I really don't know much more than that. Looking at the entries, I decided the risk was low and that I could always recover ala restore point. I took the chance and it worked out for me. It's up to you at this point.

idata
Community Manager
212 Views

I think that I will try your advice. Please, tell me one more thing - do you also have an iaStorV registry entries (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV) and a Start value is set to 3 (which means the driver is turned off)?

idata
Community Manager
212 Views

Trance,

I do have an iaStorV entry with a Start value set to 3. Also, below is a shot of my AHCI driver. Seeing that it's 6.5 years old, maybe it's time for MS to update it.

idata
Community Manager
212 Views

I added the registry entries and unfortunately still have 60 seconds freezes. I contacted Microsoft with the issue and they sent me to Intel Support. They want to know what Intel have to say about that. I've already sent an email to Support.

As for the MS AHCI driver, I think they could mess up something with the latest version. The driver version, which should eliminate the issue is 6.1.7600.20545 (date: 09-Oct-2009). May I ask what other SSD optimization did you apply? Did you also try this?

http://I added the registry entries and unfortunately I still have 60 seconds freezes. I contacted Microsoft with the issue and they sent me to Intel Support. They want to know what Intel have to say about that. As for the MS AHCI driver, I think they could mess up something with the latest version. The driver version, which should eliminate the issue is 6.1.7600.20545 (date 09-Oct-2009). May I ask what other SSD optimization did you apply? Did you try this? http://www.sevenforums.com/tutorials/177819-ahci-link-power-management-enable-hipm-dipm.html http://www.sevenforums.com/tutorials/177819-ahci-link-power-management-enable-hipm-dipm.html

idata
Community Manager
212 Views

Dang, I was really hoping that'd solve it for you. I avoided all other optimizations (other than turning off prefetch), as it was suggested not to. Also, I don't have the options listed in the link you provided:

It's also odd that the version number on the driver you posted is an older number than the one on the driver I posted, but has a newer date. A quick google, indicates that version might be 32-bit. Are you running Win7 32-bit? If so, that's a big difference between us.

I'm curious to hear what Intel support has to say. This appears to be a not uncommon issue.

idata
Community Manager
212 Views

You will see the options after you add the registry changes mentioned there. I think it's useless anyway.

Yes, I'm running W7 32bit.

Yes, it is a strange thing with the dates and version numbers.

I will wait for the answer from Intel's Support, but I don't expect much from them anyway. There is no even a single firmware update for months. Maybe I'll have to change the SSD for a different brand. I will see. Thanks for help.

idata
Community Manager
212 Views

Hi trance,

Try the following setup. It's a setting of turning off LPM for msahci driver.

If keys don't exist on your Registry, you create it.

Doing is the same as brn's method.The target driver is only different.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msahci\Controller0]

"DipmEnabled"=hex:00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msahci\Controller0]

"HipmDisabled"=hex:01

idata
Community Manager
212 Views

I think Trance hit the nail on the head...I'm simply giving up on the 330 drive and going with a samsung 840 pro,

Sorry intel, but I think your lack of response to this issue with 330 is telling. I think you wish we would just quietly go away. The 330 line should have never been released, And now that the 335 series is out, Intel is pretending it wasn't..

Thanks for nothing.

idata
Community Manager
212 Views

Tok, Thank you very much for your advice, but currently I'm not able to check your solution, because I upgraded to Windows 8. I did a clean install, but unfortunately the freezes persist. They are now shorter (around 25 seconds) and when they appear I get 2 entries in the event viewer:

"WARNING - storahci - Reset to device, \Device\RaidPort0, was issued.

"WARNING - disk - The IO operation at logical block address xxx for Disk 0 was retried."

Block addresses each time are different.

I hope that Intel release a firmware update soon, because I think this is probably an SSD/Sandforce firmware issue.

idata
Community Manager
217 Views

Please be aware that you are using a system with a SATA controller two generations behind, because of this reason you might experience slow performance and hardware compatibility issues, on this case the recommendation will be to use a SATA II port for better performance.

it is not recommended to use Solid State Drives with legacy systems (more than 4 years old computers) since the SATA controller was not designed to manage the high speed of Solid State Drives.

View solution in original post

idata
Community Manager
212 Views

I inderstand your point of view however, I don't want to upgrade my legacy system. I don't see any reason to do this. Everything works as it should except the ssd. Besides, the SSD is backwards compatible with SATA I, so everything should work, but it's not. I'm not complaining on the ssd performance, but on the ssd freezes. I read on many forums that this is a very common issue and can affect even the latest hardware available on the market.

idata
Community Manager
212 Views

I'm glad to see that Intel (eventually) replied. However, I have to agree with trance.

While the fix I suggested earlier in this thread appeared to have resolved my issue for a while, it has come back with a vengeance (three year old, not four year old, M4A785TD-V EVO motherboard). I'll try Tok's suggestion, but back to Intel's comment...

As trance says, SATA is backward compatible. The performance may not be as good, but we're talking about painful freezes here. Of several SATA devices that have been in this machine, only the Intel SSD (335 in my case) has issues. I would purchase a newer controller if I believed it would resolve the issue, but I've no reason to believe it would. I think the "buy new hardware" suggestion was too much of a wild guess.

The funny thing is that I selected an Intel branded SSD to avoid problems.

idata
Community Manager
212 Views

Sorry to say, there is some confusion about drivers in this thread, for example:

Windows has several SATA drivers that it will install when it is installed, which can be seen in the registry entries being discussed. Only one can be used per SATA chipset at a time of course, and the only way to determine which one is being used is by checking either the IDE/ATA Controllers or Storage controllers in Device Manager. For example, brn's picture shows he is (was) using the msahci driver, Windows generic AHCI driver, which is designed to work with multiple SATA chipsets. Entries for iaStor and iaStorV are for the Intel Rapid Storage Technology (IRST) drivers, and different versions, which are used in AHCI or RAID mode.

If the msahci driver is installed as the SATA chipset driver, changing registry entries for iaStor, etc, have no affect on the functioning of msahci. A Windows Hotfix or SP1 update for the msahci driver will have no affect on any other SATA driver, such as iaStor. The same is true if the iaStor driver was installed, and the registry entries for msahci were changed, no affect. So the SSD issue would also be unaffected.

brn's M4A785TD-V EVO board is an AMD CPU and chipset board, using the AMD SB710 SATA chipset. Intel's iaStor drivers are not compatible with AMD SATA chipsets, and cannot be installed/used by them. So changes to iaStor registry entries will have zero affect. Again, SSD issue unchanged.

brn could have tried the AMD AHCI driver for his board, which is part of their "All in One" driver installer.

The point that MBV2000 made was that the hardware itself has changed significantly since trance's ICH6R chipset was released. SATA may be backward compatible (in theory) but that is software not hardware. That is the reason to update the hardware. The reality is there, whether it is recognized or not.

There is also more to the picture than is obvious, this is a quote from the FAQ's for brn's mother board:

Controller limitations:

Cause: There could have been a known limitation with the existing SATA/RAID controller, such as limited support to particular SATA standards or specifications.

SATA chipsets made by Nvidia are an example of this. The D915PBL board is almost 10 years old. That FAQ also mentions another important point:

 

Driver or HDD firmware issue

 

Cause: SATA/RAID Driver loaded may need to be matched with specific versions of SATA/RAID BOOTROM, or the controller's behavior under AHCI mode, in order to allow the controller and device to function correctly. System may result in fail to install operating system, performance drop, or even not detecting HDD during OS installation process if the drivers are not matched. (Note: Some versions of Windows may have been bundled with a previously existed version of driver for a particular controller.) Only when this driver also matches with SATA/RAID BOOTROM or controller behavior under AHCI mode, would the controller be able to function without fail. The same could also happen if the HDD firmware is not fully compatible with such SATA/RAID controller.

 

The BOOTROM or SATA option ROM is code stored with the BIOS code and updated only by a BIOS update. It obviously becomes out of date once BIOS updates for a board end, assuming that the SATA option ROM is updated, which is rare.

 

No one has mentioned the Intel SSD Toolbox, that performs OS optimizations, none of you use it?

 

I must say that running Windows 7 and 8 on a D915PBL is quite a feat. Intel specs driver support for it up to Windows XP, but that's it. The ICH6R is a SATA I chipset, although it does have RAID support, via a Matrix storage driver, and supports AHCI mode, which is amazing for a board of this age. The Matrix storage driver has not been used on any new platforms for since the ICH10R chipset, the last of the ICH style chips, used in X58 systems.

My only suggestion would be choosing a Windows high performance power plan, and in the Advanced settings set Turn off hard drive after, to Never. Or in brn's case, try the AMD SATA driver.

idata
Community Manager
212 Views

parsec,

I appreciate the comments. They are helpful. With this information, some help from Intel Support, and Google, I decided to plug my SSD into a SATA port that does not have AHCI enabled. The problem went away and the performance is better than before.

I will experiment with AMD drivers, but if it all fails, I'm content with the system as it is now.

As to your question "No one has mentioned the Intel SSD Toolbox, that performs OS optimizations, none of you use it?"

 

Yes, I do use it and it says my setup is perfect.

 

- brn

idata
Community Manager
212 Views

Glad this forum could help you a bit. Also thank you parsec for the detailed information and explanation.

idata
Community Manager
69 Views

Dear Intel,

I notice you are aware of this issue by having your representatives interact with this forum.

The issue is clearly related to older sata chipsets. I myself own three 330's and they work fine in newer chipsets but I've never managed to work out a solution for the freezes in older sata 1 chipsets. Buying a SSD drive on OLDER computers along with more RAM is THE ONLY solution to prolongue the systems' life. I am extraordinary happy with this six-years-OLD computer, for subjective reasons such as "I would buy a new laptop but the new keyboards are unusable for someone who types a lot"

Your product support is a total waste of time. I opened a ticket and after stupid recommendations such as "did you try to format the drive with intel toolbox", "oh, your windows installation is five years old, did you try on a clean windows install" and so on (while I was sending out raw logs, clear explanation, etc), all you were able to do was to offer to replace the drive, while you already KNEW there are issues with these drives.

If you did not know, then your entire support line is totally out of sync with your production line. I even asked your support what happened to my failed RMA drive (i.e. did you test the drive in a sata1 generation to be able to reproduce the issue?) and he was unable to provide an answer.

I have two questions, of which one is rethoric.

1. Were you able to identify what exactly causes the freezes on sata1gen links and eventually release a firmware fix/recommend a workaround?

2. Will I ever buy an Intel SSD?

Thanks and goodbye.

Reply