In the last few months I've been having BSODs connected to iaStorA.sys, NTFS, and other drive-related stuff. So I went to check for a solution and it turned out my BIOS was still running a 12.7 ROM while Windows was using a 12.9 driver. I don't know if this was the actual cause, but I updated the latest beta driver (E7681IMS 4.4B3) for my board (MSI P67A-GD55) with UBU, and flashed it. Kudos to the UBU developer btw, it's incredibly effective.

The problem I'm having now is that the RAID ROM settings don't show up in the BIOS anymore, even after switching to RAID mode. When I enter the Ctrl-I RAID settings, one drive shows as being part of the array, while the other is 'Non-RAID'.

So I have a few questions. 1. How to fix this, of course. 2. Could this mean all data on the second disk is gone? 3. How likely is it that Windows running 12.9 and EFI running 12.7 causes BSODs?

Many thanks

It's a RAID 0 array. And with Intel RST Console, do you mean the Ctrl-I menu or the BIOS menu? Because the latter won't show up (and the former doesn't have repair options).

No I don't have access, unfortunately. As one of the drives is not part of the array anymore, it fails to boot. I can remember this happening before, but then I could set the array in the BIOS again, and it was fixed.

Would it be sensible to upgrade to a 13.x ROM and see if the menu shows up? And, will running a 13.x driver on a 6-series chipset be OK?

Sorry, I edited my post above just after you answered. I think I'll try upgrading to a 13.x ROM to see if the menu shows up, as the legacy menu won't allow building an array without erasing all data.

What exactly would you change then in the BOOT section to have the EFI utility show up? The RAID array isn't present. Also, slightly off-topic, I've always had both the legacy and EFI utility. I've seen you mention that the legacy Ctrl-I screen should disappear with one update or other, but it never did.

I just updated to a 13.x ROM and as you said, nothing changed.

The OS was installed in UEFI mode. Everything was working until I updated the EFI ROMs, strangely enough. I'll try to flash different BIOSes, see if that makes a difference.

Sadly to say, my computer has been off for the night, but the IRS utility didn't reappear. I just cleared the CMOS too to no avail.

I had a similar issue after upgrading OROM & using UBU. I also used RAID0. I would leave & come back to find the PC unable to boot. It seemed like one or both of the drives were falling out of the RAID array as there were no indications of issues in the windows system event log. I could power off the system (sometimes more than one was required) & get the system to boot again. After this happened several times, I decided it was not worth the risk to system stability to keep that configuration. I went back to latest version of the firmware / OROM provided by the manufacturer.