How to fix app crash under Win11 in coremassaging.dll

Torsten Oestreich 0 Reputation points
2023-08-24T10:57:26.8766667+00:00

Hello,

I have created an application that displays 3D objects (step, iv, wrl, …). However the program crashes reproducibly, and the cause cannot be identified.
Now it is unfortunately so that when debugging (Visual Studio debugger, Remote debugging, WinDbg) the error does not occur.
The error also only occurs under Windows 11. Under Win 10 we have no problems at all.
This crash can be reproduced in several ways on different PC’s.
The crash call stack ends always in System32/CoreMessaging.dll:
ExceptionCode: 0xe0464645CallStack
Fault offset: 0x0000000000088433

Any tip to solve the problem is welcome
Thanks Torsten

Software usage:

Visual Studio 2017, C++, Qt4 or Qt5, Coin 3 or 4, SoQt, OpenGL

Crash call stack ( 3 examples):

1)
KERNELBASE!RaiseFailFastException+0x152
CoreMessaging!CFlat::Abandonment::FailWithException+0x8c
CoreMessaging!CFlat::Abandonment::FailWithHR+0x7f
CoreMessaging!AlpcConnection::Callback_ProcessIncoming+0x3a133
CoreMessaging!Microsoft::CoreUI::Messaging::CrossProcessReceivePort$AlpcReceiveSource::OnReceive+0x4e
CoreMessaging!Microsoft::CoreUI::Dispatch::OffThreadReceiver::Callback_OnDispatch+0x26d
CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0x36f
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch+0x1f3
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::DoWork+0x206
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::WindowProc+0x14c
user32!UserCallWinProcCheckWow+0x2d1
user32!DispatchClientMessage+0x9c
user32!_fnDWORD+0x3d
ntdll!KiUserCallbackDispatcherContinue
win32u!NtUserPeekMessage+0x14
user32!_PeekMessage+0x3f
user32!PeekMessageW+0x9c
QtCore4!QEventDispatcherWin32::processEvents+0x246
QtGui4!QApplicationPrivate::openPopup+0x222
QtCore4!QCoreApplication::processEvents+0x4e

2)

KERNELBASE!RaiseFailFastException+0x152
CoreMessaging!CFlat::Abandonment::FailWithException+0x8c
CoreMessaging!CFlat::Abandonment::FailWithHR+0x7f
CoreMessaging!AlpcConnection::Callback_ProcessIncoming+0x3a133
CoreMessaging!Microsoft::CoreUI::Messaging::CrossProcessReceivePort$AlpcReceiveSource::OnReceive+0x4e
CoreMessaging!Microsoft::CoreUI::Dispatch::OffThreadReceiver::Callback_OnDispatch+0x26d
CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0x36f
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch+0x1f3
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::DoWork+0x206
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::WindowProc+0x14c
user32!UserCallWinProcCheckWow+0x2d1
user32!DispatchClientMessage+0x9c
user32!_fnDWORD+0x3d
tdll!KiUserCallbackDispatcherContinue
win32u!NtUserPeekMessage+0x14
user32!_PeekMessage+0x3f
user32!PeekMessageW+0x9c
QtCore4!QEventDispatcherWin32::processEvents+0x246
QtGui4!QApplicationPrivate::openPopup+0x222
QtCore4!QEventLoop::exec+0x26e
QtGui4!QDialog::exec+0xf1

3)

KERNELBASE!RaiseFailFastException+0x152
CoreMessaging!CFlat::Abandonment::FailWithException+0x8c
CoreMessaging!CFlat::Abandonment::FailWithHR+0x7f
CoreMessaging!AlpcConnection::Callback_ProcessIncoming+0x3a133
CoreMessaging!Microsoft::CoreUI::Messaging::CrossProcessReceivePort$AlpcReceiveSource::OnReceive+0x4e
CoreMessaging!Microsoft::CoreUI::Dispatch::OffThreadReceiver::Callback_OnDispatch+0x26d
CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0x36f
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch+0x1f3
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::DoWork+0x206
CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::WindowProc+0x14c
user32!UserCallWinProcCheckWow+0x2d1
user32!DispatchClientMessage+0x9c
user32!_fnDWORD+0x3d
ntdll!KiUserCallbackDispatcherContinue
win32u!NtUserPeekMessage+0x14
user32!_PeekMessage+0x3f
user32!PeekMessageW+0x9c
Qt5Core!QEventDispatcherWin32::processEvents+0x310
qwindows!qt_plugin_query_metadata+0x1fd9
Qt5Core!QEventLoop::exec+0x1db
Qt5Widgets!QDialog::exec+0x164

Device specifications:
Processor 11th Gen Intel(R) Core™ i7-11700 @ 2.50GHz 2.50 GHz
Installed RAM 32.0 GB (31.8 GB usable)
System type 64-bit operating system, x64-based processor

Windows specifications:
Edition Windows 11 Pro
Version 22H2
OS build 22621.2134

System information: display
Name NVIDIA T1000
PNP Device
Adapter Type NVIDIA T1000, NVIDIA compatible
Adapter Description NVIDIA T1000
Adapter RAM (1,048,576) bytes
Driver Version 31.0.15.3696

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,658 questions
C++
C++
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
3,548 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SPIEGEL Hermann 0 Reputation points
    2024-04-29T13:24:39.8366667+00:00

    Thanks for this information. I also found that Windows 8 compatibility is the only way to avoid the error.

    0 comments No comments