zlib.dll crash with the current beta 5118 every time I come in to land

[kraze]

CrashLogs.7z

 

Crashlogs plus event viewer app error report plus mis1.miz - basically I take off from the carrier, fly for about 5 minutes, return to the carrier group and just a few minutes into the CASE I recovery it crashes - every single time

 

i5 9600k @ 4.8 GHz / G.Skill 32 GBs RAM 3600 MHz (stock XMP) / GTX 1080Ti with latest drivers / Win10 x64 on 850 EVO / Game on 860 EVO / no mods whatsoever / did 'clean' and 'repair' - didn't help

[BIGNEWY]

Hi,

 

the crash seems to point to your graphics driver, are you overclocking, and have you tried reinstalling the graphics driver? 

 

thanks

 

Quote

# -------------- 20210423-212214 --------------
DCS/2.7.0.5118 (x86_64; Windows NT 10.0.19041)
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5364881c934f6ce8\nvwgf2umx.dll
# C0000005 ACCESS_VIOLATION at 72742E10 00:00000000
SymInit: Symbol-SearchPath: '.;D:\Games\DCS World;D:\Games\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'krz'
OS-Version: 10.0.19041 () 0x100-0x1
0x0000000000882E10 (nvwgf2umx): cask::SafeEnum<cask::ScalarType_ENUMCLASS_SCOPEWRAPPER>::SafeEnum<cask::ScalarType_ENUMCLASS_SCOPEWRAPPER> + 0x240650
0x00000000008ABA86 (nvwgf2umx): cask::SafeEnum<cask::ScalarType_ENUMCLASS_SCOPEWRAPPER>::SafeEnum<cask::ScalarType_ENUMCLASS_SCOPEWRAPPER> + 0x2692C6
0x00000000008ABBD3 (nvwgf2umx): cask::SafeEnum<cask::ScalarType_ENUMCLASS_SCOPEWRAPPER>::SafeEnum<cask::ScalarType_ENUMCLASS_SCOPEWRAPPER> + 0x269413
0x00000000006AC6E2 (nvwgf2umx): cask::SafeEnum<cask::ScalarType_ENUMCLASS_SCOPEWRAPPER>::SafeEnum<cask::ScalarType_ENUMCLASS_SCOPEWRAPPER> + 0x69F22
0x00000000006233E0 (nvwgf2umx): NVENCODEAPI_Thunk + 0x30B6A0
0x00000000006423EC (nvwgf2umx): NVENCODEAPI_Thunk + 0x32A6AC
0x000000000061F92A (nvwgf2umx): NVENCODEAPI_Thunk + 0x307BEA
0x000000000005228A (nvwgf2umx): cask::ShaderList<cask::ConvShader,cask::Convolution>::availableShaders + 0x355A
0x0000000000484007 (nvwgf2umx): NVENCODEAPI_Thunk + 0x16C2C7
0x00000000001F915C (nvwgf2umx): cask::ShaderList<cask::ConvShader,cask::Convolution>::availableShaders + 0x1AA42C
0x000000000021C499 (nvwgf2umx): cask::ShaderList<cask::ConvShader,cask::Convolution>::availableShaders + 0x1CD769
0x000000000007666D (nvwgf2umx): cask::ShaderList<cask::ConvShader,cask::Convolution>::availableShaders + 0x2793D
0x00000000004162B9 (nvwgf2umx): NVENCODEAPI_Thunk + 0xFE579
0x0000000000416042 (nvwgf2umx): NVENCODEAPI_Thunk + 0xFE302
0x000000000058F82C (nvwgf2umx): NVENCODEAPI_Thunk + 0x277AEC
0x0000000001170F94 (nvwgf2umx): OpenAdapter12 + 0x3FD8F4
0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
0x0000000000052651 (ntdll): RtlUserThreadStart + 0x21

 

[kraze]

Overclocking only the CPU, not GPU. 1080Ti is running at a purely stock settings.

 

Had an older driver when I've noticed crashes, updated to the new one - they are still there.

 

As for OC'ing CPU - it was at those settings before and DCS was running stable - the only things that have changed is me not playing DCS for about 4 months and also replacing 8x2 GSkill Ripjaws V 3000 MHz with 16x2 Ripjaws V 3600 MHz

[kraze]

Hmmm, it appears that after installing different memory - OC settings for the CPU were reset and it had a ceiling of 1.21v versus 1.31v I've had set before for 4.8 GHz.

 

Maybe that's the case. Lemme test.