Strahdvonzar
9 discussion posts
System : Windows 10
DF Version : 10.0
Type : Paid Version (Steam)
Issue :
App crashes soon after launching it , without any visible queue.
Can take from a few minutes to about an hour for the crash to occur
It happens randomly even while PC is idle.
When it crashes , the Tray Icon disappears and some Windows actions stop working , like Alt+Tab.
I also tried the Beta 10.3 but faced the exact same issue
Attachments : I have attached the Log from Log Level 1.
----- Windows Event Log -----
Faulting application name: DisplayFusion.exe, version: 10.0.0.0, time stamp: 0x641de100
Faulting module name: mnet.dll, version: 0.9.2.2, time stamp: 0x5ff55998
Exception code: 0xc0000005
Fault offset: 0x000000000002e565
Faulting process id: 0x4910
Faulting application start time: 0x01d97eb840a3e49d
Faulting application path: C:\Program Files\DisplayFusion\DisplayFusion.exe
Faulting module path: C:\Windows\SYSTEM32\mnet.dll
Report Id: 760045cd-4ed5-41cc-a30d-d1ddef568146
Faulting package full name:
Faulting package-relative application ID:
----- Windows Error Report -----
Fault bucket 1336773830520497680, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: DisplayFusion.exe
P2: 10.0.0.0
P3: 641de100
P4: mnet.dll
P5: 0.9.2.2
P6: 5ff55998
P7: c0000005
P8: 000000000002e565
P9:
P10:
• Attachment [protected]: DisplayFusion.log [302,740 bytes]
May 4, 2023 (modified May 5, 2023)
•
#1
If you head to "C:\Users\(YourUser)\AppData\Local\CrashDumps", is there anything listed for DisplayFusion? If so, could you send over the latest one?
Strahdvonzar
9 discussion posts
There is no CrushDump inside the "C:\Users\xxxx\AppData\Local\CrashDumps" for DisplayFusion.
How about this path: %LOCALAPPDATA%\Binary Fortress Software\DisplayFusion\CrashDumps
Strahdvonzar
9 discussion posts
There are a few there. I can provide you the Analyze here , cause attaching them is not easy due to them being quite large exceeding the forum limit (400Mb-500Mb each).
Ps : My GPU drivers are updated to the latest version.
---------------------------------------------------------------
All of them are pretty much the same and apart from a lot of "SOS does not support the current target architecture 'x64'" at the start , the rest is as follows
---------------------------------------------------------------
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 4530
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 7302
Key : Analysis.Init.CPU.mSec
Value: 1296
Key : Analysis.Init.Elapsed.mSec
Value: 33665
Key : Analysis.Memory.CommitPeak.Mb
Value: 152
Key : CLR.Engine
Value: CORECLR
Key : CLR.Version
Value: 7.0.523.17405
Key : Timeline.OS.Boot.DeltaSec
Value: 41360
Key : Timeline.Process.Start.DeltaSec
Value: 754
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 10.0.0.0
FILE_IN_CAB: DisplayFusion.exe.12908.dmp
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
CONTEXT: (.ecxr)
rax=000000000000725c rbx=0000000000000002 rcx=00000000fffffff8
rdx=0000000000000058 rsi=000002ad7cbb1c00 rdi=0000009854a7f7b0
rip=00007ffe9b6be565 rsp=0000009854a7f450 rbp=0000000000000000
r8=0000000000000058 r9=000000000000085f r10=0000000000000056
r11=000000000000085f r12=0000000000000001 r13=000000000000725c
r14=0000000000000022 r15=0000000000007204
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
mnet!crc32c_append+0x26585:
00007ffe`9b6be565 440fb60438 movzx r8d,byte ptr [rax+rdi] ds:00000098`54a86a0c=??
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffe9b6be565 (mnet!crc32c_append+0x0000000000026585)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000009854a86a0c
Attempt to read from address 0000009854a86a0c
PROCESS_NAME: DisplayFusion.exe
READ_ADDRESS: 0000009854a86a0c
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000009854a86a0c
STACK_TEXT:
00000098`54a7f450 00007ffe`9b6ba8a6 : 00000098`54a7f648 00000098`0001201b 00000000`0000007d 00000098`00000028 : mnet!crc32c_append+0x26585
00000098`54a7f5b0 00007ffe`9b6ba0c9 : 00000000`00000000 00000000`00000000 00000000`0000007d 000002ad`7cbb1c00 : mnet!crc32c_append+0x228c6
00000098`54a7f740 00007fff`54f07604 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mnet!crc32c_append+0x220e9
00000098`54a7fdb0 00007fff`550426a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000098`54a7fde0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
SYMBOL_NAME: mnet+26585
MODULE_NAME: mnet
IMAGE_NAME: mnet.dll
STACK_COMMAND: ~30s; .ecxr ; kb
FAILURE_BUCKET_ID: BITNESS_MISMATCH_X64_INVALID_POINTER_READ_c0000005_mnet.dll!Unknown
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 0.9.2.2
FAILURE_ID_HASH: {f609645f-0568-027b-65f8-a54c98ce9815}
Followup: MachineOwner
---------------------------------------------------------------
May 9, 2023 (modified May 9, 2023)
•
#5
Strahdvonzar
9 discussion posts
Can anybody point me towards DisplayFusions official support channel? What can someone, that bought their product do , when experiencing technical difficulties?
Up till now i have tried this discussion board without success. To be honest though , i thought it was an official channel at first , so my expectations where also pretty high in terms of response times. Now that i see that it is run by people trying to help others on their spare time i can understand the delays and i am not after this kind of support.
I have also tried contacting them through their email at "support@displayfusion.com" but 10 days have passed without a single reply.
Am i naive thinking that there is support for diplayfusion? Is the Project long dead and i am too oblivious to notice it? If that is the case , anyone lurking in this discussion has any alternative to propose in DisplayFusions spot? I only need the "Split Screen into Segments" feature.
May 15, 2023 (modified May 15, 2023)
•
#6
Strahdvonzar
9 discussion posts
I have uninstalled MidiHub and will report again.
While we are at it , Alt+Tab is also not working. The App Selection window appears normally , pressing Alt+Tab again cycles through the options , and upon letting go , it does not focus on the "selected" app , it just flashes the "selected" app icon on the Taskbar.
Tried so far :
Did not Help: Disabling Hooks on the Taskbar.
Did not Help: Resetting Taskbar Settings.
Did not Help: Disabling Taskbars all together and falling back to Windows.
Solved: Quitting DisplayFusion.
Solved: Disabling Application Hooks.
May 15, 2023 (modified May 15, 2023)
•
#8
Strahdvonzar
9 discussion posts
Done
• Attachment [protected]: DisplayFusionDebugInfo.zip [63,761 bytes]
Strahdvonzar
9 discussion posts
Sure. I have already used the Beta , as mentioned in my original post with the exact same results , but i would try again.
Observations Regarding the Taskbar
Important
I noticed that if i Alt+Tab slow , then it works every single time even on the Main monitor. By slow i mean giving it a solid second on the Selection Screen and then releasing it (Press Alt + Tab , release Tab and Hold Alt for a second then release Alt).
Other
There seems to be more of an issue switching focus on applications hosted on the main monitor. Switching focus between applications on different monitors (Cross Monitor) seems to work every single time , even switching between applications hosted on a specific monitor , other than the main , works every single time. (This is irrelevant of configuration either through Windows Display Configuration or physically changing cables , which i did both , with the same results)
I need to point out , that upon "fast" Alt+Tab , the Selection Popup appears normally and displays the change correctly (moves the selection box to the new window).The procedure after the selection (bring on focus the selected application) fails and i am left with a flashing taskbar icon of the selected app.
Adding on the debugging. The "state" of the selected app on the Popup display is always correct. Even when the change fails and i am left with the flashing icon , on the next try , the selection popup will correctly "state" that i never switched apps.
May 17, 2023 (modified May 17, 2023)
•
#12
You can try turning on "SetWindowPos: Disallow TopMost Calls" in the DisplayFusion Advanced Settings, and see if that makes a difference. If there's no change, send over a debug and we can have a look at it.
Thanks!
Strahdvonzar
9 discussion posts
The specific setting change did not affect the issue. Isn't the previous log i provided helpful? The issue with the Tab is not situational , but constant. If i have Display Fusion on then Alt+Tab suffers , if i quit the Software , then Alt+Tab works as expected.
Was your AltTab issue captured while the original log was running? I don't see any AltTab events in it
Strahdvonzar
9 discussion posts
The first "window hook fail" is at "2023/05/19 21:25:14.0979" ( I suppose thats what you are looking for )
I need to point out that it had been 100% reproducible till today morning. From this morning and on , i do not see it happening so often. (Even though it did not take me more than 2 minutes to reproduce it to get the log but generally its not a 100% right now). Nevertheless its impossible to guide you through changes that i have made on my machine. Due to the nature of my work a lot are installed , uninstalled and many services are running at the same time , rendering me unable to point out what exactly could be the culprit of a situational issue.
Regarding the app quitting with no indication: Has not happened for 3 days in a row , i am still waiting.
• Attachment [protected]: DisplayFusion_alt-tab.log [563,839 bytes]
May 19, 2023 (modified May 19, 2023)
•
#16
Thanks for sending that over, we'll take a look into it and let you know if we need any other info.
We're reworking the way AltTab is handled in our next beta, so we'll get you to try it out once it's released.
We've released a new beta with some changes, can you try it out and let me know if the issue persists?