DCS CRASHES

[fibola]

Hi to All, 

for the past 3-4 weeks my dcs keep crashes randomly. it can happened during the mission (SP or MP) loading page, during the spawn process or during the flight. 

most of the time the crashes are limited to DCS crashing into windows but on several occasions the crashes were by PC rebooting. 

 

there are days that i can play without any crashes and some days are intolerance like today where crashes keep happen time after time.

i have also notice that during the spawning process into the plane the layers of the cockpit are  happening slowly before my eyes (never happened before).   

i have checked my memory with memtest and GPU with Furmask.

i tried to disable the memory XMP and MT from the bios, repair dcs, run it on VR , with no VR , on MT and without. 

i uninstalled GPU driver and installed fresh ones

none of the above worked. 

my specs are : 

Processor    13th Gen Intel(R) Core(TM) i7-13700K   3.40 GHz
Installed RAM    32.0 GB (31.8 GB usable)
System type    64-bit operating system, x64-based processor
MB - MPG Z690 DDR4

Nvidia Geforce RTX 3090.

DCS installed on a SSD drive with 1.5GB free space. 

No modes installed. 

attached is my log file.

would be more than happy for some solutions - perhaps SSD error ? 

 

thank you 

 

 

 

 

dcs.log

[Flappie]

Hard reboots mean your PC has an issue, not just DCS.

In your log, we can see DCS detected an anomaly and was about to explain it, except it didn't have the time:

2024-01-26 19:24:45.190 INFO    EDTERRAINGRAPHICS41 (Main):     surface5 gc() LOD 0 8 squares
2024-01-26 19:24:45.192 INFO    EDTERRAINGRAPHICS41 (Main):     surface5 gc() LOD 1 25 squares
2024-01-26 19:24:45.192 INFO    EDTERRAINGRAPHICS41 (Main):     surface5 gc() LOD 2 26 squares
2024-01-26 19:24:45.193 INFO    EDTERRAINGRAPHICS41 (Main):     surface5 gc() LOD 3 28 squares
2024-01-26 19:24:45.193 INFO    EDTERRAINGRAPHICS41 (Main): surface5 gc() 2.878100 ms
2024-01-26 19:24:54.242 INFO    EDCORE (Main): try to write dump information

 

An SSD error would usually trigger the "IN_PAGE_ERROR" message in your dcs.log file. Try this:

1. Run the sfc command to check your Windows files.
2. Then run the chkdsk command on your DCS drive.
3. Then run another DCS cleanup and repair (choose the “slow” repair method).

Come to think of it, it could very well be a PSU issue.

[fibola]

thank you Flappie.

made all your suggestions. no issues found. 

then, run again DCS, entered into MP . chose a slot and windows reboot. .

here is the updated log file (i think its different now).

is there an app to check PSU ? 

 

dcs.log

Edited January 26, 2024 by fibola

[Flappie]

7 minutes ago, fibola said:

is there an app to check PSU ?

You can use HWMonitor to check the voltages. That would be a good start.

Here are mine (my PSU is less than 6 months old and I have no hard reboots - let's say it's in very good shape):

Ensure the voltages remain stable (first column on the left).

[fibola]

so is that mean something wrong ? 

 

[Flappie]

I'm not an expert on the matter, but I don't see anything abnormal with your voltages.

Edited January 26, 2024 by Flappie
typo

[fibola]

hi once again, 

its been a month since my post and my problem of random crashes keep occurring.

as for my system, i upgraded my RAM from 32GB to 64GB. 

As for my NVME drive where my DCS was installed, due to bad health i purchased WD SN850X 2TB and copied the DCS to it . following the continuance of the crashes, i decided to format my C drive , and installed fresh windows 11 and DCS on the WD NVME drive. 

Even all those measures yesterday after i finished installed windows, DCS new and clean GPU driver, DCS continue to randomly crashing - in SP or in MP mode. it could happen after 1-5 minutes or after 1 hour. 

I'm trying once again to seek help herein to try to solve this annoying issue. 

attached herewith is my log file - last crash was at 20:47 

as well as dcs.log-20240226-204735 file (created as zip file which couldn't be opened and renamed to txt file to try and understand it along with DxDiag.txt log file.

 

hopefully someone would be able to understand the problem.

 

Many thanks.

 

 

DxDiag.txt dcs.log dcs.log-20240226-204735.txt

[Bearskin]

I had the same problem a few months back where DCS kept crashing, I reduced visible range from Ultra down to high and I haven't had a crash since. 

This was my experience, maybe not yours but I just thought I would throw it out there just in case it helps.

[Flappie]

Hi @fibola. This time, we have a "proper" crash in your log:

2024-02-26 20:43:24.523 INFO    Dispatcher (Main): loadMission Done: Сontrol passed to the player
2024-02-26 20:43:26.402 WARNING FLIGHT (Main): NO ATC COMM HELIPAD + Static Helipad Single-1-1:127500000
2024-02-26 20:43:26.419 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-02-26 20:43:26.978 ERROR   woCar (Main): Dog Ear radar has request to level but 'GT.maxDeviationRoll' are not set!
2024-02-26 20:43:29.813 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-02-26 20:47:35.180 WARNING LOG (12568): 72 duplicate message(s) skipped.
2024-02-26 20:47:35.180 INFO    EDCORE (7604): try to write dump information
2024-02-26 20:47:35.283 INFO    EDCORE (7604): # -------------- 20240226-204735 --------------
2024-02-26 20:47:35.283 INFO    EDCORE (7604): DCS/2.9.3.51704 (x86_64; MT; Windows NT 10.0.22631)
2024-02-26 20:47:35.284 INFO    EDCORE (7604): C:\Program Files\Eagle Dynamics\DCS World\bin-mt\Scene.dll
2024-02-26 20:47:35.284 INFO    EDCORE (7604): # C0000005 ACCESS_VIOLATION at 00007fff22bcfa2b 00:00000000
2024-02-26 20:47:35.284 INFO    EDCORE (7604): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World\bin-mt;', symOptions: 532, UserName: 'Glov Family'
2024-02-26 20:47:35.284 INFO    EDCORE (7604): OS-Version: 10.0.22631 () 0x100-0x1
2024-02-26 20:47:35.285 INFO    EDCORE (7604): 0x000000000000fa2b (Scene): (function-name not available) + 0x0
2024-02-26 20:47:35.285 INFO    EDCORE (7604): 0x0000000000017418 (Scene): Graphics::SceneBase<DCSDemoSceneCollections::ObjectCollections,DCSDemoSceneCollections::LightCollections>::allowSceneWriteAccess + 0x8D8
2024-02-26 20:47:35.285 INFO    EDCORE (7604): 0x0000000000049169 (edCore): ed::this_thread::yield + 0x14CE9
2024-02-26 20:47:35.285 INFO    EDCORE (7604): 0x0000000000048497 (edCore): ed::this_thread::yield + 0x14017
2024-02-26 20:47:35.285 INFO    EDCORE (7604): 0x0000000000049d33 (edCore): ed::this_thread::yield + 0x158B3
2024-02-26 20:47:35.285 INFO    EDCORE (7604): 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71
2024-02-26 20:47:35.285 INFO    EDCORE (7604): 0x0000000000029363 (ucrtbase): _recalloc + 0xA3
2024-02-26 20:47:35.285 INFO    EDCORE (7604): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D
2024-02-26 20:47:35.423 INFO    EDCORE (7604): Minidump created.

 

The cause here is not obvious. Sometimes, "(function-name not available)" is a sign of a memory issue, especially when it's all over the place, but here is happens only once. And you've already checked it with MemTest86 and tried with XMP turned off...

This crash looks very much like that one, which remains unexplained and affected several players all at once. Maybe it was a bug this time, and nothing wrong with your PC?

 

Have you tried updating the BIOS of your motherboard yet?

Is your PC connected to the power through a surge protector?

Edited February 26, 2024 by Flappie

[fibola]

still haven't update my bios - will do that today (i got a recommendation to update hardware one at a time to see if the problem resolved, so yesterday i updated the network adapter -- played a bit to see the issue remain).  

 

yes- i do have a power supply to protect my pc from unexpected electricity issue and from bad weather .

[Flappie]

50 minutes ago, fibola said:

yes- i do have a power supply to protect my pc from unexpected electricity issue and from bad weather .

You should try to remove it (plug your PC directly to the power socket on the wall). Another user recently discovered his surge protector was preventing his PC to use max power, simply because his surge protector was 10A, not 16A.

[fibola]

for the sake of an update. 

i updated bios and until now i didnt suffered from further crashes (knock on wood). 

thank you Flappie for your time and efforts to read the log files and suggest solutions .

Fibola.