BSOD snapman.sys
just installed 2016 yesterday now getting BSOD snapman.sys.
Luckily I had a restore point and was able to go back. Left a few things in start menu.
the log is gone, i have a picture of the screen if that helps anyone I will post.
Was it a clean install of ATI 2016 or was it installed over an earlier version (if so which version).
Ian
Clean install for me. last time i used it was 2012 version on a different PC.
I have the same issue, but only when booting into safemode
win10 x64
Posted yesterday https://forum.acronis.com/forum/96717
I have the same issue than p1tr473. Snapman.sys will cause an BSOD on Windows 10 when I try to boot in safe mode.
Hello Everyone,
Tim, zig11727, as far as I understood you get BSOD NOT in safe mode. If I'm right, please contact our support team for investigation:
http://www.acronis.com/support/contact-us.html
Karl, p1r473, could you please send a system report from affected machines using in-product feedback form? Karl, do I understand correctly that you also have Windows 10 x 64 bit system?
Thank you,
Anna
I had the same BSOD when i created a WINPE based Rescue Media with the Windows 10 ADK on an USB stick and tried to boot it.
Created an standard Rescue media and that booted fine.
/Håkan
Hello Everyone,
Tim, zig11727, as far as I understood you get BSOD NOT in safe mode. If I'm right, please contact our support team for investigation:
http://www.acronis.com/support/contact-us.htmlKarl, p1r473, could you please send a system report from affected machines using in-product feedback form? Karl, do I understand correctly that you also have Windows 10 x 64 bit system?
Thank you,
Anna
My OS is Windows 10 pro x64
The first time I installed True Image 2016 endless boot loop could not even boot to the desktop I had to re-image my computer to a prior image which have True Image 2015 installed after the re-imaging I re-installed TI2016 again all was well till I tried to boot to safe mode endless loop booting into safe-mode after that I tried to remove True Image 2016 to re-install True Image 2015 that failed too.
At this point I re-image the computer with image that had True Image 2015 installed all is OK now but a solution is needed for True Image 2016 and tools to completely remove TI2016.
I have been a customer for five years and after this I will be looking at other imaging solutions.
Hi Everyone!
We were able to reproduce BSOD in safe mode on our environment and development is already working on the fix for that.
As for BSOD of the system itself, we need to investigate it on case by case basis. And that is why I ask Tim and zig11727 to contact support team in chat or via email.
Thank you,
Hello Anna, yes this is true I am running Windows 10 x64. I will reproduce the issue and will send you the eventlog / system report along with some details from bluescreenview. Curiously the past BSOD was neither logged in the event log nor visibe to bluescreenview and given the time it happens when booting safe mode it seems to happen very early during the kernel boot stage.
How so, when you launch the pre Windows Environment from the recovery partition or the DVD respective USB stick containing Windows 10, still he would launch the same affected OS, if I don't go and boot a complete different Windows environment like WinPE. Am I wrong with that assumption Echantech?
Upgraded to Windows 10 TP b10525 but the snapman BSOD still happens when trying to start in safe mode.
Quite unfortunate I cannot provide any dumps as the BSOD is not registered by the system. You won't find any entry in Nirsoft Bluescreenview nor the Windows Eventlog that could help you to find the cause.
Find my System Report attached.
All I could find is an entry that comes close to the timestamp of the BSOD:
Eventviewer, System, EventID 46, source volmgr
Protokollname: System
Quelle: volmgr
Datum: 24.08.2015 08:17:50
Ereignis-ID: 46
Aufgabenkategorie:Keine
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: Karls-PC
Beschreibung:
Die Initialisierung des Speicherabbildes ist fehlgeschlagen.
Ereignis-XML:
46
2
0
0x80000000000000
546
System
Karls-PC
\Device\HarddiskVolume4
0000000001000000000000002E0004C0091000000F0000C000000000000000000000000000000000
Karl,
Look in registry and see if the snapman.sys entry is pointing to the correct file and also as weird as it may seem, that the entry hasn't any spaces before or after snapman.sys
It would also be worth checking the upper and lower filters entries for the same thing.
Snapman is at HKLM\system\controlset\services\snapman
I'm not on the system that has TI installed, so I'll have to look up which folder under Classes has the upper and lower filters entry.
Hello Colin, thanks for your help. I found out an interesting detail. This is what regedit exports in a file
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\snapman]
"DisplayName"="Acronis Snapshots Manager"
"WOW64"=dword:00000001
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,73,00,6e,00,61,00,70,00,6d,00,61,\
00,6e,00,2e,00,73,00,79,00,73,00,00,00
"Group"=""
but the screenshot (screenshot.png) states otherwise. For some unclear reason the ImagePath turns from a string into a hex value when I export the regkey. Strange enough, isn't it?
There exist serveral versions of snapman.sys in %windir%\system32\drivers
the actual internal version of Snapman.sys is 4.6.0.2434.
Addition:
I am not an expert about setting up a Windows Service, but if I assume that the service is flagged as WOW64 = 1 shouldn't the snapman.sys rather be located in C:\WINDOWS\SysWOW64\drivers ?
Moreover if my assumption is wrong, I think the given path maybe wrong. I have checked other drivers and most of them (not all) point to %systemroot%\system32\drivers\
so it seems the Imagefile string does miss the %systemroot% variable in the path. I have edited this myself and will try out if the error is still there.
In two days i had to recover the system 2 times due to snapman.sys making the os unbootable.
But with a simple search on the forum looks like it's a problem since ATI 2011... :-/
Very nice.
Carlo you can disable snapman as long there is no fix from Acronis.
https://forum.acronis.com/forum/97512
Thanks Karl,
I have snapman.sys in both:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
and
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\
Should i put DWORD=4 to both?
Hi Karl,
did that.
If you disable snapman.sys you won't be able anymore to select a disk or a partition when defining new backups :(
C.
I don't want to disable anything just fix the problem A backup program that leaves the system bootless.
This problem also affects Windows 8.1
No wonder it was free update.
solved in build 5576
Will test today. Had same issue in win 8.1 x64.
Got BSOD after upgrade on both normal and safemode bootups.
Did a fresh windows install and fresh install of 2016 (non 5576). BSOD in regular bootup went away but safe mode got BSOD with error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (snapman.sys).
Completely removed acronis and did a full cleanup which then caused problems or corruption with Windows system restore and shadow copy functionality. Device manager shows numerous problems on Generic volume shadow copies due to "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)"
Installing version 5576 today to test and will try to post back with results.
5576 seems to have resolved the specific issues I mentioned of:
BSOD in safe mode and/or regular boot
Generic Volume Shadow Copies in device manager showing as broken due to "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)"
Windows Restore not functioning properly after initial acronis removal due to listed problems
The problems seem to have also caused the backups to either be corrupted or incomplete since they cannot be validated. Adding them as existing backup also causes issues due to missing.corrupt volumes but in my case was not as big of a deal since I have multiple other backup methods for security. I simply added them as new backup tasks.
-----------------------------------
A new problem (And possibly off topic - please point me to the correct topic if one already exists that I couldn't find while I searched) is that even if I completely remove all backup files and create a new backup task, that task is duplicated in the program. For example if I create a new task called files to replace my old one that has had all backup sets removed, it shows twice in Acronis.
Even though I removed the old tasks I do HATE that when you add an existing backup, you lose all schedules and configuration options related to the backup task. Again, off topic from this post, but if there is a way to export this configuration or save it somehow so you are not required to essentially configure the whole backup again, please point me to that post or information.
-----------------------------------
Thank you in advance. I will share any updates if necessary.
Please only modify the Currentcontrolset. The Controlset001 is used if you decide to make a Rollback. Those backup copies in the registry are not active and should not be touched.
I am a bit confused about the messages I read about snapman.sys. Can you concretize the issue and how to reproduce them? @Noisy
For the past few weeks I have been getting a BSOD about once every few days with error 0x0000007E pointing to snapman.sys. I have True Image 2017 build 8029, which has had zero problems until the past few weeks. Windows 7 Ultimate on desktop. No new hardware, no system changes. It is NOT happening in safe mode. Typically I am just working on my computer when it happens, not doing anything specific, working in ms word or doing online research or... Need this to stop. Any help?
Krispin,
I recommend that you contact Support and open a ticket with them on your issue. As version 8029 is the latest release the developers will want to investigate.
Yours is the first case I have seen with this issue so it may be something specific to your installation.
Krispin is not the only one having this issue. I've had it since the first time I installed it in July 2017. I uninstalled the program and figured out that I would have to use another product. I recently had a change of heart and reinstalled it. Same issue: snapman.sys BSOD a few days apart (not at start, apparently at random times). I'm trying to use ATI 2017 in 64-bit Windows 7 Ultimate SP1.
One more question: which services could I remove/disable and still being able to backup my system?
- Michel
Michel, welcome to these User Forums.
Sorry to hear of problems with snapman.sys - this is not an issue that I have seen reported in these forums for a long time (as shown by the previous post in this topic being from March 2017).
You should ensure that you have the final build 8058 version of ATI 2017 installed plus also check that you don't have any old versions of other Acronis products installed, such as Disk Director which may also provide another version of snapman.sys?
With regards to removing services - see KB 60522: Acronis True Image 2018: Windows services and processes which should give you a better understanding of what each of these does. Note: the key service that needs to be present is the Scheduler2 service that is required for doing backups. There is no list for the 2017 version so ignore any that are not found / shown on your computer.
Yes, I have build 8058. Looks like it hasn't been updated since June 2017. I only want to run backups manually. I've read that once I've configured the backups, I can just remove snapman.sys and keep making my backups eternally. Is this right? I guess I'd have to also define a cleanup value, otherwise I'd run out of space at some point.
BTW in the registry, the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F} appears about 20 times. Is this an issue?
Michel, if your ATI backups are using the default Microsoft VSS service then you shouldn't be using the Acronis snapman.sys process but this does not explain why you are seeing BSOD's unless there is some other reason why snapman.sys is being invoked?
With regards to the registry entries, there should only be one unique entry and the one you quoted above does not point at snapman.sys on my computer but at setupapi.dll (if I remember correctly from checking through regedit). There were only 2 entries for snapman.sys found in a search of the registry, neither were found in Class entries.
I ran VSS Doctor to make sure the service is configured properly. This might solve my issues (knocking on wood). I like to disable many of the Microsoft services to make my PC faster. I found snapman.sys in only one key and it's a service. What should I do with that duplicated key? Should I deleted them and only keep one copy? Sounds risky...
Cheers,
- Michel
Michel, whatever decision you make about the duplicate registry keys, I can only strongly recommend having a full good backup of the drive along with a backup of the registry / export of any keys that you choose to remove.
If you have another computer with the same OS etc, then take a look at what that has got for these same keys?
Personally, I would be tempted to do an in-place upgrade repair of your Windows 7 OS and let that process clean up the registry. See webpage: How to Do a Repair Install to Fix Windows 7
snapman.sys just crashed my PC again. I had not touched the registry.
Michel, snapman.sys shouldn't be invoked unless you are running an Acronis backup that is not using the MS VSS snapshot method. Apart from my previous suggestions above (i.e. in-place repair / upgrade of Win 7) - have you simply tried renaming snapman.sys to say snapmanXX.sys in the C:\Windows\System32 folder. Also, have you searched to confirm that is the only copy of this file present?
Michel,
Be very careful what you do with snapman.sys. The Acronis snapman driver is a kernel level driver that loads during Windows boot. It works in conjunction with another driver called fltsrv.sys. If you mess up these drivers, you could prevent Windows from booting!
Most likely, you have a conflict in your system between snapman.sys and a driver from another software package. These conflicts are rare. They are also difficult to pin down. My advice would be to uninstall True Image and run the cleanup tool. Then reinstall True Image. If the problem persists you should open a support case with Acronis.
Paul, thanks for joining this conversation and offering your advice on this topic.
OK I just renamed snapman.sys to say snapmanXX.sys in the C:\Windows\System32\drivers folder. I don't know how many copies I had in the system. Windows search had not even found the one above. I am now running a duplicate file finder. I'm just pondering what I'm gonna do next. Perhaps uninstall again, and repair... I don't know if Acronis will let me open a case since my support ended in 2017. I had uninstalled everything in spite after my many failed attempts. I thought I'd give it another try, but it may end up just the same way as before.
Michel, please heed the advice above from Paul ref snapman.sys