BSOD 0x0000007B error (Windows 7 transfer to different hardware)
Hi,
I have been unsuccessful in restoring to dissimilar hardware. I get a BSOD (Windows 7 image). I read the forums and and understand that it is the mass storage controller driver not being found and hence the BSOD.
I have the drivers and my BOOT CD does say True Image 2011 Plus Pack and I have checked the option 'Restore to dissimilar hardware'. I point to the folder where the drivers are but every single time after the 'successful restore' message, when I restart the laptop, the BSOD is there. The image works fine as I have restored on the original PC many times. I have been breaking my head until now.
I have had good experience with Acronis products and convinced the company I work for to purchase a Acronis Backup & Recovery 10 with Universal Restore which I occasionally use at work. Lucky for me because now I had another 'version' of Universal Restore to test. As a test I decided to bring the boot CD home today and tested the same process. It worked prefectly! No BSODs and my laptop booted fine. I then tried my Home Plus Pack Boot CD and I got the BSOD again. I tried my work CD again and no BSOD there....How weird!
FYI I had downloaded the Plus Pack Bootable CD from 'My Accounts' on Acronis web page and its the latest build ie 6696. Please help.
m8tobe

- Anmelden, um Kommentare verfassen zu können

If they were equal, they would have both worked or both not.
Universal restore is not a particular dll, whose version can be tracked down, it's a feature enabled by license. (If you install PP after TI2011, the only difference in 'program files' folder will be BartPE folder related to WinPE-based bootable media and two WinPE-related files). The same is for ABR - the basic version without UR actually has it and uses it during a process of converting a backup to a virtual machine, it just doesn't allow to specify user-defined drivers. So the question is - how much different is the source code it was compiled from? Of course it shares the common code, but that of ABR may be newer (working) or older (not broken in some place) or initially the same but with with fixed bugs related to UR.
ps - registry branch HKLM\system\controlset{number}\services that is physically locates in a file \windows\system32\config\system, taken from the machine after successful restore and its unsuccessful counterpart may give a hint about missing drivers.
- Anmelden, um Kommentare verfassen zu können