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 3375 times)

0 Members and 1 Guest are viewing this topic.

DougW60

  • member
  • Offline Offline
  • Posts: 219
Re: CTD caused by JVM.DLL
« Reply #12 on: August 22, 2019, 02:12:36 PM »

Thank you very big Mike, the problem was indeed with the DEP (Data Execution Prevention) setting.  It was set for all programs and after changing it to "essentials Windows Programs and Services only," then rebooting, the games are starting.  We are back to flying.

Problem has been identified and solved.
Logged

SAS~Storebror

  • retired
  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 21635
  • Taking a timeout
    • STFU
Re: CTD caused by JVM.DLL
« Reply #13 on: August 22, 2019, 11:48:17 PM »

Fine, glad to hear that you got that issue sorted.
Welcome back in the skies of IL-2 1946 8)

]cheers[
Mike
Logged
You live, you learn, you love, you're dead.

Toobone

  • Mapper
  • member
  • Offline Offline
  • Posts: 491
Re: CTD caused by JVM.DLL
« Reply #14 on: October 17, 2019, 04:20:24 AM »

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

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.

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x7225721e
Function name=RegisterProcTableCallback
Library=C:\Windows\system32\ig75icd32.dll


Please, help me: Is this the same case or something else?
Logged

SAS~Storebror

  • retired
  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 21635
  • Taking a timeout
    • STFU
Re: CTD caused by JVM.DLL
« Reply #15 on: October 17, 2019, 04:35:56 AM »

That's not the same, you've got an OpenGL crash in your Intel HD graphics driver.
Note that IL-2 doesn't work (right/well) with Intel HD graphics in OpenGL mode.
Use DirectX instead.

]cheers[
Mike
Logged
You live, you learn, you love, you're dead.

Toobone

  • Mapper
  • member
  • Offline Offline
  • Posts: 491
Re: CTD caused by JVM.DLL
« Reply #16 on: October 17, 2019, 04:47:07 AM »

That's not the same, you've got an OpenGL crash in your Intel HD graphics driver.
Note that IL-2 doesn't work (right/well) with Intel HD graphics in OpenGL mode.
Use DirectX instead.

Thank you. With DX the same happens sometimes.
Logged

SAS~Storebror

  • retired
  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 21635
  • Taking a timeout
    • STFU
Re: CTD caused by JVM.DLL
« Reply #17 on: October 17, 2019, 05:39:34 AM »

It cannot be the same as the error message clearly is about OpenGL.
If you switch to DirectX, this definitely cannot happen.

]cheers[
Mike
Logged
You live, you learn, you love, you're dead.

Toobone

  • Mapper
  • member
  • Offline Offline
  • Posts: 491
Re: CTD caused by JVM.DLL
« Reply #18 on: October 17, 2019, 05:48:25 AM »

It cannot be the same as the error message clearly is about OpenGL.
If you switch to DirectX, this definitely cannot happen.

In DGenPack3.0 with DX+reShade2.0 ON  logs with this names hs_err_pidXXX sometimes happened too because of reShade maybe..
Logged

SAS~Storebror

  • retired
  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 21635
  • Taking a timeout
    • STFU
Re: CTD caused by JVM.DLL
« Reply #19 on: October 17, 2019, 05:51:03 AM »

Each JVM crash is supposed to create a corresponding hs_err_pid logfile.
DGen support takes place elsewhere.
Reshade can be turned off for comparison.
Yet you should really really switch to DirectX with your IntelHD graphics solution, OpenGL will never work correctly on that combo.

]cheers[
Mike
Logged
You live, you learn, you love, you're dead.

Toobone

  • Mapper
  • member
  • Offline Offline
  • Posts: 491
Re: CTD caused by JVM.DLL
« Reply #20 on: October 17, 2019, 06:01:11 AM »

OpenGL will never work correctly on that combo.


This is reasonable, thank you, Mike :)

BTW,  DX log:

11/10/2019 22:18:50:049 [02792] | WARN  | > 'IDirect3DDevice8::CreateImageSurface' failed with '0x8007000e'!
Logged

SAS~Storebror

  • retired
  • SAS Honourable Member
  • member
  • Offline Offline
  • Posts: 21635
  • Taking a timeout
    • STFU
Re: CTD caused by JVM.DLL
« Reply #21 on: May 09, 2022, 12:03:56 PM »

Thread necromancy?
Logged
You live, you learn, you love, you're dead.
Pages: 1 [2]   Go Up
 

Page created in 0.1 seconds with 26 queries.