Urgent problem: JRE Crashes with Access violation (c0000005)

Question

I have a problem where the JRE crashes with an Access violation (c0000005) at address (6d4218ce).
The JVM is:
java version "1.3.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)The application is swing based, and I have my suspicions that the problem occurs when exec'ing (Runtime.exec()) a script file (deletes data files and FTP's data files around an internal network), but I cannot categorically prove it as yet.
The lack of a .map file does not help in analysing the Dr Watson log file. Does anyone know if a map file is available for 1.3.1?
I have tried to raise this as a bug but as we cannot reproduce it on demand, I cannot get Sun to look into it.
The Dr Watson log file shows:
State Dump for Thread Id 0x13e
eax=bf800000 ebx=0336b770 ecx=02b72168 edx=bf800008 esi=02b72168 edi=06ffd12c
eip=6d4218ce esp=08d0fdbc ebp=08d0fddc iopl=0         nv up ei ng nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000282
function: <nosymbols>
        6d4218b9 8d4df0           lea     ecx,[ebp-0x10]         ss:09c0e7e2=00000000
        6d4218bc e875000000       call    6d421936
        6d4218c1 5f               pop     edi
        6d4218c2 5e               pop     esi
        6d4218c3 c9               leave
        6d4218c4 c3               ret
        6d4218c5 56               push    esi
        6d4218c6 8bf1             mov     esi,ecx
        6d4218c8 8b5604           mov     edx,[esi+0x4]          ds:03a70b6e=????????
        6d4218cb 83c208           add     edx,0x8
FAULT ->6d4218ce 8b4210           mov     eax,[edx+0x10]         ds:c06fea0e=????????
        6d4218d1 85c0             test    eax,eax
        6d4218d3 7f25             jg      6d4218fa
        6d4218d5 7d1b             jge     6d4218f2
        6d4218d7 83c9ff           or      ecx,0xff
        6d4218da 6a04             push    0x4
        6d4218dc 2bc8             sub     ecx,eax
        6d4218de 8b4608           mov     eax,[esi+0x8]          ds:03a70b6e=????????
        6d4218e1 d3e0             shl     eax,cl
        6d4218e3 8b4a44           mov     ecx,[edx+0x44]         ds:c06fea0e=????????
        6d4218e6 8d440807         lea     eax,[eax+ecx+0x7]      ds:03a70b6f=????????
        6d4218ea 59               pop     ecx
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
08d0fddc 6d4710ee 0336b734 0336b734 6d4381b7 0336b734 <nosymbols>
State Dump for Thread Id 0x140
eax=06a82398 ebx=00000000 ecx=06ab34f0 edx=00000000 esi=0000017c edi=00000000
eip=77f682db esp=08d4fc24 ebp=08d4fc48 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000246
function: NtWaitForSingleObject
        77f682d0 b8c5000000       mov     eax,0xc5
        77f682d5 8d542404         lea     edx,[esp+0x4]          ss:09c4e62b=00000000
        77f682d9 cd2e             int     2e
        77f682db c20c00           ret     0xc
        77f682de 8bc0             mov     eax,eax
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
08d4fc48 77f04f37 0000017c ffffffff 00000000 6d466097 ntdll!NtWaitForSingleObject
08d4fc90 6d476550 00000000 00000000 00000001 00765d80 kernel32!WaitForSingleObject Any help would be much appreciated.
Regards,
Dave Jackson

Answer 1

Probably nothing to do with it but I had some dodgy memory, and windows would complain that there was an error to do with that exact memory location: c0000005