Need help on universal restore...cant get it to work

Knightsman

Well-Known Member
Reaction score
32
I have a customers laptop. His old one failed (bad mobo) and he ordered a new one.

He owns a retail OEM copy of Windows 7 Ultimate. A backup image was made with Easeus, and I have tried universal restore various ways, and I get a no parameter error after it says it has completed the restore.

Laptop Blue screens after applying the image. I cant run repair install because I cant boot into windows, and I really don't want to do a clean install because this client has a lot of software that takes a long time to reinstall and reactivate with the vendors.

Any ideas??
 
Last edited:
I have a customers laptop. His old one failed (bad mobo) and he ordered a new one.

He owns a retail OEM copy of Windows 7 Ultimate. A backup image was made with Easeus, and I have tried universal restore various ways, and I get a no parameter error after it says it has completed the restore.

Laptop Blue screens after applying the image. I cant run repair install because I cant boot into windows, and I really don't want to do a clean install because this client has a lot of software that takes a long time to reinstall and reactivate with the vendors.

Any ideas??

So this is Easeus's own universal restore then?

Why is this needed at all given that the laptop mobo is going to be the same as the old one? Why can't you just put the old hdd in?

What is the specific blue screen error?
 
So this is Easeus's own universal restore then?

Why is this needed at all given that the laptop mobo is going to be the same as the old one? Why can't you just put the old hdd in?

What is the specific blue screen error?


This is all new hardware, we could only find 1 replacement motherboard, and it had bad video.

This is Easeus todo backup workstation.

typical stop error
0x0000007B, 0x80786B58, 0xC0000034, 0x00000000, 0x00000000.
 
7B errors on image restores are usually HDC driver issues. Have you tried the HDC tools on UBCD4WIN? Sounds like the universal restore hasn't done its job in injecting the right HDC driver.

Either that or the MBR iis broken or there are disk problems. But given what you say my first guess is HDC.
 
7B errors on image restores are usually HDC driver issues. Have you tried the HDC tools on UBCD4WIN? Sounds like the universal restore hasn't done its job in injecting the right HDC driver.

Either that or the MBR iis broken or there are disk problems. But given what you say my first guess is HDC.

I havent, ill download it and try it...
 
If I'm not mistaken, don't you have to specify new drivers for the hdd controllers when you do the restore? If you're not doing that, it's not likely to work.
 
Ok, cant boot with ubcd4win, I get the same stop error... (pulling hair out)

In that case you might want to use UBCD or other non-Windows based boot disk to test the HDD. Inability to boot into Windows boot disks can be caused by bad sectors. Even boot disks need to mount the HDD and if they hit bad sectors at that point on the disk then they also error out like that.

Maybe bad sectors were what was causing universal restore to not work in the first place?
 
Last edited:
If I'm not mistaken, don't you have to specify new drivers for the hdd controllers when you do the restore? If you're not doing that, it's not likely to work.

Yeah that's what we've been discussing.

Universal restore is supposed to inject these drivers.
 
If I'm not mistaken, don't you have to specify new drivers for the hdd controllers when you do the restore? If you're not doing that, it's not likely to work.

Yeah, the instructions say if it needs drivers it will prompt for them, but it never does.

In that case you might want to use UBCD or other non-Windows based boot disk to test the HDD. Inability to boot into Windows boot disks can be caused by bad sectors. Even boot disks need to mount the HDD and if they hit bad sectors at that point on the disk then they also error out like that.

Maybe bad sectors were what was causing universal restore to not work in the first place?

I'm going to try a different drive and see if that works. Thanks for your help so far man.
 
I had this same issue with a system the other day.

I remotely edited the registry using the details below from http://support.microsoft.com/kb/922976 and it resolved the problem:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To resolve this issue yourself, enable the AHCI driver in the registry before you change the SATA mode of the boot drive. To do this, follow these steps:
Exit all Windows-based programs.
Click Start, type regedit in the Start Search box, and then press ENTER.
If you receive the User Account Control dialog box, click Continue.
Locate and then click one of the following registry subkeys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV
In the right pane, right-click Start in the Name column, and then click Modify.
In the Value data box, type 0, and then click OK.
On the File menu, click Exit to close Registry Editor.
 
Still getting the stop error with a different drive.

Just to be clear - the error is happening on this new drive when? After you've restored the image to it and try to boot to Windows? Does UBCD4Win also error out on this new drive?

If so then have you made sure you have working partition table and boot sectors for the restored partition(s)?
 
Just to be clear - the error is happening on this new drive when? After you've restored the image to it and try to boot to Windows? Does UBCD4Win also error out on this new drive?

If so then have you made sure you have working partition table and boot sectors for the restored partition(s)?

sry, should have clarified, UBCD4win did it, with a clean new drive.

But this is something different, Got this error from TODO:

Error Found on the file system, please tick sector by sector recovery and try again. So going to try that. Which I did yesterday with the other drive.
 
Back
Top