Sunday, January 25, 2015

Storahci, ID 129, Reset to device, \Device\RaidPort0, was issued - fix for Windows 10 Technical Preview

I had several system freezes in Windows 10 Technical Preview (build 9926 - but I also had those freezes on earlier builds) on my Macbook Air 2013.
System Event-Log shows a warning for ID 129, storahci, Reset to device, \Device\RaidPort0, was issued.

Seems to be some problem related to the SATA-Controller and the SSD (In my case Apple/Samsung SM0128F)

I was able to fix the problem by editing several registry entries:

1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60 and change the "Attributes" key value from 1 (default; hidden) to 2 (exposed). [This will expose "AHCI Link Power Management - HIPM/DIPM" under Hard Disk power settings]

2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\dab60367-53fe-4fbc-825e-521d069d2456 and change the "Attributes" key value from 1 (default; hidden) to 2 (exposed). [This will expose "AHCI Link Power Management - Adaptive" under Hard Disk power settings]

Now you can edit AHCI Link Power Management options in your power profiles. You can either set them to "active" - or in my case I set them to HIPM. (Host-initiated) (While DIPM would be a device initiated sata bus power down).
Those settings control the behavior of the sata bus power state - they do not power down the device.

3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\Parameters\Device

Set NOLPM to * - those keys contain several hardware ID's (vendor and device) for storage devices. Setting NOLPM to * disables LPM control messages to any storage device.

4. I also set SingleIO to * - never had any freezes or storahci warnings again.

I hope this helps those who have also been looking for a solution for a long time.

Please donate so that I can keep running this site!

Be sure to bookmark our site and follow us on twitter for more news and leaks!


  1. Great post. I had the same issue and your fix made the errors less frequent. After reinstalling Windows 10 I noticed that changing my XMP profile from 2400, 1.65v to 2100, 1.60.v had a tremendous effect. The errors are almost completely gone now and I'm gonna try set AHCI Link Power Management to Active to see if the combination solves the issue once and for all.

    (Active is the setting used by Samsung for its 840 Evo)

  2. I admire your knowledge.
    You're really the best.

  3. Unfortunately this method doesn't work with HP OMEN 15.
    We're expecting a fix in this support thread:

  4. i did what you suggested windows10 64bit lets see if system freezes or reboot automatically.

  5. THank you i will be doing this for my home computers and all of our work PC running w10 with SSD.

    Hi5 bud i hope this does it.

    Crucial 1TB SSD i had the same isssues

  6. unbelievable, that did it with my old P45-Chipset and a WD 500GB HDD !!!!

    Thanks so much

  7. Works for me on a Lenovo laptop with a WD5000BPVT-24HXZT3 hard drive running Windows 10! Nice catch!

  8. I have been having this problem since windows 7, through windows 8 and now windows 10. Finally a solution that works, thank you so much! :D

  9. When I discovered my pc got random freezes also 100% disk activity with no Read or Write and \Device\RaidPort0, was issued found in my Event Log, and then I found this blog.

    I personally doesn't try with this fix (changing registry) instead I tried bumping my FX-8350 (undervolt) vcore from -1.4v to -1.0v and set my DRAM voltage to auto (which is 1.5v).
    I'm using Windows 10 and so far no random hangs or freezes, but I'll keep an eye to Event Log if in case there still had a problem.

  10. Worked great for me! Running a Toshiba Satellite S855D-S5120 with a fresh install of Windows 10. Thank you very much for your guidance!

  11. Great! Works like a charm (Asus Netbook Core Duo, W10 64bits)

  12. Excellent ! Works perfectly
    Many thanks from France

  13. works well with Dell Inspiron i7559-763BLK with SanDisk Z400s M.2 2280 256GB SSD, Great work.

  14. No more storahci errors after firmware update:

    Windows 10 64bit

    1. This comment has been removed by the author.

    2. Been tracking down this problem on my HP Omen for months now. Just updated. Half expecting the bug to reappear, but if it doesn't - BIG TIME WIN !

  15. Any help with this part? I don't get it.

    There are hardware ID's with asterisks at the end in part 3 but not at part 4.

    What do I need to change here?

  16. Works on Lenovo Y500 Laptop fresh install.

  17. awesome!! it works for me. thank you! asus x502c, ssd kingston kc400 256gb.

  18. I started getting the storahci error and forced to reset my PC after the Win10 anniversary update.
    My system: GigaByte mobo, i3, SSD + HDD - The error occurred whenever doing a large file copy on the HDD.
    I tried the suggestions above but they didn't fix it.
    Problem was solved by updating the driver from the GigaByte website : Intel AHCI driver : mb_driver_intel_irst_100series
    Hope this helps someone else as well.

  19. If you don't want to mess with registry just change battery mode to high performance and get rid of these errors. (but in background it changes these values which is mentioned in the OP )

    1. doesnt work...however the steps highlighted int he main post worked well for me.. i dont have samsung SSD......

  20. This comment has been removed by the author.

  21. Thank you very much! Only this manual worked for me and I've tried a lot!
    Best regards!

  22. This is a very good guide.
    But I do not understand step 3 correctly. Can someone explain this to me exactly?
    Double-click NoLPM and overwrite it? If so, what exactly? With the punctuation marks * and -?
    How does this have to look exactly? A screenshot would be great.
    Thank you very much

    step 3:
    "3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci\Parameters\Device
    Set NOLPM to * - those keys contain several hardware ID's (vendor and device) for storage devices. Setting NOLPM to * disables LPM control messages to any storage device."

    1. Just add an asterisk to the end of each key when you double-click on either NoLPM or SingleIO. No space between the asterisk and the key. Of course, dont erase ANY of the keys!

      WDC WD740ADFD?00NLR1*
      Maxtor 6V???E0*
      Maxtor 6V???F0*
      Maxtor 7V???E0*
      Maxtor 7V???F0*
      SanDisk SSD P4*

  23. Wow, it worked. Thanks!
    To be clear, I setted NoLPM and SingleIO to "*".

  24. It work with me ,however more a bit, i disable "SATA Aggressive Link Power Management" in BIOS setting (a technology help your disk goto sleep overtime for save power) ,now everything work for me, no more freeze, no more 100% disk, Thank you so much.

  25. This is totally NOT a great post, and I am just shaking my head with all the people saying "wow, thx for the help, this worked for me" blah blah blah blah... Why do people never have any brain or can think logical on their own!? This is just a damn dirty WORKAROUND, which brings in 10 new problems for """fixing""" the one other problem. It might """help""" on a desktop or maybe a laptop, but it is a devil in the box solution, especially for tablets. Why? Because it deactivates the energy saving of the whole AHCI link, mostly even PCIe too. Meaning, a desktop user wont notice it, BUT, a tablet, will stay WARM all the time even in connected standby, and drain about 2400mWh which is a TERRIBLE solution to this problem. Why am I writing this? Well guess what... my "brand new" Dell Venue 11 Pro 7140 which I bought on ebay, has this issue too, on the newest Windows 10 build. Nothing worked... lots of Even 129 and BSOD of disk errors in the event log, whenever the tablet went connected standby. Turning off the AHCI power management helps for the freezes and bluescreens, but the tablets battery is faster empty than you can say faster empty.

    So I might wish to know... whats the REAL issue here? Is it a bug in Windows 10? I dont think so. Is it a bug in the SSDs firmware? I cant believe that, because I have seen a wild range of SSDs with this issue now in several forums. So what is is? Why is it working on like 99% of machines but on some not? Is it a bug in a devices bios? I have contacted Dell about this, and of course oh wonder, they know nothing about this issue...

  26. I disagree with mkdr that the post is bad advice.

    To answer the question though, this error can be caused by a bunch of different causes. I was getting 'Reset to device, \Device\RaidPort1, was issued' on my new machine that uses a Samsung 960 Pro 1TB.

    The root cause can be:
    1. Poorly validated motherboard firmware
    2. Poorly validated SSD firmware
    3. Failing SSD
    4. Failing motherboard

    No particular order, if you haven't made any changes to your system config in recent months, then it's probably 3 or 4. If you have, or you just put it together, 1 or 2.

    If it is a poorly qualified drive or board, the power changes you'll find online may resolve it. In my case, nothing helped.

    In modern machines there is pure UEFI mode & CSM (BIOS/legacy) mode for device initialization. Both paths need to be validated for all the different hardware out there. Usually, one of the two suffers, BIOS may work better with a drive than pure UEFI, or both may suffer. Intel is ending BIOS support in 2020 to help resolve that additional burden.

    I spent months on this. On my machine, I resolved it by switching from pure UEFI mode, to enabling CSM/BIOS mode for everything that I could. Of course that entails formatting your OS at least if you're on Windows.

    After updating all the firmware for your motherboard, SSD etc and the issue persists, there's nothing wrong with disabling power management features. If it resolves the issue and the system works then I'd recommend you stop there. Or if you still want to, try another brand of SSD, or another motherboard. There may be nothing wrong with your SSD or board, could just be a minor power saving incompatibility.
    I'd just wait until you need a new computer rather than replace anything unless the issue persists. It's not going to hurt anything other than use a tiny amount of energy. It would likely take decades to burn up enough to equal what you could spend on new hardware.

    Hope this helps someone.