For the past several months I've been experiencing a problem while startng windows, the first thing to appear is an Intel Rapid Storage Technology message on BIOS, saying that an Error Occured (0,1) in one of the two SSD disks that I have with a Raid 0.
Here you've got some photos:
So, what I've been doing so far is "Mark as normal" this problem in the IRST but after aprox 2-3 months the black error screen appears again and I mark it as normal again, and so on and so on.
What I am asking for is some help with that, and if possible please explain it as for a person that has almost no idea of this stuff.
I checked both SSD health and performance with different programs and it's always 100%. I checked for errors in hard disk and none were found.
The only options that the initial screen gives me are to Delete Raid Volume or to Reset disks to non-Raid but however I doubt any of them will help or are actually the solution. However Windows boots well and doesn't seem to have any problems, as I said I've had this 0,1 error for months, always marking it as normal when it appeared but I'd like to get rid off it now.
I don't know if it has something to do with it, but my laptop initially had Windows 8 on it and then I upgraded to 8,1 and then to 10.
Laptop model: Asus ux32vd-r4015h
Any help will be appreciated,
Thank you very much for joining the Intel® Rapid Storage Technology communities.
First of all at this point we recommend to do a back up of all the important information located on the RAID 0 configuration.
To answer you inquiry, it seems to be there is a hardware problem with the SSD itself, and under a RAID 0 environment we recommend to replace it, since it could get defective at any time and the information on the RAID 0 will be lost.
What happens when you choose the option, "Mark as normal" is that the IRST ignores the error and that is why you can use the laptop normally for a few months, but as you mentioned above, the error will come back again.
Please connect another SSD that has the same size or bigger and do not disconnect the hard drive that is showing the problem, eventually when the error shows again, the IRST automatically will disable that SSD and use the new one.
On the picture below you will see the instructions of how to replace the SSD using the "Mark as spare" option, please read carefully:
Just to let you know, if the laptop does not have an extra port to connect the new SSD, then in that case please do the back up of the information, replace the SSD and create the RAID 0 from scratch.
I hope this information was useful for you.
Any further questions, please let me know.
Thank you for the response.
However, I am a bit confused now, because yesterday I sent this requests twice - once in spanish and once in english, and I got a different answer from your collegue. See link:
So in general it seems that I get this error message wrongly and that everything is fine with both SSD, as it looks like my laptop model Asus UX32VD doesn't support Windows 10, and I didn't know that before upgrading from 8.1 to 10. Actually I started getting this Error about a week after I upgraded my system to Windows 10, so that might be the reason.
So, since at that point I can't get back to Windows 8.1 anymore (more than 10 days have passed since the upgrade was made), I would just have to keep "Marking it as normal" in IRST every 1-2 months, when it appears.
As I said, I checked the status of both SSD with different programs and they all stated 100% health and performance and no SMART errors.
If you would like to add something more as a recommendation, feel free to do it! I really appreciate your help.
You are welcome.
Thank you very much for letting us know that information, we really appreciate that.
In this case, if the laptop is not fully compatible with Windows® 10, then it is expected to get those errors regarding the RAID configuration. Based on the fact that you tested the SSDs already with different programs and they show no errors that indicates it could be a compatibility problem between the laptop and Windows® 10.
And yes, to keep "Marking it as normal" when the error appears will be the best thing to do for this scenario.
I hope the information posted previously was useful for you.
Any questions, please let me know.