Jump to content

Recommended Posts

  • ED Team
Posted
I got fed up lastnight and did do a clean install and it already crashed with Huey when Huey crashes with hard landing. No lockups yet but no time to do thorough testing yet today. This new pc can do hours upon hours of prime 95, handbrake and unengine heaven stress testing and benchmarking without issue so the clocks are definitely stable. It started right after the last patch. I played for a few hours the first night with this new pc on the previous build without issue and the problems all started after I updated with this patch. Shrug.

 

Huey crash is reported.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

  • Replies 105
  • Created
  • Last Reply

Top Posters In This Topic

Posted
This new pc can do hours upon hours of prime 95, handbrake and unengine heaven stress testing and benchmarking without issue so the clocks are definitely stable. It started right after the last patch.

 

exactly the same here. my OC Scanned (Nvidia tool) 2080ti passes all the benches i throw at it, it steams thru all the games i have, yet in DCS i get these odd crashes ever since i updated to the last patch

 

so far i have downgraded to the previous nvidia drivers, and resumed the stock clocks of my Palit card, and it seems to be more stable.

if it's any use to anyone, i used to have this kind of issues with DCS when i was applying any XMP profiles to my RAM, so i gave up on that a while back.

Win10 x64, Intel core I9 9900k@5ghz, 32GB DDR4, RTX2080 ti, MSI Z370 Tomahawk mobo, M.2 SSD, Warthog HOTAS, home made trackIr, Pimax 8K

Posted
And most of them are because:

 

1.- Drivers issues

2.- Using mods

3.- Overclocked Graphics Cards

4.- Not clean fresh Open Beta version ( edited files )

5.- Using external software like old reshade versions

6.- Previous fxo and metashaders folders

 

So is interesting to discard all this problems first and try:

 

1.- Brand new Users Folder from scracth

2.- Make a Clean and then a Repair of DCS

 

Or more radical, do a fresh clean install of DCS from scratch.

 

Number 5 was my case. Stick this post somewhere to reduce number of people complaining about crashes by 50% at least.

Gigabyte Z390 Gaming X | i7 9700K@5.0GHz | Asus TUF OC RTX 4090 | 32GB DDR4@3200MHz | HP Reverb G2 | TrackIR 5 | TM Warthog HOTAS | MFG Croswinds

Posted (edited)

for me no....i dont use any mods or reshade or something...

2.5.3 ran perfectly stable on the same day when i installed 2.5.4....and from exactly this point onwards dcs became totally unstable and crashes every day several times.

 

here is the last crashfile:

 

OS-Version: 10.0.17134 () 0x100-0x1
0x00007FFB21195B44 (edCore): mmfMemoryBlockPreload + 0x34
0x00007FFB2927C9C2 (edterrain4): (function-name not available) + 0x0
0x00007FFB29463B39 (edterrain4): (function-name not available) + 0x0
0x00007FFB2907432A (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x57D8A
0x00007FFB29074393 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x57DF3
0x00007FFB29074393 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x57DF3
0x00007FFB29074393 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x57DF3
0x00007FFB29074393 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x57DF3
0x00007FFB29074393 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x57DF3
0x00007FFB29074393 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x57DF3
0x00007FFB29073100 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x56B60
0x00007FFB21185149 (edCore): ed::thread::hardware_concurrency + 0x2099
0x00007FFB21182BAB (edCore): ed::StringsCacheFast::clear + 0x212B
0x00007FFB6736C4CE (ucrtbase): o_ceil + 0x4E
0x00007FFB68743034 (KERNEL32): BaseThreadInitThunk + 0x14
0x00007FFB6A563691 (ntdll): RtlUserThreadStart + 0x21

Edited by birdstrike
Posted

I've been having crashes lately as well, both with and without an overclocked (moderately) graphics card. I do use Process lasso if that could be an issue.

I'm going to make a clean install and try without any mods (have a few Viggen skins).

dcs.log-20190107-074949.zip

dcs.log-20190106-202420.zip

dcs.log-20190102-183327.zip

dcs.log-20190102-181502.zip

dcs.log-20190101-190014.zip

| Strix Z490-H | i5 10600K | MSI GeForce GTX 1080 Ti 11GB Gaming X | 32GB 3000MHz DDR4 | 256 Gb SDD Samsung 840 Pro + 480Gb SDD Kingston + 500 Gb HDD | Acer Predator Z1 2560*1440p | TM Warthog HOTAS | 2x MFD Cougar | Buddyfox A10 UFC  | TrackIR 5 | Win10 Pro 64-Bit Swedish |

 

| A-10C Warthog | AJS-37 Viggen | F-86F Sabre | F/A-18 Hornet | KA-50 Blackshark | Spitfire LF Mk. IX | UH-1H Huey | FC3 | CA | WWII Assets Pack | Supercarrier |

Posted

And here comes the next, after reinstalling DCS completely

dcs.log-20190107-120716.zip

| Strix Z490-H | i5 10600K | MSI GeForce GTX 1080 Ti 11GB Gaming X | 32GB 3000MHz DDR4 | 256 Gb SDD Samsung 840 Pro + 480Gb SDD Kingston + 500 Gb HDD | Acer Predator Z1 2560*1440p | TM Warthog HOTAS | 2x MFD Cougar | Buddyfox A10 UFC  | TrackIR 5 | Win10 Pro 64-Bit Swedish |

 

| A-10C Warthog | AJS-37 Viggen | F-86F Sabre | F/A-18 Hornet | KA-50 Blackshark | Spitfire LF Mk. IX | UH-1H Huey | FC3 | CA | WWII Assets Pack | Supercarrier |

Posted

| Strix Z490-H | i5 10600K | MSI GeForce GTX 1080 Ti 11GB Gaming X | 32GB 3000MHz DDR4 | 256 Gb SDD Samsung 840 Pro + 480Gb SDD Kingston + 500 Gb HDD | Acer Predator Z1 2560*1440p | TM Warthog HOTAS | 2x MFD Cougar | Buddyfox A10 UFC  | TrackIR 5 | Win10 Pro 64-Bit Swedish |

 

| A-10C Warthog | AJS-37 Viggen | F-86F Sabre | F/A-18 Hornet | KA-50 Blackshark | Spitfire LF Mk. IX | UH-1H Huey | FC3 | CA | WWII Assets Pack | Supercarrier |

Posted
I watched the track from your log file and there was no crash on my end.

 

Strange, it clearly crashes for me since DCS stops running and the window saying "unfortunately DCS crashed" and so on.

Crashed again today but no log was created.

| Strix Z490-H | i5 10600K | MSI GeForce GTX 1080 Ti 11GB Gaming X | 32GB 3000MHz DDR4 | 256 Gb SDD Samsung 840 Pro + 480Gb SDD Kingston + 500 Gb HDD | Acer Predator Z1 2560*1440p | TM Warthog HOTAS | 2x MFD Cougar | Buddyfox A10 UFC  | TrackIR 5 | Win10 Pro 64-Bit Swedish |

 

| A-10C Warthog | AJS-37 Viggen | F-86F Sabre | F/A-18 Hornet | KA-50 Blackshark | Spitfire LF Mk. IX | UH-1H Huey | FC3 | CA | WWII Assets Pack | Supercarrier |

Posted

:( Also here...

 

# -------------- 20190109-052501 --------------

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edterrainGraphics41.dll

# C0000005 ACCESS_VIOLATION at D5FFF935 00:00000000

SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin', symOptions: 534, UserName: 'Giorgio'

OS-Version: 6.1.7601 (Service Pack 1) 0x100-0x1

0x000007FED5FFF935 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x23395

0x000007FED603FCE4 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x63744

0x000007FED5FE9B1F (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0xD57F

0x000007FED5FF025D (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x13CBD

0x000007FED6003A78 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x274D8

0x000007FED60348CD (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x5832D

0x000007FED60344C0 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x57F20

0x000007FED6030110 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x53B70

0x000007FED6030084 (edterrainGraphics41): edtg41::TerrainRenderable::dump + 0x53AE4

0x000007FED6099078 (edterrainGraphics41): createInstancerRenderable + 0x3A1C8

0x000007FEF6814A38 (Inter): edterrain::ITerrainGraphicsEntryPoint::close + 0x18

0x000007FEF45F6696 (Terrain): createGlobalLand + 0x13A6

0x000007FEF45F52A9 (Terrain): lOilTank::getStoreType + 0x29

0x000007FEDC50894C (lua-gui_map): (function-name not available) + 0x0

0x000007FEDC512319 (lua-gui_map): (function-name not available) + 0x0

0x000007FEDC512274 (lua-gui_map): (function-name not available) + 0x0

0x000007FEF035F37E (dxgui): gui::Container::deleteWidgets_ + 0x7E

0x000007FEF035DA3B (dxgui): gui::Container::~Container + 0x3B

0x000007FEF036F2C4 (dxgui): gui::EditBoxView::EditBoxView + 0xF4

0x000007FEF035F37E (dxgui): gui::Container::deleteWidgets_ + 0x7E

0x000007FEF03A5167 (dxgui): gui::WindowBase::~WindowBase + 0x217

0x000007FEF03A49D4 (dxgui): gui::PopupWindow::onVisibleChanged_ + 0xB4

0x000007FEF0359E21 (dxgui): gui::ModalWindow::`default constructor closure' + 0x541

0x000007FEF0350D0C (dxgui): gui::GUI::destroy + 0x3BC

0x000007FEF035096A (dxgui): gui::GUI::destroy + 0x1A

0x000000014038D50B (DCS): (function-name not available) + 0x0

0x000000013FFF5C39 (DCS): (function-name not available) + 0x0

0x000000014052C44F (DCS): (function-name not available) + 0x0

0x000000007775652D (kernel32): BaseThreadInitThunk + 0xD

0x000000007798C521 (ntdll): RtlUserThreadStart + 0x21

FORTIS FORTUNA ADIUVAT

Posted (edited)
Are you running any mods, reshader, overclocking, anything like that? For me it ends like the mission was quit, sometimes I can reproduce the crash from watching the track, in this case it doesnt crash for me.

 

I did have a mild OC on both the cpu and gpu but i've removed that, at least I hope I have, I'm far from an expert on this. I almost need to know more even to be a noob :lol:

The few mods I had have been removed, I did a complete uninstall and reinstall of DCS. I have the A-10C, Hornet, Flaming cliffs and Viggen. I didn't install the SU-27 this last time since I have enough planes to learn and keep up to date on.

The mods where some skins for Viggen and a label mod called "Label mod" by Invisibull.

 

There where some "kernel-stuff" at the end of the text file in the unzipped crash log. What can that be?

Also I saw something in an event log in Windows where my TrackIr 5 had stopped working. Maybe that one is causing all the crashes? :huh:

 

edit: maybe I should have posted elsewhere since I'm not running OB 2.5.4 but maybe it doesn't matter...

Edited by Palten

| Strix Z490-H | i5 10600K | MSI GeForce GTX 1080 Ti 11GB Gaming X | 32GB 3000MHz DDR4 | 256 Gb SDD Samsung 840 Pro + 480Gb SDD Kingston + 500 Gb HDD | Acer Predator Z1 2560*1440p | TM Warthog HOTAS | 2x MFD Cougar | Buddyfox A10 UFC  | TrackIR 5 | Win10 Pro 64-Bit Swedish |

 

| A-10C Warthog | AJS-37 Viggen | F-86F Sabre | F/A-18 Hornet | KA-50 Blackshark | Spitfire LF Mk. IX | UH-1H Huey | FC3 | CA | WWII Assets Pack | Supercarrier |

Posted

DCS Freezing

 

I'm having freezing on my DCS even when it is just loading into the main screen I can watch task manager and see that it goes back and forth from "Not Responding" and working correctly. It also does it just loading a training mission then after 2 or 3 minutes in the game it will freeze completely and eventually tell me DCS isn't responding. I'm running a Ryzen 2700x 16 GB of RAM at 3200 1tb 860 evo ssd and GTX 1070ti. no OC on anything and all the latest drivers installed. I have tried different DCS versions as well as different NVIDIA drivers and nothing changed. Im currently back on the latest drivers for everthing.

Logs.zip

Logs (2).zip

Posted
Are you using any sort of mods?

No mods at all. Before the update I was able to play all night long without any issues the only thing I have yet to try is a fresh install of windows to see if that will make a difference. I just do not want to do that if I don’t have to.

Posted (edited)

Interestingly the latest version comes with a CMD window running along (looks like something to debug) and I just had a crash (the usual one, DCS just quits silently) on finals and lots of red text (something with loading and visual as far as I can remember) in that box, but it instantly vanished as well and the dcs.log does not contain what's been in the box at last, it ends like 4 minutes before the crash and my latest .crash file is from 2018-03-something. I'll see if this happens more often and if so, I'll provide some log files and stuff.

Edited by Eldur

dcsdashie-hb-ed.jpg

 

  • Recently Browsing   0 members

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