RDM Crashing with c0000005
I have been running into an issue where RDM will randomly crashing with the following error:
Description: Faulting application name: RemoteDesktopManager.exe, version: 2026.1.23.0, time stamp: 0x68270000 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00007ff97ae607f5 Faulting process id: 0xB128 Faulting application start time: 0x1DCF5AB6AB10794 Faulting application path: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe Faulting module path: unknown Report Id: 64a43909-0b43-4046-9ee0-6d6317cfd08e Faulting package full name: Faulting package-relative application ID:
I enabled crash dumps for the Remote Desktop Manager process and looking at it in windbg shows the following:
ClrmaManagedAnalysis::GetThread 8a24
ClrmaThread::Initialize 8a24
~ClrmaThread
ClrmaManagedAnalysis::get_ProviderName
ClrmaManagedAnalysis::GetThread ffffffff
ClrmaThread::Initialize 8a24
ClrmaThread::get_CurrentException
~ClrmaException
ClrmaThread::get_NestedExceptionCount
~ClrmaThread
MethodDesc: 00007ff96ec6adf0
Method Name: System.Runtime.CompilerServices.CastHelpers.ChkCastClassSpecial(Void*, System.Object)
Class: 00007ff96ec6b0b0
MethodTable: 00007ff96ec6b0b0
mdToken: 0000000006008099
Module: 00007ff96eb74000
IsJitted: yes
Current CodeAddr: 00007ff97ae607e0
Version History:
ILCodeVersion: 0000000000000000
ReJIT ID: 0
IL Addr: 00007ff9c29d4bd0
CodeAddr: 00007ff97a2c3600 (OptimizedTier1 + Instrumented)
NativeCodeVersion: 0000020C551DFA30
CodeAddr: 00007ff97ae607e0 (OptimizedTier1)
NativeCodeVersion: 0000020C558B2C00
CodeAddr: 00007ff9c24b6460 (ReadyToRun)
NativeCodeVersion: 0000000000000000
Source file: /_/src/runtime/src/coreclr/System.Private.CoreLib/src/System/Runtime/CompilerServices/CastHelpers.cs @ 369
ClrmaManagedAnalysis::GetThread ffffffff
ClrmaThread::Initialize 8a24
ClrmaThread::get_CurrentException
ClrmaException::Initialize 0000020c6b800190
~ClrmaException
~ClrmaThread
PROCESS_NAME: RemoteDesktopManager.dll
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
SYMBOL_NAME: coreclr!WatsonLastChance+1b6
MODULE_NAME: coreclr
IMAGE_NAME: coreclr.dll
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_coreclr.dll!WatsonLastChance
FAILURE_ID_HASH: {02278b9d-5c98-a887-c517-87862641b6f2}
Followup: MachineOwner
Running !clrstack shows the following:
OS Thread Id: 0x8a24 (36)
Child SP IP Call Site
00000011D8C3C450 00007ffa37390318 [InlinedCallFrame: 00000011d8c3c450]
00000011D8C3C450 00007ff9c248a416 [InlinedCallFrame: 00000011d8c3c450]
00000011D8C3C3F0 00007ff9c248a416 System.Runtime.EH.DispatchEx(System.Runtime.StackFrameIterator ByRef, ExInfo ByRef) [/_/src/runtime/src/coreclr/nativeaot/Runtime.Base/src/System/Runtime/ExceptionHandling.cs @ 760]
00000011D8C3C660 00007ff9ce8a8933 [FaultingExceptionFrame: 00000011d8c3c660]
00000011D8C3E988 00007ff97ae607f5 System.Runtime.CompilerServices.CastHelpers.ChkCastClassSpecial(Void*, System.Object) [/_/src/runtime/src/coreclr/System.Private.CoreLib/src/System/Runtime/CompilerServices/CastHelpers.cs @ 369]
00000011D8C3E990 00007ff9710592c2 MicroCom.Runtime.MicroComVtblBase.AddRef(MicroCom.Runtime.Ccw*)
00000011D8C3F688 00007ffa39e68167 [InlinedCallFrame: 00000011d8c3f688] Avalonia.Win32.Interop.UnmanagedMethods.GetMessage(MSG ByRef, IntPtr, UInt32, UInt32)
00000011D8C3F688 00007ff97105bf97 [InlinedCallFrame: 00000011d8c3f688] Avalonia.Win32.Interop.UnmanagedMethods.GetMessage(MSG ByRef, IntPtr, UInt32, UInt32)
00000011D8C3F660 00007ff97105bf97 ILStubClass.IL_STUB_PInvoke(MSG ByRef, IntPtr, UInt32, UInt32)
00000011D8C3F720 0000020c595e7799 Avalonia.Win32.WinRT.Composition.WinUiCompositorConnection.RunLoop()
00000011D8C3F800 0000020c59611a52 Avalonia.Win32.WinRT.Composition.WinUiCompositorConnection+c__DisplayClass7_0.b__0()
00000011D8C3F850 00007ff9c243595b System.Threading.Thread+StartHelper.Callback(System.Object) [/_/src/runtime/src/libraries/System.Private.CoreLib/src/System/Threading/Thread.cs @ 44]
00000011D8C3F890 00007ff9c243ce94 System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) [/_/src/runtime/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs @ 179]
00000011D8C3FB10 00007ff9ce8a8933 [DebuggerU2MCatchHandlerFrame: 00000011d8c3fb10]
Happy to provide the .dmp files if it helps.
All Comments (5)
Hi @alivebarn9212,
Thanks for the detailed report and the stack you already pulled from WinDbg, that is very helpful.
To take a closer look on our side, we would like to get the full .dmp file you mentioned. I will send you a private link in a separate message where you can upload it securely.
In the meantime, could you please confirm a few things so we can line everything up:
- The exact RDM build you are running (the dump shows 2026.1.23.0, just confirming it is current).
- Your Windows version and build (winver).
- Which data source / workspace type you are using in RDM (DVLS, SQL Server, Devolutions Cloud, local XML, etc.) and its version.
- Is the crash reproducible or does it happen at random? If you have noticed any pattern (specific session type, idle, after resizing the window, waking from sleep, multi‑monitor / DPI change, etc.), please let us know.
- If you have more than one recent dump, feel free to include all of them.
Thanks again, we will get back to you as soon as we have had a chance to review the dump.
Best regards,
Alexis Geller Peiro
I accidentally deleted the dmp that the above stack was from; however, the application crashed this morning and looking at the stack it appears to be the same issue happening. The most recent .dmp file has been uploaded.
- Here is the version from the "about" section: 2026.1.23.0 64-bit (PreJIT)
- Windows version: 25H2 26200.8655
- Data source type: Sqlite
- The crash appears to happen randomly and it always appears to happen when I'm away from the system (idle) over night.
Hi @alivebarn9212,
Thanks again for the dump and the additional information, that gave our developers something concrete to work with.
To help us narrow this down further, we would like you to try the standard build of RDM 2026.1.23.0 in place of the 2026.1.23.0 (PreJIT) build you are currently running.
A couple of notes on the swap itself: even though the version number is identical, the standard build cannot be installed on top of the PreJIT one, so the current installation has to be uninstalled first. Once the new build is in place, please use RDM normally and leave it running overnight as you would usually do, so we give the issue the same conditions to show up.
After a few days, please let us know how it went:
- If RDM crashed again, a minidump should land in %localappdata%\Crashdumps. Sharing the most recent one through the private link I sent earlier would be perfect.
- If RDM ran cleanly through the nights, that is just as useful and tells our developers where to look next.
Thanks for your patience while we work through this.
Best regards,
Alexis Geller Peiro
Hey @Alexis Geller Peiro,
I have actually updated from 2026.1.23.0 (PreJit) to 2026.2.9.00 (PreJit) and went ahead and reset my local data folder and allowed RDM to create new configuration files. As of right now the application has been running for ~4 days. Typically RDM would have crashed by day 1-2, so I'm unsure if the new version has resolved the issue OR if me renaming my local data folder allowing RDM to clean it up worked, but as of right now it seems to be stable.
Hi @alivebarn9212,
I'm glad to hear that the problem has been resolved!
Please monitor this for a few days and give us feedback.
Best regards,
Alexis Geller Peiro