Direkt zum Inhalt

BSOD in TDRPM273, removed ATTH2012 with tool, now BSOD at boot

Thread needs solution

I was getting BSOD several times a day in TDRPM273 per Bluescreenviewer.
Looked at the forums and basically it said to remove it because of possible corruption since I upgraded from 2011.
Got the removal tool, ran it, upon boot, BSOD.
Used Last know configuration. BSOD
Booted UBCD4WIN and chose a different Restore point, BSOD.

Now what?
Do I really have to recover the whole disk?
I would think this should be fixable if I can boot by hook or crook.

And even better my chat support expired TODAY Oct. 18. Plus the heavy call volume. Wonder why???

0 Users found this helpful

Did you use the 2011 or 2012 version of the Acronis cleanup tool? It sounds like you are most likely faced with a situation where your registry may have retained certain "required for boot" Acronis driver/filter entries after the files themselves have been removed. For a more detailed discussion, see http://forum.acronis.com/forum/25916 .

A system start-up under that (mis)configuration may then make it impossible to fix subsequently via the "last known good" option because it no longer has access to the required files for replacement. So yes, in those circumstances, you'd probably have to recover everything from a backup, preferably one that was made prior to the TIH2012 installation. If possible (e.g., if you're able to boot into a Windows preinstallation environment) try to save copies of any more recent user files separately for replacement/updating after the full recovery.

Thanks for the info. I will digest it.
I did use the 2012 removal tool as I saw people having problems.

I just hate having to rebuild it as it was their problem.

Well, if you can get your system to boot at all even into Safe Mode, I guess you could try fixing it manually as discussed in that other thread. It's not easy to get it right, but it would be hard to make the situation any worse and you still have the full backup to restore if you must.

Another option, if you have any kind of multiboot possiblity for another OS or WinPE or whatever, would be to load the bad system registry hive and try to fix it from there.

@Carver Smith,

If you have access to either a Windows 7 (I'm assuming you are using W7 or Vista) repair CD or the install DVD then you can get to the command line, load the registry hive and manually remove the offending entries.

If you are using XP it is much easier, you can run a repair install which will rewrite registry with default settings. Note though this will wipe out any Windows updates and service packs that are not part of the XP install CD, but you will be back up and running very quickly.

So I tried an XP repair install and I still got the 0x0000007B BSOD

So I took a spare duplicate sized HD, unplugged my second HD so there would not
be any conflicts, Looked at the manual for what to click.
My disks etc.
Recovered and it did boot although I don't think it is the most current.

Looked in the" My Backups" on the external USB 3 TB disk and there are 5 entities
in the folder with different dates.

Question is, are they all full backups as they end in TLB, and should
I have chosen the latest date? I suppose I should have "browsed" and chosen
the latest?. I can certainly redo it as the manual says it deletes everything.

Get better help here than Acronis. Called in and they did talk to me but said
the same, "repair or recover".
Thanks

Carver,

Is TLB a mistype and you mean TIB?

Choosing the latest date will always connect to the correct chain of the archive, unless there has been some sort of corruption in part of the chain as far as incremental images are concerned.

Yup!
Typo, it is TIB

Then I should go back and recover from the latest TIB?

Thanks very much.

Carver