There was an old thread from a year ago talking about something similar but there were no posts from any intel support staff and no concrete solutions found, so I'm starting it anew....
I'm on an EVGA Mobo with the X58 chipset, and until today was running the Intel Matrix Storage Manager. Over the last 6 months I've RMA'd 6 western digital hard drives thinking I just had really bad luck. I discovered after the 4th RMA that I'd purchased their standard drives which are prone to being dropped from RAID setups, so I purchased 4 new Enterprise level RE3 drives and set them up in a 1+0 array. Since then I've had two more drives drop randomly almost a dozen times, each time forcing me to "Set as Normal" and have the array rebuild itself. This is obviously not a problem with the drives, nobody has this much bad luck.
After searching around I discovered that Intel Matrix has now evolved into Intel Rapid Storage Technology and that they were at least a couple releases in so I decided that with any luck the new system might address these drive dropping issues. I upgraded. I now have RST 10.6.0.1022 installed. All seemed to be fine until I tried to open up the UI to explore and get used to the new system.
Instantly I'm presented with "IAStorUI has stopped working".
- I'm on Win7 x64, and am completley up to date on drivers.
- I've double checked on my .NET framwork and "Repair"-ed my current 4.x install.
- I've restarted half a dozen times.
- I've tried running all aspects of the intel software with Admin privileges.
I'm at my whits end here. If another drive drops out of the array and I don't have the ability to get into the UI to "Set as normal" again, I'm boned. Here is the error report from Windows...
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: IAStorUI.exe
Application Version: 10.6.0.1002
Application Timestamp: 4dd69f61
Fault Module Name: unknown
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 00000000
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
I'd really appreciate it if someone could explain what's going on, and how I'm to solve it.
Regards,
Kevin.