If your base image doesn't have support for the SCSI drivers built in you have to add them before you sysprep. I have created hardware independent images that work on IDE/SATA/SCSI computers, but the only way to do it is to modify the sysprep.inf as you noted and build the SYSPREPMASSSTORAGE section with the drivers before sysprep. then run sysprep -bmsd and reseal it. The more mass storage drivers you load, the longer it takes to sysprep because its building it into the hardware detection list for when the system starts up. the two primary causes of the BSOD in the case you're describing is HAL issues or mass storage controllers -- except in most cases I've seen the HAL give black screens instead of the BS.
Biz is right. One thing that I always got stuck on is that the sysprepmassstorage section needs to be populated before you execute sysprep.exe on the machine. Putting it in the sysprep file that LANDesk puts on the machine after the image is not good enough. You aren't required to use BMSD if you know exactly what the destination driver is, but it can't hurt.
Just to close the loop on this one, I have had success!
The guys are right, when you sysprep seal the image it 'reads' the sysprep file and builds all of the massstoragedevice info into the registry. This enables the machine to load the correct driver for the SCSI, SATA or IDE drive and effectively read the disk. If you add this information into the sysprep file Landesk injects at image time, the information will be missing from the registry and it wont be able to even read the disk to start.
After you seal the image, perform a test deployment to an already compatible machine and check the registry key 'HKEY_LOCAL_MACHINE\TEMP\CurrentControlSet\Services' and search for the inf file that you specified in your sysprep file before sealing it. That way you can ensure that the information was added to the registry successfully.