During jvm startup, the previous startup project failed and the device was reset. This error indicates that the jvm found that the flag bit of "startup in progress" has been set at startup, and the current screen message is: intentionally stop the infinite loop of "system continues to reset" and correct the incorrect startup operation of the current system.
Invalid code in 102 file system.
Invalid code found in the file system. This problem is in some. When the handheld device's system detects. Cod file. He may point out that there is an error in the generation process, that is, there is a problematic signature in the cod file. If some users operate the device to cause this problem, the code of the file system is destroyed and the reset cycle will be continuous. The only recovery method is to clean the device and restore the new system.
103 start address not found.
The startup address and the startup cod file used to start the system could not be found. This error indicates that the cod file used to boot the system is not installed on the device, or the file format is incorrect.
104 not captured: < Java-type-name >;
Unexpected: jvm with java module name diagnosed unexpected java code exception, and the program can continue to execute, or the handheld device can install a program debugger with desktop manager and USB cable to view these error messages. The event log should contain exception information.
105 example, DbRecSize
For example, the DbRecSize file system API returns an error status code for a specific operation, which may indicate that there is an invalid or wrong file system on the jvm.
106 graphics system error
Graphics system error, an error occurred in the graphics system of the device and was detected.
107 operator new () is called.
In the jvm, the new () operation calls back a c++ class, and the function code does not inherit the VMRamObject object correctly, so it needs to inherit the new operator correctly. Select the current (-reset) BUGDISP.
108 operator delete () is called.
In the jvm, operate delete.
() Call back a c++ class. The function code does not inherit the VMRamObject correctly, so it needs to inherit the new operator correctly. Select the current (-reset) BUGDISP.
109 PriorityMessageCount error: < priority count >
Error in calculating priority statistics:
< priority calculation >; RimPriorityMessageCount returns a negative value when it should always be greater than or equal to zero. This shows that this is a system error.
Extract the current (-reset) BUGDISP and view the system event log.
1 10 non-idle event downtime error:< downtime & gt& lt idle downtime & gt
Non-idle state time event error:; < idle time > an error was detected in the statistics of jvm idle time, which means that JVM has been idle for a long time.
This usually indicates an error in the handheld device or JVM. If the counter is idle for more than 400 days, it may also appear.
1 1 1 font engine error.
Font Engine Error: A font engine error of the system device was detected. Please check the current error display and event log.
1 12 Java native assertion failed.
Java localization instance failed. Localization code error detected. Please check the current error display and event log.
The application manager threw an unexpected thread exception, and the program could not continue execution. Reset the handheld device.
20 1 failed to encrypt initialization code
Failed to encrypt initialization code. Encryption module initialization failed. The handheld device cannot continue.
202 A crack attack has been detected in the keystore, and the program cannot continue.
203 console process died
The console process died. The application manager console process has been paused. This looks like an exception when executing a program.
204 Persistent content exception
The local memory content is abnormal. An application tried to submit a text object to local memory. This only happens when the content protection service is turned on, and then a process tries to save some text label data in local memory. If the exception is not handled correctly, it may indicate that the local memory is in a damaged state. We need to reset and roll back to the last normal submission point. Description: This jvm exception reflects an error in Java code, and the Jvm only diagnoses this error. If this is not a jvm problem, then the event log will contain enough Java code error information.
300-303 Poor load
Invalid load. Continue. Run the application loader and reload the operating system and applications on the handheld device.
3 10-3 14 hardware failure
Hardware error. Try resetting the handheld device: turn it off, remove the battery, wait a while, change the battery to see what happens when the device restarts, or run the application loader to reload the operating system and applications on the handheld device. Note: If these methods cannot solve this error, please contact your service provider.
320-325 AMX fault
AMX failed. Please run the application loader to reload the operating system and applications on the handheld device.
330-339 Application task failed.
The application task failed. Please run the application loader to reload the operating system and applications on the handheld device.
340-343 Memory Failure
Memory error. You may see the handheld device reporting the following error code:
Device error 340
Device error 34 1
Device error 342
Device error 343
Reason: Memory error
Solution: Reduce the number of calendar appointments synchronized in the mobile phone.
1. In the Desktop Manager, double-click the Intellisync icon, and then click the Configure PIM button.
2. In the device application list, select the calendar.
3. Click Configure and Advanced Settings.
4. On the Data Area Options page, complete a task to reduce the number of calendar appointments synchronized in your phone. If you select the "Schedule Best Future Item Selection" option, the handheld device will only synchronize future calendar appointments. If you click and enter the date range scheduling item option, the handheld device will only synchronize calendar scheduling appointments within the selected date range.
5. Click OK to save the changes and close the window.
6. In the configuration window, make sure that the check box of the calendar program is selected, and then click OK.
7. In the Intellisync window, confirm that the Synchronize PIM check box is selected, and then click Synchronize Now. The device will reduce at least one calendar appointment item.
If you still see this error message. Please run the application loader to reload the operating system and applications on the handheld device.
350-359 Software Application Failure
Application software error, you may see the handheld device report the following error code:
Device error 350
Device error 352
Device error 353
Device error 354
Device error 355
Device error 356
Device error 357
Device error 358
Device error 359
Cause: Application software error.
Solution: Try to hard reset the handheld device, run the application loader, and reload the operating system and applications for the handheld device. In the wizard window, do not select any third-party applications. In Advanced Options, select the Clear all currently installed applications check box.
360-363 Flash Memory Failure
Flash memory error. Try to hard reset the handheld device and run the application loader to reload the operating system and applications of the handheld device.
365-368 This is often followed by "OHHH @%! ! "
This is a frequent "OHHH @%! ! "An error occurred, please contact your service provider.
395 Unclassified error code
Unclassified error code
Reason:
The device 395 code represents an unclassified error code. Third-party applications installed on handheld devices may have caused this error.
Solution 1
Try resetting the handheld device: turn it off, take out the battery, wait for a while, and then replace the battery to see what happens when the device restarts.
Solution 2
Clear and reload the data of the handheld device.
1. In BlackBerry Desktop Manager, use backup and recovery tools to create data backup files of mobile phones. For more information, please refer to "Handheld Device Backup Information" in the online help of Desktop Manager. Warning: The following steps may erase the data of handheld devices.
2. Open the Desktop Manager and double-click the application loader icon.
3. Click Next to open the application selection window.
4. Confirm that the necessary applications have been selected, and then click Next.
5. Click "Advanced"
6. Select Clear all application data and currently installed applications, and then click Next.
7. Click Finish. When the operating system and application programs of the handheld device are reloaded, the data of the handheld device is cleared,
8. Use backup and recovery tools to restore the backed-up data files to handheld devices. For more information, please refer to "Handheld Device Recovery Information" in the online help of Desktop Manager.
Page 400-564 error
Page file is invalid. Run the application loader to reload the operating system and applications to the handheld device.
4 10 radio failure
Radio service failed.
Try to hard reset the handheld device and run the application loader to reload the operating system and applications of the handheld device. Note: If this does not resolve this error, please contact your service provider.
Error: 4 1 1= battery module problem, replace the battery.
Error: 499= Software problem, restart the handheld device.
50 1 virtual machine thread switching
Thread has been switched, internal error, this is an error return message used internally by VM. It should not be reported as a device error code.
502 Virtual Machine _ Process _ Death
The process is dead (suspended), all processes quit, the last java process has been terminated, and no programs can be executed.
503 Virtual Machine _ Thread _ Death
Thread dead (suspended), internal error, which is an error return message used internally by VM. It should not be reported as a device error code.
504 virtual machine thread switching
Thread has been switched, internal error, this is an error return message used internally by VM. It should not be reported as a device error code.
505 virtual machine bad code 5 I
Invalid code: invalid byte code, error in Jit compiler.
506 uncaught exception
Unknown exception: an unknown java exception was thrown when initializing the java thread of VM, which caused the system to end the only active thread. The event log contains abnormal rollback records!
507 dissatisfied links
There are inappropriate file links in the cod file, and the cod file may be lost.
Device error 5059
Device error 5077
The handheld device does not have any applications installed.
Reason 1
When the application loader works, the existing applications on the BlackBerry device have been cleared, but the application loader failed to load new applications.
solution
1. Make sure that the device software is installed correctly on your computer.
2. Please connect your BlackBerry device directly to the USB interface of your laptop.
3. If a third-party program (such as antivirus software) uses the same COM port as the desktop manager handheld device, please close the third-party program to release the COM port.
4. If you use USB cable to link the BlackBerry device to the serial port of the computer, please use USB port to directly link bb.
5. In the Desktop Manager, double-click the application loader.
6. Install the equipment system software with the application loader.
Reason 2
If you enter the password incorrectly for more than 10 times, all data and programs on your bb will be erased.
solve
1. In the Desktop Manager, double-click the application loader.
2. Install the equipment system software with the application loader.
508 Invalid object
Invalid object, when the vm executes the debugger command, it detects a problem: invalid object.
509 virtual machine _ PPO _ infinite loop
An infinite loop was found in the PPO stage of junk mobile phones. In the PPO stage of GC, the maximum total number of iterations must be the maximum number of file handles in the system. This error indicates that the total number of iterations has exceeded this number, so the PPO loop is defective or the file system is incorrect. You can extract a special integer value 16 from the error string, which is the id value of the currently detected infinite loop record.
5 10 deadlock
Deadlock, all thread objects are waiting, but one thread has been deadlocked when returning the result. The system cannot recover from this deadlock because all threads are locked.
5 1 1 debug connection is dead
Debugger connection has been deadlocked. When debugging, sending vm problems or incorrect debugging commands to the vm may cause this problem.
5 12 GC aborted
GC (garbage collection) has been terminated, and the space garbage collector program is forcibly terminated by user operation events, such as squeezing the keyboard or moving the wheel.
5 13 & lt； Clinit & gt needs to run.
& ltclinit & gt needs to run the class first. This class name
5 14 & lt； Init & gt needs running.
& ltinit & gt needs to run. A new class instance must be initialized and allocated memory space through the default constructor before it can be used.
The 5 15 object group is too large.
The object group is too large. The jvm cannot get the object group correctly, either because there are too many objects or because the object group is too large.
5 16 Permanent id has been exhausted.
Ids firmware device has failed. When accessing a firmware object, jvm finds that the local memory id counter has reached the maximum value. The object could not be submitted and a fatal error was reported. This error may never occur unless the equipment has been used extensively for several years.
5 17 file system is corrupted.
The file system is incorrect. An incorrect (contradictory) allocation address was detected in jvm local memory.
5 18 unexpected longjmp5
Unexpected longjmp instruction. The garbage collector instruction ended the longjmp instruction. This may indicate that the marking phase was interrupted by the error when the instruction did not interrupt the operation to be completed. This should never happen, because these operations will be performed when the device is not idle, and at the same time,
The work of the garbage collector will be interrupted only when the device is idle.
5 19 internal error
Internal server error. The Jvm system is missing or disabled.
520 internal return
An error is returned internally, indicating the internal state returned by the java method needs to be executed.
52 1 dangerous waiting object
A dangerous waiting object. The thread is locked by another object while executing the Wait () method. This will only be checked when controlling the debugging application switching in the jvm-based simulator.
522 interlaced synchronization
Interactive synchronization error, the thread of the object obtained two locks through one command, but before the thread was locked, the two types of locks obtained did not match the command. This means that a potential deadlock situation is reported. This will only be checked when controlling the debugging application switching in the jvm-based simulator.
523 system process death
System process is dead (suspended). A fatal java program error caused the system to terminate and the equipment could not continue to operate normally. Please reset and restart the handheld device.
524 LMM error
LMM error. An object was marked for recycling by the low memory manager, but it was not released correctly during memory garbage collection. This will only be checked when controlling the debugging application switching in the jvm-based simulator.
525 wrong persistent object
Corrupt local memory object. During garbage collection, it was detected that an automatic operation was submitted to a non-persistent local object from the local memory root directory, and this type of object has been recorded in the event log.
526 cannot find java.lang.Object
The class definition java.lang.Object object cannot be found.
527 cannot find java.lang.String
The class definition java.lang.String object cannot be found.
528–529 Corrupted file system
Wrong file system. Unrecoverable error, if you continue to execute, all data will be lost. This error message contains the numeric code of the internal "Error Reason". If a cod file is deleted, this error will not be diagnosed because of JVM.
The objects defined in the COD file (deleted) must be deleted, so this error will not occur when the equipment is running normally.
Common error codes of jvm compiler
1. The root array reference is not a valid array reference.
2. The root array type is not object []
3. The size of the root array is less than 1, such as Object[0].
4. The memory in root [0] is not a valid reference.
5. The root [0] type is not a long hash table.
6. The array header contains an invalid reference.
7. There is an invalid reference in the project of local object [].
8. The object type refers to an unknown cod file.
9. In memory, the size of the type description file of the object in the cod file does not match.
Invalid type field reference in 10. object.
The reference type field in the 1 1. object is linked to an invalid type of another object.
12. Missing local object [] in descriptor!
13. The object is not marked as a persistent table in local memory.
14. The root array is divided, and the divided segment is invalid.
530 Virtual Machine _ Prevention _ Garbage Collection _ Overflow
_preventGC overflow. The fixed value of the original object will be protected from being taken away by the garbage collector. This mistake shows that,
This value may exceed the fixed limit of protected objects. If the device is reset or a thread rollback event is logged, the actual value can be extracted.
53 1 Flash is exhausted
Memory is used up. The jvm can't tolerate some operations beyond memory space. This error will be reported if the jvm cannot complete the allocation of the required memory space.
532 Virtual machine assertion failed.
Maintenance task failed. Usually this jvm error will not be reported when the equipment is not started to allow maintenance. The simulator may report this error when debugging, indicating that a vm maintenance operation violates the contract. You can try to enter BKPT to activate the debugger, and then dump this local stack and give it to the vm group.
533 virtual machine running method
& lt method & gt this method needs to be called by using the international standard ECMAScript script to run.
534 Quick reset of virtual machine is disabled.
Fast reset is prohibited. This code is usually used internally to indicate that the quick reset function is invalid. Always use the code developed by the platform.
535 Virtual Machine _ Unused _535
Unused virtual machine error. Error 535 means memory overflow. One reason for the 535 error may be that the running thread overflowed, causing the virtual memory thread scheduler to terminate. This error is known to occur during starting the queue or when the main event thread stops.
Solution:
First, hard boot the handheld device. If you can't solve the problem, please get and install the latest version of BlackBerry handheld ROM software from your operator, and then run the application loader in the desktop manager to update the handheld device. Or delete some ringtones and theme files to free up storage space.
536 Virtual Machine Quick Reset Error Instance
Vm fast reset instance check failed. Internally, it is usually represented by the following code: the vm structure skipped the wrong address space, or the vm has been corrupted.
537 Virtual Machine Quickly Resets Bad Heap
Quick reset error, heap check failed. Internally, this code is used to indicate that the vm heap or pointer heap is invalid.
538 Virtual Machine Quickly Resets Bad IRAM
Quick reset of IRAM damage, IRAM check failed. This code used to indicate that an invalid vm data structure (thread+local stack) or a pointer registered in IRAM was detected in the IRAM check of vm.
539 Virtual Machine Quick Reset Non-Idle
The quick reset state is not idle. Internally, this code is used to indicate that the vm is busy when the reset occurs, and problems like this will prevent the quick reset from continuing.
540 Virtual Machine Quick Reset Multiple Reset
Multiple reset errors. Internal used to be represented by this code: the last reset time was less than the minimum reset interval. Because it is forbidden to reset many times in a short time, this can prevent the infinite loop of quick reset.
54 1 virtual machine heap compact infinite loop
A dead cycle was detected in heap compression. Vm detected a problem in the memory heap, indicating that the memory block is invalid. When the memory heap is compressed, this problem can be detected if it is confirmed that there may be an infinite loop. When the device contains this error condition, bugdisp records and event logs can quickly extract this error information. If possible, the memory image will be saved.
542 temporary memory leak
Instant memory leak. The Jvm has detected that some memory has not been released, which indicates that a memory leak has occurred. I hope to find out the reason as soon as possible and avoid this situation.
543 Virtual machine file system mismatch
File system mismatch. An incompatible java file system is installed. The Jvm has detected that the existing system code is different from the system code commonly used to create java file systems. This means that java native methods may not compile and link correctly, so the integrity of the system is uncertain. The system cannot use the virtual machine.
The DLFX and DLPS commands will resume, and the errors in the local memory cannot be deleted or fixed. This may erase all data and firmware content. Please re-link the compiled file system to match the new system code. The recovery sequence is very
Important: 1. To delete an application, press 2. To delete the contents of the local memory, press 3. Reset the device.
544 Virtual Machine _ Partition _ Map _ Overflow
A module references more than 255 other modules. Vm detected that one module tried to reference more than 255 other modules. When an error is detected, the file system should get it immediately.
545 The virtual machine is incompatible with the file system.
The Vm detected an incompatible or invalid file system. When an error is detected, the file system should get it immediately.
546 Virtual Machine _ Unused _546
Not used (internal error code of). Vm detected that the memory image in the file system is invalid (CRC redundancy check failed), so it is better to reset the machine than to copy the wrong memory.
content
547 Virtual Machine _ Unused _547
Not used (internal error code of). Virtual machine error
548 Virtual Machine _ Unused _548
Not used (internal error code of). Virtual machine error
549 Virtual Machine _ Unused _549
Not used (internal error code of). Virtual machine error