Skip to main content

TI 2010 BSODs with removable media

Thread needs solution

I'm bumping this up again from:

http://forum.acronis.com/forum/3828

This is (roughly) what I said:

About 50% of the time on SD insertion I get a BSOD. To note, the SD reader is part of my laptop and non-removable (plus I use it everyday).

I have the latest released build 5,055. Supposedly this is fixed for Backup & Recovery users by installing a new SnapAPI driver (and or the newest build). However that was actually some time ago and quite a bit older than ATI 2010, thus I'm hesitant to install SnapAPI.

BTW - this is pretty insidious. I would have had no idea ATI was the issue unless I happened upon it in a Google search (and that was a real piece of luck). I know Acronis won't like this idea, but I suggest they notify their end users lest they think something is intrinsically wrong with their PCs.

Acronis has a very good reputation, but something like this can go a long way toward changing that.

Acronis, please provide a fix.

ADDENDUM:

According to this thread:

http://forum.acronis.com/forum/3235

Posted 10/18 of this year:

"We have released a new build of Acronis Disk Director Suite 10.0 (Build # 2239), it works correctly with the latest build of the SnapAPI module"

So a fixed SnapAPI should exist - in which case, why no fix for us ATI users?

Thanks.

0 Users found this helpful

Also posted this here:

http://forum.acronis.com/forum/3828

--------------------------------------------------------------------

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...