There are two sets of drivers that "may" be needed here. Be sure NOT to confuse them.
1) Windows PE drivers. These are VISTA, no matter what image you're placing. They're applicable to BootWiz and a recomplie of the automation envirionment.
2) Your target OS drivers. These are for DeployAnywhere, and MUST match the OS version you use exactly or they will not work.
When you're adding drivers in the console, there are two tabs - one for each of these. If you add to the wrong one, well, you gain little or nothing.
When you get a boot failure like above, unfortunately, we don't know WHERE that failure happened. Right now, the failure appears to be when attempting to boot to WinPE, which if that is the case, then affects your image in now way at all. You may want to remove the drivers you added IF that is the case, especially if this happened only after adding them. Remember that Automation is WinPE 2.1 and that is VISTA, not XP, not Win7/8. Not until the next release...
However, if this failure is happening when you boot the main OS that you just deployed, then the drivers are missing to access the Hard Drive most likely (Mass Storage). This is a hard-stop for the OS. If those are missing, you MUST add the drivers to DeployAnywhere, NOT to bootwiz, and a recompile of the automation environment makes no difference at all. The drivers added MUST be in the right format, and MUST match exactly the OS you are deploying (e.g. Windows 7 x86) or they will not work.
So, determine where the error is, add the right drivers, and you should be well on your way.