Failed Windows 10 upgrade iaStorA.sys problem

[dgmphoto]

I tried to upgrade desktop PC from Windows 7 to Windows 10. I think it got to configuring drivers (had restarted at least once) then went to a light blue screen with the following.

Recovery
Your PC/Device needs to be repaired
The operating system couldn't be loaded because a critical system driver is missing or contains errors.
File:\windows\System32\drivers\iaStorA.sys
Error code: 0xc0000359
You'll need to use recovery tools. If you don't have any installation media contact your PC administrator or PC/Device manufacturer

Press Enter to try again
Press F8 for Startup Settings
Press F9 to use a different operating system

I'm back in Windows 7 having used a boot CD I created earlier.
IRST which is the storage controlled by the iaStorA.sys driver seems to be working fine.
The Motherboard is a Gigabyte GA-Z68AP-D3

I still want to do the Win 10 upgrade, any suggestions on the way forward?

 

[Colif]

After installing Intel Storage Matrix Manager v14.5.0.1081, don't say yes to rebooting, choose no at the end of the install, then download the floppy drivers for an older version of the storage matrix, one more in line with the era of your motherboard. I chose v12.9.0.1001, which worked well for me but you might have to experiment to find the right driver version for your system. Once you have downloaded the floppy version you have chosen, be sure to use the correct 32 or 64 bit download link. Then manually copy the iaStorA.sys and iaStorF.sys into the \Windows\System32\drivers\ directory and reboot your machine. My machine is now rebooting properly everytime and the Intel Matrix Storage Manager reports the raid arrays status just as it used to in Windows 7.

If you are in a situation where you cannot get your Windows 10 install to boot because of the BSODs, either pull the OS drive and copy the iaStorA.sys and iaStorF.sys manually on another machine, or download those files onto a memory stick and copy them from the command line in Windows Repair.

https://communities.intel.com/thread/78198

 

[dgmphoto]

After installing Intel Storage Matrix Manager v14.5.0.1081, don't say yes to rebooting, choose no at the end of the install, then download the floppy drivers for an older version of the storage matrix, one more in line with the era of your motherboard. I chose v12.9.0.1001, which worked well for me but you might have to experiment to find the right driver version for your system. Once you have downloaded the floppy version you have chosen, be sure to use the correct 32 or 64 bit download link. Then manually copy the iaStorA.sys and iaStorF.sys into the \Windows\System32\drivers\ directory and reboot your machine. My machine is now rebooting properly everytime and the Intel Matrix Storage Manager reports the raid arrays status just as it used to in Windows 7.

If you are in a situation where you cannot get your Windows 10 install to boot because of the BSODs, either pull the OS drive and copy the iaStorA.sys and iaStorF.sys manually on another machine, or download those files onto a memory stick and copy them from the command line in Windows Repair.

https://communities.intel.com/thread/78198

Thanks for the response - I had found that thread but I don't understand Where the Intel Storage Matrix Manager fits in. I don't even know how to check the driver version currently installed. I have the file versions
iaStorA.sys 11.7.0.1013
iaStor.sys 10.8.0.1013
iaStorF.sys. 11.7.0.1013
iaStorV.sys 8.6.2.1014
The Gigabyte site give the Windows 7 64bit Intel® Rapid Storage Technology driver version as 12.8.0.1016 for my motherboard.
There is no such driver available for Windows 10

 

[Colif]

Current Win 10 64bit driver is 14.8.0.104 - see: https://downloadcenter.intel.com/product/55005/Intel-Rapid-Storage-Technology-Intel-RST-

I am not sure what it is either, I just found link searching the sys file name and that error you got

Are you even running RAID? I know some motherboards need those drivers to run SSD?

Have you ever tried a fresh install rather than upgrading? You can use the win 7 key to activate 10 and it might be an old driver causing this problem, not sure you should have 2 versions of same sys file for instance.