
Speedy-VI
8 discussion posts
Hello,
I have been using the licensed version of DisplayFusion for many years without crashes on my computer running Windows 10. DisplayFusion began crashing immediately after upgrading from v12.0.2 to v12.1. The crashes continued after upgrading to v12.1.1. The crashes are repeatable. Reliability Monitor shows multiple crashes beginning on the day I upgraded to v12.1.
WinDbg analysis of application dumps from both v12.1.0 and v12.1.1 produced the same Failure Bucket ID and identical Failure Hash {4f335f13-e945-3e5a-08b5-ab793970a677}, and reports the exception occurring in coreclr.dll!ProcessCLRException+0x13f with an access violation (0xC0000005). I have seven Windows Error Reporting (WER) full-memory application dumps and can provide one or more of them if they would be helpful. Please let me know if you would like me to provide one or more of the WER dump files or provide additional WinDbg output. They vary in size from 533MB to 1.32GB, which even Zipped will exceed the 50MB attacment limit. I can provide a Dropbox Link.
DisplayFusion v12.0.2 was stable on this system for months prior to upgrading to v12.1.
Details from the most recent crash:
Windows 10 Pro 22H2 (19045)
.NET Runtime 10.0.10
Faulting application: DisplayFusion.exe
DisplayFusion version: 12.1.1.0
Faulting module: coreclr.dll
Module version: 10.0.1026.32716
Exception code: 0xC0000005 (Access Violation)
Failure Bucket:
INVALID_POINTER_READ_c0000005_coreclr.dll!ProcessCLRException
Failure Hash:
{4f335f13-e945-3e5a-08b5-ab793970a677}