I had a very annoying problem on my Windows 8 system recently.

Once in an hour of active use system would suddenly hang for 10-40 seconds. System event log then would contain following records:

Source: iaStorA EventID: 129  Reset to device, \Device\RaidPort0, was issued.
Source: disk    EventID: 153  The IO operation at logical block address 9e1c5b for Disk 1 was retried.
Source: disk    EventID: 153  The IO operation at logical block address 7af577b for Disk 1 was retried.
Source: disk    EventID: 153  The IO operation at logical block address 7100db for Disk 1 was retried.
Source: disk    EventID: 153  The IO operation at logical block address 5cf489b for Disk 1 was retried.
Source: disk    EventID: 153  The IO operation at logical block address b6fdc73 for Disk 1 was retried.

and so on...

Disk 1 is Intel 520, SSDSC2CW120A310 and it is my boot drive. Motherboard is based on Intel H61 Express chip set. Lastest Intel storage drivers are used.

  • 2
    Have you checked your cables? SATA is well known for being prone to loose data and/or power cables. Feb 7, 2013 at 14:28

6 Answers 6


I'm having a similar problem, which I'm still searching for a better fix. However, I did detail a work around for Win7/8 in the Lenovo forum.

The Win 8 work around is:

  1. Remove Intel's "Rapid Storage Technology Driver" in favour of MS's generic version
  2. Apply registry hack to enable MS's power manger to show the HIPM and DIPM options
  3. Disable HIPM and DIPM located here
  4. Set HIPM/DIPM to active.

My dream is to able to use the Intel AHCI driver and this drive.


I don't have a solution, but I have a setting that makes it less painful.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\disk] "TimeoutValue"=dword:00000014

I changed this from 3C hex (60 seconds) to 14 hex (20 seconds). This means that when the I/O stack is not responding, Windows will wait for 20 seconds before issuing the reset instead of 60 seconds. My guess is that if it is too long, and there are too many I/O's stacked up, Windows bluescreens on purpose.

For me, it only happens on startup or resume from hybrid sleep on Windows 8.1. The HIPM and DIPM suggestions did not help me, nor the PCI Express LPM (Link State Power Management). I also have a normal disk, not SSD. I am running version of iastora.sys.

EDIT: Well now, I installed version of Intel Rapid Storage Technology, and now I can suspend and hybrid sleep no problem now, even though (perhaps on Windows 8, not 8.1) I had the problem with that installed.


I was able to solve this problem on my machine running Windows 7 Pro x64 on a MB that includes the Intel ICH10R RAID controller:

  1. A temporary work-around is to disable the Paging Executive. Disabling the Paging Executive prevents Windows from swapping memory used by device drivers out to the paging file. The path to the registry entry is here:

    \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

    and the key is:


    Change the value from 0 to 1 to disable. You will need to reboot to put the change into effect.

  2. An actual fix, as apposed to the work-around, appears to require a BIOS update. Motherboards with the Intel RAID controller (mine happens to be ICH10R, but there are others) include BIOS code for the chip. This is called a ROM option. Upgrading the MB's BIOS includes any available upgrades to the RAID controller's BIOS. My upgrade took me from version of the Intel Matrix Storage Manager to version of the Intel Rapid Storage Technology (Intel has renamed their RAID software to Rapid Storage Technology).

    Prior to updating the BIOS, remember to boot into your current BIOS and take note of every setting. Don't just write down the values in the order in which they appear. Write down the item and its value. The new BIOS very likely introduces more settings and may move some settings from one menu to another.

    A BIOS upgrade resets all the BIOS settings to their default, which usually includes the RAID controller being disabled. On your first boot-up after the BIOS upgrade, if you go to the BOOT section of the BIOS configuration screen, you'll probably see all the individual hard drives that make up your RAID volumes. Even changing the BIOS settings back to using RAID won't change what you see on the BOOT configuration page until you re-boot. So the order is, restore all your previous settings, including changing the settings back to RAID if that's what you had before up to the BOOT menu, save the changes and re-boot. Then you can continue restoring your previous settings starting with the BOOT menu.


OK, just sharing experience. I've managed to eliminate a problem by switching SATA controller from AHCI to IDE mode in boot setup.

It is not trivial - OS won't boot after the change. Check out this question: Change from IDE to AHCI after installing Windows 8

  • 3
    Ancient IDE mode will stress your harddisk a lot less (e.g. only one command at a time rather than a queue of requests). This might simple mask the problem.
    – Hennes
    Feb 7, 2013 at 16:55
  • Actually not, but in any case I've tried to exchange the drive, but it was returned to me with a label "Perfectly fine". Feb 12, 2013 at 8:03
  • You should not do this. In IDE mode, your SSD will die in months.
    – kinokijuf
    Feb 12, 2013 at 8:33
  • 1
    Why would it die in months? Can you add a reason for that? (Mind you, I think I can guess that you are referring to TRIM, but right now that is a WAG).
    – Hennes
    Feb 12, 2013 at 11:02
  • :) Weird how IT field attracts all kind of suppositions. Feb 12, 2013 at 15:32

Really would need a lot more details as to what this is supposed to do. From what I found this was related to the RC of Windows 8 and was patched.

disabledynamictick [ yes | no ]

Enables and disables dynamic timer tick feature. The option is available starting with Windows 8 and Windows Server 2012.

Note This option should only be used for debugging.

"On a computer that is running Windows 8 Release Preview or Windows Server 2012 Release Candidate, the system may randomly stop responding (hang) when you work on multimedia or communication activities. This problem may occur during video editing, unified communications, or other multimedia activities.

This problem may occur because of an issue in the interaction between the state-machine driving dynamic tick transitions and the state-machine-driving clock rate changes."

bcdedit /set disabledynamictick yes
  • 6
    you might want to explain what this does
    – Sathyajith Bhat
    May 22, 2013 at 2:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.