increase of asz size cauased bsod '7B' error
I am a bit miffed that Acronis has bricked my good working system. Tried making a new backup it said not eneough space in asz partition so followed wizard to increase size. When it rebooted otself it goes into a reboot loop. I stopped the auto reboot on error and I have a BSOD with error 0x0000007B.
I have searched forums and it seems this error 7B comes up a lot with Acronis but cant find a specic thread to help me. I am sure Acronis will have a workaround to revover a system that won't boot at all with this error message. I'm on Windows 7 Home Premium with Acronis True Image 2013.
Looking for guidance please. Eric

- Log in to post comments

Hi Shadowsports. thanks for response. Tried most you have said. After F8, none of options work, recover from last known good configuration just reboots back into loop. System repair fails for same reason. WIn7 was pre installed so I dont have boot disk. I cant get to a command prompt. I did F11 to get into Acronis boot menu and did downsize the asz partition back to original size but still boots into loop. Thought then that Acronis boot loader might be problem so disabled that within Acronis so no longer get the F11 start option.
Don't really want to have to go back to last backup since foolishly it was two years ago. One thing I have noticed different is I get the Gigabyte BIOS splash screen on each boot.
My system is Gigabyte GA-Z77-D3H with Intel i5 3750 & 2xCrucial 4GB (8Gb) RAM & GTX660 c/w 2GB graphics ram.
Drives are 120Gb SSD system drive, 1Tb WD data storage drive & 3Tb drive for music/movies/photos. The asz partition was set initially to 30Gb on the 1TB data drive which I tried to increase to 70Gb and then put back to 30Gb. I have tried booting with just the system drive installed but no different. So I believe Acronis should not have changed anything on the boot drive. I just hope someone at Acronis will know the answer since it obviously changed something which hopefully is reversible.
Regards Eric
- Log in to post comments

Hi Eric,
ASR (Start up Recovery Manager) F11 at boot time is what alters the boot drive. Now that you have told us your ASZ (secure zone) was NOT on your boot drive, I'm surprised it can't start normally. Are you sure the ASZ wasn't on the boot drive? Will the system start in SAFE Mode? F8 option?
In any event, removing the ASR from your boot drive should return it to how it was before a boot time option was introduced. If you cannot start in SAFE Mode, I think the next step is windows boot media.
https://www.microsoft.com/en-us/software-download/home
This should open up some options for you:
Start up repair
System Restore
BCD edit / repair
- Log in to post comments

Thanks again Shadowsports. ASZ definitely on the 1TB (D) drive. I have copied all files from the system drive (C) 120Gb SSD to a laptop so I can at least recover some data files. I did try booting with the 1Tb & 3Tb drives unplugged so only the SSD system drive in but still same issue. I have looked into the 1Tb drive and it has the 70Gb ASZ which was the size I increased it to from 30Gb that caused all the problems in the first place. I have found I do have the Win 7 disk and started the install process to see whats available. Tried the repair option but told its wrong version so can't repair??? (the original licensed disk from which install built on!!) so opted to go for new install. Now tells me that install wont install on either of the SSD partitions ( a 100Mb System partition & a 112 GB primary partition) since the disk has an MBR partition table and Windows can only be installed on an EFI system to a GPT disk????
The original system was custom built from Scan Computers (a 3XS system so how they installed and setup the windows aprtitions I don.t know. Maybe I should get some advice from hem also.
regards
Eric
- Log in to post comments