Remote Desktop Connection has stopped working

Using Build 10041. Occurs on 2 separate systems I have when trying to use Remote Desktop Connection through a 2012 R2 RDS Gateway. I am 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:
JW

Tried this with no luck.  I have the same issue as the OP.  It was failing on 10041 and is still failing with an AV on 10049.  See below event log entry after registering mstscax.dll and rebooting.  Still failing.
Log Name:      Application
Source:        Application Error
Date:          4/11/2015 12:18:21
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Chuck1
Description:
Faulting application name: mstsc.exe, version: 10.0.10049.0, time stamp: 0x55137bff
Faulting module name: mstscax.dll, version: 10.0.10049.0, time stamp: 0x55137d3f
Exception code: 0xc0000005
Fault offset: 0x000000000046d74c
Faulting process id: 0x1870
Faulting application start time: 0x01d0748c29e55e06
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\system32\mstscax.dll
Report Id: 83921b7c-e07f-11e4-960f-40f02f7ad3a4
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<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="2015-04-11T19:18:21.000000000Z" />
    <EventRecordID>73626</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Chuck1</Computer>
    <Security />
  </System>
  <EventData>
    <Data>mstsc.exe</Data>
    <Data>10.0.10049.0</Data>
    <Data>55137bff</Data>
    <Data>mstscax.dll</Data>
    <Data>10.0.10049.0</Data>
    <Data>55137d3f</Data>
    <Data>c0000005</Data>
    <Data>000000000046d74c</Data>
    <Data>1870</Data>
    <Data>01d0748c29e55e06</Data>
    <Data>C:\WINDOWS\system32\mstsc.exe</Data>
    <Data>C:\WINDOWS\system32\mstscax.dll</Data>
    <Data>83921b7c-e07f-11e4-960f-40f02f7ad3a4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Similar Messages

  • "remote desktop connection has stopped working" When printing from remote desktop connection

    I have been having a issue when using a windows 7 machine. I have Remote Desktop to a session on Windows2008 R2, I am using the local printer resources to redirect the printing. However everytime i try to print it crashes the remote desktop application.
    Gives me "remote desktop connection has stopped working." I have 4 other computers connected and printing with no issues what so ever. This only happens when i print. It does print by the way just the application crashes.
    -I have also updated the printer drivers to newest possible thru the manufactorer website. The printer is a Brother MFC-8890DW. Windows 2008 R2 is up to date for the RDS server. 3 other machines are able to Remote in and print. The user is able to print using
    diffrent machines just not the Windows 7 machine.

    Hi,
    Happy to hear that you resolved your issue. For another issue which you are facing here trying to provide some suggestion.
    As you have commented that you are facing issue with second screen resolution on wide screen. The setting which I am suggesting can only applies when you are using multi-monitor Remote Desktop connections.  If you are making Connections using a single
    monitor do not use this setting. 
    So for this you can try to apply “Limit maximum display resolution” setting in group policy, where you can mention the width & height for the screen to display. The setting can be applied on below mentioned
    path.
    Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
    Meanwhile sharing article with you for more information.
    Remote Session Environment
    http://technet.microsoft.com/en-us/library/ee791847(v=ws.10).aspx
    Hope it helps!
    Thanks.

  • "Remote Desktop connection has stopped working." problem in Windows 8

    here is the event log.  Only happens on a few of our servers
    Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
    Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505ab405
    Exception code: 0xc0000005
    Fault offset: 0x0000000000002acd
    Faulting process id: 0x13c4
    Faulting application start time: 0x01cdbd0d09091fcd
    Faulting application path: C:\Windows\System32\mstsc.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 4d923a55-2900-11e2-be73-cc52af4d02a3
    Faulting package full name:

    Your Ricoh printer drivers cause the crashes:
    * Exception Analysis *
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for RC5BE130.DLL -
    FAULTING_IP:
    ntdll!memcpy+21a
    000007f8`1fed2acd f30f6f4402f0 movdqu xmm0,xmmword ptr [rdx+rax-10h]
    EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007f81fed2acd (ntdll!memcpy+0x000000000000021a)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 00000000bd9e440c
    Attempt to read from address 00000000bd9e440c
    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: 00000000bd9e440c
    READ_ADDRESS: 00000000bd9e440c
    FOLLOWUP_IP:
    RC5BE130!PrinterProperties+2a1ea
    00000000`71c4c46a 8b442430 mov eax,dword ptr [rsp+30h]
    DETOURED_IMAGE: 1
    NTGLOBALFLAG: 0
    APPLICATION_VERIFIER_FLAGS: 0
    APP: mstsc.exe
    FAULTING_THREAD: 0000000000001198
    PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ
    BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ
    LAST_CONTROL_TRANSFER: from 0000000071c4c46a to 000007f81fed2acd
    STACK_TEXT:
    000000bb`ba9cf248 00000000`71c4c46a : 000000bb`00000040 000000bb`ba9cf618 000000bb`bd7a1458 00000000`00000000 : ntdll!memcpy+0x21a
    000000bb`ba9cf250 00000000`71c4bf68 : 000000bb`b45ccc40 000000bb`bae6e7c8 000000bb`bd7a1458 00000000`00000000 : RC5BE130!PrinterProperties+0x2a1ea
    000000bb`ba9cf2a0 00000000`71c4b2f9 : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`71c10000 : RC5BE130!PrinterProperties+0x29ce8
    000000bb`ba9cf380 00000000`71c2a08a : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`02000000 : RC5BE130!PrinterProperties+0x29079
    000000bb`ba9cf3d0 00000000`71c283de : 000000bb`ba9cf618 000000bb`badfb050 000000bb`00000000 00650074`00730079 : RC5BE130!PrinterProperties+0x7e0a
    000000bb`ba9cf440 00000000`71c2209d : 00000000`00000000 000000bb`ba9cf618 00007989`001a0019 000007f8`169fafa0 : RC5BE130!PrinterProperties+0x615e
    000000bb`ba9cf550 000007f8`169e5ea0 : 00000000`00000000 000000bb`ba9cf618 000000bb`bd7a1458 000000bb`bd7a1458 : RC5BE130!DrvDocumentPropertySheets+0x1d
    000000bb`ba9cf580 000007f8`169e6b9f : 000000bb`00000000 000000bb`ba9cf670 00000000`00000000 00000000`00000004 : winspool!DocumentPropertySheets+0xb0
    000000bb`ba9cf5f0 000007f8`169e6aa5 : 00000000`00000002 000007f8`ffffffff 00000000`00000000 00000000`00000000 : winspool!DocumentPropertiesWNative+0xcf
    000000bb`ba9cf680 000007ff`f4f3dc32 : 00000000`00000000 000000bb`b93f3990 00000000`000004d4 000000bb`ba9cf790 : winspool!DocumentPropertiesW+0x7d
    000000bb`ba9cf6e0 000007ff`f4f9a09b : 00000000`00000000 000000bb`ba9cf7b0 00000000`00000000 000000bb`b93c7530 : mstscax!CTSClientPrintDriver::DocumentPropertiesW+0x37e
    000000bb`ba9cf730 000007ff`f4f994d4 : 000000bb`b93c7530 000007f8`00000000 00000000`00000000 000000bb`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Invoke_DocumentPropertiesW+0x12b
    000000bb`ba9cf7e0 000007ff`f4f8ff0c : 000000bb`b93c7530 000000bb`b93f29e0 000000bb`b94060d0 00000000`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Dispatch_Invoke+0x68
    000000bb`ba9cf840 000007ff`f4f95a84 : 000000bb`b93c7530 00000000`00000000 000000bb`b93c7530 000000bb`b93cccc0 : mstscax!CStub<IMMClientNotifications>::Invoke+0x64
    000000bb`ba9cf8b0 000007ff`f4f94310 : 000000bb`b93cccc0 000000bb`b93c7530 000000bb`ba9cf930 000000bb`b693b3c0 : mstscax!CRIMStreamStub::OnDataReceived+0x98
    000000bb`ba9cf8e0 000007ff`f4f18c5a : 000000bb`b93cccc0 000000bb`b93f4cd8 000000bb`b93f4b10 000000bb`b93f4cd8 : mstscax!CRIMObjManager::OnDataReceived+0x150
    000000bb`ba9cf960 000007ff`f4f20132 : 000000bb`b93c6908 00000000`00000000 000000bb`b93c6908 00000000`00000e28 : mstscax!CDynVCChannel::HandleAsyncCall+0x12e
    000000bb`ba9cf9b0 000007ff`f4ed94e7 : 000000bb`b93f36a0 000000bb`b93c68c0 00000000`00000000 000000bb`b93f40d0 : mstscax!CDynVCThreadPoolThread::ThreadPoolEntry+0x102
    000000bb`ba9cfa00 000007ff`f4c5aba9 : 000000bb`b7ddeb58 00000000`00000000 000007ff`f4b50000 00000000`00000000 : mstscax!CTSThread::TSStaticThreadEntry+0x33b
    000000bb`ba9cfa90 000007f8`1e41167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!PAL_System_Win32_ThreadProcWrapper+0x25
    000000bb`ba9cfac0 000007f8`1fef3501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
    000000bb`ba9cfaf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: rc5be130!PrinterProperties+2a1ea
    FOLLOWUP_NAME: wintriag
    MODULE_NAME: RC5BE130
    IMAGE_NAME: RC5BE130.DLL
    DEBUG_FLR_IMAGE_TIMESTAMP: 4bd67428
    STACK_COMMAND: ~18s; .ecxr ; kb
    FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_RC5BE130.DLL!PrinterProperties
    BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_DETOURED_rc5be130!PrinterProperties+2a1ea
    WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/ntdll_dll/6_2_9200_16420/505ab405/c0000005/00002acd.htm?Retriage=1
    Followup: wintriag
    0:018> lmvm RC5BE130
    start end module name
    00000000`71b00000 00000000`71cdd000 RC5BE130 (export symbols) RC5BE130.DLL
    Loaded symbol image file: RC5BE130.DLL
    Image path: C:\Windows\System32\spool\drivers\x64\3\RC5BE130.DLL
    Image name: RC5BE130.DLL
    Timestamp: Tue Apr 27 07:20:40 2010 (4BD67428)
    CheckSum: 001E2D52
    ImageSize: 001DD000
    File version: 0.3.0.0
    Product version: 1.0.0.0
    File flags: 1 (Mask 3F) Debug
    File OS: 40004 NT Win32
    File type: 2.1 Dll
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: RICOH CO., LTD.
    ProductName: RICOH RPCS Printer Driver
    InternalName: RC5BE130.DLL
    OriginalFilename: RC5BE130.DLL
    ProductVersion: 1.0.0
    FileVersion: 7.6.9
    FileDescription: RICOH RPCS Printer Driver
    LegalCopyright: Copyright(C) 1999-2010 RICOH CO., LTD.
    so check for a printer driver update and what you can also do is to avoid mapping your printer to the Remote Desktop. Maybe this also fixes the issue.
    "A programmer is just a tool which converts caffeine into code"

  • Remote Desktop Connection has stop'd working.

    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: mstsc.exe
      Application Version: 6.2.9200.16384
      Application Timestamp: 50108ae1
      Fault Module Name: ntdll.dll
      Fault Module Version: 6.2.9200.16384
      Fault Module Timestamp: 5010acd2
      Exception Code: c0000005
      Exception Offset: 0000000000005512
      OS Version: 6.2.9200.2.0.0.256.48
      Locale ID: 1033
      Additional Information 1: 2534
      Additional Information 2: 25341db0b9a417145dca7b48f0cbb4e4
      Additional Information 3: a713
      Additional Information 4: a71352bbdf06cb9997aaf28933a5ca7d

    Hi,
    Based on the current situation, this error means mstsc.exe made a call into ntdll.dll (which is part of the Windows operating system) and whatever they're doing, they're doing it wrong because it caused a crash.
    Let us try capture a dump file  and upload your app dump file.
    First enable app crash dump collection by copying following words into notepad, saving it as dump.reg and importing it:
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\localdumps\mstsc.exe]
    "DumpFolder"=hex(2):63,00,3a,00,5c,00,63,00,72,00,61,00,73,00,68,00,64,00,75,\
      00,6d,00,70,00,73,00,00,00
    "DumpCount"=dword:00000010
    "DumpType"=dword:00000001
    "CustomDumpFlags"=dword:00000000
    Then, do a Remote Desktop Connection which may cause the issue. If error appeared, please find the crashdump file under c:\.
    Note: I highly recommend you use SkyDrive to upload collected files and to post screen shots/pictures. Although you might not be used to it, SkyDrive features a lot of free advanced functionality around file storage capacity, sharing, privacy, and collaboration:
    http://skydrive.com
    Keep post.
    Regards,
    Kelvin hsu
    TechNet Community Support

  • SOLVED: BlackBerry Desktop Manager Has Stopped Working

    Good morning.
    Let me start off by saying I have a Dell laptop runing Vista 64 bit with 4 gig ram.  I have Desktop Manager v 4.7 installed and has been working great synching my Outlook calender and my Blackberry.
    Starting about a week ago, the synch process gets all the way to the end and I get a message saying:
    "BlackBerry Desktop Manager Has Stopped Working" and I have the choice to "check online for a solution and close the program" or "close the program".  When I click on "view problem details I get this:
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: DesktopMgr.exe
      Application Version: 4.7.0.37
      Application Timestamp: 49c1b7ab
      Fault Module Name: StackHash_6d57
      Fault Module Version: 6.0.6001.18000
      Fault Module Timestamp: 4791a783
      Exception Code: c0000374
      Exception Offset: 000aada3
      OS Version: 6.0.6001.2.1.0.768.3
      Locale ID: 1033
      Additional Information 1: 6d57
      Additional Information 2: a8064b034a1a2f2f618d075073f8fe42
      Additional Information 3: 2dc5
      Additional Information 4: dbcf31406c7084dbad1f33e2de526f4e
    Read our privacy statement:
      http://go.microsoft.com/fwlink/?linkid=50163&clcid​=0x0409
    Any ideas?
    Message Edited by The_Geek on 09-29-2009 06:51 AM
    Message Edited by The_Geek on 09-29-2009 07:38 AM
    Solved!
    Go to Solution.

    I found this on another site:
    1.) Start the Desktop Manager software 
    2.) Connect the blackberry using USB Connector
    3.) Select "back-up and restore"
    4.) Select "advanced"
    5.) Look at the list of information showing in the "device memory" window on your computer
    6.) Select "calender all" and DELETE it
    7.) Go back to the main screen and syncronize.
    8.) Everything should work fine!
    In essence it was a corrupt calendar data file on the Blackberry device, apparently.

  • BB Desktop Software has stopped working (V6.1.0)

    My BlackBerry Desktop Software has stopped working.
    My Devise: BB Torch 9800
    OS: Win 7
    Issus: When I connect my BB or double click on BB Desktop icon - it open the BB Desktop Software and closes instantly with an message "BB Desktop Software has stopped working. Windows is checking if a solution is available. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
    I have uninstalled and installed BB Desktop Software but still I get this message. I am unable to sync and use the desktop software.
    I have called my carrier and they couldnt help me and mentioned it is a problem with my PC. But I dont think so as this was working all these days  and now suddenly I am getting this error. I dont remember but I might have updated the BB Desktop Sofware to 6.1.0 version.
    Please help.

    I may have fixed this...
    I totally removed desktop software (again) and - for the record - removed ALL user settings (If I couldn't get this working I was gunna call in my upgrade to another brand anyway )
    I then re-installed BB Desktop - again for the record - from build 34, (610_b034_multilanguage.exe) which I happened to have in my download directory still (this might work with b038 though to be fair).
    I then re-installed it, as I have done like 10 times, BUT this time, I changed the install directory to "c:\program files" instead of the default - on widnwos 7 64 bit - which is "c:\program files (x86)"
    by putting it here, you get round some sticky windows issues, including UAC **bleep**. I than ran it, and low and behold it detected and synced and loved my Bold  9700 all over again!
    Maybe I will get that BB 9900 (or torch 9810) after all I can feel my new music flooding onto my memory card as I type

  • Blackberry Desktop Software has stopped working. A problem has caused the program to stop...

    I have a Tour 9630 and just installed v6.0 and receiving an error window "Blackberry Desktop Software has stopped working. A problem as caused the program to stop working correctly.  Windows will close the program and notify you if a solution is available."  I have not received any message from Windows after 2 days.  Has anyone experienced this problem?  If so, I would appreciate any guidance.  I have Windows 7, if that matters. Thank you. in advance.

    Hi somewhatstock
    How far did you get with them? Did they have any ideas what might be causing the problem? Trying to work on it myself, so trying to eliminate what others might have tried. Curious why it works on my Desktop however. Losing tethering really causes problems as I rely on tethering with my laptop quite a lot.  
    Any information most welcome,
    regards,
    John

  • Remote Desktop Connection has encountered a problem and needs to close. We are sorry for the inconvenience.

    Remote Desktop Connection has encountered a problem and needs to close. We are sorry for the inconvenience.

    Hiya,
    What O/S versions(RDP) are you connecting to and from? Try and open the target machines event log and see what it throws when you try to connect.

  • Blackberry Desktop Software has stopped working

    Blackberry Torch 9850 on the Verizon Wireless Network
    Blackberry OS: 7.1 Bundle 1737 (v 7.1.0.580, Platform 5.1.0.429)
    Windows 7 Home Premium, SP11 with an full admin account
    HP Desktop computer
    For some unknown reason whenever I attempt to execute Blackberry Desktop Software version 7.1 the application returns the following error: "Blackberry Desktop Software has stopped working: A problem caused the program and notify you if a solution is available." The last successful use of DM was on Sunday, October 7, 2012 when I synched my phone and did a backup of the device.
    I have uninstalled and re-installed the application; uninstalled Microsoft .Net Framework version 3.5 and 4.0 then re-installed .Net Framework; then re-installed DM under a new admin account and still getting the same problem. I even went as far as uninstalling Office and re-installing office and still getting the same problem. Whenever I uninstalled DM I did a manual uninstall where I removed all registry keys associated with Research in Motion including folders and still getting the same problem. I Googled the error and the articles worth reading I have already the things they mentioned.
    NOTE: I have done a lot more troubleshooting that is listed. But since I did so much to get this to work it will take me an entire novel to list all the things I have done to get this app to work again.
    Called VZW and they got me in contact with RIM. RIM did pretty much the same things I did and after spending 7 hours on the phone with them they concluded I need to reformat my drive. When the tech made that suggested I wanted to reach thru the phone and knock her teach out of her mouth. Suffice to say I am not able to get DM to work on my machine and there appears to be no apparent reason why the software will stop working. Not have DM work means I cannot synch my phone. I have one personal computer and I am not going to install DM on my laptop because it will do me no good since I need to synch it with Outlook which is on my personal desktop. I cannot install my personal copy of office on my work laptop because it will probably cause other issues.
    Anyone have any suggestions how I can get this application working on my desktop. It was working before and all of a sudden it stopped  working

    http://www.blackberry.com/btsc/KB02206
    1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
    2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you!

  • Blackberry Desktop Software 6.1.0.35 fails to launch with "BlackBerry Desktop Software has stopped working"

    OS: Windows 7 32bit
    BB Desktop Manager version: 6.1.0.35
    I bought a new notebook a few days ago and tried to install the above software (latest version) from Blackberry's website. The whole thing installed fine but when I tried to launch it after installation, I get the message:
    "BlackBerry Desktop Software has stopped working"
    I tried the clean uninstall with removal of folders and registry entries, rebooting it, running regsvr32 atl.dll and then reinstalling it and still I have the same problem.
    I had experienced a similar issue with my previous computer which I fixed by changing the permission and ownership of two registry keys "HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion" and "HKEY_CURRENT_USER\SOFTWARE\Research In Motion". But this time round, I found that:
    1) There is no "HKEY_CURRENT_USER\SOFTWARE\Research In Motion"
    2) I can't find a  "Desktop.log" in "C:\Users\<username>\AppData\Roaming\Research In Motion\BlackBerry Desktop" but I did find it in "C:\Users\<username>\AppData\Local\Research In Motion\BlackBerry Desktop\Logs"
    And this what it says:
    Date|Log Level|Thread ID|Module ID|Log ID|Message [2011-06-10 03:18:51.794]03:18:51.810|INFO |1|Rim.Desktop.Shell|1|Application Started03:18:51.826|INFO |1|Rim.Desktop.Shell|2|Commandline: "C:\Program Files\Research In Motion\BlackBerry Desktop\Rim.Desktop.exe"03:18:51.826|INFO |1|Rim.Desktop.Shell|2|Rim.Desktop.exe Version: 6.1.0.3503:18:51.826|INFO |1|Rim.Desktop.Shell|2|Product Installation Variant: none03:18:51.857|INFO |1|Rim.Desktop.Shell|2|OS Version: Windows7 [Microsoft Windows NT 6.1.7601 Service Pack 1] 03:18:51.857|INFO |1|Rim.Desktop.Shell|2|CLR Version: 2.0.50727.544403:18:51.872|INFO |1|Rim.Desktop.Shell|2|AppLoader Version: 6.0.1.3303:18:51.872|INFO |1|Rim.Desktop.Shell|2|Device Manager Version: 6.0.0.3003:18:51.888|INFO |1|Rim.Desktop.Shell|2|BBDevMgr Version: 4.2.0.1203:18:51.888|INFO |1|Rim.Desktop.Shell|2|Serial USB Driver Version: 2.2.0.303:18:51.888|INFO |1|Rim.Desktop.Shell|2|USB Driver Version: 4.2.0.1203:18:51.888|INFO |1|Rim.Desktop.Shell|2|PlayBook RNDIS Driver Interface: 1.0.0.16Date|Log Level|Thread ID|Module ID|Log ID|Message [2011-06-10 03:25:49.579]03:25:49.594|INFO |1|Rim.Desktop.Shell|1|Application Started03:25:49.610|INFO |1|Rim.Desktop.Shell|2|Commandline: "C:\Program Files\Research In Motion\BlackBerry Desktop\Rim.Desktop.exe" 03:25:49.610|INFO |1|Rim.Desktop.Shell|2|Rim.Desktop.exe Version: 6.1.0.3503:25:49.610|INFO |1|Rim.Desktop.Shell|2|Product Installation Variant: none03:25:49.610|INFO |1|Rim.Desktop.Shell|2|OS Version: Windows7 [Microsoft Windows NT 6.1.7601 Service Pack 1] 03:25:49.610|INFO |1|Rim.Desktop.Shell|2|CLR Version: 2.0.50727.544403:25:49.625|INFO |1|Rim.Desktop.Shell|2|AppLoader Version: 6.0.1.3303:25:49.625|INFO |1|Rim.Desktop.Shell|2|Device Manager Version: 6.0.0.3003:25:49.625|INFO |1|Rim.Desktop.Shell|2|BBDevMgr Version: 4.2.0.1203:25:49.625|INFO |1|Rim.Desktop.Shell|2|Serial USB Driver Version: 2.2.0.303:25:49.625|INFO |1|Rim.Desktop.Shell|2|USB Driver Version: 4.2.0.1203:25:49.625|INFO |1|Rim.Desktop.Shell|2|PlayBook RNDIS Driver Interface: 1.0.0.16Date|Log Level|Thread ID|Module ID|Log ID|Message [2011-06-10 03:27:36.709]03:27:36.726|INFO |1|Rim.Desktop.Shell|1|Application Started03:27:36.743|INFO |1|Rim.Desktop.Shell|2|Commandline: "C:\Program Files\Research In Motion\BlackBerry Desktop\Rim.Desktop.exe" 03:27:36.743|INFO |1|Rim.Desktop.Shell|2|Rim.Desktop.exe Version: 6.1.0.3503:27:36.745|INFO |1|Rim.Desktop.Shell|2|Product Installation Variant: none03:27:36.745|INFO |1|Rim.Desktop.Shell|2|OS Version: Windows7 [Microsoft Windows NT 6.1.7601 Service Pack 1] 03:27:36.745|INFO |1|Rim.Desktop.Shell|2|CLR Version: 2.0.50727.544403:27:36.750|INFO |1|Rim.Desktop.Shell|2|AppLoader Version: 6.0.1.3303:27:36.754|INFO |1|Rim.Desktop.Shell|2|Device Manager Version: 6.0.0.3003:27:36.757|INFO |1|Rim.Desktop.Shell|2|BBDevMgr Version: 4.2.0.1203:27:36.759|INFO |1|Rim.Desktop.Shell|2|Serial USB Driver Version: 2.2.0.303:27:36.761|INFO |1|Rim.Desktop.Shell|2|USB Driver Version: 4.2.0.1203:27:36.762|INFO |1|Rim.Desktop.Shell|2|PlayBook RNDIS Driver Interface: 1.0.0.16Date|Log Level|Thread ID|Module ID|Log ID|Message [2011-06-10 03:52:59.084]03:52:59.099|INFO |1|Rim.Desktop.Shell|1|Application Started03:52:59.115|INFO |1|Rim.Desktop.Shell|2|Commandline: "C:\Program Files\Research In Motion\BlackBerry Desktop\Rim.Desktop.exe" 03:52:59.115|INFO |1|Rim.Desktop.Shell|2|Rim.Desktop.exe Version: 6.1.0.3503:52:59.131|INFO |1|Rim.Desktop.Shell|2|Product Installation Variant: none03:52:59.131|INFO |1|Rim.Desktop.Shell|2|OS Version: Windows7 [Microsoft Windows NT 6.1.7601 Service Pack 1] 03:52:59.131|INFO |1|Rim.Desktop.Shell|2|CLR Version: 2.0.50727.544403:52:59.131|INFO |1|Rim.Desktop.Shell|2|AppLoader Version: 6.0.1.3303:52:59.131|INFO |1|Rim.Desktop.Shell|2|Device Manager Version: 6.0.0.3003:52:59.131|INFO |1|Rim.Desktop.Shell|2|BBDevMgr Version: 4.2.0.1203:52:59.146|INFO |1|Rim.Desktop.Shell|2|Serial USB Driver Version: 2.2.0.303:52:59.146|INFO |1|Rim.Desktop.Shell|2|USB Driver Version: 4.2.0.1203:52:59.146|INFO |1|Rim.Desktop.Shell|2|PlayBook RNDIS Driver Interface: 1.0.0.16Date|Log Level|Thread ID|Module ID|Log ID|Message [2011-06-10 03:54:52.634]03:54:52.651|INFO |1|Rim.Desktop.Shell|1|Application Started03:54:52.669|INFO |1|Rim.Desktop.Shell|2|Commandline: "C:\Program Files\Research In Motion\BlackBerry Desktop\Rim.Desktop.exe" 03:54:52.669|INFO |1|Rim.Desktop.Shell|2|Rim.Desktop.exe Version: 6.1.0.3503:54:52.670|INFO |1|Rim.Desktop.Shell|2|Product Installation Variant: none03:54:52.671|INFO |1|Rim.Desktop.Shell|2|OS Version: Windows7 [Microsoft Windows NT 6.1.7601 Service Pack 1] 03:54:52.671|INFO |1|Rim.Desktop.Shell|2|CLR Version: 2.0.50727.544403:54:52.675|INFO |1|Rim.Desktop.Shell|2|AppLoader Version: 6.0.1.3303:54:52.679|INFO |1|Rim.Desktop.Shell|2|Device Manager Version: 6.0.0.3003:54:52.683|INFO |1|Rim.Desktop.Shell|2|BBDevMgr Version: 4.2.0.1203:54:52.685|INFO |1|Rim.Desktop.Shell|2|Serial USB Driver Version: 2.2.0.303:54:52.686|INFO |1|Rim.Desktop.Shell|2|USB Driver Version: 4.2.0.1203:54:52.687|INFO |1|Rim.Desktop.Shell|2|PlayBook RNDIS Driver Interface: 1.0.0.16Date|Log Level|Thread ID|Module ID|Log ID|Message [2011-06-10 05:31:32.231]05:31:32.295|INFO |1|Rim.Desktop.Shell|1|Application Started05:31:32.364|INFO |1|Rim.Desktop.Shell|2|Commandline: "C:\Program Files\Research In Motion\BlackBerry Desktop\Rim.Desktop.exe" 05:31:32.364|INFO |1|Rim.Desktop.Shell|2|Rim.Desktop.exe Version: 6.1.0.3505:31:32.365|INFO |1|Rim.Desktop.Shell|2|Product Installation Variant: none05:31:32.366|INFO |1|Rim.Desktop.Shell|2|OS Version: Windows7 [Microsoft Windows NT 6.1.7601 Service Pack 1] 05:31:32.366|INFO |1|Rim.Desktop.Shell|2|CLR Version: 2.0.50727.544405:31:32.543|INFO |1|Rim.Desktop.Shell|2|AppLoader Version: 6.0.1.3305:31:32.675|INFO |1|Rim.Desktop.Shell|2|Device Manager Version: 6.0.0.3005:31:33.021|INFO |1|Rim.Desktop.Shell|2|BBDevMgr Version: 4.2.0.1205:31:33.105|INFO |1|Rim.Desktop.Shell|2|Serial USB Driver Version: 2.2.0.305:31:33.183|INFO |1|Rim.Desktop.Shell|2|USB Driver Version: 4.2.0.1205:31:33.325|INFO |1|Rim.Desktop.Shell|2|PlayBook RNDIS Driver Interface: 1.0.0.16
    I have scanned through it and I can't find anything that says "fatal".
    Any suggestions? I am at my wits end after combing through this forum and other BB forums for the past few long days and nights.
    HELP!

    Well folks. I've had enough.
    The 9780 is a great phone, it's easy to use, practical and dependable. However, the Desktop Manager software has been giving me too many sleepless nights. On two occassions I must add: once at the end of last year when I bought it and only managed to solve it by myself after 4 weeks of trawling through online forums, blogs and other BB help sites and the recent one was last week when I tried to install it on my new Windows 7 notebook.
    I know this is not entirely the fault of RIM, Microsoft also has a part to play. But considering the state of technology these days, it shouldn't have to be so difficult. I want a phone and software that makes my life easier and not have to be a slave to it by trying days and nights to solve its problems.
    Hence, I have officially decom my phone and gotten an iPhone 4 instead. The switch ain't that difficult for me as I have always been platform neutral. As long it fits my needs, does it job well and doesn't give me too much headache, I'm cool with it.
    Ciao folks!

  • Desktop Manager Has Stopped Working @ Processing Device Calendar During Sync Process

    I have a BB 8330 and have an annoying issue....it sync'd with MS Outlook for about 2 months after i got it then I started getting an error inthe sync process "Blackberry Desktop Manager Has Stopped Working, Windows is shutting it Down"....this always happens at the exact same point inthe sync process..."Processing Device Calendar".
    I've done everything, Verizon tech support...BB tech support...uninstall/reinstall...nothing has fixed it. I even deleted everything out of outlook and started over. The odd thing is that everything EXCEPT the calendar will sync....it's just when it gets to the "processing device calendar" is stops syncing and I get the 'DM Has stopped working' error and it closes.
    I am going to scream if I can't get this fixed...it's been going on since last October!!
    Any fixes out there?

    Hmm. That may be something in your calendar database is corrupt. Was your device ever synched before? There is a way of clearing the calendar database. So if you have your device synching with Outlook, after it's cleared from the BlackBerry, you could try synching again.
    To clear the calendar database you can go into Desktop Manager | Backup and Restore | Advanced. On the right hand side select the calendar database and hit the Clear button. Afterwards try synching again
    If someone has been helpful please consider giving them kudos by clicking the star to the left of their post.
    Remember to resolve your thread by clicking Accepted Solution.

  • Desktop software has stopped working

    See error message below:
    10:54:15.775|FATAL|1|Exception|0|Fatal Error
    System.TypeInitializationException: The type initializer for 'System.Windows.Media.FontFamily'
    Upon launch of 6.0, the error occurs with this note:
    Blackberry Desktop Software has stopped working
    A problem caused the program to stop working correctly. Windlwos will close the program and notify you if a solution is available.
    I found the above log file under:
    C:\Users\Dave\AppData\Roaming
    What is the deal with the font and how do I get rid of it so we can use the Blackberry software. We are running Windows 7 pro.
    chrismt

    Thanks for the reply.
    Follow all of the steps in this KB article and once completed restart your computer:
    www.blackberry.com/btsc/KB02206
    Then once the computer is up and running, disable all start up items in msconfig.
    Restart the computer again and install BlackBerry Desktop Software again.  
    -ViciousFerret
    Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
    Be sure to click Like! for those who have helped you.
    Click  Accept as Solution for posts that have solved your issue(s)!

  • Blackberry Desktop Software Error "Blackberry Desktop Software Has Stopped Working"

    Hi everyone,
    I’ve had a Blackberry Playbook (PB) for almost a year now. Recently I decided I was going to back my data up, but the Blackberry desktop software I was using was 5.0... Something. So I went to http://uk.blackberry.com/software/desktop.html to update the software. I uninstalled the old one and installed the new one.
    When I tried to open the newly installed software I got this error "Blackberry Desktop Software Has Stopped Working." So I did my research and found that this was happening to other people.
    These are the methods I used to try to fix the problem.
    - Clean Uninstall
    - Removing registry
    - Deleting research in motion (appdata)
    - Restarting my computer about 5 times
    I went into event properties this is what i got. 
    Log Name: Application
    Source: Windows Error Reporting
    Date: 24/12/2013 18:47:10
    Event ID: 1001
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: chris-PC
    Description:
    Fault bucket , type 0
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: rim.desktop.exe
    P2: 7.0.0.32
    P3: 4ec52db7
    P4: PresentationCore
    P5: 3.0.0.0
    P6: 5167b4a6
    P7: 5021
    P8: 0
    P9: System.TypeInitialization
    P10:
    Attached files:
    C:\Users\chris\AppData\Local\Temp\WER149C.tmp.WERInternalMetadata.xml
    These files may be available here:
    C:\Users\chris\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_rim.desktop.exe_9bdef9e2dd7fbaf28513bb5d4d0211dfedde59_0d63197c
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: ca93e8f6-6ccb-11e3-923b-c89cdc60362a
    Report Status: 1
    Event Xml:
    <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-12-24T18:47:10.000000000Z" />
    <EventRecordID>41859</EventRecordID>
    <Channel>Application</Channel>
    <Computer>chris-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>CLR20r3</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>rim.desktop.exe</Data>
    <Data>7.0.0.32</Data>
    <Data>4ec52db7</Data>
    <Data>PresentationCore</Data>
    <Data>3.0.0.0</Data>
    <Data>5167b4a6</Data>
    <Data>5021</Data>
    <Data>0</Data>
    <Data>System.TypeInitialization</Data>
    <Data>
    </Data>
    <Data>
    C:\Users\chris\AppData\Local\Temp\WER149C.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\Users\chris\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_rim.desktop.exe_9bdef9e2dd7fbaf28513bb5d4d0211dfedde59_0d63197c</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>ca93e8f6-6ccb-11e3-923b-c89cdc60362a</Data>
    <Data>1</Data>
    </EventData>
    </Event> 
    Please help thanks.

    Use SEARCH function on your computer and enable it to search EVERYWHERE and remove all   "blackberry"   files found.

  • Windows desktop gadgets has stopped working

    As of a few days ago my desktop gadgets have stopped working.  When I start Windows they appear to function normally for a minute or so then the error message "Windows desktop gadgets has stopped working" appears.  Sometimes there is a second attmept to launch the gadgets but it fails in the same manner.
    Worryingly for the general robustness of Windows 7, performing a System Restore to a time before the problem arose did NOT fix the problem. 

    I have found this solution and worked perfectly for me, you might want to try it out!
    I own no credit over this!
    Thanks to " Ramesh Srinivasan   "
     Is your Windows Sidebar (Windows Desktop Gadgets) crashing after adding a third-party gadget, with the error "Windows Desktop Gadgets has stopped working" or "Windows
    Sidebar has stopped working" (Windows Vista) at every start? You can stop the offending gadget from loading by editing the Windows Sidebar Gadgets settings file. Here are the instructions, which apply to Windows 7 and Windows Vista.
    If Sidebar.exe process is running, you wouldn’t be able to write to its settings file. Launch Task Manager (taskmgr.exe), select the sidebar.exe process and terminate it if it’s running.
    Click Start, type the following path in the Search box and hit ENTER.
    %LOCALAPPDATA%\Microsoft\Windows Sidebar
    (You can type it in the Run dialog as well.)
    The above location is where the desktop gadgets store their configuration information, in a file named Settings.ini
    First, make a copy of Settings.ini
    Double-click Settings.ini to open it in Notepad.
    Configuration information for the last installed desktop gadget is usually located at the end of the INI file. Using the PrivateSetting_GadgetName line as the hint, locate the corresponding [Section #], select all lines underneath
    and delete it. Trim any blank lines that may have resulted from the deletion.
    Then, move to the top of the INI file, and delete the Section# line that references the offending gadget. As you’ve removed the entries in [Section 5], also delete the following line:
    Section4="5"
    Trim any blank lines that may have resulted from the deletion, and save the Settings.ini file.
    Right-click on the Desktop, and click Gadgets. This starts the Sidebar.exe process and shows the gadgets listed in the Settings.ini file.

  • RIM.Desktop Helper has stopped working

    Hi there,
    I just download Desktop Software v6 to my laptop HP window7 64 bit. when i installed, it open the WELCOME window and before i can press the Get Started button, it pop up another window saying RIM.Desktop Helper has stopped working  and the windows is checking but after that it closed.
    What should i do?
    Many thanks

    Hmm. That may be something in your calendar database is corrupt. Was your device ever synched before? There is a way of clearing the calendar database. So if you have your device synching with Outlook, after it's cleared from the BlackBerry, you could try synching again.
    To clear the calendar database you can go into Desktop Manager | Backup and Restore | Advanced. On the right hand side select the calendar database and hit the Clear button. Afterwards try synching again
    If someone has been helpful please consider giving them kudos by clicking the star to the left of their post.
    Remember to resolve your thread by clicking Accepted Solution.

Maybe you are looking for

  • Itunes & external hard drive questions "original file could not be found"

    I recently got my first apple, a Powerbook G4, and I am trying to figure out how to store and access my music files that are on my external hard drive. I have some music stored on my laptop and the majority of it on the hard drive. I can play the fil

  • My Illustrator does not allow me to change colors using swatches panel. Help pleas.

    Few days ago I started having strange problems with my Illustrator CS5 application. I am using MacBook Pro with Intel Processor.  After major update on the Mac OS  few days ago  I noticed I can not change colors in my drawings using swatches panel. T

  • Can't Create a NEW LIBRARY

    I'm trying to create a new library to do some maintenance on certain files (I'll spare you the details as to WHY). I can't figure out how to create a new library. I've tried holding the SHIFT key when starting iTunes per the instructions here: http:/

  • Time machine dropping old backups after migrating

    I recently changed from an iMac to a retina Macbook Pro. I read that I could continue my time machine after migrating my mac. My new macbook keeps trying to create a brand new backup. I enter time machine and go back to find all my old dates but it d

  • Process Chain display

    Hi All, I am looking after process chains everyday , today I can see process failed at  RSPCM ,I when to particular process chain at RSPC double on process chain not unable to display any process chain in production system. when I double click on pro