solved Semi-regular Crash AH64 CPG seat

[ChessurCat]

# -------------- 20220414-233932 --------------
DCS/2.7.11.22211 (x86_64; Windows NT 10.0.19044)
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c0e159863e7afdde\nvwgf2umx.dll
# C0000005 ACCESS_VIOLATION at 4405D1A3 00:00000000
SymInit: Symbol-SearchPath: '.;E:\SteamLibrary\steamapps\common\DCSWorld;E:\SteamLibrary\steamapps\common\DCSWorld\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'starw'
OS-Version: 10.0.19044 () 0x300-0x1
 

 i7-8700K 

16gb ram

Nvidia GTX 1080 TI

 

Happens semi regularly but not every time I enter a hot CPG seat with the TADS on, or if cold start it sometimes happens when I switch the TADS screen from off to day or night. 

dcs.20220414-233932.crash

[ChessurCat]

Update: I validated the game files through steam and then I changed my page file to 16384, It appears to be happening now consistently everytime I start the 30mm Gun training mission.

I have no DCS modifications installed except for a couple F-16 liveries. 

dcs.20220415-001343.crash dcs.20220415-002018.crash dcs.20220415-002959.crash

Edited April 15, 2022 by ChessurCat

[ChessurCat]

Another update, I am running DCS on an external SSD through a 3.0 USB port. This could potentially be the issue, I apologize if this is already a known bad idea. I didn't really have much choice I am going to install an actual internal m.2 nvme soon, this was just a short term solution. 

[Flappie]

2 hours ago, ChessurCat said:

I apologize if this is already a known bad idea.

It is no recommended, indeed.

[ChessurCat]

Hey ! So another update, I tried a lot of different things with the external SSD. Couldn't get it to work. So today I installed an 1TB PCIe NVMe Gen3 M.2 2280 into my mobo. My performance has increased a lot and everything is much better, however even though it happens significantly less frequently I still run into this crash. Do note that is only when one of the MFDs with the TADS camera is on, it happens in pilot and CPG seat. 

dcs.20220418-070630.crash

[Flappie]

Hey, the repeated "NVENCODEAPI_Thunk" messages make it look very much like a RAM crash.

# -------------- 20220418-070630 --------------
DCS/2.7.11.22211 (x86_64; Windows NT 10.0.19044)
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c0e159863e7afdde\nvwgf2umx.dll
# C0000005 ACCESS_VIOLATION at D6B0C848 00:00000000
SymInit: Symbol-SearchPath: '.;F:\SteamLibrary\steamapps\common\DCSWorld;F:\SteamLibrary\steamapps\common\DCSWorld\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'starw'
OS-Version: 10.0.19044 () 0x300-0x1
0x000000000025C848 (nvwgf2umx): NVENCODEAPI_Thunk + 0x122B28
0x000000000025A974 (nvwgf2umx): NVENCODEAPI_Thunk + 0x120C54
0x00000000002C30F9 (nvwgf2umx): NVENCODEAPI_Thunk + 0x1893D9
0x00000000000C557A (nvwgf2umx): (function-name not available) + 0x0
0x000000000045C0A5 (nvwgf2umx): NVDEV_Thunk + 0x16EEB5
0x000000000045BE58 (nvwgf2umx): NVDEV_Thunk + 0x16EC68
0x000000000059D54A (nvwgf2umx): NVDEV_Thunk + 0x2B035A
0x000000000130A6E8 (nvwgf2umx): OpenAdapter12 + 0x5C2F38
0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
0x0000000000052651 (ntdll): RtlUserThreadStart + 0x21

 

It's often caused by an automatic XMP mode, or worse, a faulty RAM stick. See examples here:

Faulty RAM

 

XMP profiles set to Auto (need to set it to ON of OFF, but not AUTO)

 

Edited April 18, 2022 by Flappie

[ChessurCat]

interesting! I will try to narrow it down and report back, I will start by memtest my ram, thanks for the heads up flappie!

[ChessurCat]

Another update so, I ran the windows memory diagnostic and got no errors on my ram, checked my bios and the XMP profile is disabled but there are a lot of settings set to auto, I am not quite sure how to set the proper settings in bios I will need to look into that and also try another memtest beyond the windows memory diagnostic, will report back. 

[Specter]

On 4/18/2022 at 8:09 PM, ChessurCat said:

Another update so, I ran the windows memory diagnostic and got no errors on my ram, checked my bios and the XMP profile is disabled but there are a lot of settings set to auto, I am not quite sure how to set the proper settings in bios I will need to look into that and also try another memtest beyond the windows memory diagnostic, will report back. 

I only found an error when I ran Memtest86 from a bootable USB.  Good luck.

[Flappie]

On 4/18/2022 at 9:09 PM, ChessurCat said:

Another update so, I ran the windows memory diagnostic and got no errors on my ram, checked my bios and the XMP profile is disabled but there are a lot of settings set to auto, I am not quite sure how to set the proper settings in bios I will need to look into that and also try another memtest beyond the windows memory diagnostic, will report back. 

If XMP is disabled, no need to mess with BIOS settings. Just run MemTest as indicated by Specter.

[ChessurCat]

Hey so final update, I tried everything I could short of replacing the ram, gave up, got new 32gb of ram and it works now. I wanted to wait a few days and play it for atleast 5-10 hours before I made an update. I can safely say the ram was the issue and it is fixed now. Thanks Flappie and Specter for responding to my post your advice really helped. 

[Flappie]

I'm glad you sorted it out. Many, many thanks for your precious feedback. The more users give feedback, the more we know what the logs are trying to tell us.