Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® OS Smartphones

Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.

New Contributor
Posts: 9
Registered: ‎06-30-2010
My Device: storm 9530
My Carrier: Verizon

Re: Desktop Manager 6.0 Crashing

I just updated the desktop manager, and when I went to synch it kept giving me an "unknown error"  so I went back to the original version of the desktop manager, and the same thing happened.  Has anyone had this problem?  I can't synch my calendar or contacts.  It worked fine last week.  Don't know if this is a computer or phone problem, or both.  Thanks!

Posts: 41
Registered: ‎08-14-2010
My Device: 8900 Curve

Re: Desktop Manager 6.0 Crashing

Who says this is solved?


Anyone still having problems despite moving the Video folder.


I have moved, even deleted the video folder - to no avail - the DM6 icon just won't launch the program!


Anyone else still facing this non-start issue ?

Posts: 41
Registered: ‎08-14-2010
My Device: 8900 Curve

Re: Desktop Manager 6.0 Crashing

Any Windows 7 Whizz kid out there who could tell us where to find a good debug tool or set up some trace or something that could help us get a clue as to what is causing this insane DM6 crash problem!


And you are right, do not understand why RIM remains so impassive.

Anyway one can buy support to get some decent response or action from RIM ?

Posts: 1
Registered: ‎08-17-2010
My Device: Bold 9700

Re: Desktop Manager 6.0 Crashing

The problem has NOT been solved. Tried moving the videos with no success. Program launches fine, but when you click on anything (options, help, tools, etc...) the program crashes. HELP!!! Bold 9700 Windows 7 

New Contributor
Posts: 4
Registered: ‎08-11-2010
My Device: Not Specified

Re: Desktop Manager 6.0 Crashing

In mechanicus post near the beginning of the thread he says:


"If the application simply disappears, you can try to set the following Registry key:


HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerryTranscoder\SkipSupportCheck (DWORD) to a value of ‘1’"


Now myself and others couldn't find this at all.  In fact I couldn't even find Research In Motion listed there.  So I did a little search of my registry and found:


HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Research In Motion\BlackBerryTranscoder



Notice the Wow6234Node  comes after software.   Since this is the only place I could find BlackBerry Transcoder I tried adding the SkipSupportCheck here.  I'm not saying this is where your registry key is but that's where the installer put it on my pc.  So do a registry search to find it.


Well now it appears to work fine.  It used to crash 20-30 seconds after launch.  I have now been using it for 15 minutes and all seems well.


Now my question is what features are disabled by adding in that dword?  Obviously I can't tell what I'm missing since it never ran right in the first place.


And when the fix comes out, will I have to manually delete that key?


I hope this helped some of you.









Posts: 41
Registered: ‎08-14-2010
My Device: 8900 Curve

Re: Desktop Manager 6.0 Crashing

Thanks Steve,


I am going to look into regedit and do what you say... which version of Wiindows are you running?

Vista  /  Win 7 32 or Win 7 64 ?


In the meantime, I went into the Windows error reporting log which says this and does seem to refer to some "out of memory exception" ....  This is all jibberish to me but it does relate to RIM!  And it did leave a WER file on my laptop... which I  cannot open.  Never looked at WER files before!





16/08/2010 11:19              Windows Error Reporting           


Fault bucket 1306260832, type 5
   Event Name: CLR20r3
 Response: Not available
Cab Id: 0

Problem signature:
P1: rim.desktop.exe
P3: 4c58acef
P4: PresentationCore
P6: 4b595103
P7: 46f
P8: 13
P9: System.OutOfMemoryException

Attached files:

These files may be available here:

Analysis symbol: 
Rechecking for solution: 0
Report Id: 011ba5fa-a928-11df-bf8d-60380e1621c4
Report Status: 0



Posts: 41
Registered: ‎08-14-2010
My Device: 8900 Curve

Re: Desktop Manager 6.0 Crashing

Steve -


I went into Regedit, found the BlackberryTranscoder entry. Added the Keyword and set value of 1.

Still - did not work - still experiencing the same crash as before.


Like you  know,  not sure what this is meant to do !


But many thanks for helping! (And I  realise you run Vista, I am on Win 7 32bit.



New Contributor
Posts: 4
Registered: ‎08-11-2010
My Device: Not Specified

Re: Desktop Manager 6.0 Crashing

I'm running Vista 64.  Also it shoudln't make a difference but it's the Ultimate version.



New Contributor
Posts: 6
Registered: ‎08-13-2010
My Device: 8330
My Carrier: Sprint

Re: Desktop Manager 6.0 Crashing

More info for the brain-trust who released this alpha-version software as a release candidate:



- System 

  - Provider 

   [ Name]  Application Error 
  - EventID 1000 

   [ Qualifiers]  0 
   Level 2 
   Task 100 
   Keywords 0x80000000000000 
  - TimeCreated 

   [ SystemTime]  2010-08-17T20:38:30.000000000Z 
   EventRecordID 15739 
   Channel Application 
   Computer Dan-TP 

- EventData 

   C:\Program Files\Research In Motion\BlackBerry Desktop\Rim.Desktop.exe 


Faulting application name: Rim.Desktop.exe, version:, time stamp: 0x4c58acef
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b21e
Exception code: 0xc0000374
Fault offset: 0x000c2913
Faulting process id: 0xda8
Faulting application start time: 0x01cb3e4ad1e7aa74
Faulting application path: C:\Program Files\Research In Motion\BlackBerry Desktop\Rim.Desktop.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 648dcedd-aa3f-11df-a95d-001c2593c0cd



New Contributor
Posts: 6
Registered: ‎08-13-2010
My Device: 8330
My Carrier: Sprint

Re: Desktop Manager 6.0 Crashing

By the way, it is totally unconscionable to expect end users to (1) delete all videos from the My Videos folder -- which every other application on their computer looks to for videos and (2) expect an end user to make a registry change. 


I have always supported BlackBerry - have had one for as long as I can remember, and my Curve 8330 has been my pal for as long as they've been shipping.


I am considering upgrading. At this point, it appears that BlackBerry will not get any consideration from me. The way this problem is being handled is just unbelievable to me that a large organization can take such a callous point of view with their customers.


As part of my job duties, I need the BlackBerry sync to work everyday and seemlessly as I manage a large project with lots of scheduled meetings with a number of vendors, customer contacts, etc. that I was updating to my phone daily. Assuming this sync issue is not working within a week from now, I have no choice but to go buy a new phone and it won't be a BlackBerry.