WorldGeneral.dll

[rcl]

Hi everyone,

 

Sorry if this is the wrong section.

My DCS is not starting. It either won't even show up or it gives me a crash. I looked in event viewer and the problem seems to be the WorldGeneral.dll located in the bin folder. I have tried updating my drivers, repairing the install. Deleting the WorldGeneral.dll then repairing. Running as admin, running in compatibility mode. Nothing worked. Plz help

Logs.rar

[rcl]

=== Log opened UTC 2018-07-07 15:43:10

2018-07-07 15:43:10.433 INFO EDCORE: try to write dump information

2018-07-07 15:43:10.440 INFO EDCORE: # -------------- 20180707-154310 --------------

2018-07-07 15:43:10.441 INFO EDCORE: C:\WINDOWS\SYSTEM32\ntdll.dll

2018-07-07 15:43:10.442 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 7FB6B64D 00:00000000

2018-07-07 15:43:10.444 INFO EDCORE: 00000000 00000000 0000:00000000

2018-07-07 15:43:10.447 INFO EDCORE: 7FB6B64D 0017F020 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlEnterCriticalSection()+D

2018-07-07 15:43:10.449 INFO EDCORE: 231345AF 0017F050 0000:00000000 C:\DCS World OpenBeta\bin\physfs.dll PHYSFS_setWriteDir()+1F

2018-07-07 15:43:10.450 INFO EDCORE: 23D83D8D 0017F090 0000:00000000 C:\DCS World OpenBeta\bin\edCore.dll ?init@InitPhysfs@core@ed@@UEAAXXZ()+2D

2018-07-07 15:43:10.451 INFO EDCORE: 23D8545F 0017F0D0 0000:00000000 C:\DCS World OpenBeta\bin\edCore.dll ?init@Initializer@ed@@QEAAAEAV12@PEAVIInitObj@2@@Z()+3F

2018-07-07 15:43:10.451 INFO EDCORE: D85348A2 0017F8B0 0000:00000000 C:\DCS World OpenBeta\bin\DCS.exe

2018-07-07 15:43:10.452 INFO EDCORE: D8A626B3 0017F8F0 0000:00000000 C:\DCS World OpenBeta\bin\DCS.exe

2018-07-07 15:43:10.452 INFO EDCORE: 7FA53304 0017F920 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14

2018-07-07 15:43:10.452 INFO EDCORE: 7FB79351 0017F970 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

2018-07-07 15:43:10.539 INFO EDCORE: Minidump created.

[Nealius]

I had a similar issue with .dlls in the bin folder causing issues. Rolling back to the last patch, then re-updating solved the problem for me.