I'm having the same issue. I think that all of the drivers you list to load either through txtsetup.sif or textsetup.oem method get loaded into memory during the phase of setup enumerating the plug and play drivers. I'm using a single image delivered with Windows Deployment Services that supports lots of different models of Lenovo and older IBM desktops and laptops. I need the new Iastor.sys for some of the newer models, and it works just fine for them, but it's giving some of the older machines a BSOD. Just like your issue the machine getting the BSOD doesn't even need the iastor.sys driver to begin with.
