Event ID 129 – storachi - Reset to device, DeviceRaidPort0, was issued.
<!--[if lt IE 9]>
<![endif]-->
Comments
Anonymous
January 01, 2003
I really appreciate this blog entry -- I was having serious issues with my Blu Ray drive being reset in the middle of various operations, and thought maybe my motherboard was starting to fail -- you saved me from replacing it in vain. Awesome information.Anonymous
January 01, 2003
thanksAnonymous
July 07, 2013
Apparently it solved my computers problem. The same hanging off the system happened as stated when I re installed windows 7 for my Dell XPS 1340.Anonymous
July 12, 2013
Seems to have solved this issue on my Intel DH87MC mainboard. For the benefit of future readers, there is also a setting for Link Power Management under "Performance" in the Intel RST console.Anonymous
July 14, 2013
Hi, unfortunately the power setting in the Intel Rapid Storage Technology software doesn't help. Just started my Computer and the event log has this error again logged 3 times. But now I will also try the above mentioned power option integrated in Windows 7. Please note that this didn't happen BEFORE I installed the IRST ... I don't know if this happens also with Intel SSDs, or if it only happens with SSDs from other manufacturers. If the latter is the case then you can assume that Intel is doing that on purpose.Anonymous
July 20, 2013
Thanks for the write up, this helped my issue.Anonymous
July 25, 2013
The power settings have not changed anything for me. I stil get the reset. This has plagued my Dell XPS for 5+ years and there does not seem to be a solution. Do not buy anything with nVidia in it!Anonymous
July 31, 2013
I have the same error on my Win2008 R2 server and the settings did not fix the error...Anonymous
August 18, 2013
I noticed this warning in the event log as it occurred 4 times on August 18, 2013. The source for me is "amd_sata" simply because I have an AMD board with AMD AHCI sata driver. I filtered the log and found that the same warning occurred 20 (TWENTY) times on January 26, however, it never happened in the months between January and now. I have no idea what caused it and I doubt that turning link state power management off will solve the issue.Anonymous
October 01, 2013
Hi, I've the same Dell Precision 690 2xXeon E5345. 12 G Ram, 3xHitachi 143 SAS 15k, running into RAID 0 (Stripe) mode (LSI Raid SAS Controlle). OS is Windows Server 2012 and I''ve the same issue. I've changed the power option, but that doesn't help. Can you share if there is some specific BIOS configuration, in order to make it work correctly. I've updated all the drivers and I've checked the system with Dell utility from the dell.com site. It says everything is up to date. Thanks in advance,Anonymous
October 18, 2013
I rebuilt this same system with Windows Server 2012 R2 and was experiencing the same issue. I made the same change, and it resolved it, again. So, this continues in Windows Server 2012 R2.Anonymous
October 31, 2013
I had this problem as well, Win 7x64, AMD PII 925 4 core, Asus M4A79XTD Evo, Nvidia GST450, running 3 Hitachi Deskstar 1TB drives, primary boot drive configured IDE, other 2 drives configured AHCI and setup as a mirrored pair (Win 7's inbuilt "RAID 1"). Had never had this issue before, but after a clean reinstall for other issues, I found 20 of these warnings in my Admin events log the next morning. There was a clear pattern, a pair in rapid succession (about 18 seconds apart) and then another pair about every 20 min. I checked the advance power settings and my PCIE link power state setting was already set to off. But I noticed that the "Hard Disk - Turn off hard disk after" was set to power off the disk after (yep you guessed it) 20 mins. Setting that to "never" has seemed to resolve this issue for me. I've got 5 Win 7 machines in a home network and this is the only one that has had this problem. It is also the only AMD based machine and the only one with some of the SATA ports configured as IDE (win 7 x64 would not accept the AHCI drivers during setup, said they were unsigned, which meant I could not setup the boot drive as AHCI, so I configured the 2 SATA ports that could be setup as IDE while still leaving me 4 ports that could be setup as AHCI or RAID, and used those 2 ports for my boot drive and my DVD). Have not been happy with the AMD product. The AMD RAID configuration was so bad I dumped it and used the inbuilt Win 7 mirroring feature instead. Could not gtet any info on the physical drives in the RAID array (had a long discussion with the guy who created Hard Disk Sentinel about this and it is a problem with the AMD firmware and drivers), and AMD only reports a temp for one core which is just idiotic. This will be the last AMD based system I ever build.- Anonymous
October 17, 2016
Thank you, this helped with Hitachi Deskstar 1,5 Tb on Windows10 x64. Before that "event 129" was occurring with every disk addressing ,sometimes about 2-5 times a minute.
- Anonymous
Anonymous
November 24, 2013
Hope this fixes my system hangs, its either this or the stupid bing weather app errors in event viewwer.Anonymous
December 02, 2013
Thank you! Solved my problem on a Surface pro 2.Anonymous
February 19, 2014
Have the exact same issue, i keep getting the warning every minute. It can hang for 2-10 minutes and it will come back. tried this solution, but doesn't change anything I'm afraid...Anonymous
May 04, 2014
This sounds good. Been searching alot for a solution and I think this is it! Thanks.Anonymous
May 22, 2014
The comment has been removedAnonymous
June 14, 2014
Thank you, it worksAnonymous
June 14, 2014
I too had this issue, and to solve it I had to take 2 more steps: Change the value on the option "Hard Disk - Turn off hard disk after" to "never" and Disable my DVD Driver (it seems that it is failiing badly).
Thank you for the post -Anonymous
June 17, 2014
I had this issue after reinstalling windows 7 on an Asus Maximus V Gene (Intel Z77) mainboard. I might not have had the IRST installed before, but now I do since reinstalling, I have this problem.
I have an SSD installed for the operating system, but the system hang only occurred when trying to access a regular harddisk. Windows would respond normally (I could find this website for instance), but the explorer window where I was browsing the second harddisk would hang. As soon as I made the change in power settings, the explorer window snapped out of it and the file I had clicked inside it opened.
I''ll keep an eye on the IRST software to make sure it doesn't change the value back to power saving.Anonymous
June 30, 2014
I had same issue with HP server running backup from unix OS, the server is 2008 R2 enterprise. When we are running full backup its getting failed one of the server which is running this OS. We change the power settings as its mentioned but still we are having the same issue. Backups are keep on failing. Pls suggestAnonymous
August 01, 2014
I had to turn off Link Power Management in both the Intel Software (requires a reboot) and in the Windows Power Management settings show above. I have a Samsung 840 Pro SSD.Anonymous
August 08, 2014
The comment has been removedAnonymous
August 09, 2014
Confused about the final settings to choose. Are these the settings to use to address the problem?
(HIPM = Allow Host-initiated Interface Power Management; DIPM = Allow Device-initiated Interface Power Management; HIPM+DIPM = Allow Both Host-initiated AND Device-initiated Interface Power Management; Active = Do NOT Allow either HIPM or DIPM)
Thanks.Anonymous
August 12, 2014
I discovered the correlation between the periodic system hang and the Event ID 129 log entry on a HP Envy Notebook running Windows 7. Turning off Link Power State Management seemed to fix the issue. When I found this blog entry, I considered it the confirmation I needed. So thanks for posting and for all the good comments too.Anonymous
August 12, 2014
I discovered the correlation between the periodic system hang and the Event ID 129 log entry on a HP Envy Notebook running Windows 7. Turning off Link Power State Management seemed to fix the issue. When I found this blog entry, I considered it the confirmation I needed. So thanks for posting and for all the good comments too.Anonymous
August 14, 2014
A Windows Server 2012 was performing so bad that applying this solution took me 1 hour to get the events out of the eventlog and 1,5 hour to apply your solution. It solved the problem perfectly. Thanks.Anonymous
August 16, 2014
The comment has been removedAnonymous
September 02, 2014
This resolved my issues. Thanks!Anonymous
September 15, 2014
Turning off LPM in the Intel RST had no effect. I had resets of the bus every 30 seconds (including a strange sound from the CD rom). But turning off the PCI-express energy option shown here has helped to have a quite system again. Thanks a lot!Anonymous
October 03, 2014
Thanks! This was enough of a clue for me to finally fix an issue which had been affecting my system for a month or so which until now I had no clue how to fix. I've now resolved the problem.Anonymous
November 11, 2014
You the man Kevin! Ive been looking all over the internet for a solution after just building this brand new computer. I ran a lot of test to check things and your solution just fixed it. Thanks!Anonymous
November 26, 2014
The comment has been removedAnonymous
December 07, 2014
I'm slowly losing my mind to those issue myself. I have a Lenovo Y40 laptop, consisting of a i7 processor, Liteon 256GB ssd, 8GB ram, AMD R9 275X dedicated gpu. This thing freezes up for the 20-30 seconds in windows, games, media, whatever - with this same event ID. I've tried setting the Link power management from HIPM to DIPM and then to Active, none of which help. I've checked for any updated bios and drivers and I appear to have the latest of everything. What could I be missing?Anonymous
December 13, 2014
It didn't really help me. I turned it off and the problems vanished for a couple of days, then they came back. I used the registry trick and disabled the HDD low power settings too, didn't help either. Now I turned both settings on again and I didn't notice and hangs for the past 2 days. I have no idea what's the cause or how to solve it, other than it seems to be the AHCI driver.
It seems to happen at random. I used a ThinkPad L440 with Windows 8.1 x64 and a Crucial MX100 SSD. I feel like it is a problem with the Intel AHCI driver and they need to look into it.Anonymous
January 05, 2015
I'm having the same problem with a new PNY Optima 240 G SSD and a fresh install of Win 10. None of the other fixes have worked yet for me.Anonymous
January 07, 2015
The comment has been removedAnonymous
January 15, 2015
Thank you, I have had this issue every time I did a clean install. I fixed it before but didn't document the settings I was changing. Your solution seems to be the key! Thanks again!Anonymous
January 19, 2015
I finally found a solution to my problem (four post above it is posted). I changed my SATA AHCI driver in the device manager. I even still use the Intel driver (didn't change to the basic Microsoft one), Just go to properties->update driver, then let it give you a list of drivers on the PC and select the Intel driver with the "8C03" at the end. No more hang ups since then!
Hope this helps!Anonymous
March 06, 2015
In my case the reason was a weak sata cableAnonymous
April 02, 2015
I tried everything to fix this - BIOS AHCI power settings, the power settings in this blog, upgrading the Intel RST drivers, upgrading the USB 3 drivers. Nothing worked. I've finally managed to fix it by disabling write caching on the disk using Device Manager. Three days now and not a single 'reset to device' or 'the logical operation at the address was retired'.Anonymous
April 13, 2015
thank youAnonymous
April 29, 2015
Thank you very much! The solution has worked for me.Anonymous
May 09, 2015
Just posting to say thanks for the write up!
I am having same issue and have changed the setting. Hope it fixes the problem for me.Anonymous
May 26, 2015
Seems to help a lot, but got that same pesky error again today, sorry to say. I'm still thinking that the fix given is a big help.Anonymous
May 28, 2015
Thanks! Was a partial solution. With my Win 8.1 laptop and a new Crucial MX100 256GB SSD, it got lots better after the mentioned tweak, but the error still happened on occasion. Just updated the Crucial SSD firmware from MU01 to MU02, and hoping that this will take care of those few errors.Anonymous
September 02, 2015
Thanks, great post! I was getting the issue on a lenovo Y410P ideapad laptop running Windows 10.Anonymous
September 07, 2015
The comment has been removedAnonymous
December 14, 2015
Tanks to author and Erik (page 2 of discussion)!
I received the same issue after upgrade from Win 8.1 to Win 10 on the system based on MSI FM2-A85XA-G65 board. (Have to say: performance on 8.1 was OK.)
I even tried the complete installation (with system disk format) - no avail.
I found this article: http://blogs.msdn.com/b/ntdebugging/archive/2013/04/30/interpreting-event-153-errors.aspx?PageIndex=2#comments
which points out that possible cause of the conflicts may be SATA driver.
So I change (in BIOS Setup) my disk controller interface from AHCI to IDE and reinstall Windows 10 again. It seemed to cut the problem at the very same root!
For the sake of curiosity, I tried also clean installation with controller in AHCI mode and set of "PCI Express Link - Link State Power Management" to OFF state - it does not help.
I also tried to change only hidden power management setting "Hard disk - AHCI Link Power Management - HIPM/DIPM" to "Active" and it worked for me!
Conclusion:
IDE mode
- IMHO, switching controller to IDE interface in BIOS is safer and more persistent (it's less likely anyone will change it back without notice)
- Switching to less problematic (for Microsoft problematic) interface seems to cut the the problem at the very same root
- There may be performance drawback (disputable) against AHCI mode
- Very likely, Windows would not boot after switching the controller mode in BIOS (very likely, they don't not have any IDE drivers installed at the moment)... so you have to reinstall Windows to get proper drivers on board. Possibly, there are other less dramatic scenarios how to fix this (installation with fix/recovery option, forced installation of IDE drivers before the change in BIOS...) but I did not try anything of this.
Power Management correction
- non-invasive fix (nothing need to be reinstalled)
- you have to manually change the registry to make this change (not a big challenge...)
- updated settings may be unintentionally lost by switching to another Power management profile, or by reverting current profile to defaultAnonymous
January 06, 2016
I experience the same problem.
My platform is AMD APU with A75 chipset, and a Plextor M6V SSD.
When I open Chrome or history of Firefox, I always waiting at least 1 minute and can find ID 129 in Event Viewer.
I changed the Link State Power Management to off and reinstalled AMD chipset driver, but without luck.
Finally I tried to find a SSD firmware update and in release notes says "“Power management ” mechanism to improve compatibility for potential problem that drive might hang under specific condition."
After updated firmware, the world is quiet.
So, fireware update is should be a consider of solution.Anonymous
January 31, 2016
Thanks very much - experienced this on both Windows 8.1 and 10, exactly the same symptoms. All resolved now.Anonymous
February 05, 2016
Also suffering this problem since upgrading from Windows 8.1 to Windows 10, with a AMD A8-6500 APU and Gigabyte F2A88XM-DS2 motherboard.
Drivers for everything are at the very latest version.
Firmware for the motherboard is also latest (F8c) as is the SSD firmware.
I've tried:
- chkdsk
- sfc /scannow,
- creating new users on the system so they have clean profiles
- clean install of Windows 10
- cloning the SSD to a completely different (newer) brand
- memory testing software
- different memory
- different sata cables
Hopefully this power management setting does the trick and I don't have to change from AHCI to IDE and reinstall. Will post back if this has fixed it. Thanks!Anonymous
February 09, 2016
The comment has been removedAnonymous
February 18, 2016
Awesome! I think this solved my problem. My music collection is on a second drive that doesn't get accessed frequently. Since switching to Windows 10, I found iTunes would periodically freeze for 20-30 seconds, a few times per hour. The event log showed warnings like the one above coincident with the freezes, and a Google search led me here. I've turned of the PCI Express Link State Power Management setting about an hour ago and there hasn't been another freeze since then.Anonymous
February 18, 2016
buena aportacionAnonymous
February 23, 2016
thank you for the detailed explanation, very helpful!Anonymous
March 27, 2016
The comment has been removedAnonymous
April 08, 2016
No more storahci errors after firmware update:http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=7152804&swItemId=ob_162663_1&swEnvOid=4192Windows 10 64bitAnonymous
May 05, 2016
Helpful info, thanks. Note that you must hit apply and reboot the computer for the setting to take effect... make sure you double check after the reboot to make sure it stuck. Also, if you have Intel Rapid Storage Technology installed, make sure you disable "Link Power Management" on the performance tab so that software does not try to re-enable the setting.Anonymous
May 31, 2016
I got this error as soon as migrated to windows 10 and Office 2016. I've run check disk and did some Power settings adjustments proposed in dozens of articles. After I realized that error is generated while working with Skype for Business 2016 and Outlook 2016 in parallel, I've fixed the issue by updating Office 2016. I do recommend before someone starts trying different solution try to identify exact applications/drivers that causes this error event.- Anonymous
June 23, 2016
EDIT - in fact update of Office 2016 just reduce the error but update of Intel Rapid Storage Technology solved it.
- Anonymous
Anonymous
June 10, 2016
The comment has been removedAnonymous
June 16, 2016
Always thought it was because of my browsing habits tending to fill up with many, many tabs, would typically stop doing it if I killed the browser and restarted the session (though it would eventually go back to doing this)After months and months of this happening here and there, I finally checked the event viewer, quick google came here. So if this does fix it, then I cannot express enough thanks :)Anonymous
August 10, 2016
Thank you a lot for this blog post. I started getting these errors on my Windows 10 x64 after Anniversary Update.Following your advice to switch off PCI Express > Link State Power Management resolved the issue.- Anonymous
September 06, 2016
I had absolutely the same symptoms with my Win10 HP notebook after the Windows 10 anniversary update (1607). Turning the PCI Express Power Saving stuff to "Off" solved it.
- Anonymous
Anonymous
August 20, 2016
The comment has been removed- Anonymous
September 03, 2016
The comment has been removed
- Anonymous
Anonymous
October 21, 2016
Posting this in case somebody else might be having the same issue. I was receiving "Reset to device, \Device\RaidPort0, was issued" errors in Event Viewer. It was always one SSD (of three) that seemed to be failing when this happened. I consulted my ASUS Maximus VI Formula motherboard documentation, and discovered that my SATA 5 port would automatically disable if another function of my motherboard was used (another mini card that provided wifi). This would explain why the drive would work sometimes, and fail others. I moved my drive to another SATA port and all is well.Anonymous
November 11, 2016
fingers crossed. 3 comments today after no comments in 3 years. maybe a bug in a recent update.- Anonymous
November 11, 2016
oh there are more comments i didn't see. still maybe it is win 10 anniversary update as stated elsewhere
- Anonymous
Anonymous
December 31, 2016
The comment has been removedAnonymous
January 23, 2017
The comment has been removedAnonymous
January 25, 2017
I have a brand-new Dell Latitude E7450...it's 3 months old. It is running Windows 7 Enterprise and I will be moving to Windows 10 around the first week of February 2017. I have had this problem since the day I got it. I have gone to Dell's website and updated my BIOS and all my drivers. I have verified that my PCI Express Link Stated Power Management is set to "OFF", for both battery and plugged in mode.Yet this problem continues to plague me AT LEAST once a day, usually more like 3-4 times per day.Anonymous
February 19, 2017
The above did not solve the problem on my system.The following solved the problem:In registry editor open:HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60 Change attribute from 1 to 2.Open Power Options from control panel. Now there is a new option under Harddisk: AHCI Link Power Management.Change it's setting from HIPM/DIPM to active.This solved the problem.BTW.: My "hangs" were always exactly 30 seconds long and started when I replaced a normal harddisk with an SSD.Anonymous
March 07, 2017
This did not resolve the same error I am experiencingAnonymous
April 04, 2017
Awesome, thanks! My laptop was set to "Maximum power savings," both on battery and plugged in. I've been receiving this 'warning' in Event Viewer once daily for months. Very glad you shared!!Anonymous
June 24, 2017
Thanks for the post,not worked for me..... with me the issue related to the intel graphic drivers,,, solved with installing the right driver for graphic.- Anonymous
July 30, 2017
All the above solution still fail me, ive clean installed win 7 so many times it hurts, fresh build gtx 970, kaby lake processor asus gene vii.I still see the IaStorA, issue ,to add to this post, there are further energy saving options available in asus rog mobos, which deal with taking away the power of the OS to deal with ASPM, so be wary.Even with all that disabled, i still get it so im very stuck. Still in July 2017
- Anonymous
Anonymous
July 31, 2017
My reply to my above post which i think i've now fixed, on a clean win 7 install the errors and hangs go away has been running fine for 24 hours will keep updated.Solution: If you have a Asus ROG MOBO, DO NOT install the IRST from the MOBO CD provided, i honestly dont know what happens or why, but i can reproduce this, as soon as you install IRST from the CD, even if you uninstall it after, the errors seem to be are permanent and hangs start to occur. I have yet to check if installing IRST from the intel website or the Asus website helps, but in all honesty im probably not going to bother trying, since i dont really know what IRST full does.Similarly DO NOT install the USB drivers from the disk if you are installing windows 7 on a new Asus mobo without a USB2 port, the IaStora errors also stopped my USB input for some reason until reboot, so if you install the USB drivers they'll clash with the installation USB drivers (i used the ones from Asus website to make my installation usb), not sure how ill overcome the usb 3.1 drivers, but ignoring it since i dont have a need for 3.1. My build now runs smoother than ive ever experiencedCurrently going through the CD to see if any other software from the Asus disk affects the situation, i would like AI suite back but i dont know if its too big a risk, i really dont want to clean install win7 again.- Anonymous
July 31, 2017
turns out usb issue was separate from iastora issue, i installed the 3.1 and 3 drivers from disk , issue reoccured, teamviewered into comp since usbs disabled, no error logs or anything, i uninstalled the ASMedia USB 3.1 XHCI 1.1 Host Controller from device manager and suddenly usbs came back, still testing if that was the issue, i can no longer install 3.1 drivers from disk after uninstalling that for some reason. Oh well
- Anonymous
Anonymous
August 27, 2017
How do I find which drive is this happening on, for example I have only "Reset to device, \Device\RaidPort2, was issued." but I have 3 HDD and SSDsThanksAnonymous
February 16, 2018
This is awesome! Thank you for posting this. Hopefully it solves my issues. It's been happening on my Dell Latitude. It came with an HDD, but I threw in the SSD from my old laptop and that's when I noticed it happening. I assumed it was CPU or RAM issues, but I was getting almost the exact error that you reported.Anonymous
August 10, 2018
The same issue happens in windows 10 version 1703 on dell n5010 with intel rapid storage driver and it seems that your suggested solution is working.Thanks for sharing