none
Windows 8.1 RDP crashes very frequently after upgrade from Windows 8

    Question

  • Hello,

    I installed Windows 8.1 EE x64 as upgrade from Windows 8 EE x64 on my personal computer. After that RDP crashes very frequently.

    Here is my errors from event viewer (I have Czech language so sorry for it)

    Application Error (ID: 1000)
    ==================
    General
    -------
    Název chybující aplikace: mstsc.exe, verze: 6.3.9600.16384, časové razítko: 0x5215e2b5
    Název chybujícího modulu: ntdll.dll, verze: 6.3.9600.16384, časové razítko: 0x5215f938
    Kód výjimky: 0xc0000005
    Posun chyby: 0x000000000002de46
    ID chybujícího procesu: 0x1ef8
    Čas spuštění chybující aplikace: 0x01ceb5de1d230682
    Cesta k chybující aplikaci: C:\Windows\System32\mstsc.exe
    Cesta k chybujícímu modulu: C:\WINDOWS\SYSTEM32\ntdll.dll
    ID zprávy: 6e76e3a0-21d1-11e3-824d-005056c00008
    Úplný název chybujícího balíčku: 
    ID aplikace související s chybujícím balíčkem: 

    Details
    -------
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Application Error" /> 
      <EventID Qualifiers="0">1000</EventID> 
      <Level>2</Level> 
      <Task>100</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2013-09-20T08:48:34.000000000Z" /> 
      <EventRecordID>36478</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>JIRKA-PC.sandster.local</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>mstsc.exe</Data> 
      <Data>6.3.9600.16384</Data> 
      <Data>5215e2b5</Data> 
      <Data>ntdll.dll</Data> 
      <Data>6.3.9600.16384</Data> 
      <Data>5215f938</Data> 
      <Data>c0000005</Data> 
      <Data>000000000002de46</Data> 
      <Data>1ef8</Data> 
      <Data>01ceb5de1d230682</Data> 
      <Data>C:\Windows\System32\mstsc.exe</Data> 
      <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data> 
      <Data>6e76e3a0-21d1-11e3-824d-005056c00008</Data> 
      <Data /> 
      <Data /> 
      </EventData>
      </Event>

    Windows Error Reporting (ID: 1001)
    =======================
    General
    -------
    Chybný blok 127057472, typ 4
    Název události: APPCRASH
    Reakce: Není k dispozici.
    ID souboru CAB: 0

    Podpis problému:
    P1: mstsc.exe
    P2: 6.3.9600.16384
    P3: 5215e2b5
    P4: ntdll.dll
    P5: 6.3.9600.16384
    P6: 5215f938
    P7: c0000005
    P8: 000000000002de46
    P9: 
    P10: 

    Připojené soubory:
    C:\Users\Jirka.SANDSTER\AppData\Local\Temp\WER3B11.tmp.WERInternalMetadata.xml
    C:\Users\Jirka.SANDSTER\AppData\Local\Temp\WER440B.tmp.appcompat.txt

    Tyto soubory mohou být k dispozici zde:
    C:\Users\Jirka.SANDSTER\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_mstsc.exe_b612095447011e21536732396929f9b226636_4012f314_1494441a

    Symbol analýzy: 
    Opětovné hledání řešení: 0
    ID hlášení: 6e76e3a0-21d1-11e3-824d-005056c00008
    Stav hlášení: 1
    Zakódovaný interval: 9db086049b946847d22aeaa96b0e9f58

    Details
    -------
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Windows Error Reporting" /> 
      <EventID Qualifiers="0">1001</EventID> 
      <Level>4</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2013-09-20T08:48:37.000000000Z" /> 
      <EventRecordID>36479</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>JIRKA-PC.sandster.local</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>127057472</Data> 
      <Data>4</Data> 
      <Data>APPCRASH</Data> 
      <Data>Není k dispozici.</Data> 
      <Data>0</Data> 
      <Data>mstsc.exe</Data> 
      <Data>6.3.9600.16384</Data> 
      <Data>5215e2b5</Data> 
      <Data>ntdll.dll</Data> 
      <Data>6.3.9600.16384</Data> 
      <Data>5215f938</Data> 
      <Data>c0000005</Data> 
      <Data>000000000002de46</Data> 
      <Data /> 
      <Data /> 
      <Data>C:\Users\Jirka.SANDSTER\AppData\Local\Temp\WER3B11.tmp.WERInternalMetadata.xml C:\Users\Jirka.SANDSTER\AppData\Local\Temp\WER440B.tmp.appcompat.txt</Data> 
      <Data>C:\Users\Jirka.SANDSTER\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_mstsc.exe_b612095447011e21536732396929f9b226636_4012f314_1494441a</Data> 
      <Data /> 
      <Data>0</Data> 
      <Data>6e76e3a0-21d1-11e3-824d-005056c00008</Data> 
      <Data>1</Data> 
      <Data>9db086049b946847d22aeaa96b0e9f58</Data> 
      </EventData>
      </Event>



    Could you help me please?

    Thanks
    Friday, September 20, 2013 9:42 AM

Answers

  • Hi Jiří,

    looks like a bad Audio codec (bdmpega64.acm) causes the crash:

    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    *** WARNING: Unable to verify timestamp for bdmpega64.acm
    *** ERROR: Module load completed but symbols could not be loaded for bdmpega64.acm
    APPLICATION_VERIFIER_HEAPS_CORRUPTED_HEAP_BLOCK_EXCEPTION_RAISED_FOR_PROBING (c)
    Exception raised while verifying the heap block.
    This situation happens if we really cannot determine any particular
    type of corruption for the block. For instance you will get this if
    during a heap free operation you pass an address that points to a
    non-accessible memory area.
    This can also happen for double free situations if we do not find the
    block among full page heap blocks and we probe it as a light page heap block. 
    Arguments:
    Arg1: 000000aa6c971000, Heap handle used in the call. 
    Arg2: 000000005d0b4440, Heap block involved in the operation. 
    Arg3: 0000000000000000, Size of the heap block. 
    Arg4: 00000000c0000005, Reserved. 
    
    FAULTING_IP: 
    verifier!VerifierStopMessage+28a
    00007ffd`f922a43a cc              int     3
    
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 00007ffdf922a43a (verifier!VerifierStopMessage+0x000000000000028a)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
    
    CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
    rax=000000aa5cfc0000 rbx=0000000000000000 rcx=000000aa5cfc0000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=00007ffe08bc808a rsp=000000aa5e83cb08 rbp=000000aa5e83d950
     r8=0000000000001000  r9=0000000000000000 r10=0000000000000040
    r11=0000000000000286 r12=0000000000000000 r13=0000000000000000
    r14=000000aa5cfb0000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000203
    ntdll!NtWaitForMultipleObjects+0xa:
    00007ffe`08bc808a c3              ret
    
    DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT
    
    PROCESS_NAME:  mstsc.exe
    
    ERROR_CODE: (NTSTATUS) 0x80000003 - {AUSNAHME}  Haltepunkt  Im Quellprogramm wurde ein Haltepunkt erreicht.
    
    EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Mindestens ein Argument ist ung ltig.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    NTGLOBALFLAG:  2000100
    
    APPLICATION_VERIFIER_FLAGS:  48004
    
    APP:  mstsc.exe
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    FAULTING_THREAD:  0000000000001630
    
    PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT
    
    BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT
    
    LAST_CONTROL_TRANSFER:  from 00007ffdf92292e4 to 00007ffdf922a43a
    
    STACK_TEXT:  
    ntdll!NtWaitForMultipleObjects
    ntdll!RtlReportExceptionEx
    ntdll!RtlReportException
    verifier!AVrfpVectoredExceptionHandler
    ntdll!RtlpCallVectoredHandlers
    ntdll!RtlDispatchException
    ntdll!KiUserExceptionDispatch
    verifier!VerifierStopMessage
    verifier!AVrfpDphReportCorruptedBlock
    verifier!AVrfpDphCheckNormalHeapBlock$filt$0
    ntdll!_C_specific_handler
    ntdll!RtlpExecuteHandlerForException
    ntdll!RtlDispatchException
    ntdll!KiUserExceptionDispatch
    verifier!AVrfpDphFindBusyMemoryNoCheck
    verifier!AVrfpDphFindBusyMemory
    verifier!VerifierCheckPageHeapAllocation
    verifier!AVrfpHeapFree
    bdmpega64
    0x0
    0x0
    0x0
    
    
    
    IMAGE_NAME:  bdmpega64.acm
    
    
    FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_bdmpega64.acm!Unknown
    
    
      
        Loaded symbol image file: bdmpega64.acm
        Image path: C:\Windows\System32\bdmpega64.acm
        Image name: bdmpega64.acm
        Timestamp:        Thu Aug 09 09:40:14 2012 

    From what I can see the file bdmpega64.acm belongs to a tool called http://www.bandicam.com

    Update the tool to the latest version 1.9.0.397:

    http://www.bandicam.com/downloads/

    If this doesn't fix it, remove it or disable Audio in the RDP options.


    "A programmer is just a tool which converts caffeine into code"

    Saturday, September 21, 2013 10:48 AM

All replies

  • Have  you tried to remove contents of C:\Users\user\AppData\Local\Microsoft\Terminal Server Client\Cache?
    Friday, September 20, 2013 10:15 AM
  • Check minidump files and resolve it (%SystemRoot%\MEMORY.DMP) and also run "sfc /scannow" and "chkdsk" in command prompt 

    Thanks

    Friday, September 20, 2013 11:32 AM
  • I removed Terminal Server Client cache. It looks good, I'm testing it.

    Thanks

    Friday, September 20, 2013 5:03 PM
  • Check minidump files and resolve it (%SystemRoot%\MEMORY.DMP) and also run "sfc /scannow" and "chkdsk" in command prompt 

    Thanks

    I have no minidump file created so it looks that crashing RDP do not write to this file. I ran sfc and chkdsk and it did not found any issue.

    Thanks

    Friday, September 20, 2013 5:06 PM
  • Have  you tried to remove contents of C:\Users\user\AppData\Local\Microsoft\Terminal Server Client\Cache?

    I removed Terminal Server Client cache and I have still this issue.
    Friday, September 20, 2013 5:28 PM
  • Have you read this thread?

    http://social.technet.microsoft.com/Forums/windows/en-US/7b3272a1-df1a-4955-a0ae-d438d46a7d66/rdp-crashes-everytime-while-connectiong-to-windows-2008-server

    It doesn't deal with RDP connection of Windows 8, but I suggest you to check it out.


    • Edited by T. Kujala Friday, September 20, 2013 5:50 PM
    Friday, September 20, 2013 5:49 PM
  • please download this reg file from my Dropbox:

    https://www.dropbox.com/s/v81q3got2ts52x6/WER_remoteDesktop_full.reg

    and make a double click on the .reg file to import it.

    When the RDP client crashes, Windows Error Reporting Service [1] creates a dmp file under C:\Localdumps. Please upload the file, compresssed as zip, to your public Skydrive [2] folder and post the link here. I take a look at the dump with the Debugger, maybe I can see the cause.

    After you generated the dumps, download and import this regfile:

    https://www.dropbox.com/s/8ixfw7kbjm32ach/WER_remoteDesktop_uninstall.reg

    to stop the dump creation.

    André

    [1] http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx
    [2] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code"

    Friday, September 20, 2013 8:16 PM
  • please download this reg file from my Dropbox:

    https://www.dropbox.com/s/v81q3got2ts52x6/WER_remoteDesktop_full.reg

    and make a double click on the .reg file to import it.

    When the RDP client crashes, Windows Error Reporting Service [1] creates a dmp file under C:\Localdumps. Please upload the file, compresssed as zip, to your public Skydrive [2] folder and post the link here. I take a look at the dump with the Debugger, maybe I can see the cause.

    After you generated the dumps, download and import this regfile:

    https://www.dropbox.com/s/8ixfw7kbjm32ach/WER_remoteDesktop_uninstall.reg

    to stop the dump creation.

    André

    [1] http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx
    [2] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code"

    Thanks André,

    here is the link: https://skydrive.live.com/redir?resid=9291C15EA3870F9F!569&authkey=!AAD8cO74hwoXlrk

    Saturday, September 21, 2013 9:39 AM
  • Have you read this thread?

    http://social.technet.microsoft.com/Forums/windows/en-US/7b3272a1-df1a-4955-a0ae-d438d46a7d66/rdp-crashes-everytime-while-connectiong-to-windows-2008-server

    It doesn't deal with RDP connection of Windows 8, but I suggest you to check it out.



    Thanks, I will check it
    Saturday, September 21, 2013 9:44 AM
  • Hi Jiří,

    looks like a bad Audio codec (bdmpega64.acm) causes the crash:

    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    *** WARNING: Unable to verify timestamp for bdmpega64.acm
    *** ERROR: Module load completed but symbols could not be loaded for bdmpega64.acm
    APPLICATION_VERIFIER_HEAPS_CORRUPTED_HEAP_BLOCK_EXCEPTION_RAISED_FOR_PROBING (c)
    Exception raised while verifying the heap block.
    This situation happens if we really cannot determine any particular
    type of corruption for the block. For instance you will get this if
    during a heap free operation you pass an address that points to a
    non-accessible memory area.
    This can also happen for double free situations if we do not find the
    block among full page heap blocks and we probe it as a light page heap block. 
    Arguments:
    Arg1: 000000aa6c971000, Heap handle used in the call. 
    Arg2: 000000005d0b4440, Heap block involved in the operation. 
    Arg3: 0000000000000000, Size of the heap block. 
    Arg4: 00000000c0000005, Reserved. 
    
    FAULTING_IP: 
    verifier!VerifierStopMessage+28a
    00007ffd`f922a43a cc              int     3
    
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 00007ffdf922a43a (verifier!VerifierStopMessage+0x000000000000028a)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
    
    CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
    rax=000000aa5cfc0000 rbx=0000000000000000 rcx=000000aa5cfc0000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=00007ffe08bc808a rsp=000000aa5e83cb08 rbp=000000aa5e83d950
     r8=0000000000001000  r9=0000000000000000 r10=0000000000000040
    r11=0000000000000286 r12=0000000000000000 r13=0000000000000000
    r14=000000aa5cfb0000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe cy
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000203
    ntdll!NtWaitForMultipleObjects+0xa:
    00007ffe`08bc808a c3              ret
    
    DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT
    
    PROCESS_NAME:  mstsc.exe
    
    ERROR_CODE: (NTSTATUS) 0x80000003 - {AUSNAHME}  Haltepunkt  Im Quellprogramm wurde ein Haltepunkt erreicht.
    
    EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Mindestens ein Argument ist ung ltig.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    NTGLOBALFLAG:  2000100
    
    APPLICATION_VERIFIER_FLAGS:  48004
    
    APP:  mstsc.exe
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    FAULTING_THREAD:  0000000000001630
    
    PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT
    
    BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT
    
    LAST_CONTROL_TRANSFER:  from 00007ffdf92292e4 to 00007ffdf922a43a
    
    STACK_TEXT:  
    ntdll!NtWaitForMultipleObjects
    ntdll!RtlReportExceptionEx
    ntdll!RtlReportException
    verifier!AVrfpVectoredExceptionHandler
    ntdll!RtlpCallVectoredHandlers
    ntdll!RtlDispatchException
    ntdll!KiUserExceptionDispatch
    verifier!VerifierStopMessage
    verifier!AVrfpDphReportCorruptedBlock
    verifier!AVrfpDphCheckNormalHeapBlock$filt$0
    ntdll!_C_specific_handler
    ntdll!RtlpExecuteHandlerForException
    ntdll!RtlDispatchException
    ntdll!KiUserExceptionDispatch
    verifier!AVrfpDphFindBusyMemoryNoCheck
    verifier!AVrfpDphFindBusyMemory
    verifier!VerifierCheckPageHeapAllocation
    verifier!AVrfpHeapFree
    bdmpega64
    0x0
    0x0
    0x0
    
    
    
    IMAGE_NAME:  bdmpega64.acm
    
    
    FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_bdmpega64.acm!Unknown
    
    
      
        Loaded symbol image file: bdmpega64.acm
        Image path: C:\Windows\System32\bdmpega64.acm
        Image name: bdmpega64.acm
        Timestamp:        Thu Aug 09 09:40:14 2012 

    From what I can see the file bdmpega64.acm belongs to a tool called http://www.bandicam.com

    Update the tool to the latest version 1.9.0.397:

    http://www.bandicam.com/downloads/

    If this doesn't fix it, remove it or disable Audio in the RDP options.


    "A programmer is just a tool which converts caffeine into code"

    Saturday, September 21, 2013 10:48 AM
  • Thank you very much André
    Saturday, September 21, 2013 11:16 AM
  • Andre:

    I am having the same problem immediately after 8.1e upgrade.  I hope you don't mind my asking, but would you mind looking at my dmp file?  I am desperate to get access to my remote machine!

    http://sdrv.ms/1bVHehw

    Micah

    Monday, November 18, 2013 10:13 PM
  • Andre:

    I am having the same problem immediately after 8.1e upgrade.  I hope you don't mind my asking, but would you mind looking at my dmp file?  I

    an old DLL from 2007 semas to crash the program:

    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    
    FAULTING_IP: 
    dlxbrjdm+7356
    00000000`01007356 66f2af          repne scas word ptr [rdi]
    
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 0000000001007356 (dlxbrjdm+0x0000000000007356)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 000000001706ed20
    Attempt to read from address 000000001706ed20
    
    CONTEXT:  0000000000000000 -- (.cxr 0x0;r)
    rax=000000bc09710000 rbx=0000000000000003 rcx=000000bc09710000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000003
    rip=00007ffbcb056b2a rsp=000000bc1706d088 rbp=000000bc1706d4e8
     r8=0000000000001000  r9=0000000000000000 r10=0000000000000040
    r11=0000000000000286 r12=0000000000000010 r13=000000bc1706d4e8
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
    ntdll!NtWaitForMultipleObjects+0xa:
    00007ffb`cb056b2a c3              ret
    
    DEFAULT_BUCKET_ID:  INVALID_POINTER_READ
    
    PROCESS_NAME:  mstsc.exe
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  000000001706ed20
    
    READ_ADDRESS:  000000001706ed20 
    
    FOLLOWUP_IP: 
    dlxbrjdm+7356
    00000000`01007356 66f2af          repne scas word ptr [rdi]
    
    NTGLOBALFLAG:  2000100
    
    APPLICATION_VERIFIER_FLAGS:  48004
    
    APP:  mstsc.exe
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    FAULTING_THREAD:  00000000000001cc
    
    PRIMARY_PROBLEM_CLASS:  INVALID_POINTER_READ
    
    BUGCHECK_STR:  APPLICATION_FAULT_INVALID_POINTER_READ
    
    IP_ON_HEAP:  ffffffffffffffff
    The fault address in not in any loaded module, please check your build's rebase
    log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
    contain the address if it were loaded.
    
    FRAME_ONE_INVALID: 1
    
    LAST_CONTROL_TRANSFER:  from ffffffffffffffff to 0000000001007356
    
    STACK_TEXT:  
    ntdll!NtWaitForMultipleObjects
    KERNELBASE!WaitForMultipleObjectsEx
    verifier!AVrfpWaitForMultipleObjectsExCommon
    verifier!AVrfpKernelbaseWaitForMultipleObjectsEx
    kernel32!WerpReportFaultInternal
    kernel32!WerpReportFault
    KERNELBASE!UnhandledExceptionFilter
    ntdll!RtlUserThreadStart$filt$0
    ntdll!_C_specific_handler
    ntdll!RtlpExecuteHandlerForException
    ntdll!RtlDispatchException
    ntdll!KiUserExceptionDispatch
    dlxbrjdm
    0x0
    0x0
    0x0
    ntdll!RtlDebugSizeHeap
    0x0
    0x0
    
    
    IMAGE_NAME:  dlxbrjdm.dll
    
    
    FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_dlxbrjdm.dll!Unknown
    
    FAILURE_ID_HASH_STRING:  um:invalid_pointer_read_c0000005_dlxbrjdm.dll!unknown
    
     
        Loaded symbol image file: dlxbrjdm.dll
        Image path: C:\Windows\System32\spool\drivers\x64\3\dlxbrjdm.dll
        Image name: dlxbrjdm.dll
        Timestamp:        Fri Mar 16 00:45:50 2007

    update this (printer) driver or disable the printer in the RDP options.


    "A programmer is just a tool which converts caffeine into code"

    Tuesday, November 19, 2013 6:06 AM
  • A. I am getting the same crashes.

    B. How do I get the log files to see what is causing the crash.

    C. No, not NO DEVICE should cause windows to crash. This is a weakness of an operating system!

    FIX IT!!!

    I, I should not have to fix an OS. Would not have to fix in MAC!!!!! Yes I own one and know!

    Friday, December 13, 2013 8:10 PM
  • I need your assistance. My product 8.1 is crashing and dumping frequently.

    How do I fix? where do I start?

    Friday, December 13, 2013 8:14 PM
  • To start troubleshooting, on the local resources tab, unselect the Printers and Clipboard boxes as well as all the boxes in "More".  It may be that one of those resources is the cause of the crashes.  If you can connect successfully without crashes, then add one resource at a time to see if one of them starts the crashing again.  If it Printers, for example, you can try deleting the printer drivers from your remote computer and then trying to access and seeing if it connects without crashing.

    Good luck.

    Monday, December 23, 2013 2:39 AM
  • Hi All,

    Having a similar issue however no program is listed as causing the issue, and I have tried removing local printers and disabling the various resources to no avail. Running windows 8.1 with all updates current, not really sure what is causing the issue, event log is below:

    Faulting application name: mstsc.exe, version: 6.3.9600.16384, time stamp: 0x5215e2b5

    Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73

    Exception code: 0xc0000005

    Fault offset: 0x000000000006361a

    Faulting process id: 0x1644

    Faulting application start time: 0x01cfa5a423047da3

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

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report Id: 643abedc-1197-11e4-8261-a01d48e62973

    Faulting package full name:

    Faulting package-relative application ID:

    Anyone else having similar problems?

    Tuesday, July 22, 2014 12:12 PM