solved CTD Multiplayer

[SharpeXB]

Two CTDs in multiplayer, logs attached

DxDiag.zip

Edited February 26 by SharpeXB

[sleighzy]

Your DCS logs don't appear to contain crashes, which is normally indicative that Windows itself is killing the process. Looking at the DxDiag reports however they contain numerous BlueScreen events with an error code of c0000005 and 3b. Based on a quick internet search it would appear that this is potentially related to RAM issues.

Can you remove any overclocking you have on your RAM. Can you also run a memory test, this link contains some info on how to do so using the standard windows tools How to Test Your Computer's RAM for Problems

There are also a few errors in the logs, appear to be possibly unrelated, but run a slow repair of the game and delete your C:\Users\username\Saved Games\DCS\fxo and metashaders2 folders.

You don't appear to have any mods other than Tacview and SRS but try without those as well. 

Some additional feedback, some from the DCS log analyzer. Your preload radius is really high at the max of 150000. Drop that back to 60000 as you're loading a bunch of stuff into RAM which may be redundant.

• Consider using DLAA.
• Turn off SSLR.
• Turn off SSAO.
• Disable civil traffic.
• Disable Game Mode
• Disable Hardware accelerated GPU scheduling
• Disable Core Isolation

[SharpeXB]

My 

It looks to me like the log contains a lot of game related items:

2025-02-07 00:50:05.760 ERROR   GRAPHICSVISTA (Main): Can't open model Ural-375_p_1.
2025-02-07 00:50:05.760 ERROR   woCar (Main): can't load destroyed model 'Ural-375_p_1' for '1L13 EWR'
2025-02-07 00:50:05.787 ERROR   GRAPHICSVISTA (Main): Can't open model Ural-375_p_1.
2025-02-07 00:50:05.787 ERROR   woCar (Main): can't load destroyed model 'Ural-375_p_1' for '55G6 EWR'
2025-02-07 00:50:05.801 ERROR   GRAPHICSVISTA (Main): Can't open model Ural-375_p_1.
2025-02-07 00:50:05.801 ERROR   woCar (Main): can't load destroyed model 'Ural-375_p_1' for '1L13 EWR'
2025-02-07 00:50:05.817 ERROR   GRAPHICSVISTA (Main): Can't open model Ural-375_p_1.
2025-02-07 00:50:05.817 ERROR   woCar (Main): can't load destroyed model 'Ural-375_p_1' for '55G6 EWR'
2025-02-07 00:50:05.832 ERROR   GRAPHICSVISTA (Main): Can't open model Ural-375_p_1.
2025-02-07 00:50:05.832 ERROR   woCar (Main): can't load destroyed model 'Ural-375_p_1' for '55G6 EWR'

 

[SharpeXB]

another crash on the same server

dcs250209.log

[sleighzy]

2 hours ago, SharpeXB said:

another crash on the same server

dcs250209.log 137.86 kB · 0 downloads

Same as above. No crash shown in the log. Still contains those other items. No DxDiag so can't confirm the Windows side.

Are you able to replicate this on other servers, in case an issue with something on this server (not sure why'd it'd appear to crash as Windows "killing" it), or single player at all?

[SharpeXB]

1 hour ago, sleighzy said:

Same as above. No crash shown in the log. Still contains those other items. No DxDiag so can't confirm the Windows side.

Are you able to replicate this on other servers, in case an issue with something on this server (not sure why'd it'd appear to crash as Windows "killing" it), or single player at all?

This has happened on two different servers. I did an update of my BIOS and ran that Windows Memory Diagnostic but it didn’t produce any result in the Event Viewer. Other games run fine. I haven’t been able to check DCS single player yet though. DCS is simply quitting to the desktop, not freezing or anything.

I am wondering if these servers have updated to the most recent version of the game since that only included SP Campaign improvements. That could cause a crash I imagine. 

Edited February 10 by SharpeXB

[SharpeXB]

Happens in SP too

dcs.zip

[Flappie]

When it happens, do you see one of your CPU core stuck at 100%?

 

[SharpeXB]

8 hours ago, Flappie said:

When it happens, do you see one of your CPU core stuck at 100%?

 

Crashed in SP again but no core was at 100%. I have tried cleaning out my fxo and metashader 2 folders already. I have not tried disabling the memory overclock (DOCP) yet  

The problems started when I updated to 2.9.12.5336.1

Events250210-1.zip

Edited February 10 by SharpeXB

[Flappie]

The exception code found in your Event viewer is "0xc00000fd", stack overflow, which means your system ran out of memory. Your PC has 64GB of RAM, which should be enough for DCS. Try lowering DCS Preload Radius value (it's 150 000 - make it 60 000 which is default), and it this help, start looking at your memory OC settings.

[SharpeXB]

1 hour ago, Flappie said:

The exception code found in your Event viewer is "0xc00000fd", stack overflow, which means your system ran out of memory. Your PC has 64GB of RAM, which should be enough for DCS. Try lowering DCS Preload Radius value (it's 150 000 - make it 60 000 which is default), and it this help, start looking at your memory OC settings.

I just tried the Preload Radius at 60,000 but it still crashed. I'll try the oc next

[SharpeXB]

Turned off the mem overclock, still crashed

dcs250210-2.log Events250210-2.evtx

[SharpeXB]

No memory errors found

[Flappie]

I don't have many ideas because your crash isn't written in the log file. It ends abruptly.

But I've just come across this interesting thread: same symptom, same CPU. You should take a close look.

Have you already tried what @sleighzy has suggested, especially these below?

• Disable Game Mode
• Disable Hardware accelerated GPU scheduling
• Disable Core Isolation

You can also try these, which helped users with the same symptom:

1. In the BIOS, set Min/Max Cache Ratio to "Auto", if you have such an option.
2. Ensure Windows Power mode is set to High Performance.
3. Ensure no drive is full or nearly full (especially your system drive and your DCS drive).
4. Disable HPET.

autoexec.cfg

By the way, here's another user with the same issue, and the same CPU. Not solved yet.

 

[SharpeXB]

27 minutes ago, Flappie said:

Have you already tried what @sleighzy has suggested, especially these below?

• Disable Game Mode
• Disable Hardware accelerated GPU scheduling
• Disable Core Isolation

You can also try these, which helped users with the same symptom:

1. In the BIOS, set Min/Max Cache Ratio to "Auto", if you have such an option.
2. Ensure Windows Power mode is set to High Performance.
3. Ensure no drive is full or nearly full (especially your system drive and your DCS drive).
4. Disable HPET.

I’m going to try plugging the machine directly into the wall and bypassing my surge protector. The Mem Test was run on the surge protector.
For those others:

- Disable Game Mode and Disable Hardware accelerated GPU scheduling: These are easy enough to test but I’ve been running the game with those enabled for years so I’m not sure why they’d suddenly cause a problem  

- Disable Core Isolation: Don’t know how to do this nor probably want to mess with it. 

- In the BIOS, set Min/Max Cache Ratio to "Auto", if you have such an option: BIOS is set for Optimized Default. Prefer not to mess with that  

- Ensure Windows Power mode is set to High Performance: This is done  

- Ensure no drive is full or nearly full (especially your system drive and your DCS drive): Drive is not full  

- Disable HPET: I understand hyperthreading is supposed to be enabled for this CPU. In any case again I rather not mess with that. 

Edited February 11 by SharpeXB

[Flappie]

23 minutes ago, SharpeXB said:

I’m going to try plugging the machine directly into the wall and bypassing my surge protector. The Mem Test was run on the surge protector.

That is a very good idea. There was a precedent in the forum where the surge protector was causing CTDs because it limited the power drained by the PC.

[SharpeXB]

1 hour ago, Flappie said:

That is a very good idea. There was a precedent in the forum where the surge protector was causing CTDs because it limited the power drained by the PC.

Tried it plugged into the wall, still crashed

DCS250211-1.zip

[Flappie]

Try updating your motherboard: 

 

[SharpeXB]

26 minutes ago, Flappie said:

Try updating your motherboard: 

 

I did update the motherboard BIOS at the start of this trouble. Other games are crashing now too so not just DCS.

[Flappie]

OK, then I'm afraid you need to mess with BIOS settings. What is your motherboard model? Is that an ASUS Z790?

We'll try and find solutions from users with the same issue with the same hardware.

EDIT: you should try this step by step guide:

Edited February 12 by Flappie

[SharpeXB]

23 minutes ago, Flappie said:

OK, then I'm afraid you need to mess with BIOS settings. What is your motherboard model? Is that an ASUS Z790?

We'll try and find solutions from users with the same issue with the same hardware.

EDIT: you should try this step by step guide:

Oh I did that one already back when the degradation thing happened. The BIOS default now turns off the Asus MC enhancement and runs the Intel settings. 

[Flappie]

Apparently, Intel pledged to grant RMA to all impacted users.

 

[SharpeXB]

33 minutes ago, Flappie said:

Apparently, Intel pledged to grant RMA to all impacted users.

 

I wonder if that's the problem, despite the BIOS fix. The benchmark scores for the 14900 are still good. When the 13900 went boom I could see it in the scores.

Edited February 12 by SharpeXB

[sleighzy]

8 hours ago, SharpeXB said:

- Disable HPET: I understand hyperthreading is supposed to be enabled for this CPU. In any case again I rather not mess with that. 

Randomly saw this forum comment get posted a few hours ago re: hyper threading on the same CPU as you. Might be worth a shot (shrug)

 

[Flappie]

6 hours ago, SharpeXB said:

I wonder if that's the problem, despite the BIOS fix. The benchmark scores for the 14900 are still good. When the 13900 went boom I could see it in the scores.

I've read users saying the same thing: the CPU apparently behaves perfectly even during intense benchmarking, but as soon as it is asked to run a game, it becomes unstable.