The error code indicates that the iaStorA.sys file has been corrupted or is no longer valid.
The only situation where I've seen a similar error is if I had mixed architecture drivers that were conflicting (both 32-bit and 64-bit drivers available). Ensure that you have architecture isolation of your drivers, if available.
WDS on 2012 states that it automatically filters drivers based on client architecture in driver groups. Strange thing is, if I change the controller settings from RAID (the default) to AHCI, I no longer get that error! There's no RAID card in the T5610 I have, though our older T5600 have the Perc H310.
The next problem is the T5600 USB3 driver is installing instead of the T5610 driver. I tried using filtering by model name "Precision T5610" - but it the filter doesn't seem to work.
I'm also running into this issue myself with SCCM 2007. I've done almost exactly what you have done.
I'm not getting the BlueScreen on the LSI driver that seems to be going in fine. But I am getting the Corrupt or missing iaStorA.sys driver after the initial restart of the Task Sequence.
I've removed the drivers and reimported the driver. I've redownloaded and extracted the driver again. I keep coming back the the iaStorA.sys issue.
I've changed the controller mode to Legacy, ATA, AHCI and RAID and they all produce the same issue.
After each change I've rerun the Task Sequence. I'm still getting the error. We have a number of these systems coming it. I'd really like to be able to provide a working TS for this system.
I'm having the exact same problem when tying to install windows 7 x64 on Dell Optiplex 9020. I'm running WDS on 2012r2. The image installs perfectly on other machines, but not on the 9020. iaStoreA.sys missing or corrupt. Tried everything in this thread but it's not working.
DELL-Warren B
1 Rookie
•
1124 Posts
844
0
Posted October 29th, 2013 13:00
The error code indicates that the iaStorA.sys file has been corrupted or is no longer valid.
The only situation where I've seen a similar error is if I had mixed architecture drivers that were conflicting (both 32-bit and 64-bit drivers available). Ensure that you have architecture isolation of your drivers, if available.