ST Crash After ~2 hours of Game Time

[Derbroomaster]

Playing in Caucasus on Multiplayer map.

Log and DXDiag files attached, as well as VR settings.

I'm consistently experiencing crashes in ST after the latest update. I've pretty much given up on MT as that is a sure crash after only minutes of game play.

 

DxDiag0314231403.txt dcs.log-20230314-195822.zip

I neglected to add system specs & VR headset:

Processor AMD Ryzen 7 5800X 8-Core Processor                3.80 GHz

Installed RAM Corsair Vengeance 32.0 GB DDR4 3200 (4 x

Device ID D8749A90-EBC2-49B6-8D28-8308E9ABFEA9

Product ID 00330-80000-00000-AA577

System type 64-bit operating system, x64-based processor

nVidia RTX4090 24GB RAM

1TB Samsung 980 NVmA

2TB HDD

1TB SSD (System)

MoBo MSI X-570 A Pro

PSU: Corsair RM1000X

VR: HP Reverb G2 v2

 

Edited March 15, 2023 by Derbroomaster
I neglected to add system specs & VR headset

[Flappie]

Hi. Unfortunately, your crash zip dooes not contain the full dcs.log (it happens sometimes). But I can clearly see this was a terrain-induced crash.

Does it always happen around the same location?

# -------------- 20230314-195822 --------------
DCS/2.8.3.37556 (x86_64; Windows NT 10.0.19044)
S:\DCS World OpenBeta\bin\edterrainGraphics41.dll
# C0000005 ACCESS_VIOLATION at 00007ffd963fda00 00:00000000
SymInit: Symbol-SearchPath: 'S:\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'DerBr'
OS-Version: 10.0.19044 () 0x100-0x1
0x00000000000cda00 (edterrainGraphics41): createInstancerRenderable + 0x301E0
0x00000000000cf7e3 (edterrainGraphics41): createInstancerRenderable + 0x31FC3
0x00000000002560af (edterrain4): landscape5::Surface5File::verticalIntersection + 0x644F
0x00000000002545ff (edterrain4): landscape5::Surface5File::verticalIntersection + 0x499F
0x0000000000250bb6 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF56
0x0000000000250be1 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF81
0x0000000000250be1 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF81
0x0000000000250be1 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF81
0x0000000000250be1 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF81
0x0000000000250be1 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF81
0x0000000000250be1 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF81
0x0000000000255341 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x56E1
0x0000000000252674 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x2A14
0x000000000025784f (edterrain4): landscape5::Surface5File::querySceneObjectsTris + 0x85F
0x0000000000251213 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x15B3
0x0000000000251281 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x1621
0x0000000000251281 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x1621
0x0000000000251281 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x1621
0x0000000000251281 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x1621
0x0000000000256e64 (edterrain4): landscape5::Surface5File::queryRuntimeSceneObjects + 0x104
0x00000000000d0c55 (edterrainGraphics41): createInstancerRenderable + 0x33435
0x00000000000cff32 (edterrainGraphics41): createInstancerRenderable + 0x32712
0x0000000000035b1b (edCore): ed::this_thread::yield + 0x319B
0x0000000000034ca2 (edCore): ed::this_thread::yield + 0x2322
0x00000000000365e3 (edCore): ed::this_thread::yield + 0x3C63
0x0000000000031fc0 (edCore): ed::thread::_get_current_thread_id + 0xA0
0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14

 

Are you using any terrain mod?

[Derbroomaster]

No terrain mod. It's never in the same place when, regardless of whether I'm running in ST or MT. Just happens quicker in MT.

[Flappie]

OK. Then, the next time it happens to you, please attach your dcs.log file. It will be easier to understand what happens.

[Derbroomaster]

For anyone running a HP Reverb G2, ensure you follow the directions in this link: 

 

After doing these steps, I have no more issues, and everything looks great. I don't know why the thread in the link isn't pinned, but it sure ought to be.