How to resolve "Faulting application name: mstsc.exe"

Brady Dotson 0 Reputation points
2024-04-15T14:06:39.0166667+00:00

Receiving the below error when trying to connect to an RDP session. I log in , everything works grweat for 10 seconds or so then it crashes. No pop ups or errors shown. Only in event viewer can I see the failure.

Faulting application name: mstsc.exe, version: 10.0.19041.3996, time stamp: 0x310ef712

Faulting module name: KMUU84HG.DLL, version: 8.4.17.16, time stamp: 0x6462cc1a

Exception code: 0xc0000005

Fault offset: 0x000000000012e1f3

Faulting process id: 0xa9c

Faulting application start time: 0x01da8f3d444f0922

Faulting application path: C:\WINDOWS\system32\mstsc.exe

Faulting module path: C:\WINDOWS\system32\spool\DRIVERS\x64\3\KMUU84HG.DLL

Report Id: e8bb3e10-242a-4e3b-966b-b9a6f71097d3

Faulting package full name:

Faulting package-relative application ID:

Steps taken:

  1. Check for updates
  2. chkdsk
  3. sfc /scannow
  4. rebuilt the connection, same result
  5. removed all un-needed applications
  6. checked AV logs, no blocking.

Please help.

Thanks,

Bdot

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,688 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,595 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Michael Taylor 54,731 Reputation points
    2024-04-15T15:16:20.5233333+00:00

    That is an access violation issue meaning somebody referenced memory. Given that it is a print driver (KMUU84HG) then I'd recommend you disable access to the printer(s) when connecting via Remote Desktop. That should avoid the issue I believe.

    1 person found this answer helpful.
    0 comments No comments

  2. Karlie Weng 18,531 Reputation points Microsoft Vendor
    2024-04-17T06:42:34.3733333+00:00

    Hello,

    It is an access violation issue, and the error code 0xc0000005 means access denied.

    In your log, faulting module is: C:\WINDOWS\system32\spool\DRIVERS\x64\3\KMUU84HG.DLL

    You can try to update your printer driver. If you still have this issue, you can config a WER dump, it will be collected when issue repro.

    You can follow this link to config a crash dump trigger in your PC.

    https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

    Note that it will only be triggered if you have application ID 1000 (WER crash) in your event log.

    Finally, you will have a dump at your location; you can find the error stack in your program.


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.