Acronis True Image 2019 Perpetual "Blue Screen" Freeze (Stop Code CLDFIT.SYS
Several days ago I replaced my 10 year old HP PC (WIN 10) that included a working (flawlessly) copy of Acronis True Image 2016. I decided to upgrade my license to Acronis True Image 2019 on my brand new HP Envy desktop. Midway through my first attempted backup I got the dreaded "BSOD" with a StopCode = CLDFIT.SYS. Since my computer worked perfectly until I installed Acronis I decided I would uninstall/reinstall the software. When I went to enter the encryption password in the Options for my new backup, I got the dreaded BSOD again followed by a hard reboot. Several more uninstall/reinstalls resulted in BSOD again. I then contacted Acronis Chat Tech support who reviewed the Windows Event log, again showing no issues. I also ran a System File Scan and DISM scan on my computer with no errors. I uninstalled Acronis again and did not reinstall. I used Windows 7 backup instead. No more BSOD. I am not a computer expert by any means, but I think their is a System file conflict caused by Acronis interacting with Windows. Don't get me wrong, I love Acronis True Image but this release is causing a big insurmountable issue on my Windows 10 computer. I will try to see if I can reinstall the older Acronis 2016 release that worked fine until two days ago on basically the same Windows 10. Also, I made sure all Windows updates were installed. I various HP provided system diagnostics. No problems noted. One other thing I did was to remove Acronis from Windows Start (it worked fine on my old machine). Anyone have any ideas of the problem would be appreciated.
Update: 02/03/18. Yes. I installed the latest build for the 2019 release. I also installed Acronis 2016 that worked well on my old Win 10, but caused BSOD on the new machine. It could be that There is a corrupted windows install at the factory or some new system file. The Windows stop codes are detailed enough to tell you which driver is problematic. I checked the version of the Cloud Mini Driver Filter (CLDFIT.SYS) and dated sept 2018 so it seemed current.
My next step included a Microsoft tech support at which time I did a complete Windows Home 10 reinstall. I hope this is the answer. I will know later today.


- Log in to post comments