Windows Fault Tolerance Bootable from iSCSI Target using ietd

The Windows endpoint boots through iSCSI blue screens and reboots as soon as the target fails. Up to this point, Windows appears to be "frozen". Blue screen codes are sometimes 0x00000f4 and sometimes 0x000007a. Now, with failover, the secondary supports the same iqn, and the Windows disk source is independent of the iSCSI target. Now that the network is down for a loaded terminal, the same freeze occurs and the system resumes when the network is back online. But when the target device stops working, it doesn't resume, but blue screens and reboots. Targets are displayed using ietd / iscsi-target on Ubuntu 8.10

Any ideas why?