Skip to main content

BOSD by Acronis 2019?

Thread needs solution

I recently purchased a copy of ATI 2019 to back up my computer and everything seem to be working fine. About a week ago I got a BSOD indicating KMODE_EXCEPTION_NOT_HANDLED What failed: partmgr.sys. I restarted the system and everything seemed to work fine and tossed it up to some fluke. Las night I had another BSOD with the same error so I knew something was not right. I began to review the dump file which stated the following:

 

On Thu 4/4/2019 7:44:44 PM your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: fltsrv.sys (fltsrv+0x3996)

Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8021B9719E9, 0xFFFFAA81F05AA138, 0xFFFFAA81F05A9980)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\Windows\system32\drivers\fltsrv.sys

product: Acronis Storage Filter Management

company: Acronis International GmbH

description: Acronis Storage Filter Management Driver

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: fltsrv.sys (Acronis Storage Filter Management Driver, Acronis International GmbH).

 

And

 

On Thu 4/4/2019 7:44:44 PM your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\040419-7625-01.dmp

This was probably caused by the following module: snapman.sys (snapman+0x2D829)

Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8021B9719E9, 0xFFFFAA81F05AA138, 0xFFFFAA81F05A9980)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\Windows\system32\drivers\snapman.sys

product: Acronis Snapshot API

company: Acronis International GmbH

description: Acronis Snapshot API

Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.

This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: snapman.sys (Acronis Snapshot API, Acronis International GmbH).

 

I’ve attached the dmp files to this post in hope it helps determine or if this is an already known issue could you advise on what I need to do? I un-install ATI 2019 to see if I anymore BSOD occur. Any help would greatly be appreciated.

 

***Edit***

This is odd but it's not letting me upload the dmp file.

Attachment Size
Dump_Files.zip 267.02 KB
0 Users found this helpful

Carlos, welcome to these public User Forums.

I am not aware of any recent issues with ATI 2019 causing BSOD's in Windows and have not seen any reports of this type of serious issue in the forums for 2019, 2018 or earlier products for a very long time.

If you are confident that this is definitely caused by ATI 2019, then I would recommend that your open a Support Case direct with Acronis Support who will then provide you with details of how to upload any dump files via FTP for analysis by the developers.

Note: there is a problem in the forums at present that is not allowing file attachments which we are hoping will be resolved soon though this may not help if your files are larger than 2MB, which is the size limit in the forums.

If you have had older Acronis products installed previously, then it is possible that the filtsrv.sys and/or snapman.sys drivers could be miss-matched to ATI 2019 and cause issues.  In this case, please download and run the Acronis Cleanup Tool - link below in my signature - which will attempt to remove all residue of any Acronis True Image or Disk Director applications.  The computer should be restarted after using the tool.

Is this system using any over clocking of memory or CPU? There have been a few users report that with OC, they start to see instability with ATI. I myself have a 6600k OC to 4.3 but that's all I can go. Memory is OC to 3000 too and I'm stable. So OC will vary from system to system.

If so, test be remonvig the OC completely for awhile.   Then, gradually up it a little to see if/when it returns.

I do have overcloked memory via XMP. I've sent in a ticket with the latest dump file from this mornings BSOD pointing to ATI (also now added these files to my post). I don't understand when it triggers this since I won't be using ATI at the moment when it crashes.