T7820 windows 11: ssd in flexbay windows does not boot after driver update

Just looked back in the threads. Indeed you sent me a link to "this driver" which is as I see now the same. Came at the moment when I sent back my workstation for HW repair and sorry, the thread got somehow forgotten on the way. When I was yzlking about a driver which not worked, I talked aboit te one recommended by Dell through the diagnostics tool.

Well in any case. Thanks to you two in particular for having continued to support my issue in spite of all the confusion between hw, driver issues, my learning about the Dell support site and my hesitations on the way.

I appreciate very much. Have a good week-end.

Yeah, I am happy it works now an sorry for all the fuss on the way to get there. Always difficult, when there are two or mor issues simultaneously and when they do not depend on each other. 

In any case I appreciate your implication and tenacity very much - the both of you.

A good result is more important.  I was under pressure thinking that my suggestion had caused the crash and I was actively finding alternatives (running tests).  Similar issues with these systems after upgrading to Windows 11 and just want to let the community know which drivers are working for me.

Two screws dropped during assembly which caused a short circuit on the motherboard. A great classic on HW assembly. My supplier replaced the faulty parts without discussion in one week. 

If I may ask, what was the hw failure that you had to get fixed ?

The booting issue is with Intel Rapid Storage driver. I would suggest to use the native MVMe drivers of Windows rather than using the Bios's drivers. What you should do is:

1. Change "Raid on" mode to AHCI in BIOS

2. Disable VMD on BIOS

3. Now boot using Windows Installation USB-> Repair-> Troubleshoot->Advanced ->Command Prompt-> type: "bcdedit /set {default} safeboot minimal" then close the cmd.

4. Restart the PC -> before system restart remove USB. Windows should log-in to safeboot. 

5. in Safeboot, open cmd -> type "bcdedit /deletevalue safeboot" -> close cmd

6. Restart

@tennant_uk , have you tried updating ( or downgrading ) to the version I mentioned (in the post that was then accepted as solution) ?

I am having a similar issue with a T7920 trying to upgrade from W10 to W11 using Windows Update which says it is now compatible. However when the installation reboots I get a BSOD for iaStorA.sys (rather than iaStorE.sys). Windows is installed on an NVMe drive and I have six SATA SSDs.

I really don’t want to do a clean install of Windows 11 if I can avoid it. I tried deleting the INTEL C600+/C220+ series CHIPSET SATA RAID Controller driver but it just reinstalls the same one again.

Is there a definitive way to solve this? Anyone know if there are Intel Rapid Storage drivers on their way that work with both W10 and W11 that means now workarounds will be required to do the upgrade?

Hi, got to find the right driver. See one of mazzina's posts above.

"...

7.0.2.1015, A12|Older versions
File Name

Intel-Rapid-Storage-Technology-Enterprise-Driver_22P84_WIN_7.0.2.1015_A12.EXE

..."

This is an driver issue. Windows does not provide any and in the Dell proprietary list you have to find the right one.

Yes, have installed the driver Intel-Rapid-Storage-Technology-Enterprise-Driver_22P84_WIN_7.0.2.1015_A12; although it declares itself as driver version 7.0.2.1004 in Intel Memory and Storage Tool.

Tried installing Windows 11 again (via the Windows Update route) but still get the BSOD when it reboots with Stop code: DRIVER_IRQL_NOT_LESS_OR_EQUAL What failed: iaStorE.sys

Any other suggestions?

At this point I'm not sure... this version worked for the other person, but a little amount of time has passed and that includes monthly windows updates and feature changes, so maybe "now" a different match is needed.

The only idea i can provide is : download the various releases of the driver, upgrade by one version > test the upgrade and if not working try the next version and so on.
But this also means that , imo, Dell should chat a bit with microsoft to offer their clients a seamless upgrade path for the top of the line workstations ( the fault is not on dell... it's entirely on microsoft imo ).

My 7820 is still on win10 and while it says "eligible" it's still saying "stay tuned, you will get offered the upgrade eventually" . But at this point, maybe the best path is win12, that should get out before the 2025 eol of win10....

Hello @RABAsirap  @mazzinia @tennant_uk 
I had the same issue when my boot drive was NVME. When the boot drive is SATA there were no issues upgrading or booting Windows 11 on my precision 5820.
However, if the boot drive was the NVME disk, it is important to note two paths:

1) If upgrading from Windows 10 to 11 make sure you are not using the latest NVME Drivers as they will cause a blue screen. Before updating, make sure the NVME Drivers version is version 7.0 or lower...
2) If you install an nvme drive (no update), when loading the NVME Drivers in the Windows installation (to detect the NVME disks in the installation, since Microsoft does not provide the drivers in the ISO Image), load the drivers Drivers version 7.0 or lower (I don't remember, but it's the version available before August 2020). Any later version will cause problems.
I say this because I made several installations to detect the problem and tested all possible Intel VROC DRIVERS.

My boot configuration was RAID from NVME disk (They weren't necessarily Raid, but the RAID ON option was enabled in Bios).

One more detail I posted in the topic I opened at the time...

"

BIOS RAID MODE:

INTEL C600+/C220+ series CHIPSET SATA RAID Controller  (PROBLEM! WIN11 UPGRADE, MUST BE DELLETED before performing the upgrade)."

I mentioned this in my Windows 11 thread. And I had to do it this way using the NVME boot drive...

And anyway the Intel Volume Management Device NVME RAID Controller driver must be version 7.0.2 OR LOWER

I've tried upgrading to W11 again now that v22H2 is released; but still get the same BSOD when the install process reboots and it reverts back to W10.

Anyone found any other solutions?