Recognize an Error Code on Blackberry

Below an information to recognize an Error Code on blackberry

Code 1xx

• 101: Internal JVM Error
• 102: Invalid code in file system. The .cod files in the handheld have been checked for modification and it has been determined that there is a problem with one or more .cod files
• 103: The starting address for the boot .cod file cannot be found. This might mean that a boot .cod file has not been installed on the handheld, or that its format is invalid or corrupt.
• 104: An uncaught Java exception was thrown in the Java code and diagnosed by the JVM. Execution can be continued or the handheld can be attached to a debugger on a desktop through a serial or USB cable. The event log should contain the traceback of the thrown exception.
• 105: An OS file system API returned an error status for a certain operation. This can indicate a corrupt file system or an error in the JVM.
• 106: An error has been detected in the graphics system of the handheld.
• 107/108: Internal JVM error.
• 109: Internal OS error.
• 110: Non-idle event downtime error. A problem has been detected in the accumulation of JVM down time that represents how long the JVM has been idle. This indicates an error in either the OS code or the JVM code. 

Code 2xx

• 200: Application manager threw an uncaught exception. The application manager event thread threw an uncaught exception and so cannot continue running.
• 201: Initialization of the cryptographic system failed and the handheld cannot continue to operate.
• 202: An attack on the key store has been detected, and the handheld cannot continue to operate.
• 203: The application manager console process, usually the Home screen ribbon, has failed, like due to an uncaught exception.

Code 3xx

• 310-314: Hardware failure
  Perform a hard reset on the handheld: Shut down, remove the battery wait a few second... replace battery then see when happens when it starts OR Run Application Loader to reload the operating system and applications onto the handheld.
  Note: If these tasks do not resolve the error, contact your service provider.
• 320-325: AMX failure
  Run Application Loader to reload the operating system and applications onto the handheld.
• 330-339: Application tasks failure
  Run Application Loader to reload the operating system and applications onto the handheld.
• 340-343: Memory failure
  You receive one the following error messages on your handheld:
  Cause
  Memory failure.
  
  
  Resolution
  Reduce the number of calendar appointments synchronized to your handheld.
  1. In BlackBerry? Desktop Manager, double-click the Intellisync icon.
     Click Configure PIM. The Handheld Configuration window appears.
  2. In the Handheld Applications list, select Calendar.
  3. Click Configure > Advanced Settings. The Advanced Settings for Calendar window appears.
  4. In the Date Range tab, perform one of the following tasks to reduce the number of calendar appointments synchronized to your handheld:
     If you click the Transfer only Future items option, only future calendar appointments will be synchronzied to your handheld.
     If you click the Transfer items within a range of Days option and enter date range in the fields provided, only the calendar appointments that scheduled within the date range will be synchronized to your handheld.
  5. Click OK to save your changes and close the window.
  6. In the Handheld Configuration window, ensure that the check box beside the Calendar application is selected, then click OK.
  7. In the Intellisync window, ensure that the Synchronize PIM check box is selected, then click Synchronize Now. The number of calendar entries on your handheld is reduced.
     If you still receive the error
     
     
     Run Application Loader to reload the operating system and applications onto your handheld.
• 350-359: Software application failure
  You receive one of the following error messages on your handheld:
  Device Error 350, 352, 353, 354, 355, 356, 357, 358, 359
  Cause
  Software application failure.
  
  
  Resolution
  Perform a hard reset on the handheld OR Run Application Loader to reload the operating system and applications onto your handheld. In the Application Loader Wizard window, do not select any third party applications. In the Advanced options, select the Erase all currently installed applications check box
• 360-363: Flash memory failure
  Run Application Loader to reload the operating system and applications onto the handheld.
  
  
• 365-368: This one is often followed by 
  Contact your service provider.

Code 4xx

• 400-564: Breaking lines, sistem data link lost, possibility of bad sector in hard drive
• 410: Radio Failure
• 411: Battery Error, Replace Internal or External Battery module
• 499: Software problems, continue to handheld device OS installation or application updates via Apploader 

Code 5xx

• 501: Internal error.
• 502: All processes exited. The last Java process has terminated, and there is nothing left to execute.
• 503-505: Internal error.
• 506: An uncaught Java exception was thrown in the initial VM Java thread thus killing the only live thread in the system. The event log contains the traceback for the exception.
• 507: A dependency on a .cod file could not be satisfied due to a missing .cod file. Load the missing .cod file onto the handheld.
  You receive one of the following errors on your BlackBerry device while using Application Loader to install device software. 
  
  
  Device Error 505
  Device Error 507
  Both errors indicate that no applications are loaded on the BlackBerry device.
  Cause I
  During the Application Loader process, the existing applications on the BlackBerry device were erased, but Application Loader failed to load the new applications.
  Resolution
  Complete the following steps:
  1. Verify that device software is installed on your computer.
  2. If your BlackBerry device is connected to a laptop in a docking station, disconnect the laptop from the docking station and connect the device directly to the laptop.
  3. If a third-party program (e.g. virus scanner) is using the same COM port as BlackBerry Desktop Manager, close the third-party application to free the COM port.
  4. If you are using a USB adapter to connect your BlackBerry device to a serial port on your computer, temporarily connect your device to a computer with a USB port.
  5. In Desktop Manager, double-click Application Loader.
  6. Use Application Loader to install the device software.
  Cause II
  You erased all the data and applications on your BlackBerry device by typing an incorrect password ten times in Application Loader.
  Resolution
  Complete the following steps:
  1. In Desktop Manager, double-click Application Loader.
  2. Use Application Loader to install the device software
• 508: Invalid object. A problem has been detected with a debugger command to the VM.
• 516: Error occurred during garbage collection, which might indicate a corrupted file system.
• 510: All threads are waiting on objects, which results in a deadlock. The system cannot recover from this state since no thread can release a lock.
• 511: A problem has occurred during debugging.
• 515: The reachable objects form a group that cannot be represented properly by the VM because there are too many objects or the total size of the objects is too large.
• 516: When committing a persistent object, the VM found that the persistent store id counter has reached its limit. The object was not committed.
• 517: An inconsistency has been detected in the VM persistent object store.
• 518-520: Internal error.
• 521: Indicates that Object.wait() has been executed by a thread that holds a lock on another object; occurs only in simulator if the JvmDebugWaits application switch.
• 522: A thread has acquired two locks on objects in an order that doesn’t match the order that previous locks for the two types were acquired, which indicates a future potential deadlock situation; reported only in the simulator when the JvmDebugLocks application switch is set.
• 523: A critical Java process has died and the device cannot continue to operate normally.
• 524: An object has been marked as recovered by the Low Memory Manager but it was not freed during a garbage collection. This is only checked in the simulator under the control of the JvmDebugLMM application switch.
• 525: Bad persistent object. An auto-commit operation during a garbage collection has detected a non-persistent object reachable from the persistent store root. The type of the object has been output into the event log.
• 526: The class definition for java.lang.Object cannot be found.
• 527: The class definition for java.lang.String cannot be found.
• 528: The file system is corrupted. Data on the handheld is unrecoverable.
• 529: The file system is corrupted. An attempt is going to be made to recover data, but some data might be lost.
• 530: Internal JVM error.
• 531: Flash memory has been exhausted.
• 532: A JVM assertion has been violated. This error can occur only in the simulator, not on an actual handheld. 

Source : repo.antihackerlink.or.id