Special Aircraft Service

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1] 2   Go Down

Author Topic: CTD caused by JVM.DLL  (Read 953 times)

0 Members and 1 Guest are viewing this topic.

DougW60

  • member
  • Offline Offline
  • Posts: 212
CTD caused by JVM.DLL
« on: August 19, 2019, 08:08:28 PM »

Request assistance with this one please.  I am experiencing CTD after the opening screen appearing for a split second. No eventlog or logfile files are being created.

Inspected Windows Event Viewer and the following is listed:

Faulting application name: il2fb.exe, version: 5.0.0.2, time stamp: 0x44fe754b
Faulting module name: jvm.dll, version: 0.0.0.0, time stamp: 0x3af53001
Exception code: 0xc0000005
Fault offset: 0x000b08b0
Faulting process id: 0x320c
Faulting application start time: 0x01d556e55f1871a6
Faulting application path: K:\05 - BAT updated version of CUP\BATil2fb.exe
Faulting module path: K:\05 - BAT updated version of CUP\bin\hotspot\jvm.

I have the following IL-2 version 4.12 games:

BAT - through BAT 3.7 Le Grand Cirque
HSFX 7.03
IL-2 ver. 4.13.4
IL-2 VPMod
Clean Il-2 ver. 4.12

I have attempted to open each version but had the same CTD in the same fashion as described above. Each opening screen opens for a split second, then disappears, then the loading process stops.  Each has the same jvm.dll error listed in Windows Event Viewer.

Each game uses jvm.dll dated: 8/26/2002 4:44PM; size 748 KB

Current jvm.dll listed C:\Program Files (x86)\Java\jre1.8.0_221\bin; date installed 7/19/19; size 3,802 KB.
C:\Program Files (x86)\Java\jre1.8.0_212\bin; date installed 4/22/19; size 3,803 KB.

I have not flown for a couple of months, since before the last Windows 10 update.  The only changes I made was installing Windows 10 updates and installation of BAT 3.7. And since each version of the game is having the same error, it must be with Windows.

An interesting note: when using Il-2 Selector; the selector will open, I can change / modify the settings as normal, but when I select  START IL-2 now!, the game will CTD as described above.

Current version of Windows is Windows 10 Home; Version 1903; 64-bit (10.0, Build 18362) installed on 6/23/2019.

I just checked for any windows updates hoping that there was something there that may rectify this problem, but according to window update, I am up to date.

I'm operating a 64 bit system but the game being 32 bit, do I look at downloading and installing the latest 64 bit and 32 bit versions of jvm.dll?

Before I attempt to royally screw up the operating system by manually attempting to download the most current jvm.dll files, I request advice regarding this problem.

thank you
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 18974
  • Failure is not an option.
    • What goes around comes around, you'll see
Re: CTD caused by JVM.DLL
« Reply #1 on: August 20, 2019, 12:39:08 AM »

Hi Doug,

Please use the Selector's Startup Debugger functionality in order to get log data of your early stage CTD.

]cheers[
Mike
Logged
People love using Strategy as a disguise for Non-Action.
In loving memory of times when I cared.

DougW60

  • member
  • Offline Offline
  • Posts: 212
Re: CTD caused by JVM.DLL
« Reply #2 on: August 20, 2019, 10:31:37 AM »

thank you SAS; my initlog.txt

Code: [Select]
2019-08-20 12:23:28:974 (dinput.dll) : JVM Parameters injector activated
2019-08-20 12:23:28:975 (dinput.dll) : Applying JVM Memory Settings from IL-2 Selector...
2019-08-20 12:23:28:975 (dinput.dll) : Added JVM Option: -Xms444M
2019-08-20 12:23:28:975 (dinput.dll) : Added JVM Option: -Xmx444M
2019-08-20 12:23:28:975 (dinput.dll) : Added JVM Option: -Xss4096K
2019-08-20 12:23:28:976 (dinput.dll) : Added JVM Option: -XX:PermSize=64M
2019-08-20 12:23:28:976 (dinput.dll) : Added JVM Option: -XX:MaxPermSize=64M
2019-08-20 12:23:28:976 (dinput.dll) : Checking mandatory JVM Options...
2019-08-20 12:23:28:976 (dinput.dll) : Added JVM Option: -Djava.class.path=.
2019-08-20 12:23:28:976 (dinput.dll) : Added JVM Option: -Xverify:none
2019-08-20 12:23:28:976 (dinput.dll) : Added JVM Option: -Xcomp
2019-08-20 12:23:28:977 (dinput.dll) : IL-2 Process ID = 00002DB8
2019-08-20 12:23:28:977 (dinput.dll) : Starting Watchdog at K:\05 - BAT updated version of CUP\bin\selector\basefiles\IL-2 Watchdog.exe 1
2019-08-20 12:23:32:512 (dinput.dll) : Watchdog process started.
2019-08-20 12:23:32:512 (dinput.dll) : Starting Pipe Logger at K:\05 - BAT updated version of CUP\bin\selector\basefiles\PipeLogger.exe
2019-08-20 12:23:32:547 (dinput.dll) : PipeLogger process started.
2019-08-20 12:23:32:587 (PipeLogger) : Starting
2019-08-20 12:23:32:590 (PipeLogger) : PipeLogger Process ID: 00000B1C; Parent (IL-2) Process ID: 00002DB8
2019-08-20 12:23:32:591 (PipeLogger) : Listener thread awaiting client connection on \\.\pipe\SAS_PIPE_LOGGER
2019-08-20 12:23:32:636 (dinput.dll) : Hooked "SAS_CreateJavaVM" function activated
2019-08-20 12:23:32:636 (dinput.dll) : OpenGL Mode detected, checking IL-2 Graphics Extender Availability...
2019-08-20 12:23:32:636 (dinput.dll) : Trying K:\05 - BAT updated version of CUP\il2ge.dll
2019-08-20 12:23:32:637 (dinput.dll) : Trying K:\05 - BAT updated version of CUP\il2ge\lib\il2ge.dll
2019-08-20 12:23:32:637 (dinput.dll) : Trying K:\05 - BAT updated version of CUP\bin\selector\basefiles\il2ge.dll
2019-08-20 12:23:32:637 (dinput.dll) : IL-2 Graphics Extender not available.
2019-08-20 12:23:32:638 (dinput.dll) : Injecting JVM Parameters
2019-08-20 12:23:32:683   (watchdog) : IL-2 Parent Process Handle = 0000018C, ID=00002DB8
2019-08-20 12:23:32:683   (watchdog) : IL-2 Watchdog started.
2019-08-20 12:23:32:683   (watchdog) : Splash Screen Mode = 1
2019-08-20 12:23:32:685   (watchdog) : Message Window Created.
2019-08-20 12:23:32:787   (watchdog) : Splash Screen Created.
2019-08-20 12:23:33:461 (dinput.dll) : JVM Parameters injector deactivated
2019-08-20 12:23:33:464 (PipeLogger) : il2fb.exe Termination detected, terminating Pipe Logger.
2019-08-20 12:23:33:464 (PipeLogger) : All Writers Threads finished, exiting.
Logged

DougW60

  • member
  • Offline Offline
  • Posts: 212
Re: CTD caused by JVM.DLL
« Reply #3 on: August 20, 2019, 10:34:52 AM »

Part 2 of response: created the startuplog.txt, rebooted the system, attempted to run the game with same results.  The game did create entries in the initlog.txt file (above) but the startuplog.txt file remained blank - no entries.

Also, console.exe, when doubled clicked, will open the cmd window but only long enough to see it.  It disappears immediately.

error recorded in event viewer:

Code: [Select]
Faulting application name: console.exe, version: 5.0.0.3, time stamp: 0x44fe754b
Faulting module name: jvm.dll, version: 0.0.0.0, time stamp: 0x3af53001
Exception code: 0xc0000005
Fault offset: 0x000b08b0
Faulting process id: 0x1010
Faulting application start time: 0x01d55775daad725b
Faulting application path: K:\05 - BAT updated version of CUP\console.exe
Faulting module path: K:\05 - BAT updated version of CUP\bin\hotspot\jvm.dll
Report Id: 1088bae8-77cb-46a8-9b4d-da27c8dc6969
Faulting package full name:
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 18974
  • Failure is not an option.
    • What goes around comes around, you'll see
Re: CTD caused by JVM.DLL
« Reply #4 on: August 20, 2019, 10:45:05 AM »

created the startuplog.txt
Nice. Would you mind showing it to us?
Because that's what the Startup Debugger is all about.
The other logs you've shown unfortunately don't contribute to solving this issue.

]cheers[
Mike
Logged
People love using Strategy as a disguise for Non-Action.
In loving memory of times when I cared.

DougW60

  • member
  • Offline Offline
  • Posts: 212
Re: CTD caused by JVM.DLL
« Reply #5 on: August 20, 2019, 02:27:52 PM »

Mike, the startuplog.txt file is completely blank, nothing is on it, and is 0 kb in size.
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 18974
  • Failure is not an option.
    • What goes around comes around, you'll see
Re: CTD caused by JVM.DLL
« Reply #6 on: August 20, 2019, 02:50:54 PM »

Time for using a restore point then maybe.
I'd rule out the Windows Update as many of us are up to date with Windows 10 / 64 Bit and have no such issues.

]cheers[
Mike
Logged
People love using Strategy as a disguise for Non-Action.
In loving memory of times when I cared.

DougW60

  • member
  • Offline Offline
  • Posts: 212
Re: CTD caused by JVM.DLL
« Reply #7 on: August 20, 2019, 03:07:12 PM »

Yes I was thinking of that if I have one from that far back.  It is interesting that the jvm.dll file is unique to Il-2 as I outlined above. All versions/modded Il-2s games and a clean / unmodded version of Il-2 all have the same CTD.  All other programs and games are opening without any problems.
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 18974
  • Failure is not an option.
    • What goes around comes around, you'll see
Re: CTD caused by JVM.DLL
« Reply #8 on: August 21, 2019, 09:56:41 AM »

The JVM shipped with IL-2 is Java 1.3.1 build 24.
It's unique in that you won't find that version "in the wild" anymore.
The closest you can get publically available today is Java 1.3.1 build 28 for windows, or build 24 for Solaris: https://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase13-419413.html

]cheers[
Mike
Logged
People love using Strategy as a disguise for Non-Action.
In loving memory of times when I cared.

DougW60

  • member
  • Offline Offline
  • Posts: 212
Re: CTD caused by JVM.DLL
« Reply #9 on: August 22, 2019, 09:43:17 AM »

Thanks for the assistance Mike, but sadly, we are experiencing the same problem. I'm not sure how to proceed with this one as the problem is unique to Il-2 1946.  Il-2 BOX and all other games / programs run just fine. I will continue to try to determine what is the problem but hopefully the next Window update will correct it.
Logged

SAS~Storebror

  • Editor
  • member
  • Offline Offline
  • Posts: 18974
  • Failure is not an option.
    • What goes around comes around, you'll see
Re: CTD caused by JVM.DLL
« Reply #10 on: August 22, 2019, 10:41:01 AM »

Better don't concentrate on JVM.dll - the file is fine, believe me.

The error log...
Code: [Select]
Faulting application name: il2fb.exe, version: 5.0.0.2, time stamp: 0x44fe754b
Faulting module name: jvm.dll, version: 0.0.0.0, time stamp: 0x3af53001
...only means that it's IL-2 that crashed (il2fb.exe) and this happened in the module ( => dll) jvm.dll, which comes natural considering that IL-2 runs in just that Java virtual machine.
Any native crash has such pattern if the Java Virtual Machine doesn't manage to do a clean exit.

What's probably more interesting is this:
Code: [Select]
Exception code: 0xc0000005
Fault offset: 0x000b08b0

0xc0000005 is an access violation and offset 0x000b08b0 is inside the Java method "GetField".

First steps to try would be to reinstall the graphics driver and to make sure that DEP (Data Execution Prevention) is turned on for essentials Windows Programs and Services only.

]cheers[
Mike
Logged
People love using Strategy as a disguise for Non-Action.
In loving memory of times when I cared.

DougW60

  • member
  • Offline Offline
  • Posts: 212
Re: CTD caused by JVM.DLL
« Reply #11 on: August 22, 2019, 10:51:13 AM »

Roger, will update GPU driver and check DEP, will get back with you in a few hours. Mrs. has chores for me to do, haha.
Logged
Pages: [1] 2   Go Up
 

Page created in 0.015 seconds with 27 queries.