Windows 10 crash with True Image 2017 (Insider Preview Fast Ring)

I'm running True Image 2017 on 4 separate Windows 10 PCs. One is on the standard Creators Update, two are on the Insider Preview Fast Ring (16288) and one is on the Fast Ring Skip Ahead (16362). It is this last one that I've just started having problems with.

After running my PC for about 5-10 minutes, it just shuts off, with no warning. I can't see anything in the Event Log.

If I run Task Manager before, I can see that Acronis True Image starts and runs for a couple of minutes before the crash.

If I stop all the Acronis services, and also use SysInternals Autoruns to stop the two Acronis jobs, then everything works fine (apart from no backups!)

I had been running this build without problems for a few days. However I only got this problem last night, when my scheduled backup was due to take place.

David, I have not seen any recent reports of significant problems being caused by these latest Insiders builds - just one for 16362 that I can recall.

I am running ATIH 2018 & 2017 on Insiders 16288 with no problem on two separate computers but have never been on the Fast Ring Skip Ahead path, which I believe is now closed to new users. At least when I tried to enable it, I was given a message to that effect.

I can only recommend opening a Support Case direct with Acronis for this, as this should equate to the changes to be introduced with the Fall Creator's Update 1708? due next month, so I would hope that development have had some systems testing this too.

Note: previous issues with Insiders builds tend to have been resolved by the next build rather than by any action on Acronis' part.

The Skip Ahead branch will be for the first release of Windows 10 in 2018, not the Fall release. The 1708 release doesn't appear to be affected.

I ended up having to restore back to a previous Windows 10 build following other issues, and then put my updates on a 1 week freeze. This took me up to the release of build 17004 earlier this week. This has been more stable, but still has a GSOD with Acronis True Image 2107 when it started its weekly backup this evening.

At least I now get an error when it crashes - TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE

Removing the backup via the Acronis UI stops the crashes, so I'm pretty sure it is related to Acronis.

The Fall Creators Update will be released soon, so after that all Fast Ring PCs will be on the same build. I'll move one of my PCs on the Slow ring and keep one on the Fast ring. The hopefully I can see if it is just one bad PC, or potentially more widespread.

Russell, after filling in the form as shown in your screen shot, can you scroll further down to where it shows fields for your email address and telephone number, then below that your country and finally, a button showing NEXT which when you click submits the ticket.

I have just done this myself based on this forum topic with a copy of the topic pages, so hope they don't ask me for more information as I don't have a system with 17017 yet so haven't seen this actual problem myself!

@thecreator I found the reason for the missed Insider builds - on my Insiders settings page I had a message informing me that these were being blocked by my Organisation Group Policy settings despite being a home user, no organisation etc!

Made a registry change per webpage: Insider Preview Build settings - restarted and 17017 has since been downloaded and is installing (currently at 82%)...

@snuffy smith, welcome to these User Forums. Please open a New Topic if you still cannot install ATI 2018 when not in Safe Mode, as that is a different issue to this topic thread.

I have the same problem. The WhoCrashed tool shows the following. I filed a support ticket.

On Sat 11/11/2017 2:31:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111017-7671-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0xA840)
Bugcheck code: 0xCF (0xFFFFF04A6DB9A840, 0x10, 0xFFFFF04A6DB9A840, 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.

I didn't need to delete any of my backup tasks when updating Windows to build 17035 and all was fine after doing the upgrade though I did reselect the source & destination for my backups just for the sake of ensuring there was no issues due to any new Recovery partitions being created.

@ martin stein , computer had crashed. When you restart the computer from the crash involving Acronis, the Acronis programs will start trying to complete the Backup Task within a few minutes of reaching the Desktop, I learned from the crashes.

That's why, it would crash repeatedly, until I deleted the Backup Job, I had created to back up the New Build.

By the way, it takes me about 10 minutes to restore a partition using Windows, as oppose to using the Bootable Rescue CD.

Morton, thanks for the clarification - I was fortunate that any BSOD's I hit with the earlier Insiders builds didn't give me the scenario you described as I have always disabled the task Error Handling options to prevent any runaway retries etc.

Same issue here on 17025; Fortunately I too do manual recoveries if there is a failure so I didn't get stuck in the reboot loop. I pretty reliably see "TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE". I opened an Acronis case.

The issue seems to have been resolved in the latest fast ring build, however, Acronis support did accept my support request and have been actively investigating (it was escalated twice to a higher level of tech support and then to the devs).

I've emailed since to report that the issue is resolved but I would imagine they would be keen to discover this issue in case it's something they have to account for in future builds.