Using Sysinternals Process Explorer I found out that one thread seems to cause this problem. I captured the stack trace of the relevant thread multiple times, it always looked as follows:
Code: Select all
ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x712
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!_misaligned_access+0xba0
ntoskrnl.exe!_misaligned_access+0x183d
ntoskrnl.exe!IoFreeErrorLogEntry+0x297
Qt5CoreXn.dll!QMutex::lock+0x16
Qt5CoreXn.dll!QThread::isRunning+0x1f
xnviewmp.exe+0x3dafe9
xnviewmp.exe+0x3db074
xnviewmp.exe+0x44f89d
xnviewmp.exe+0x44f974
Qt5CoreXn.dll!QObjectPrivate::deleteChildren+0x8d
Qt5WidgetsXn.dll!QWidget::~QWidget+0x563
xnviewmp.exe+0x45a8c4
xnviewmp.exe+0x47dbaf
xnviewmp.exe+0x3ae594
xnviewmp.exe+0x663fd5
xnviewmp.exe+0x6610dd
kernel32.dll!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x21
This application is special in this way that it runs with "High integrity level" (UAC elevated).
Most time I recognize the remaining xnviewmp.exe task the next day after powering up my pc, waking it from hibernate.
Version 0.78 x64 (Jan 12 2016)