Haevn't seen a BSOD in years until Acronis 2017...
I have read several posts that indicate uninstalling Acronis creates more problems; an unbootable computer being one of them. The fact that Acronis doesn't have a dedicated installer was my first red flag. No dedicated installer and posts about going into the registry or using a cleaning utility to "completely" remove registry modifications indicates to me that Acronis doens't actually know how to make a dedicated uninstall program for thei own product. What else am I to think?
I am not a beta tester, certainly not with anything that can make my workstation unbootable.
I should blame myself, perhaps. I'm not exagerating when I say it's been years since I saw a BSOD. The reason is I usually run a tight ship; really tight. I had used the WD version in the past with no problems so I made the mistake of thinking the full vesion would work as reliably. Now I am at risk of having to rebuild a system drive that will take several weeks to do so. Several weeks.
To make matters worse I disovered that Acronis won't allow me to use an alternative that has the potential to do what Acronis can't.
Snapman.sys is apparrently the prolem and it has apparently been a problem for some time if forum posts are any indicateion. It's also apparently a "known bug" and has been for years.
I am at a loss.


- Accedi per poter commentare

Win7 Pro
Install, shut down BSOD.
No upgrade. Previously had WD version installed (as per my OP), unisntalled it, installed full version, BSOD at shutdown.
Define stop code.
I had several cloned drives from the WD version, Acronis bricked them all. Now... no backups.
I clone instead of backup.
I've had viruses that were less destructive than this. Every drive the full version of Acrionis has touched is now "infected" or bricked by Acronis' buggy undisciplined coding.
And, yes, I understand the "flies" "honey" "vinegar" maxim but this is sending me over the top.
- Accedi per poter commentare

Sorry but I am still struggling to know how to try to help you with so little information.
When you have a BSOD, it shows a raft of numbers on the screen, where towards the bottom of this, it normally shows the text:
Stop code: 0x000000?? followed by the name of a program that is deemed to be the main cause of this error, i.e. snapman.sys - see example BSOD attached below.
m1ckDELTA wrote:I had several cloned drives from the WD version, Acronis bricked them all. Now... no backups.
I clone instead of backup.
Sorry again, but the downside of doing cloning is that you have no safety net if anything goes wrong. It may not be a great comfort at this time, but please see post: 128231: [IMPORTANT] CLONING - How NOT to do this!!! which was written in response to the many problems we see in these forums that is caused by cloning going wrong.
I would strongly recommend opening a Support Case directly with Acronis Support for this problem, where someone can try and work with you to try to recover your system and investigate why you saw the BSOD in the first place.
Allegato | Dimensione |
---|---|
410376-138262.png | 110.95 KB |
- Accedi per poter commentare

Hello m1ckDELTA,
Thanks for reporting the issue. We will gladly help you to resolve it! The issue that you have faced is not a "known bug" that has been for years. BSOD with snapman.sys is a sympthom that may have many different causes. The issue is uniquely identified only by memory stack, saved into a memory dump file, which will be worked on by Acronis experts. I have opened a support ticket for you, case number is 02971187.
If you have any disk defragmentation software, like DiskKeeper, you can see if it has some relation to the issue by uninstalling it and seeing if the BSOD reoccurrs. As this kind of programs and Acronis both work at the same level of access to the disk, potentially there might be a conflict between them.
A comment regarding the uninstallation. There is a dedicated installer and a dedicated uninstaller (two). Files, folders and registry entries left by the built-in uninstaller are absolutely normal for every software. Mostly these are small configuration files and settings that would be reused if you re-install the program in the future. You do not have to remove them and use another uninstaller - CleanUp Tool.
CleanUp tool should not be used for every uninstallation. It has been created for troubleshooting a very limited set of technical issues. As you may expect from any troubleshooting procedure, it includes non-standard actions, like working with the registry. Again, you do not have to do this in normal situation. Moreover, working with the registry here is a double-checking measure. It is expected that by using the registry editor you just verify that the CleanUp tool did its job.
Regards,
Slava
- Accedi per poter commentare