Situation: the client tries to access Windows 2008 R2 using RDP. He is able to connect to the remote systems and access the environment for a short period prior to MSTSC.EXE crashing. “A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.” Eventlog has the following: Log Name: Application Source: Application Error Date: 3/25/2015 2:50:21 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Description: Faulting application name: mstsc.exe, version: 10.0.10041.0, time stamp: 0x5503b1a7 Faulting module name: mstscax.dll, version: 10.0.10041.0, time stamp: 0x5503b315 Exception code: 0xc0000005 Fault offset: 0x000000000046d78c Faulting process id: 0x2164 Faulting application start time: 0x01d06734abf028a0 Faulting application path: C:\WINDOWS\system32\mstsc.exe Faulting module path: C:\WINDOWS\system32\mstscax.dll Report Id: 2b084e37-d328-11e4-ab40-7c7a9191e005 Faulting package full name: Faulting package-relative application ID:
chicahotech.net Resolution: 1. According to the error message, this problem caused by mstscax.dll which is Windows Remote Desktop Client relevant file. To fix this problem, you can try to use the command below to register this Dll file again for test.
Open CMD with administrator, Type the command below and press enter: regsvr32 %systemroot%\system32\mstscax.dll
After that, restart your computer to test this problem.
2. Try these 3 options: Option 1. Disabling Printer redirect on RDP connection resolved the crashing. Crashing was taking place on a Windows 10 PC using the native Desktop RDC. Option 2. Download the Microsoft Remote Desktop app from Windows 10 store. Option 3. Access our Remote7 instead of remote5 and remote6. 3. Or try this: Run the system file checker tool. Check the article http://support.microsoft.com/kb/929833 “How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7” 4. Allow Remote Desktop Via Windows Firewall. Especially, if the network is setup using public connection, make sure the Remote Desktop is allowed in Public firewall settings. Disable remote mapping or audio playback settings. In our case, When I clicked in the Remote audio playback settings I noticed Play on this computer was selected. Check Do bot play fix the problem. That fixed it! 5. if you repeatedly connect to the same computers that have the same desktop setups, the terminal service client will save a cached copy locally on your system so you don’t have to keep downloading it from the remote computer. It’s located here: %USERPROFILE%\AppData\Local\Microsoft\Terminal Server Client\Cache You could rename the .bmc files to .bmc.old and then retry your terminal services connection efforts. I believe the key to solving this issue specific to each case is looking in the event viewer. Look at not just the “Faulting application name” but also the “Faulting module name.” For me the faulting module was “dlxcrjdm.dll” which is an old Dell Printer Driver dll that I am guessing isn’t compatible with Windows 10 (which I just upgraded to). Anyway, after uninstalling the Dell printer, my problem was resolved. This type of approach may also solve the issue for those looking to use printers or audio as a local resource in the remote environment. To run event viewer, just hit the Start button and start typing in “Event Viewer.” You should be able to see in the “Summary of Administrative Events” any Errors (under “Event Type”) in the last hour and then find the one related to your issue. After you do find the “Faulting module name”, I suggest googling it to find out what it is and go from there. In our case, the client is running Windows 2008 R2 RD services. Their RDP client version is RDC 10.0.16299.15 (the latest build 2017.10.13). This version is not supported on Windows 2008 R2.
