JVM Crash

Hi All,
The JVM is crashing giving the following error.
I have gone through the sites, everybody have mentioned the problem but no proper solution.
Can somebody guide me in this.

Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x80D8355
Function=JVM_RegisterUnsafeMethods+0x12A8
Library=D:\E(z)RF Application Suite\WebNMS\jre\bin\client\jvm.dll

Current Java thread:
at java.lang.Throwable.fillInStackTrace(Native Method)
- locked <0x1345b688> (a java.lang.NullPointerException)
at java.lang.Throwable.<init>(Unknown Source)
at java.lang.Exception.<init>(Unknown Source)
at java.lang.RuntimeException.<init>(Unknown Source)
at java.lang.NullPointerException.<init>(Unknown Source)
[error occured during error reporting]

PC configuration:
java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)

Windows Server 2003, service pack 2, 3.06 GHz processor speed and 4 GB RAM.

Thanks in advance.

Regards,
Satya

In general, a "EXCEPTION_ACCESS_VIOLATION" occurs in Windows when a program attempts to modify memory that it does not "own." Think of virtual memory as a stack of paper - your program requested several pages to use for variables, but then some part of the program tries to write to a piece of paper that belongs to, say, Firefox. Windows sees this, and kills the process before it can do so.

This can happen a lot in languages like C and C++ where you work with memory "pointers" a lot directly, in Java not so much. Were you doing running multi-threaded or fiddling with memory specifically? Wherever you're messing with memory, try to use Java's built-in variables and similar, that's why we're using a high-level language, so you don't have problems like this

Your JVM is an old patchlevel of an old JVM:

1.4.2 is two major versions ago, and within the 1.4.2 series, the patch levels went up to... 17? Something like that. So they released 9 patches to the JVM you're running. If you must run 1.4.2, you need to get a 1.4.2_17 JVM package. It may fix whatever bug you're seeing.

Joseph Macer wrote:In general, a "EXCEPTION_ACCESS_VIOLATION" occurs ...

Great explanation Joseph!

Glad to be helpful