Get BSOD on boot after Restore to Larger Drive with Home version 11

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 2
Comments: 1

I backed up a 100 GB working boot drive from my Toshiba M400 XP SP3 laptop using Acronis True Home 11, then restored it to a 500 GB Drive.

The new drive starts to boot, but then gives a BSOD, and error starting with 0x0000007B 0xf78aa524 0xc0000034, etc.

Having read the forums, I tried doing this in two passes, I.E. restoring the Disk Partition resizing it as I wanted, then restoring the MBR in a second pass. This made no difference.

I am doing the backup and restore on a Windows Vista 64 machine, connecting the original and new drives using an E-Sata device. I have successfully backed up and restored boot drives on this machine before. I first use Windows Disk Manager to partition the new drive into two equal partitions, and make the first partition active.

Any suggestions how I get this to work?

Paul Wasserman

Wed, 04/21/2010 - 00:13
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 45
Comments: 4263

BSOD 0x7B usually means the mass storage driver is incorrect. Is the new drive using the same controller mode the old drive used (IDE Compatible, AHCI, RAID, etc.) or a different mode? You should be able to check in the BIOS for the setting.

There can also be problems on some computers when the drive is restored outside the computer (especially on some laptops). If possible, try restoring to the 500GB drive while it's installed in the laptop.

Wed, 04/21/2010 - 05:21
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 2
Comments: 1

Well, that was an adventure. Thanks for setting me off in the right direction - the BIOS. For anyone else who encounters this, here's the deal.

After further investigation, I found that I could boot from the new drive when it was in the M400's secondary drive bay, but got the error again as soon as I replaced the primary built-in drive with it.

Toshiba's M400 BIOS has RAID support, and it turns out that the primary boot drive has to be initialized as a Raid Drive. It was showing up as 1RAID-0 in BIOS, while the new drive was just showing up as JBOD.

I had to convert the new drive to 1RAID-0 in BIOS, then I cloned it with True Image right on the Toshiba. Popped it into the built-in drive bay, and all is well.

Paul Wasserman

Thu, 04/22/2010 - 02:19
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 0
Comments: 1

Paul, in hopes of duplicating your success with a Toshiba m400 clone, I just bought myself the Toshiba Ultra Slim Bay® HDD Adapter (Black Bezel), Part Number: PA3408U-2ETC.

But I've got a question for you: Did you actually use the TrueImage "clone" function or something else (such archive and restore) to reach a success? I ask because I've many times in many ways tried using a USB external drive chasis and TrueImage Home 2010 with Plus Pack to clone my target drive (which I'd set to 1Raid-0) when that target drive was located in the primary drive bay. But after each cloning attempt, I can't book and when I go into the bios, find the partition on the target drive is reset to JBOD instead of 1Raid-0, after the clone, though it was set as 1Raid-0 prior to the TI cloning. And the source drive (which I've installed in the USB chasis) proves to retain it's 1Raid-0 setting (thank God) when I return it to the primary bay.

I'm wondering why, if I put the target drive in the Toshiba Ultra Slim Bay® HDD Adapter in the second bay and set that drive to 1Raid-0 before cloning it, that drive won't (after cloning) ALSO be set to JBOD and therefore fail to boot. (As no doubt you learned, I can't apparently successfully clone a target drive with JBOD parititioning then install it in the primary drive and thereafter use BIOS screen 3 to change the drive partitioning from JBOD to 1Raid-0 - since the change wipes all data in the partition.

Alan Girelli

Wed, 07/14/2010 - 14:57