Jump to content

[RESOLVED]1.5 Crash after some time flying


Recommended Posts

Posted (edited)

I've seen crashes in both versions (1.5 and 2.0) after flying for some variable amount of time. This rarely happens. Both time in cruise flight. No weapons being used nor conflicts with AI. It is single player.

 

I think it might be related to toggling mirrors on/off...maybe.

 

I've attached the crash dump and log. This is from a flight in the Mi-8.

dcs.logs.zip

Edited by BIGNEWY
TITLE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Intel i7-8700K @4.9Ghz | 32Gb memory DDR4 | Evga GTX 1080ti | Saitek Eclipse keyboard |

Logitech Mx518 | CH Fighterstick, Pro Throttle/Pedales | TIr5 | Win10 x64

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  • 2 weeks later...
Posted (edited)

With the last update to DCS world, I'm still seeing crashes (DCS has stopped working).

 

I've been staying with 1.5.x and flying the Mi-8 and UH-1. Both will crash (stop working) after a few minutes.

 

[DCS is so vast now, with so many modules and mission, it's hard to pin down a way to reproduce each time it crashes]

 

Lately, I've been flying the 1st UN Pilot mission. I've repaired DCS. Removed all mods. Checked VC++ runtime. Rolled back vid driver to prior version.

 

After this last update, I can go longer before the crash, but still have crashes. About 15 -20 mins. I'm sad.

 

Questions:

 

Is this a module issue? Would flying only the A-10C solve my crashing?

Would a clean install help?

Would any devs or interested individuals like to see my latest logs etc?

Anyone else having this issue?

 

[adding logs]

Logs.zip

Edited by Scratchy
adding all logs

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Intel i7-8700K @4.9Ghz | 32Gb memory DDR4 | Evga GTX 1080ti | Saitek Eclipse keyboard |

Logitech Mx518 | CH Fighterstick, Pro Throttle/Pedales | TIr5 | Win10 x64

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  • 1 month later...
Posted

Update for the curious

 

It's been a long and dismal journey, but I made it!

 

TL;DR:

 

My memory data rate/frequency was causing the problem.

 

The Story:

 

After a long period of not being able to fly for more than 10-12 minutes before a "DCS has stopped working." error message, I have finally solved the problem. This post is a history of the problem and how I finally tracked down the solution.

 

I have a fairly hefty system (my specs are in my signature) but nothing special. I've been running 8Gb of DDR3 memory for some time (few years) with a data rate set at 2133. With this setting I'd been running DCS without any issues. Then, problems began after some point.

 

What triggered the problem was unknown. A Windows 10 update? Driver update? DCS update? I couldn't pin it down. I tried rolling back video drivers. I cried on the DCS forums, hoping for some kindred spirit would point me in the right direction. Clean installs of DCS versions. Nothing helped. I gave up.

 

What does one do without DCS to enjoy? Play other games. In my case: Factorio. But, you can only swat bitters and spitters for so long, so I started playing other games. And to my dismay the games using Unity or directX 10 also crashed after 10 minutes or so. Ah ha!

 

One more bit of information is needed at this point: I added 8 Gb of memory; doubling the total amount to 16 Gb. After all, I needed to get ready for the Red Flag campaign. All I did was add the memory, check the BIOS settings and verify the memory was detected and running at the same data rate. I also ran benchmark and stress tests (RealBench).

There wasn't a add memory and experience crashes event. The crashes began some time after adding the memory.

 

Back to the story:

 

Crashing regardless of the app running. That's the clue I needed.

 

I ran extensive memory tests over-night. No problem. I did clean install of old nvidia drivers--still crashing. So, it must be the memory, right? It was.

 

I toned down the memory's data rate to 800. All is well and everything runs fine. I moved the data rate to 1600. A modest but acceptable data rate. Still A-Ok.

 

I can't tell a difference between 1600 and 2133 data rates. I may take it (the data rate) up to the next setting (1866 maybe? Not sure) and see what happens.

 

Long story, I know. But some might find it helpful or interesting.

 

Summary:

 

16 Gb of memory with a 2133 data rate on my motherboard is a no-go.

 

Theory:

 

As you may or may not experience with DCS and other high performance open-world applications, there are instances where it is necessary for additional data to be fetched into memory. It may be a predictive algorithm or maybe it just happens when you approach a chunk border. Dunno. However, this instant causes a slight hiccup on my system. Further, this is where my crashes were occurring. This data fetch into memory exposed the problem with my system's configuration.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Intel i7-8700K @4.9Ghz | 32Gb memory DDR4 | Evga GTX 1080ti | Saitek Eclipse keyboard |

Logitech Mx518 | CH Fighterstick, Pro Throttle/Pedales | TIr5 | Win10 x64

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  • ED Team
Posted

Hi Scratchy,

 

thanks for the logs

 

are you running dcs with administration rights?

 

I dont know much about memory, I have always allowed my motherboard to do its stuff, on auto.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted

I am running as Administrator.

 

I didn't make it clear I guess. I'm error free at last! I was able to complete a couple of campaign missions last night, including the very long 1st mission for the UH-1H campaign.

 

Thanks for looking.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Intel i7-8700K @4.9Ghz | 32Gb memory DDR4 | Evga GTX 1080ti | Saitek Eclipse keyboard |

Logitech Mx518 | CH Fighterstick, Pro Throttle/Pedales | TIr5 | Win10 x64

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  • ED Team
Posted
Exactly similar issue here. DCS (especially the Mi-8 module) is stopped after a few minutes flying.

The whole game is crashed.

Not happened earlyer, only since the last update.

 

Please make a new thread and attach your whole logs folder, also include your system spec in the post and we will try to assist you

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...