I thought I would post a followup message for others to reference in the
event they run into the same thing.
We had run into a similiar problem in the past and there is a MS KB Article
that provided a solution to that problem. That article is:
This article references moving XP to a new system and getting the following
stop code when starting up the new pc:
STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
There is a mergeide.reg file at this KB article that you can run on the old
pc before cloning/moving it to the new pc. The reg file adds info about
hardware back into the registry and when the new pc starts up, it 'knows'
about this hardware and doesn't bomb when it sees those devices.
However, this time around, we got a slightly different stop code on the
BSOD, but it was pretty much an identical situation.
STOP 0X0000007B (0XF78AE640, 0XC00000034, 0X00000000, 0X00000000)
We've believe we have fixed our problem by adding additional hardware info
into the reg file from the KB article. The new computer we were having
problems with uses an Intel 82801 FB/FW ICH6/ICH6W SATA Controller. We added
the device id for this controller (and additional Intel controllers) into the
reg file following the same syntax in the reg file for the Intel devices and
then our disk to disk clone from an old pc to this new pc worked fine.
Obviously if others try this do it at your own risk, but since MS had
previously released a KB article with a fix, I'm guessing we are on the right
track with the solution. As an FYI, the Intel devices in this reg file from
Microsoft are Vendor 8086.