This is 100% reproducible and seems to have been around since forever.
I install the WPK (Windows Performance Tools Kit) from the latest Windows SDK, follow the instructions on how to do a complete boot trace file that I can open with xperfview to analyse what happens during boot, how much time drivers and boot tasks take etc... And during boot I get a BSOD. The only way to get back into Windows is to select "last known good configuration" to clear the trace flag. I run an OCZ Vertex 4 128GB (latest firmware) in one of the Intel SATA 6Gbit ports, AHCI mode, as my boot/OS drive.
The command I use to enable
xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP
However, if I remove +DRIVERS from the xbootmgr command I successfully boot into windows and can open the trace log, but obviously it's not much use since I want the driver boot times as well.
I've tried several different versions of iRST but same result (using latest available for my ASUS Sabertooth P67, iRST11.7). I will keep the minidumps if the developers want to look at them. It is the ONLY driver that cause this boot-BSOD.
There's an old discussion on MSFN.org that mentions this issue in 2009i (albeit not iaStorF.sys specifically): http://www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/