This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 62%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPT%3C/text%3E%3C/svg%3E)
Since upgrading to Windows 10 my machine has been freezing for about 30 seconds at a time. I've tracked this down using event viewer to the dreaded Error 129, with a source of storahci. I've made sure my SSD firmware is up to date (according to the manufacturer), and Device Manager tells me that the disk drivers are all up to date. I see that the AHCI driver (storahci) is dated 2006, which well predates Windows 10 - is there a better one somewhere?
Most of the time these events are associated with playing games or watching videos, so it is possible that the graphics card (or its drivers) is responsible. However, when I logged in as an administrator just now, the machine froze for several minutes with 6 consecutive error 129s.
This is becoming untenable - it stops me viewing/listening. It all worked fine with Windows 7.
I've seen various threads (fairly old) on this subject, but nothing recent. Are other people still getting this, or have they managed to cure it?
Configuration:
Mobo: Asus P7P55D-E (from about 2010).
Graphics card: NVidia GeForce 210
SSD: Samsung 60 EVO
HD: Western Digital WD1002FAEX-00Z3A0
USB drive: Western Digital Passport
OS: Windows 10 Home build 1903
Hi
“Event ID: 129 Source: storahci” indecstes: IOs to the disk were paused because the storahci driver was in an inconsistent state.
You could try changing "AHCI Link Power Management" settings following these steps:
I hope this information above can help you.
Thanks @Dale Kudusi
It didn't work I'm sorry to say. Even after a reboot I got some error 129s.
Very frustrating
Sorry that was meant to be a comment
Try this right click on the AHCI driver in Device Manager, and select Update driver. Does a new driver get downloaded from Windows Update?
There's no new driver, but there is a pending update (KB4497165) which I'll apply in case it makes any difference.
And after applying the update the ACHI driver's exactly the same ,and I got an error 129 from it. Sorry, but nice try.
Hi
I’m sorry that this issue hasn’t been resolved, you might need a thorough investigation on this issue.
Please understand that from our professional level, we do not provide dump/log analysis. In addition, if this problem is more urgent for you, I still recommend that you open a case to Microsoft for further professional help.
https://support.microsoft.com/en-us/help/4341255/support-for-business
Thanks for your understanding and cooperation.
Thanks @Dale Kudusi If I were a business, that might be an option. As it is, I'm a private individual. It's a **** nuisance having to stop work (or play games) for sometimes minutes at a time.
It looks as if some component of my rather ageing self-build PC is incompatible with Windows 10 - if only Microsoft had been more upcoming about incompatibilities it would have helped.
There's a bit more information that might help: the System Information Conflicts tab gives this, which implies that the graphics card might be interfering with the PCI-PCI bridge in some way (see screenshot). Unfortunately I don't know enough about Windows to work out if this is significant.
Hi
Information on the screenshot isn’t error massage but a list telling us which device is using I/O.
I’m afraid there isn’t much we can do at this moment without a specific analysis on the logs and monitoring of the process.
I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below:
Global Customer Service phone numbers
https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers
Thanks for your understanding and cooperation.
Thanks again.
I'm sure that the problem isn't directly with MS code, but with the driver support for my rather antique kit. But if MS says that the kit is OK for Windows 10 (which it did), then it should work.
I don't think I have the money to pay for consulting fees. This problem has been the subject of many forum (not this one) comments in the past 4 years, and it's time that MS got round either to providing a fix or better diagnostic information. Without having done any research, I would guess that a new computer would be cheaper.
I can't use the telephone due to a medical condition - no voice.
Hi
I’m sorry this issue hasn’t been resolved.
Check out this user answer in this thread with similar issue:
https://answers.microsoft.com/en-us/windows/forum/windows10-hardware/event-id-129-storahci-resetting-raidport0/7b30c512-6597-438b-80cb-22fb2f85d62e?page=6
also, you could try updating your driver from official site from your hardware provider.
Something to consider: if you upgraded to Windows 10 using in-place upgrade, you could try reinstalling Windows: Reinstall Windows 10
Please back up all the date you want to keep.
As you mentioned, there might be hardware issue since it has been running for years, you could try to contact with your PC/hardware provider, or post your questions in their official forum for more clues: