Direkt zum Inhalt

[SOLVED] Cloning SSD to larger SSD on same PC causes 0x0000007B BSOD!

Thread needs solution

I bought Acronis True Image 2016 for a SSD to SSD clone, which I thought would be simple enough.

I've been trying to get this to work for days now and truly tried every possible solution I could think of apart from completely reinstalling Windows.

My OS is very customized, so I'd rather not reinstall.

My current setup is a Windows 7 Pro 64bit system (installed from official DVD), with an OCZ SSD and several attached HDDs. BIOS is set to IDE Compatible mode (OCZ didn't like ACHI for some reason). The system has been running smooth for years...

I'm running out of diskspace and want to clone my current OCZ SSD with the OS to a larger SSD. Nothing else is changed, the rest of the hardware is exactly the same. Whatever I try, after shortly showing the Windows logo, the system BSODs with the error STOP : 0x0000007B (0xFFFFF880009A97E8, 0xFFFFFFFFC0000034, 0x000000000000000 , 0x0000000000).

Tried both a brand new Sandisk Extreme Pro and an Samsung 850 EVO, even using it's own cloning software. Didn't work. (Cloning backup images to the current SSD work flawlessly btw). Tried almost every suggested solution I could find online (from System Repairs to switching SATA cables to BIOS changes).

WITHOUT SUCCESS, tried the following:
- repaired MBT and BCD
- system repair (finds NoRootCause and after repairing MBT and BCD tried to boot into Safe Mode, crashes at CLASSPNP.SYS with same BSOD)
- changed BIOS settings to AHCI (original was IDE) after changing the registry HKEY_LOCAL_MACHINE\System\CurrentControlSet\Service\Msahci setting to 0
- changed BIOS settings to RAID (original was IDE) (which is ridiculous)
- changed the registry settings to LastKnowGood
- switched the SATA cables
- switched to the Marvell SATA controller
- cloned using a switched SATA cables, cloned using an external USB docking station
- cloned with and without other HDDs attached

No success at all.

Tried using Universal Restore, but it hangs on finding an Etron 3.0 USB driver, which I point to, but it doesn't load. But I find it hard to believe this is the problem, considering the USB driver was never a problem before.

What am I doing wrong? Please advise, this is very frustrating.

Thanks in advance for any help.

0 Users found this helpful

Tom,

You need to perform the clone using user created bootable Recovery Media.  Trying to run a system disk clone using the Windows installed app almost always ends in failure, in your case your machine is not rebooting into the Linux based Recovery environment properly.  Because this is your issue you will need to discover why our machine will not boot into the Linux environment.

You can create Recovery Media from within the Windows app, just look for the tools icon on the left side of the GUI, click that and select the Media Builder option.  The Media Builder app will build bootable media on CD/DVD or USB your choice.  There is also an option to create a WinPE media but you should not need to do that, the standard Linux media should work fine.

Create the media, boot your machine into the bios, select the boot media as first choice in boot menu options in the bios, save and exit to reboot the machine.  The Media should boot into a menu from which you can select and run the True Image application.  The Clone operation can be found under the Tools option there.  After performing the clone shutdown the machine and remove the original drive from the machine before you reboot.

This link may be helpful as well:    https://www.youtube.com/watch?v=KlXkYKzY6vs

Enchantech,

Sorry, but this is too obvious. Please read my post again. THIS IS NOT AN ERROR WITH AN OBVIOUS SOLUTION.
I tried the Recovery Media in every possible configuration, but it does NOT work and neither does Universal Restore (unless it would depend on a single USB driver). I've cloned at least 10 times already (not great for the SSD) using different setups.
It just will not work.

As a test I tried a SYSPREP /Generalize before the clone and then it does acutally boot, but of course I lose all the settings and profiles that I want to keep. In that case I might as well reinstall everything, which is not why I bought imaging software...

If anyone is familiar with this problem, help is very much appreciated (I'll buy you a beer, really).

Ok, I get that you used the Recovery Media, you had not said that in the first post and that is imperative to cloning a System disk with any success.  Keep in mind here that I am a user like you, nothing more, do not get mad that I offer a possible solution to your problem when it is not apparent that you have already tried that!

Now, I would suggest that if you cannot get the clone to work that you use the recovery media to create a backup image of current system disk while installed in the PC to a secondary location.  Next, remove the current system disk and replace it with the new disk in the same location in the PC (same SATA port).  Now boot the PC with the recovery media again, locate the backup file on the secondary location, and restore/recover the backup file to the new disk.  Shutdown the PC after the rescovery is completed, remove the recovery media, boot into the PC bios and set the boot order so that the new drive is first in the list of boot devices, save and exit the bios and your machine should boot to the new drive.

It is not often that clones do not work but it does occur, in these rare cases the use of a backup image and restore of that image will produce the same end result.  Just a little more work is involved in this process.

As a side note Universal Restore is not used nor necessary for a clone operation and cannot be used to perform a clone or backup/restore operation.

(Didn't mean to sound mad, was just going nuts trying to figure this out for days on end... tried many many times and my frustration came to a boiling point)

YES! YES! YES! Finally something that worked! THANKS, Enchantech. A deep bow to you, sir!

The trick was to do a Backup with the Sector-by-Sector option selected using the Recovery Media, not a normal backup or clone. This performed nicely, but I did need a lot of extra space to write the image. In my quest for a solution, I tried many other products (Macrium, Clonezilla, Partition Wizard, etc.), but none succeded. I was almost ready to reinstall and ask for a refund, but I'm really happy with my True Image purchase now.

There is one thing that irks me though. Wanting to figure out what was going on with the driver errors, I launched Universal Restore from the Recovery Media again and ran the check. It showed the expected USB 3 Etron driver error and I was not able to replace/correct it, so I ignored it. After rebooting, the SSD bombed to the BSOD yet again and I have absolutely no idea why. Thankfully I still had the Backup Image, so I was able to restore without a problem. What did Universal Restore change, that caused this?

Anyway, thanks again Enchantech. And if you have Paypal, pm your email and I'll buy you that beer...

Glad you got it working with backup and recovery and sector-by-sector.

What is the BSOD message your're getting

You menioned your image was running with the bios in IDE compabitilbiy mode.  My guess would be that after running UR, and before starting the OS, that you need to swtich the SATA mode in the BIOS to either SATA or AHCI and see if that helps.  The default drivers for whichever mode you select should get installed with the first boot of the OS launch.

Alternatively, I've found that running this MS fixit tool (direct from Microsoft), going into the bios and changing the SATA mode before bootign the OS, has a similar effect
 

STOP 0x0000007B INACCESSABLE_BOOT_DEVICE_Error message occurs after you change the SATA mode of the boot drive

The Universal Restore routine undoubtedly dumped the driver for the Etron USB 3 in favor of a generic, should work driver which failed at boot and ultimately caused the BSOD.  With a functioning restored image to a drive there is no need for Universal Restore to be used. 

Question, is the Etron USB an add on card?  Not being familiar with it I'm a bit curious.  I have a feeling that it is and is probably a bit dated.  Not sure of your procedures here but if you had for example once restore was completed, shutdown the PC, ininstalled the add in card, restarted the machine and let it boot up then, shutdown again, install the add in card, restart the PC and let it boot (which it shoud) then install the drivers for the add in card anew you would have avoided the issue.

When using Universal Restore it is best to start with a bare bones system.  One HDD for the System disk, no add on cards, restore image, run the Universal Restore, then boot the machine.  After that you can then add the rest of your hardware to the machine as you would with a fresh build and use Windows Device Manager to install all necessary drivers for such add on hardware.

@Bobbo_3C0X1, thanks for your reply. I think you're right, it probably is a switch to ACHI that doesn't comply with the BIOS settings. Don't want to test it though! Happy with the way the system is running now... (BTW, weird that a Fixit would cause a BSOD!)

@Enchantech, the Etron is one of the MB controllers, so drivers shouldn't have to be changed. BUT, these are nasty little buggers. After the Z68, these controllers got kicked due to bad performance and replaced by Intel and ASMedia.

Thanks for the explanation on using Universal Restore. Next time (if I ever need it), I'll unplug everything first.

Again, thanks for all the support!

Thanks for posting back, the next time I see reference to Etron I'll know they are problem children!