Hello Frobozz ,

According to the provided information, the issue is not connected to Acronis, the report just says that it did not find symbols for our drivers.

However, we cannot check it without a dump file.

Would you have the possibility to contact Acronis Customer Cental? The link is in my signature below.

I can, will, contact support and, I guess, start a "new ticket".

I'd prefer to have found the Symbols for the WinDBG machine beforehand. Do you know where I can get them for the SYMBOLS folder here?

Also would prefer to have uninstalled this latest version, whatever it is, and try an earlier one. I do not find a tab or link to tell me what the build is that I am running, however.

What 'Dump' do you refer ? I have the Crash-Dump.

This BSOD has happened today twice ... never happened until a version or two ago.

We cannot share the Symbols for our drivers as they are company's private data.

Here are the logs needed for support to investigate the issue:

https://kb.acronis.com/content/46370#Windows0

As for the previous versions, you can find them in your account at acronis.com. When you log in, click "Downloads" and select the version as in the screenshot below.

In the product you will also have "Account" tab where you will see which build you are currently using.

You can uninstall Acronis True Image via Programs and Features or with the Cleanup utility: https://kb.acronis.com/aticleanup

Please, just make sure to act according to instruction if you choose Cleanup utility and export your backup settings: https://www.acronis.com/en-us/support/documentation/ATI2018/#10147.html

Status is that I used your suggestions to uninstall/re-install .... however, I've left it uninstalled, so far, to see if I get any BSOD's.

I will reply again after a few days of testing with No-Acronis installed.

Thank you for the help so far.

Thank you! I will be waiting for your reply.

I am satisfied that the system here was fully put to work sans Acronis.

I just now installed AcronisTrueImage2018_9207 and am running it (again).

We will see if the system as well as equipment control programs (here) function without a BSOD.

If so, after a few days, I will "upgrade" to whatever is your latest version and further test.

Thanks for the patience.

Crashed just now.. Had 9207 installed. What is the next oldest version please. I will try that.

Remember, Acronis ran flawlessly for a good deal of time, in months. There was an update then this occurred.

I will now uninstall Acronis and wait a day or two as I re-test the system sans Acronis.

Also. I can not get normal spell-check to work on this site, in my Firefox (current updates)

A right-click on a squiggly-underlined word brings up "Paste" instead of list of possible spelling corrections. In all other text scenarios I run across in this Firefox, I get spelling choices.

However, about 30 mins after I used the Acronis Folder "uninstall", I restarted ... then used Sysinternals Process Explorer to search for remnant Acronis pgms, found none ... then suddenly a BSOD.

EDIT: I did get the CleanupTool to run .. once it completed and I rebooted, I am back ow to letting system and equipment run usw. Sans Acronis ...

Then I will install a different version to see if I can attain the stability I had prior to recent Acronis updates.

Will advise ....

Still getting a BSOD. I "thought" I had removed all elements of Acronis. I see I did not.

the other day I began a support ticket. However nobody from Acronis never replied.

Am unsure how to make sure that all previous Acronis-9207 off my computer and out of the registry

Hello!

If after the cleanup nothing has changed, the issue does not seem to be connected to Acronis. As the Cleanup utility should have removed all the traces of Acronis True Image from the registry. Plus, all the Acronis drivers were also removed.

Acronis Support would be able to investigate the case more precisely.

Here's what I see after performing the Cleanup just now ... these two remnants may not be an issue? What I DID see was that I had NOT stopped Acronis System Monitor or whatever it's called ... on the iteration of removing 9207 .. thus Acronis wasn't really removed. Now, there is no icon in the System Tray for the watchdog .. so I am guessing that this test phase is officially Sans-Acronis again.

As for Support, as I said, I never heard back from them.

I am testing the base-level which is No-Acronis, before  re-install some older version.

I personally have no doubt that Acronis is now and was then, causing the BSOD.

I'd gone a few years W/O seeing a BSOD; ... bought Acronis ... eventually an Acronis update came along, then the BSOD's began.

This current testing showed that having it caused a BSOD .. removing it produced no BSOD ; re-installing a ]slightly older version caused a BSOD ...and THEN I tried to remove (9207) and did not follow directions to stop a certain process. Thius, with its entrails still there, I got the recent BSOD .

At this point I will try a few days of testing to make sure no BSOD and then put some version back on in an attempt to get back to the level where I bought Acronis a few months ago and had no BSOD until an unknown update.

It would be immensely helpful if Acronis tech-support was guiding me through this.

BBL

Sorry to have to say this but I do not see any involvement by Acronis software in the screen images you have posted recently.

klbackupdisk.sys and klbackupflt.sys and klif.sys listed in your earlier symbols image are not Acronis components but are linked to BSOD's if you do a Google Search on their names!

These are components from Kaspersky software, not Acronis - they are not found on any of my computers running ATI 2018.

Oy, OK, thanks for the guidance.

then maybe Kaspersky is reacting to an update from Acronis; a change in some parameter ... dunno .. perhaps there was an update to both programs, one of which caused this.

I'll disable Kaspersky and run Acronis for a few days ... I suppose I can turn Windows FW back on

But why do I see that " klbackupflt.sys " in the Acronis Key UpperFilters position? Or is that Key universal and no just Acronis.

The UpperFilters is a more widely used key than just by Acronis.

See KB 48668: Acronis True Image: Cleanup Utility and scroll down the page to section 5. where it deals with cleaning the Acronis entries for UpperFilters if still present after running the cleanup tool.  You will see that they reference very specific entry strings to be deleted with no mention of any starting with 'kl' for Kaspersky Labs.

You will be also asked to reboot the system to complete the uninstallation. Do not reboot the machine immediately (press "n"). Do the following first:

1. 1. Go to Start -> Run -> regedit
   2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
   3. Click on the key
   4. Locate UpperFilters or LowerFilters (if present)
   5. Check for snapman*, tdrpman*, fltsrv, timounter strings: 
         
   6. If there are snapman*, tdrpman*, fltsrv, timounter strings, remove the strings from the UpperFilters and LowerFilters: double-click on the   UpperFilters/LowerFilters and delete the strings: 
          
        (!) Do not delete the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318} key.
   7. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}, check for snapman*, tdrpman*, fltsrv, timounter strings and remove the strings from the UpperFilters and LowerFilters if they are present. (!) Do not delete the key!

Yes, I followed this thoroughly last time, a while ago.

Originally I WinDSbg was telling me Probable casue was PartMgr and that belongs to Acronis and THAT was the reason I began to suspect my install of Acronis.

The other "kl" stuff, well, I am inexperienced using WinDbg .. at this moment I have again messed up the settings and it doesn't work. So who knows what I am not understanding when I copy from it. At this time, WinDBG does not have a line telling me "Probably caused by" because as I said I've messed up its settings

Frobozz ,

PartMgr does not belong to Acronis, it belongs to Windows. Only these belong to Acronis: snapman*, tdrpman*, fltsrv, timounter

for example, from minidumps, here's partmgr

am I correct? Is this from Acronis? I've seen this Probably caused by, a dozen BSOD's

Aye, yer right, if I'd read farther in the module, debugger then I'd see

CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     partmgr.sys
    OriginalFilename: partmgr.sys
    ProductVersion:   6.1.7601.17796

sorry

I have never used WinDBG and it seems that it produces a lot of information that requires a good level of knowledge about the internal working of Windows / applications.

The normal tool that I use for getting an idea of root cause of system crashes is 'Who Crashed' which presents information in a fairly short but clear manner.  This is a free dump analysis tool.

thanks, I'll look it up

I just re-installed that which I D/L when I bought this in August .. to my horror it's

AcronisTrueImage2017_NG_6209.exe

so if it doesn't BSOD me, Ill let the "update" run and see how she runs after that.

--------------addenda-------------------i bought pro version of  'who crashed'

I'm vindicated. Though it's yer fault LOL .. I bought the pgm

--------------------------------here are a few--------------

On Thu 10/26/2017 07:30:50 your computer crashed
crash dump file: C:\Windows\Minidump\102617-31543-01.dmp
uptime: 00:04:18
This was probably caused by the following module: fltsrv.sys (fltsrv+0x415B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800CA04F10, 0x0, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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).
Google query: Acronis International GmbH KMODE_EXCEPTION_NOT_HANDLED

On Thu 10/26/2017 07:01:37 your computer crashed
crash dump file: C:\Windows\Minidump\102617-29437-01.dmp
uptime: 10:42:25
This was probably caused by the following module: fltsrv.sys (fltsrv+0x415B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800E8F9530, 0x0, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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).
Google query: Acronis International GmbH KMODE_EXCEPTION_NOT_HANDLED

On Wed 10/25/2017 20:18:17 your computer crashed
crash dump file: C:\Windows\Minidump\102517-27471-01.dmp
uptime: 1 day, 06:54:19
This was probably caused by the following module: fltsrv.sys (fltsrv+0x415B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800F412530, 0x0, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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).
Google query: Acronis International GmbH KMODE_EXCEPTION_NOT_HANDLED

On Tue 10/24/2017 13:23:15 your computer crashed
crash dump file: C:\Windows\Minidump\102417-29078-01.dmp
uptime: 00:22:04
This was probably caused by the following module: fltsrv.sys (fltsrv+0x415B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800CBDEF10, 0x0, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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).
Google query: Acronis International GmbH KMODE_EXCEPTION_NOT_HANDLED

On Tue 10/24/2017 12:36:44 your computer crashed
crash dump file: C:\Windows\Minidump\102417-18751-01.dmp
uptime: 00:30:29
This was probably caused by the following module: fltsrv.sys (fltsrv+0x415B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88009867F10, 0x0, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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).
Google query: Acronis International GmbH KMODE_EXCEPTION_NOT_HANDLED

On Tue 10/24/2017 10:14:30 your computer crashed
crash dump file: C:\Windows\Minidump\102417-23493-01.dmp
uptime: 01:53:15
This was probably caused by the following module: fltsrv.sys (fltsrv+0x415B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880039F5F10, 0x0, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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).
------------------------------------------------------------------------------------------------------------------------

Frobozz, have you had any BSOD / crashes since doing the clean install of ATI - all your dumps are a few days old?

If you are still seeing crashes, then you need a Support Case open with Acronis Support - we are all just Users here with no ability to investigate the issue further.

Clif Notes: Yes, have had BSODs

What I've been doing, until u suggested the wonderful program, is to remove Acronis completely then wait a few days and run everything here ..which is intensive stuff ... and see if I get BSOD'd ... then re-install Acronis and try different versions ... I went from August until maybe two or three weeks ago, without any problems .. I remember two quick Acronis updates in short order maybe two weeks or sooner. After that, the horses were out of the barn.

I already started a Ticket but they never responded.

Say, tell me please how to make Spell Correction work on this Forum? I use it in Firefox all over the internet. Byt here, a right-click on an underlined wrd brings up "Paste"

It may take a few days to get a response for your Support Ticket, especially when there is a weekend involved and are using email, but they will get back to you (eventually!).

Not sure about the spell correction and the forum, haven't been able to figure that one out myself yet and I am using Google Chrome as my browser - some of the underlining is down to the differences between US and UK English so I ignore that the US folks don't know how to spell according to the Queen's English rules!

Long live the Queen!

To check spelling use CTRL with right click.

Thanks Thomas, that works for me!

Steve (Smith), I had the same problem with spell checking when using Chrome; it turns out you have to install the spell-checking extension (Spell Checker for Chrome): it supports UK English (and if I recall correct Australia English).

Ian

Thanks Ian, not really an issue with the spell checking but the tip from Thomas was useful to use Ctrl when clicking as I occasionally have a senior moment when remembering how to spell some words!  I try to keep to the bare minimum of Chrome extensions with just Xmarks being my only one used (for my bookmarks).

also, thanks Thomas .. WFM  too , I just tested it on Works For Me.

BTW, I have had three BSOD today on build 9850 of ATI 2018

And Steve, many thanks the tip on "WhoCrashed" Program

"Say, tell me please how to make Spell Correction work on this Forum? I use it in Firefox all over the internet. Byt here, a right-click on an underlined wrd brings up "Paste"  "

This has been commented on (read: complained about) a number of times.  (So has the inability to quote from previous posts.  I hope it's clear that the above was a quote.)  There used to be a sub-forum specifically about the new forum format and features but I can no longer find it.  And I don't actually know that that was the appropriate venue for complaints and requests for changes.  There is someone in Acronis-land that knows we are unhappy about the non-standard invocation of spell-check but I don't know if that unhappiness has been formally directed to Acronis.

Patrick, there is still a dedicated forum called: 

Forum Administration

Discussions about ideas and issues related to these Forums and Website

It is hidden away a little in the Non Product Related Forums section.

Same issue. BSOD immediately when starting back up task.

It is definitely Acronis True Image. 

On Thu 11/2/2017 4:57:33 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\110217-37312-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0xA840)
Bugcheck code: 0xCF (0xFFFFC6D129F9A840, 0x10, 0xFFFFC6D129F9A840, 0x2)
Error: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that a driver has been incorrectly ported to the terminal server.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Thu 11/2/2017 4:57:33 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: snapman.sys (snapman+0x222E9)
Bugcheck code: 0xCF (0xFFFFC6D129F9A840, 0x10, 0xFFFFC6D129F9A840, 0x2)
Error: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
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 driver has been incorrectly ported to the terminal server.
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).
Google query: Acronis International GmbH TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE

I have tried a repair, full clean removal and reinstall with fresh setup, compatibility settings, run as admin, disabled all AVFW, no matter what it BSOD every time.  To be sure I installed it a 100% fresh install of windows 10 creator with updates up to 11/1/17. It duplicated the behavior.

I am not sure if this is related, but it also shows two physically different drives as identical hardware despite them not being the same. These crash as well but this could be an unrelated bug I guess.

Strangely, I did get a file-based backup to work yesterday so I am thinking this is only related to full partition/drive backups.

Matt

Matt, based on your dump analysis data pointing to win32kbase.sys and snapman.sys, it looks like you are running on a Windows 10 Insiders build such as 17017 or 17025, both of which are known to cause these dump / BSOD / GSOD issues, and both of which are unsupported by Acronis for running ATI 2018 (or other versions).

See KB 60589: Acronis True Image: Windows Insider Program (beta) builds support for the official statement on this situation.

snapman.sys seems to be one of the causes of BSOD. 

Microsoft (R) Windows Debugger Version 10.0.15063.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows 10 Kernel Version 17025 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17025.1000.amd64fre.rs_prerelease.171020-1626
Machine Name:
Kernel base = 0xfffff800`558fc000 PsLoadedModuleList = 0xfffff800`55c56fd0
Debug session time: Thu Nov 16 02:00:04.241 2017 (UTC - 8:00)
System Uptime: 0 days 23:58:58.957
Loading Kernel Symbols
...............................................................
..........Page b6267 not present in the dump file. Type ".hh dbgerr004" for details
........Page bd888 not present in the dump file. Type ".hh dbgerr004" for details
..............................................
................................................................
..................................
Loading User Symbols

Loading unloaded module list
........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck CF, {ffffaae18660a840, 10, ffffaae18660a840, 2}

*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : win32kbase.sys ( win32kbase!IsProcessDwm+0 )

Followup:     MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE (cf)
Arguments:
Arg1: ffffaae18660a840, memory referenced
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation
Arg3: ffffaae18660a840, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, Mm internal code.
    A driver has been incorrectly ported to Terminal Server.  It is referencing
    session space addresses from the system process context.  Probably from
    queueing an item to a system worker thread.
    The broken driver's name is displayed on the screen.

Debugging Details:
------------------

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17025.1000.amd64fre.rs_prerelease.171020-1626

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  2801

BIOS_DATE:  11/11/2015

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  GRYPHON Z97

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  1

BUGCHECK_P1: ffffaae18660a840

BUGCHECK_P2: 10

BUGCHECK_P3: ffffaae18660a840

BUGCHECK_P4: 2

READ_ADDRESS:  ffffaae18660a840 

FAULTING_IP: 
win32kbase!IsProcessDwm+0
ffffaae1`8660a840 ??              ???

MM_INTERNAL_CODE:  2

IMAGE_NAME:  win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: win32kbase

FAULTING_MODULE: ffffaae186600000 win32kbase

CPU_COUNT: 8

CPU_MHZ: f9e

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xCF

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  HADES-DESK

ANALYSIS_SESSION_TIME:  11-16-2017 10:21:38.0545

ANALYSIS_VERSION: 10.0.15063.0 amd64fre

TRAP_FRAME:  fffffc0195e2ff10 -- (.trap 0xfffffc0195e2ff10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffaae18660a840 rbx=0000000000000000 rcx=ffffae83ec2ef280
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=ffffaae18660a840 rsp=fffffc0195e300a8 rbp=0000000000000002
 r8=ffffae83ec2ef200  r9=ffffae83ec2ef280 r10=7ffffffffffffffc
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
win32kbase!IsProcessDwm:
ffffaae1`8660a840 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80055a892fb to fffff80055a60910

FAILED_INSTRUCTION_ADDRESS: 
win32kbase!IsProcessDwm+0
ffffaae1`8660a840 ??              ???

STACK_TEXT:  
fffffc01`95e2fc88 fffff800`55a892fb : 00000000`00000050 ffffaae1`8660a840 00000000`00000010 fffffc01`95e2ff10 : nt!KeBugCheckEx
fffffc01`95e2fc90 fffff800`559ca60d : 00000000`00000010 ffffaae1`8660a840 fffffc01`95e2ff10 ffffc489`67f283c0 : nt!MiSystemFault+0x13debb
fffffc01`95e2fd30 fffff800`55a6a472 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffaae1`86609c92 : nt!MmAccessFault+0xa8d
fffffc01`95e2ff10 ffffaae1`8660a840 : fffff80a`126b9e4c 00000000`00000000 ffffae83`ec2ef280 00000000`00000040 : nt!KiPageFault+0x132
fffffc01`95e300a8 fffff80a`126b9e4c : 00000000`00000000 ffffae83`ec2ef280 00000000`00000040 ffff53cb`a6947972 : win32kbase!IsProcessDwm
fffffc01`95e300b0 fffff80a`126ba4c2 : ffffae83`ec2ef280 00000000`00000000 fffffc01`95e30194 fffff800`55e6400c : dxgkrnl!CCompositionSurface::Open+0x3c
fffffc01`95e300e0 fffff800`55e63bc8 : ffffc489`67f283b0 ffffae83`ec2ef280 00000000`00000001 ffffae83`f63ce080 : dxgkrnl!DxgkCompositionObject::Open+0x82
fffffc01`95e30130 fffff800`55d9b9af : 00000003`00000000 ffffae83`ec2ef280 ffffae83`ec2ef280 ffffae83`ec2ef280 : nt!ObpIncrementHandleCountEx+0x338
fffffc01`95e30240 fffff800`55d9b1bd : fffffc01`95e30700 00000000`00000040 ffffae83`ec2e2080 fffff800`55a6bd00 : nt!ObDuplicateObject+0x21f
fffffc01`95e304f0 fffff800`55a6bd53 : ffffae84`02f79040 fffffc01`95e307a8 ffffae83`ec2ef280 ffffae84`00000000 : nt!NtDuplicateObject+0x12d
fffffc01`95e30580 fffff800`55a63bb0 : fffff80a`116922e9 00000000`00000010 00000000`00000082 fffffc01`95e307b8 : nt!KiSystemServiceCopyEnd+0x13
fffffc01`95e30788 fffff80a`116922e9 : 00000000`00000010 00000000`00000082 fffffc01`95e307b8 ffffae84`07c34800 : nt!KiServiceLinkage
fffffc01`95e30790 fffff80a`11692342 : fffffc01`95e308b8 fffffc01`95e308a0 ffffffff`80004d58 ffffffff`ffffffff : snapman+0x222e9
fffffc01`95e307f0 fffff80a`11695c91 : fffffc01`95e308b8 fffffc01`95e308a0 fffffc01`95e30940 fffff80a`00000000 : snapman+0x22342
fffffc01`95e30840 fffff80a`116926b5 : fffffc01`000005b0 00000000`00000000 00000000`00000000 fffffc01`95e308f0 : snapman+0x25c91
fffffc01`95e30890 fffff80a`116830ad : fffffc01`95e30930 00000000`00000002 ffffae84`06370700 fffff80a`11682d93 : snapman+0x226b5
fffffc01`95e30910 fffff80a`1168b171 : 00000000`00000002 ffffae84`06370700 fffff800`55ba67b0 ffffae84`02f70000 : snapman+0x130ad
fffffc01`95e30960 fffff80a`1168b03e : 00000000`00000002 fffff80a`11695b1a 00000000`00000002 ffffae84`04b176e0 : snapman+0x1b171
fffffc01`95e30a10 fffff80a`11681298 : ffff8880`0b8de7c8 fffff800`559f3b3c 00000000`00000000 fffff800`559f38cf : snapman+0x1b03e
fffffc01`95e30a50 fffff80a`116812f4 : fffffc01`95e30aa4 fffffc01`90e36c90 fffffc01`95e30aa8 00000000`00000004 : snapman+0x11298
fffffc01`95e30ab0 fffff80a`11691d05 : fffff800`55d089c0 00000000`00000000 fffff80a`11691cec ffffae84`06079ad0 : snapman+0x112f4
fffffc01`95e30ae0 fffff800`5599cb8c : ffffae83`fce492d0 fffffc01`90e36c90 ffffae83`ec2e9c40 fffff80a`107f3ec0 : snapman+0x21d05
fffffc01`95e30b10 fffff800`559e8fc5 : ffffae83`ec2e9c40 ffffae84`02f79040 fffff800`5599ca60 ffffaa9c`40006010 : nt!IopProcessWorkItem+0x12c
fffffc01`95e30b80 fffff800`5592a427 : ffffaa9c`43353c08 00000000`00000080 ffffae83`ec2ef280 ffffae84`02f79040 : nt!ExpWorkerThread+0xf5
fffffc01`95e30c10 fffff800`55a65e96 : ffff8880`0a4c0180 ffffae84`02f79040 fffff800`5592a3e0 ffffaa9c`00000000 : nt!PspSystemThreadStartup+0x47
fffffc01`95e30c60 00000000`00000000 : fffffc01`95e31000 fffffc01`95e2b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  e6a50d2a27931a848418d3e9d6fbbfe2c41df78c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b1fa425dd883027f9aecfefe39bf33b71bb6644d

THREAD_SHA1_HASH_MOD:  5b98a3fd357244d81e986f261f8146ef99acaaf1

FOLLOWUP_IP: 
win32kbase!IsProcessDwm+0
ffffaae1`8660a840 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32kbase!IsProcessDwm+0

FOLLOWUP_NAME:  MachineOwner

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  0xCF_INVALID_BAD_IP_win32kbase!IsProcessDwm

BUCKET_ID:  0xCF_INVALID_BAD_IP_win32kbase!IsProcessDwm

PRIMARY_PROBLEM_CLASS:  0xCF_INVALID_BAD_IP_win32kbase!IsProcessDwm

TARGET_TIME:  2017-11-16T10:00:04.000Z

OSBUILD:  17025

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-10-20 19:57:01

BUILDDATESTAMP_STR:  171020-1626

BUILDLAB_STR:  rs_prerelease

BUILDOSVER_STR:  10.0.17025.1000.amd64fre.rs_prerelease.171020-1626

ANALYSIS_SESSION_ELAPSED_TIME:  6b6

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xcf_invalid_bad_ip_win32kbase!isprocessdwm

FAILURE_ID_HASH:  {53e178ec-2883-7ef7-0c20-d76a64b59073}

Followup:     MachineOwner
---------

Noisy, Vatsan

Please raise a support ticket at https://www.acronis.com/en-us/support/contact-us/ and share the ticket ID with me. Such issues should be investigated with the help of Acronis support team, as any kinds of crashes usually depend on the environment. We'd welcome an opportunity to find the root cause and fix it.