Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[hotas01]

Hello all,
since a week my game 4.122 + SAS MODACT don't start and I did nothing special.
so I think it's a technical problem linked with something but what ???
I've verified Windows Defender (I stopped it) and verified Avast too (I cleared the .exe) nothing (notice that with avast all was OK)
I've done a restore of windows 1 month before, nothing
I've checked new clean install, idem, nothing
according your forum I did DEP, nothing

the only thing I did was a cleaning with CCCleaner so ???

If you have any thing, welcome !! Thanks in advance

Thierry

[Satanas]

The only time I've had a problem like this was when a dll (msvcp71.dll or msvcr71.dll I can't remember which, but you need both at the root of the simu) was missing. A quirk of my antivirus, which had quarantined it, see if you're not in that situation.

[hotas01]

Thanks but all are present in stock game, Avast verified, nothing in Quarantine.
Searching

[Flying H]

Log.lst resides in the game root folder. If you can´t find it go here https://www.sas1946.com/main/index.php/topic,49972.0.html and read.

[hotas01]

initlog.lst here :
2024-06-01 13:10:10:857 (dinput.dll) : IL-2 Process ID = 00001C74
2024-06-01 13:10:10:857 (dinput.dll) : Starting Watchdog at D:\ubisoft\4122sas53\bin\selector\basefiles\IL-2 Watchdog.exe
2024-06-01 13:10:10:968 (dinput.dll) : Watchdog process started.
2024-06-01 13:10:10:969 (dinput.dll) : JVM Parameters injector activated
2024-06-01 13:10:10:971 (dinput.dll) : Applying JVM Memory Settings from IL-2 Selector...
2024-06-01 13:10:10:971 (dinput.dll) : Adding JVM Option: -Xms444M
2024-06-01 13:10:10:972 (dinput.dll) : Adding JVM Option: -Xmx444M
2024-06-01 13:10:10:972 (dinput.dll) : Adding JVM Option: -Xss4096K
2024-06-01 13:10:10:973 (dinput.dll) : Adding JVM Option: -XX:PermSize=64M
2024-06-01 13:10:10:973 (dinput.dll) : Adding JVM Option: -XX:MaxPermSize=64M
2024-06-01 13:10:10:974 (dinput.dll) : Checking duplicate JVM Options...
2024-06-01 13:10:10:974 (dinput.dll) : Checking mandatory JVM Options...
2024-06-01 13:10:10:975 (dinput.dll) : Adding JVM Option: -Djava.class.path=.
2024-06-01 13:10:10:975 (dinput.dll) : Adding JVM Option: -Xincgc
2024-06-01 13:10:10:976 (dinput.dll) : Adding JVM Option: -Xverify:none
2024-06-01 13:10:10:976 (dinput.dll) : Adding JVM Option: -Xcomp
2024-06-01 13:10:10:976 (dinput.dll) : Final JVM Option List:
2024-06-01 13:10:10:977 (dinput.dll) : -Xms444M
2024-06-01 13:10:10:977 (dinput.dll) : -Xmx444M
2024-06-01 13:10:10:978 (dinput.dll) : -Xss4096K
2024-06-01 13:10:10:978 (dinput.dll) : -XX:PermSize=64M
2024-06-01 13:10:10:978 (dinput.dll) : -XX:MaxPermSize=64M
2024-06-01 13:10:10:978 (dinput.dll) : -Djava.class.path=.
2024-06-01 13:10:10:979 (dinput.dll) : -Xincgc
2024-06-01 13:10:10:979 (dinput.dll) : -Xverify:none
2024-06-01 13:10:10:980 (dinput.dll) : -Xcomp
2024-06-01 13:10:11:035   (watchdog) : IL-2 Parent Process Handle = 000001BC, ID=00001C74
2024-06-01 13:10:11:035   (watchdog) : IL-2 Watchdog started.
2024-06-01 13:10:11:040   (watchdog) : Message Window Created.
2024-06-01 13:10:11:073 (dinput.dll) : Hooked "SAS_CreateJavaVM" function activated, injecting JVM Parameters
2024-06-01 13:10:11:145   (watchdog) : Splash Screen Created.
2024-06-01 13:10:12:946 (dinput.dll) : JVM Parameters injector deactivated

[Paulo Hirth]

https://www.sas1946.com/main/index.php/topic,71235.0.html

[Flying H]

That is eventlog.lst, wrong log. Log.lst is the one a little further down or ifit´s not there go to the site I showed above and read how to.

[hotas01]

All is done
Impossible to have a LOG because don't start, only the starting panel appear and stop, so INITLOG.
I have the same problem with a new clean install
I'm sure it's a problem with FIREWALL (AVAST)
I'm going to uninstall  AVAST, clean REGISTRY, stop DEFENDER and will be back

Here last INITLOG :

https://pastebin.com/sFsJ76vA
 

[SAS~Storebror]

Initlog is useless here.
Check your Windows Event Log (the one coming with Windows, in the Event Viewer).
In the application log, there will most likely be something similar to this:

Code: [Select]

Failed application name il2fb.exe, version: 0.0.0.0, timestamp: 0x44fd7bbb
Failed module name: jvm.dll, version: 0.0.0.0, timestamp: 0x3af53001
Exception Code: 0xc0000005
Error Offset: 0x000b08b0
Failed process ID: 0x1b80
Failed application start time: (whatever...)
Failed application path: (whatever...)\il2fb.exe
Failed module path: (whatever...)\bin\hotspot\jvm.dll
Report ID: 6b6aff84-44fd-41bd-a7a3-6ea79459c9a3
Full name of the failed package:
Application ID related to the failed package:
Please check and report back.


Mike

[hotas01]

Thanks, done
event journal report 1 error and 1 information

http://pastebin.fr/137974

[SAS~Storebror]

As expected.
Code 0xc0000005 (access violation) at offset 0x000b08b0.
100% definitely sure: The cause is DEP.
Go back to https://www.sas1946.com/main/index.php/topic,71235.0.html and adjust DEP settings again.
Obviously something went wrong when you tried to do so before.


Mike

[hotas01]

According all recomandations I modified DEP but "access refused" so for me DEP corrupted
I tried to modify that by CMD and "bcdedit.exe" but "access refused" even with "admin"
After internet searching on some forum it was evident to repair Window according my ISO
So I did it and after 2 minutes IL2 is now fonctionning as before 
So it really was a technical pb pearhaps on the disk
Thanks all for your help 
Good flights