Open up registry editor and change the following settings. Here is how i solved the issue:įirst of all we need to change " AHCI Link Power Management" which is a hidden setting on power management. I had exact the same problem on quite a lot of my dell systems. If anyone from AMD checks the forum maybe you can coordinate with Mushkin to see what is causing this as people have noticed this issue and noted it on as well. If not and the drive manufacturer doesn't have a solution I'll be going back to a single boot disk and just storage drives in RAID. If anyone else has any ideas I'm all ears. A failing drive can temporarily delay response to the controller causing what you are seeing as well. Usually this error may mean that there is a failing drive in your system so to rule out that you may want to try Crystal Disk Info, hddscan, or Hard Disk Sentinel to test your drives. So far I have been unable to fix this issue. Tesladev as for your issue I would suggest you try some of the fixes I was referenced to online as it is likely a similar problem with the chipset controller. I contacted the SSD manufacturer yesterday because if this isn't going to work I want to return the drive while I still can.
Tried windand 1703 thinking maybe it was related to the reported difficulties with intel ssds on 1803.
Different versions of the PreBoot Raid drivers and 3 different Gigabyte BIOS revisions for the x370 Gaming K7 and nothing works. I tried 3 clean installs with different raid cache settings. The following information was included with the event: "If the event originated on another computer, the display information had to be saved with the event.
You can install or repair the component on the local computer.
Either the component that raises this event is not installed on your local computer or the installation is corrupted. The description for Event ID 129 from source rcraid cannot be found. (Mushkin Reactor 1TB) and as soon as I made a new RAID 0 array for my boot drive I began having the system freeze up for 10-45 seconds and in my system Event log I get the following: I recently purchased a 1TB SSD to raid with an identical drive. Unfortunately I have a similar problem but not with StorMI. Uninstalled and reinstalled StoreMI software (didn't break my tier) SeaTools Scans (SMART, Short, Long (bad sector scan), all passed)Ĭonfigured Power Settings on the AHCI controller (recommended via the web) Windows Update-Install (to ensure Windows wasn't the issue)
Update (List of things I've tried so far): I've tried adjusting power options and updating my chipset/bios to the latest. I have uninstalled and reinstalled the storemi and I am still getting this error.
The source is envirtahci, which I tracked down to the AMD Virtualized AHCI Controller for Ryzen 400 series. Eventually I tracked it down to occurring when Event 129s started appearing in my Event Viewer every minute while these freezes are occurring. After several months of having zero issues, my system suddenly started having freezes and apps not responding. I am running a Store MI tier drive for my data (games) drive with an NVME SSD and HDD. Asus Strix x470-F Gaming, Bios Revision 4018 (latest).3 (fast tier) + Seagate 4TB BarraCuda SATA 6Gb/s 256MB Cache (ST4000DM004) (slow tier) Drives in storeMI tier: Corsair Force Series MP500 240GB M.2 NVMe PCIe Gen.