All 3 of the latest versions have intermittent crashes in Windows 10. I'm currently on 1803 but I believe all previous crashes were on 1709. This mostly happens when I RDP to my PC which already has RDTabs running. Either RDTabs will crash while I'm connected via RDP to my main PC or it will crash after I disconnect and when I come into work the next day it had crashed. In Application of Event Viewer I get these entries:

Faulting application name: RDTabs.exe, version: 3.0.11.643, time stamp: 0x5b1d98d6
Faulting module name: msmpeg2vdec.dll_unloaded, version: 10.0.17134.112, time stamp: 0x566cfb2e
Exception code: 0xc0000005
Fault offset: 0x000000000015fd10
Faulting process id: 0x6d78
Faulting application start time: 0x01d4120b85d40765
Faulting application path: C:\Program Files\Avian Waves\RD Tabs\RDTabs.exe
Faulting module path: msmpeg2vdec.dll
Report Id: 9208f82a-cc4b-4963-bf71-e46ed23e4f43
Faulting package full name:
Faulting package-relative application ID:


Application: RDTabs.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFED8A0FD10
Stack:

The faulting module is not a module that is included as a part of RD Tabs: msmpeg2vdec.dll. Doing a little bit of Google-Fu, it seems that's the H.264 (and probably other mpeg) codec DLL for Windows. The report you posted looks like it comes from a Windows process crash (APPCRASH) report. RD Tabs traps and handles all crashes available to it, which is basically everything handled within the .net framework and directs the exception data to a built in error reporting module that is different from the Windows one. It provides debugging data that is a lot more useful to me. So if the process crashes like this, it's happening outside of the framework code and typically means it's not something I can fix since it's not code I'm writing.

Based on this, I'm going to make a slightly educated guess that the crash is happening somewhere in the graphics subsystem. My best guess is possibly a video card driver issue. Are your graphics drivers up to date? But being that it's in the codec DLL, it's also possible it may be due to other codecs installed on the system. Do you have any third party codecs installed? Like maybe for a game or a video application? Since Windows 7, RDP uses accelerated graphics for performance reasons, including video compression using a special codec for RDP. So I can see how there might be some related bits here.

Can you reproduce this using a different PC? Does the same thing happen using the built-in remote desktop?

This has also been happening for me on Windows 10 (Only), for all the RDTab 3.0 versions. It intermittently crashes when trying to RDP to a machine. It normally happens once per day. Please see crash logs below:

Faulting application name: RDTabs.exe, version: 3.0.11.643, time stamp: 0x5b1d98d6
Faulting module name: Windows.UI.XamlHost.dll, version: 10.0.17134.1, time stamp: 0x6e0ca433
Exception code: 0xc0000409
Fault offset: 0x0000000000001e8c
Faulting process id: 0x1cfc
Faulting application start time: 0x01d41373d4ef1b1f
Faulting application path: C:\Program Files\Avian Waves\RD Tabs\RDTabs.exe
Faulting module path: C:\Windows\System32\Windows.UI.XamlHost.dll
Report Id: 1d9a2c9b-1111-4296-a5f3-311811d68b97
Faulting package full name:
Faulting package-relative application ID:

Fault bucket 1384230832985798697, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: RDTabs.exe
P2: 3.0.11.643
P3: 5b1d98d6
P4: Windows.UI.XamlHost.dll
P5: 10.0.17134.1
P6: 6e0ca433
P7: 0000000000001e8c
P8: c0000409
P9: 0000000000000007
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7C1D.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8380.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER841D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER841B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER842C.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_RDTabs.exe_7f69ecada5fe535459463db4cf576feb59a71d8_3aa9c5e9_5b0689f7

Analysis symbol:
Rechecking for solution: 0
Report Id: 1d9a2c9b-1111-4296-a5f3-311811d68b97
Report Status: 268435456
Hashed bucket: c7b1c48ad08dd2021335c69bcf42f829
Cab Guid: 0


Its a shame as I have been using RD Tabs for over 10 years and its been stable. This is the only this version that is causing issue.

Windows.UI.XamlHost.dll is also not a library that RD Tabs loads. RD Tabs is a WinForms app (basically, the oldest GUI available for .Net, it's just a thin wrapper for Win32). XAML is used with WPF and later technologies. So there's no reason RD Tabs would load that DLL unless there's a third party application hooking into RD Tabs. Is it possible you have a window manager type of application running? Something that manages window sizes, positions, or graphical elements? Or maybe hooks into the mouse or keyboard?

You can inspect the DLLs loaded by RD Tabs by using Process Explorer. https://docs.microsoft.c...wnloads/process-explorer 

I'm attaching what it should look like (this is a slightly newer build than online, so there may be slight variances).

I updated my graphics driver and I'll see how that goes and let you know. Thanks for the recommendation!

Graphics drivers didn't fix it. However, I did some more Googling and found info on codecs (which was already mentioned above). So far this solution has fixed it for me. Fingers crossed!
https://filestore.commun...4-433f-8a97-ec21127013e3 

Excellent find. Check back in a week or two to let us know if it worked. This may be helpful to others in the future.

I'm ready to call this issue resolved. Since doing that Codec tweak I have not had any issues!