Nothing has changed - ATI 2010 - BSOD

EXACTLY!!! That is indeed the problem. Acronis tries so hard to make a great product. I think too hard.

Add another unhappy camper to the list.

Acronis True Image Home 2010 / Lexar JD Firefly 8gb USB stick.

Didn't see the issue on my older PC , an Asus A8n32SLI-Deluxe, running Win 7 x86 build 7100

But i certainly have this issue on my new GA-EX58-UD5 , running Win7 x64 RTM.

OK I've turned in a support ticket for this and it has caused one hard drive to be unusable completely. Removing it and replacing it with a new hard drive I just bought. Going to install and remove regs and file for the service and the . sys file will be deleted.
If it cause's anothjer hard drive to fail and I loose any more time here on my business computer- I'm filing a lawsuit for damages and prepared to take this to the media to stop this from happening to anyone else. ASAP.
Thanks Acronis

Charles Woodrome wrote:

it has caused one hard drive to be unusable completely.

Can you give more details on what you mean by unusable?

the . sys file will be deleted.

Which sys file, there is more than one if you are talking about Acronis files?

Be careful when deleting sys files, Windows may be using them, you could make your system unbootable or cause it to crash.

The drive is no good - I've bought a new sata hard drive and still have problems. The drive is dead - will not format or anything. I did a fresh install of vista with no updates what so ever and still have problems with this 2010 version.
Whats the deal here?
I'm really getting upset with all this and it is costing me time and money!
Uninstalling your product before I have another failure.
Will be in touch with whom it may concern via phone monday morning!

First things first!

Does the 'dead' drive still spin up?
Does your PC's BIOS recognise the drive?

What brand and, model and firmware number is your drive?

Have you checked the drive with the drive manufacturers drive check utility?

I can't see (at this moment) how TI could render your drive totally inoperable or unrecoverable. As you are the first person to report such a problem (to my knowledge) the more details about your system and what you tried to do the more some of us might be able to help you.

Some Seagate drives have a known firmware bug, that will render them inoperable, these however, can be persuaded to act civily again. Even so this is an internal drive error, and I don't believe an external program can be the direct cause of the 'pointer' bug occuring.

I would urge caution before attaching another drive to that particular Sata position on your MB, just in case you have a power problem or a faulty chipset.

Check to see if any of the capacitors on your MB are bulging or have a brownish residue on their tops. The caps will be cylindrical - upright and on their tops will be an 'X' type indentation and on one sideof the cap's can you will see downward facing arrows. They will have an inscription such as 2700uF/6.3v or similar.

I've already replaced the drive due to the fact that WD support instructed me to return the drive to them for replacement. The drive failed all of their test. I have a new power supply here and nothing wrong with any of my system. I just finished installing Vista without any updates and after installing ATI 2010. When I plug in my Iron Key to a usb port and access my drive it crashed the system; BSOD. I have crash dump files and plenty of documentation for everything here.
I've uninstalled the product and will not use any Acronis software on the system again.
These people have known about this for sometime now and are not taking any action.
I will!
Thanks for your comments - but I have plenty of computer knowledge here - I will not explain myself here in this forum. Which is very bad place to try and get support info from what I have seen thus far.
I believe Acronis needs to be investigated...

Out of curiosity, more than anything else, what brand devices etc are causing the BSOD when plugging in... EG my Lexar JF Firefly causes my machine to crash, yet my ipod, generic brand USB sticks, WesternDigital USB HDD, Digital Camera's etc etc all plug and unplug perfectly fine.

I note someone else in this thread reported their Lexar card reader caused them issue... is it Just Lexar devices ?

Gary Finlayson wrote:

...what brand devices etc are causing the BSOD when plugging in...

I have "OCZ Rally 2" Flash Drive 32Gb. Kept BSODing on Win7 all the time. Additionally I have a no-name 1Gb Flash Drive which BSODed just the same.

Thanks, yeah, ok, i've also heard reports of TomTom GPS, and "Yum-Cha" USB tuner also exhibiting the issue.

Here a Corsair 8GB Thumb Drive is causing a BSOD, but not always... when it has been formated it works, but when it contains a few files - BSOD...

MAY HAVE A FIX!:

I can't promise because I haven't run it that long, but I have been able to insert my "SD" card multiple times without BSOD (about 50% of the time it would BSOD).

Ok, first from all the threads I've read, the issue is in the SnapAPI (snapapi.dll). Second this thread said that the same BSOD issue was fixed for "Disk Director" via a SnapAPI fix:

http://forum.acronis.com/forum/3235?page=1

(see last post by Acronis).

So, that got me looking and I found a "snapapi.dll" in "C:\Program Files\Common\Acronis" that was version 3.8.0.473 with a date of 9/8/09. I then installed a demo of Disk Director. This file ("snapapi.dll") in "C:\Program Files\Common\Acronis" did not change.

So, I started looking again and found another copy in "C:\Windows\System32". That one was far older - 3.0.0.33 and dated 2/22/07. That location also made more sense - that's where Windows would be looking for DLLs, not "C:\Program Files\Common\Acronis".

So, I backed up the "C:\Windows\System32" copy, and then overwrote it with the newer "C:\Program Files\Common\Acronis" version (ie: copy "C:\Program Files\Common\Acronis\snapapi.dll" to "C:\Windows\System32\snapapi.dll").

Voila. Seems to maybe be fixed.

My guess is that the System32 version came from Dell or something as their usual pre-installed bloatware (I'm using a Dell laptop) and Acronis' installed doesn't have the sense to overwrite it.

Or maybe I haven't given it enough time and my next insertion will blow the PC up.

Try it at your own risk - I can't promise there isn't a good reason for the System32 version being older but...

I have been using Acronis for many years and just upgraded from 11 to 2010. Lots of problems and Sooo slow! I am asking for a refund. They must have lost key developers or major change in management. What a staggering mistake!

Ive only got the one SNAPAPI.DLL ...

in "C:\Program Files\Common\Acronis" that was version 3.8.0.473 with a date of 9/8/09

I'll cross my fingers for you...

Lewis Berrie wrote:

I had the same issue of my machine suddenly Blue Screening when attaching my TomTom (Windows 7 x64 Ultimate).

I performed a debug of the memory dump, and it pointed at tdrpm251.sys, the Acronis Try & Decide filter driver. The really annoying thing is, I have Try & Decide disabled, yet clearly the filter driver is always loaded :-(

Anyway, I managed to remove the driver and keep access to my USB/memory card readers. The process is

1) remove the filter driver registry entry (using SC DELETE at the CMD prompt is the "polite" way to do this)

2) search the registry for the references to the filter driver, and remove them (not the whole values, just the specific entries for the driver).

It was registered as a High filter and a Low filter for two events relating to removable drives on my machine (interestingly, it was listed twice in one of the MULTI_SZ entries: first and last entry).

Having rebooted, I no longer have the Try & Decide filter driver loaded, I still have access to my USB/memory cards, and my main system drive still gets imaged every 8pm :-)

Windows doesn't like having references to filter drivers that it can't load, which is probably causing the issues people are having when just removing the driver file or the driver entry: you need to clean all references to it.

Hi Lewis, could you explain the process you followed with a little more detail?

Hi Lewis, could you explain the process you followed with a little more detail?

Yeah, that would be nice. I also have a question for Lewis: Did you delete the file "tdrpm251.sys"?

'Cuz when I removed registry entries pointing at "tdrpm251.sys" AND deleted the file itself, I got BSOD on next boot and had to restore "Last Good Configuration".

I hear a lot of noise regarding ATI 2010 and this makes me wonder if I should part with my fine friend, the reliable and faithful ATI 11...

I don't necessarily agree that all these reported problems are directly related to Acronis True Image. They may. Or they may not.

But what really stuns me is the apparently complete and conspicuous absence of Acronis moderators or representatives either providing any explanation, pointing to any solution, or deflecting any (possibly) unjustified complaints...

I've seen the same problems being posted amd repeated countless times, almost to the level of nausea, and no one from the company side steps in to say... whatever?

I have to say this: I have been a frequent and enthusiastic defender of ATI in various forums. Just out of my own experience with this product, and nothing else. And the first time I step into Acronis own forum (this is just my second post) my previous seemingly unshakable confidence in ATI suffers a rude shock...

Help, anyone!?

Ok, i've had a little play in Regedit, and i think i have figured out what Lewis meant... (suffice to say i havent seen a BSOD since trying this..)

For starters , i have no "services" relating to 'Acronis Try and Decide' , so his suggestion to perform an SC DELETE is of no relevence for me. For those who do have such a service, you could either set that service to disabled, else use SC.EXE to delete it.

Now, onto the registry..
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\tdrpman251]
i found a "ImagePath=" reference to the full path to the tdrpman251.sys file. I simply removed the 'data' from that value. In other words, leave it as "ImagePath" with no further information.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}]
In here i found a reference to "trdpm251" in an "UpperFilters=" value. I just removed that reference, leaving any other "UpperFilters" in place.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}]
In here i found a reference to "trdpm251" in an "LowerFilters=" value. Again i just removed that reference, leaving any other "LowerFilters" in place.

Now, i dont know how specific those UID numbers are , from build to build, machine to machine, so maybe like me, you should use the 'F3' find capability of regedit to search the entire registry for references to 'trdpm' (i suggest you just search for the first 5 letters, to be sure you find all possibilities of what you are looking for. ALSO there is no need to concern touching things in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\ or 002\ as these are just 'backups' used for recovery when using "last known good configuration" etc. Basically these will self cleanse themselves after a successful restart of the machine, once the above changes were made.)

And thats it , the actual file itself, i left alone... I dont see any need for it to be deleted, given there is no references to it in the registry or services area.
Now, just because this appears to have worked for me, without adverse effect, doesnt mean it will for you. Take all the usual precautions, have a good backup and recovery plan, just incase it all goes to poo.

Finally, thanks for all your help with this, Acronis support... :)

GarFin_au:

Thank you so much for detailed description on how to modify registry settings. I've done it and it seems to have fixed BSOD issues with my flash drives!!!

ALL:

If you suffer from BSOD on insertion of flash drives, I strongly suggest that you try the solution proposed by GarFin_au.

I am having the same problem with Windows 7 x64. I also have a multicard reader that puts ups drives when nothing is inserted. I get the BSOD from tdrpm251.sys. Why doesn't Acronis find a solution to this? No one is going to back up to the USB ports on these card readers. The program should be smart enough to ignore these ports or allow a configuration to ignore USB all together. Anyway, with most people over a hundred gigabytes, who would back up to a USB drive anyhow? That has to be pretty slow.

This needs to be fixed.

Follow this Thread ..

After closing this thread, I went on to read another: http://forum.acronis.com/forum/5417

I wonder if the reference to Snapapi may have some bearing here?

I saw this post from Dmitry, Acronis Moderator:

This problem has been around a long time and there apparently is still no reprogramming solution for Try and Decide from Acronis. This problem is perhaps symptomatic of ongoing attempts to put three pounds in a one pound bag; this feature has nothing to do with the basic function of TI Home. Following the work around instructions of GarFin_au above or the solution by Dmitry below should prevent the BSOD's.

http://forum.acronis.com/forum/3243

I downloaded this SnapAPI update, but before I installed it I checked the build version of the .dll. The SnapAPI .dll that comes with TI2010 build 6029 is 3.8.0.486 (19 oct 2009). The one in this update is 3.1.0.329 (15 feb 2007).

This doesn't look like they have kept it updated to the current version.

Hello all,

Please accept our apologies for the inconvenience caused by the BSOD issues.

The issues should be separated.

The solution mentioned by Richard Emery can be applied to the previous builds of Acronis software, i.e. to Acronis Backup & Recovery 10 (build #11105) and to the outdated builds of Acronis True Image Home 2009 and Acronis True Image Home 2010. The issue was caused by an outdated build of SnapAPI module that handled some kinds of USB devices improperly (snapman.sys is mentioned in the dump files) and can be resolved by installing the latest builds of the programs (Acronis True Image Home 2009 build # 9809, Acronis True Image Home 2010 build #6053 and Acronis Backup & Recovery 10.0 build #11133). Please see this article on how to view the build number in Acronis True Image Home 2009 and Acronis True Image Home 2010.  In Acronis Backup & Recovery 10 the build number is available in the Help -> About section.

Therefore, this solution is considered to be an actual one for the UK versions of Acronis Backup & Recovery 10 only, a new build is still unavailable for them.

The issue caused by tdrpman.sys drivers (this driver is mentioned in the dump files) has another nature. The issue has been fixed for the current versions of SnapAPI module and the latest build of Acronis True Image Home 2009 and Acronis True Image home 2010 already posses this build of the module.

Therefore, the solution is to update the programs to the latest builds (you can learn more on how to do it here).

Please note that the BSOD issue can have another reasons. It can be caused by incompatibility with another software, by corrupted memory module, by video drivers, etc.

To find the exact reason you should obtain the below information and create an e-mail request or contact Live chat service available on this page, under Contact us click on the Start here button and follow the step-by-step guide. 

1) Please do the following in order to enable mini-dumps:

In Windows XP:

In Windows Vista and Windows 7:

2) - Open Start\Programs\Accessories\System Tools\System Information;

Also you can attach the files to your next post, we will analyse them and provide you with a possible solution.

Thank you.

I was strongly considering upgrading from TI 2009 to 2010. Then I logged into the forum. I am sure glad that I did! I don't need the 2010 problems. I am having enough problems with understanding how to use 2009.

I checked on Symantec's current offering. Their Ghost was never on my 'just got to have it' list. And, reviews I read indicate that new program is Ghost 10 wrapped in a new and easier to use shell. So much for that one!

Where are the Acronis moderators? Is Acronis too short on staff for someone to moderate the forum? If so, time to do some restaffing.

*****

Dear Acronis customers,

Let me clarify the current state of this situation:

Today I have consulted with our Development Team and they reported that the issue with tdrpm251.sys BSOD has been fixed in current update for Acronis True Image Home 2010 (6053).

So please complete uninstall your current version from PC via Add or Remove Programs, after that please download the latest build, which is available here. To get access to updates you should first register Acronis software.

This should fix the issue.

If this solution does not help, please let us know and we'll do our best to get the situation resolved.

Thank you.

Matt,
Your fix has worked for me! Insertion of an SD card or iPod sync was randomly crashing my PC since I installed ATI 2010. Never would have put the two together.
Thanks,
Bob

GarFin_au wrote:

Ok, i've had a little play in Regedit, and i think i have figured out what Lewis meant... (suffice to say i havent seen a BSOD since trying this..)

For starters , i have no "services" relating to 'Acronis Try and Decide' , so his suggestion to perform an SC DELETE is of no relevence for me. For those who do have such a service, you could either set that service to disabled, else use SC.EXE to delete it.

Now, onto the registry..
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\tdrpman251]
i found a "ImagePath=" reference to the full path to the tdrpman251.sys file. I simply removed the 'data' from that value. In other words, leave it as "ImagePath" with no further information.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}]
In here i found a reference to "trdpm251" in an "UpperFilters=" value. I just removed that reference, leaving any other "UpperFilters" in place.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}]
In here i found a reference to "trdpm251" in an "LowerFilters=" value. Again i just removed that reference, leaving any other "LowerFilters" in place.

Now, i dont know how specific those UID numbers are , from build to build, machine to machine, so maybe like me, you should use the 'F3' find capability of regedit to search the entire registry for references to 'trdpm' (i suggest you just search for the first 5 letters, to be sure you find all possibilities of what you are looking for. ALSO there is no need to concern touching things in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\ or 002\ as these are just 'backups' used for recovery when using "last known good configuration" etc. Basically these will self cleanse themselves after a successful restart of the machine, once the above changes were made.)

And thats it , the actual file itself, i left alone... I dont see any need for it to be deleted, given there is no references to it in the registry or services area.
Now, just because this appears to have worked for me, without adverse effect, doesnt mean it will for you. Take all the usual precautions, have a good backup and recovery plan, just incase it all goes to poo.

Finally, thanks for all your help with this, Acronis support... :)

GarFin_au: yeah, I wasn't exactly clear in my posting, sorry about that :-)
You can use the SC DELETE command to remove Device Drivers, as well as Services, which is what I meant. So instead of deleting the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\tdrpman251
registry key, you just issue
SC DELETE tdrpman251
which will get Windows to "politely" delete it.
The "lowerfilters" and "upperfilters" locations look right to me :-)

I've just installed the new build, so will give it a go to see if this is fixed ... otherwise, we know the cure :-)

BSOD when plugging in TomTom GO 930T device. Using Windows 7 64-bit. BIOS loses track of hard drive selection resulting in Missing NTLDR message.

Happens about 1/3 of the time.

Tomtom forum pointed to Acronics...which I do have running: ATI 2010 bld 5,055.

Gerald Martinez wrote:

BSOD when plugging in TomTom GO 930T device. Using Windows 7 64-bit. BIOS loses track of hard drive selection resulting in Missing NTLDR message.

Happens about 1/3 of the time.

Tomtom forum pointed to Acronics...which I do have running: ATI 2010 bld 5,055.

The simple answer is to update your Acronis installation to the latest build, available via the "My Account" area in the Support section of the Acronis website.
I've had Build 6053 installed for a while now, and I haven't had a BSOD when connecting my TomTom 910, and I didn't need to manually remove the Acronis Try & Decide filter driver :-)

Hello all,

I just want to confirm that we receive lots of positive answers regarding this issue - it has been fixed in the latest build (6053) for the product as I stated in my previous answer. So if you experience the same issue as described in this thread, please complete uninstall your current version from PC via Add or Remove Programs, after that please download the latest build, which is available here. To get access to updates you should first register Acronis software.

Anyway, please feel free to ask us if you have any questions concerning the products, we would be glad to help.

Best regards,

I have ATIH 2010 build 6053 installed and I am still getting BSOD PAGE_FAULT_IN_NONPAGED_AREA in module tdrpm251.sys (1,0,0,251) + 2b6b0 when inserting a USB Sandisk. Vista Home Premium 32-bit. So it appears this issue is NOT "fixed in the latest release". Minidump attached.

ACRONIS SUPPORT: do you even look at these postings? I posted on 2/28/2010 (#84) and I am STILL getting BSOD PAGE_FAULT_IN_NONPAGED_AREA in module tdrpm251.sys (1,0,0,251) + 2b6b0 when inserting a USB Sandisk. I have many minidumps for you to look at if you would care to fix your software.

Steven Williams wrote:

ACRONIS SUPPORT: do you even look at these postings? I posted on 2/28/2010 (#84) and I am STILL getting BSOD PAGE_FAULT_IN_NONPAGED_AREA in module tdrpm251.sys (1,0,0,251) + 2b6b0 when inserting a USB Sandisk. I have many minidumps for you to look at if you would care to fix your software.

Steven,

Something is a little bit amiss with your installation, I think.
TDRPM251.SYS was used in build 5055
TDRPM258.SYS was used in build 6053

So I think your "Try and Decide" filter driver was not upgraded correctly.
Since the driver has changed name, it's not just a matter of overwritting the old driver with the new one.

You may wish to try to Modify/Repair the current installation, or try a full uninstallation/reinstallation.
Afterwards, check the version of the driver installed (in SYSTEM32\DRIVERS).

Hello all,

Thank you for posting.

Steven, I agree with Lewis, please repair the installation or reinstall the latest build from the scratch.  You can learn more on how to download the latest build in this article. 

By the way, we expect the new build release very soon, you can wait a little bit to avoid the duplicating of your efforts.

Thank you.

Hello all,

We have released a new build of Acronis True Image Home 2010 # 7046. I would recommend you to update the software to the latest build. Please see Release notes for your information.

You can learn more on how to download the latest build here. 

Here are the articles available in our Knowledge base: 

Acronis True Image Home 2010: Updating to build 7046 

Acronis True Image Home 2010 Plus Pack: Updating to build 7046 

This build already contains SnapAPI module of the latest build, that's why please uninstall the separate SnapAPI module (if there is any) by Add or Remove programs utility prior installing 7046.

Your feedback regarding the latest build is greatly appreciated. 

Please do not hesitate to ask additional questions if the provided information is not clear or you need a further assistance. 

Thank you.

OK, I uninstalled the SnapAPI.503_s_e module and rebooted. Then installed TrueImage2010.7046_s_en.exe to upgrade from build 6053 to 7046. Upon rebooting my computer blue screens with PAGE_FAULT_IN_NONPAGED_AREA and it won't even boot up. Not even in Safe Mode. I tried boot logging but apparently the error is too early in the boot process as ntbtlog.txt doesn't capture anything. So I had to restore completely from a backup. Then I tried uninstalling the SnapAPI.503_s_e module and rebooting, followed by uninstalling ATIH 2010 build 6053 completely and rebooting, then reinstalling TrueImage2010.7046_s_en.exe again. Upon rebooting my computer again blue screens with PAGE_FAULT_IN_NONPAGED_AREA and it won't even boot up. Not even in Safe Mode. This is Vista Home Premium 32-bit SP2 with all the latest patches. My userid has admin authority.

One thing that is interesting is that looing in C:\WINDOWS\SYSTEM32\DRIVERS after completely uninstalling both the SnapAPI module and ATIH 2010 build 7046 completely and rebooting, there are still several Acronis drivers in this directory including:
tdrpm251.sys Friday, July 31, 2009 8:00:31 AM
tdrpm258.sys Tuesday, October 20, 2009 1:39:48 AM
snapman.sys Monday, February 08, 2010 6:41:03 AM
snman517.sys Monday, February 08, 2010 6:41:03 AM
timntr.sys Tuesday, September 29, 2009 7:37:51 AM

So it appears to me that you uninstall doesn't do a very good job of cleaning up after itself and this may be part of the problem why I can't even boot up successfully after installing or upgrading.

So now what?

Thanks...Steve

I am trying to install the 7046 updates for True Image Home 2010 and Plus Pack but I get the error message about failed in attempting to create c:\programdata\microsoft\windows\startmenu\programs Can I create this directory and if so how or any other solution?

Hello all,

Oleg,
I already had kernel dumps enabled and automatic restart disabled on my system. I verified that DevCon was installed and downloaded/installed Msizap.exe, and then downloaded and ran the Acronis True Image Home 2010 Clean Up Utility per the instructions in article 7533, and the cleanup utility appeared to run successfully and I rebooted as requested by the cleanup utility. Now, again, my system will not boot up at all. It blue screens with a generic "your system has been shut down to prevent damage" stop error 0x0000007b (0x80799bb0,c0000034,0x00000000,0x00000000). I tried booting in safe mode, same BSOD. I tried booting the last known good configuration, same BSOD. I tried booting with Enable logging, same BSOD and inspection of the c:\windows\ntbtlog.txt file from another rescue partition on my PC sows nothing logged in the ntbtlog.txt file and no dumps. The crash is apparently happening too early in the boot process while drivers are loading for Winblows to log or produce a kernel dump. VERY FRUSTRATING! Again, inspection of the c:\windows\system32\drivers directory from another rescue partition shows the following files are still there even after running the cleanup utility:
timntr.sys
snapman.sys
snman517.sys

What is your next suggestion? Should I delete the remaining Acronis files from c:\windows\system32\drivers directory and see if my system boots? At this point I have an unbootable system and my only choice is to restore from my last backup and try something else again.

Hello Steven,

Thank you for your response.

You shouldn't remove the traces manually, it is rather dangerous procedure, manual uninstalling should be performed in a corresponding order. 

To make the system bootable please use the Bootrec.exe tool. Please let me know if this tool is able to do it. 

We are looking forward to hearing back from you. If the provided information is not clear or if you have any other questions do not hesitate to post them and we will be glad to answer.

Thank you.

I gave up. Bootrec.exe tool couldn't fix it and my system was still unbootable after uninstalling ATIH build 6053. I had to reinstall Vista and all my programs from scratch in a new partition to get a working system again. So much for having backup software. I have now installed ATIH 2010 build 7046, and now I'm having other problems like intermittent MFT bitmap is corrupted errors but chkdsk /f finds no problems, and scheduled backups running for an hour, deleting old backups from the ASZ, and after the backup completes NOTHING in the ASZ! I've tried removing the ASZ, running chkdsk /f on the disk that the ASZ was on, recreating the ASZ, and still the same problems. I used to love Acronis, and I've been using it for years. Now its nothing but problems, and it's totally unreliable as a backup product.

Have you checked to make sure you are not having a memory issue by running the Vista memory diagnostic?

Hello all,

Thank you for posting.

Steven,

I have placed my response in this thread.

Certainly, it will be useful to run the memory  test suggested by Thomas.

You can learn more on how to run Windows Vista memory test in this article.

Please do not hesitate to ask additional questions if the provided information is not clear or you need a further assistance. 

Thank you.

Oleg, I ran an extended memory test with 2 passes and no memory errors were detected. I have also run a chkdsk /r on all partitions with no errors detected.

Hello Steven,

Thank you for your response.

If F:\ partition doesn't contain operating system, copy the data to another location and reformat the partition. You can use built-in Disk management utility or Acronis Disk Director 10.0.

Please do not hesitate to ask additional questions if the provided information is not clear or you need a further assistance. 

Thank you.

Lewis Berrie wrote:

GarFin_au wrote:

Ok, i've had a little play in Regedit, and i think i have figured out what Lewis meant... (suffice to say i havent seen a BSOD since trying this..)

For starters , i have no "services" relating to 'Acronis Try and Decide' , so his suggestion to perform an SC DELETE is of no relevence for me. For those who do have such a service, you could either set that service to disabled, else use SC.EXE to delete it.

Now, onto the registry..
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\tdrpman251]
i found a "ImagePath=" reference to the full path to the tdrpman251.sys file. I simply removed the 'data' from that value. In other words, leave it as "ImagePath" with no further information.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}]
In here i found a reference to "trdpm251" in an "UpperFilters=" value. I just removed that reference, leaving any other "UpperFilters" in place.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}]
In here i found a reference to "trdpm251" in an "LowerFilters=" value. Again i just removed that reference, leaving any other "LowerFilters" in place.

Now, i dont know how specific those UID numbers are , from build to build, machine to machine, so maybe like me, you should use the 'F3' find capability of regedit to search the entire registry for references to 'trdpm' (i suggest you just search for the first 5 letters, to be sure you find all possibilities of what you are looking for. ALSO there is no need to concern touching things in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\ or 002\ as these are just 'backups' used for recovery when using "last known good configuration" etc. Basically these will self cleanse themselves after a successful restart of the machine, once the above changes were made.)

And thats it , the actual file itself, i left alone... I dont see any need for it to be deleted, given there is no references to it in the registry or services area.
Now, just because this appears to have worked for me, without adverse effect, doesnt mean it will for you. Take all the usual precautions, have a good backup and recovery plan, just incase it all goes to poo.

Finally, thanks for all your help with this, Acronis support... :)

GarFin_au: yeah, I wasn't exactly clear in my posting, sorry about that :-)
You can use the SC DELETE command to remove Device Drivers, as well as Services, which is what I meant. So instead of deleting the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\tdrpman251
registry key, you just issue
SC DELETE tdrpman251
which will get Windows to "politely" delete it.
The "lowerfilters" and "upperfilters" locations look right to me :-)

I've just installed the new build, so will give it a go to see if this is fixed ... otherwise, we know the cure :-)

I wouldn't do it this way as you will delete the whole tdrpm251 key. That led me to a blue screen upon restart and I couldn't come into Windows anymore. If you follow GarFin_au's directions exactly you should be good to go.

If you edit something in the registry and Windows doesn't start you might think you have a problem as you no longer can access and edit the registry to fix the problem. But if you can access another hard drive with a working copy of Windows or another computer with Windows, you can plug in your sick hard drive and access its registry editor. Following are my directions for Windows 7. For Windows XP see here: http://forums.pcper.com/showthread.php?409638-Remote-Registry-Editing-a…

1. Go into Registry Editor (run... regedit)
2. Highlight HKEY_LOCAL_MACHINE
3. Click File -> Load Hive
4. Browse to G:\Windows\System32\config (replace G with whatever drive letter you have assigned to your sick hard drive).
5. Find SYSTEM and open it.
6. Now you will be asked to create a name for the hive. I enter "a" so it shows up first on the list.
(when you are finished editing your registry remotely move to the top level of the named key ("a"), and click File->Unload Hive. DO NOT SKIP THIS STEP)

Now when you go into "a" you will see all the HKEY_LOCAL_MACHINE registry entries for your sick hard drive with the exception of SYSTEM/CurrentControlSet. This key cannot be accessed remotely. If you need to access it all is not lost however.

If you had any system restore points saved on your sick drive, navigate to G:\Windows\System32\config\RegBack (again replace G with the drive letter assigned to the sick drive) and copy the SYSTEM file. Paste it into G:\Windows\System32\config, replacing the file that is there currently. The only downside will probably be that you will have to re-install any programs since that restore point was created.

Alternatively, if you have a clone of the sick drive from before it was sick you can copy the SYSTEM file from G:\Windows\System32\config (replacing G with the drive letter assigned to the CLONED DRIVE) instead. If you have both restore points on the sick drive AND a clone of the drive before it became sick I would recommend you to choose whichever SYSTEM file was created last.

Good luck!
Thank you GarFin_au!