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}

Yes. In fact, DisplayFusion crashed again today. The Dump file is 926MB. I tried compressing it into a RAR file and a ZIP file but both exceed your 50MB file upload limit, so I copied the latest Dump file into a Dropbox folder. The link is below. It will expire in one week. I have 7 more Dump files. If you would like to look at the others, let me know and I will copy them to the Dropbox folder. I tested this link and it works, but please let me know if you have any trouble downloading the Dump file.

https://www.dropbox.com/scl/fo/djwmcapnrwfdbt0fwgqc2/AHBfbGkpthtt7dNeNbYT3tg?rlkey=0ljihkonxecx495x367rgwbjt&st=q91hjd1y&dl=0

Thanks

Thank you. I misspoke in my last post. The latest crash Dump file was generated on 03-August, not 04-August. I thought it crashed yesterday (04-August) because midday yesterday I noticed that my DisplayFusion multi-monitor task bars were gone and DisplayFusion was not running. I restarted DisplayFusion and it’s been fine since then. Whatever happened yesterday (04-August) did not generate a Dump file, and the Windows Reliability Monitor did not record a DisplayFusion crash on 04-August. It did report a crash on 03-August. That crash is what generated the Dump file in the Dropbox folder.

Hi again. DisplayFusion v12.1.1 crashed again this evening. I rebooted after a day of heavy computer use and when the reboot was complete, DisplayFusion was not running. The Reliability Monitor recorded another crash and there was a new Dump file. I copied it to the Dropbox folder that I provided a link to in case your Devs want to look at the most recent crash Dump file.

DisplayFusion has crashed one more time since my lsat post. I do run Windhawk. I will shut it down and prevent it from starting automatically and see if the DisplayFusion crashes stop. If they do, does this mean I cannot run Windhawk and DisplayFusion? Windhawk offers a bunch of Windows mods, mostly for Windows 11. I am running Windows 10 v22H2 Build 19045.7548 and only have 3 Windhawk mods running. They are "Better file sizes in Explorer Details", "Explorer Up → New Window/Tab Cntrl-click on explorer up-button opens parent in a new window or tab", and "Modernize Folder Picker Dialog". Does your dev team know if 1 of these 3 Windhawk mods is causing DisplayFusion to crash?

Many thanks for your support!

One other potentially relevant finding: I had also been experiencing intermittent Event Viewer freezes. I captured a user-mode dump of mmc.exe while Event Viewer was actually frozen and analyzed it in WinDbg. The MMC UI thread was blocked in a synchronous COM/RPC call involving UIAutomationCore/MSAA focus handling (get_accFocus, GetFocusedChild, etc.).

Running lmv m AppHook64* on that dump showed the DisplayFusion 12.1.1 application hook loaded in the frozen MMC process:

C:\Program Files (x86)\DisplayFusion\Hooks\AppHook64_3418A085-A63A-458D-9353-8B7E894A2778.dll

I then added both C:\Windows\System32\mmc.exe and C:\Windows\SysWOW64\mmc.exe to DisplayFusion Compatibility and enabled "Disable Application Hooks (this application only)". Event Viewer has not frozen since making that change.

I realize this does not by itself prove the DisplayFusion hook was the root cause, but the combination of the hang-dump stack, the DisplayFusion hook being loaded in the frozen process, and the freezes stopping after disabling the hook for MMC seemed worth mentioning.

Yes I plan to leave the mmc.exe hooks disabled in DisplayFusion, at least until the crashing issue is resolved. DisplayFusion crashed again today. This is the first time it has crashed since I disabled Windhawk 2 days ago. I copied today's Dump file into the shared Dropbox folder. Its the one dated today. I appreciate the efforts to figure out what is causing DisplayFusion v12.1.0 and v12.1.1 to crash on my Windows 10 system.