DCS crash on start

[markturner1960]

As per title suddenly ( This morning after runnng perfectly fine, I flew 2 30 minute flights in the F15E, with no issues, went away, restarted 30 minutes later and boom, wont run....) started crashing on start up. I have disabled all mods, done a full, slow repair......still crashes. Enclose the log files from 2 latest incidents, oone before repair, one after. Any help appreciated thank you

dcs.log-20230625-090315.zip dcs.log-20230625-113815.zip

Seems to be happening in both single and multithreaded

Edited June 25, 2023 by markturner1960

[markturner1960]

Several downloads of the log and no comments? 

 

[Flappie]

Hi @markturner1960. You sim crashes during GPU detection:

2023-06-25 09:03:15.056 INFO    VISUALIZER (Main): LAUNCH IN VR OpenXR: Meta Quest Pro
2023-06-25 09:03:15.057 INFO    VISUALIZER (Main): render thread initialization...
2023-06-25 09:03:15.062 INFO    GRAPHICSVISTA (10148): renderer: 'dx11backend.dll'
2023-06-25 09:03:15.118 INFO    DX11BACKEND (10148): DX11Renderer initialization (w:1920 h:1440 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1)
2023-06-25 09:03:15.321 INFO    EDCORE (10148): try to write dump information
2023-06-25 09:03:15.323 INFO    EDCORE (10148): # -------------- 20230625-090315 --------------
2023-06-25 09:03:15.323 INFO    EDCORE (10148): DCS/2.8.6.41363 (x86_64; MT; Windows NT 10.0.19045)
2023-06-25 09:03:15.324 INFO    EDCORE (10148): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\dx11backend.dll
2023-06-25 09:03:15.324 INFO    EDCORE (10148): # C0000005 ACCESS_VIOLATION at 00007fffe9595074 00:00000000
2023-06-25 09:03:15.325 INFO    EDCORE (10148): SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'mark'
2023-06-25 09:03:15.325 INFO    EDCORE (10148): OS-Version: 10.0.19045 () 0x300-0x1
2023-06-25 09:03:15.326 INFO    EDCORE (10148): 0x0000000000015074 (dx11backend): RenderAPI::DX11Renderer::initDevice + 0xB4
2023-06-25 09:03:15.326 INFO    EDCORE (10148): 0x00000000000143a6 (dx11backend): RenderAPI::DX11Renderer::init + 0x3C6
2023-06-25 09:03:15.327 INFO    EDCORE (10148): 0x000000000002a04f (GraphicsVista): Graphics::Renderer::initialize + 0x69F
2023-06-25 09:03:15.327 INFO    EDCORE (10148): 0x00000000001121af (Visualizer): smSceneManager::DestroySceneManager + 0xAF7F
2023-06-25 09:03:15.327 INFO    EDCORE (10148): 0x00000000001056ac (Visualizer): smCamera_Implement::getClipRegion + 0x167BC
2023-06-25 09:03:15.327 INFO    EDCORE (10148): 0x00000000000f5196 (Visualizer): smCamera_Implement::getClipRegion + 0x62A6
2023-06-25 09:03:15.327 INFO    EDCORE (10148): 0x0000000000108792 (Visualizer): smSceneManager::DestroySceneManager + 0x1562
2023-06-25 09:03:15.327 INFO    EDCORE (10148): 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2023-06-25 09:03:15.327 INFO    EDCORE (10148): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2023-06-25 09:03:15.327 INFO    EDCORE (10148): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
2023-06-25 09:03:15.447 INFO    EDCORE (10148): Minidump created.

 

See how it goes on my PC:

2023-06-27 15:49:22.307 INFO    VISUALIZER (Main): render thread initialization...
2023-06-27 15:49:22.320 INFO    GRAPHICSVISTA (14032): renderer: 'dx11backend.dll'
2023-06-27 15:49:22.442 INFO    DX11BACKEND (14032): DX11Renderer initialization (w:3440 h:1440 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1)
2023-06-27 15:49:22.739 INFO    DX11BACKEND (14032): Driver Concurrent Creates - 1
2023-06-27 15:49:22.739 INFO    DX11BACKEND (14032): Driver Command Lists - 1
2023-06-27 15:49:22.875 INFO    DX11BACKEND (14032): NVIDIA API init OK
2023-06-27 15:49:22.875 INFO    DX11BACKEND (14032): NVIDIA Display Driver Version 53141.r531_37
2023-06-27 15:49:22.875 INFO    DX11BACKEND (14032): GPU count:1

 

If your PC has an internal GPU, ensure it is not used by DCS (either in Windows gaming menu or in your NVIDIA/AMD software.

Also check that your GPU drivers are OK. Re-install them if needed.

Does it crash the same way if you start in "pancake" (2D) mode ?

[markturner1960]

Yes, it crashes in 2D as well. I can however get it to run in VR if I use a non powered link cable....My original Meta link cable seemed to be causing issues of freezing etc, so I have a standard aftermarket cable, a powered cable and finally a powered USB C hub. Lukas wolta has been helping me troubleshoot, on Friday, I installed (using DDU and a clean minimal install) an older driver, 522.25 at Lukas's request. I will check regarding the onboard GPU.

If I use either the powered hub, or the powered cable, DCS will crash on starting VR. It works using a standard cable.

Does that suggest anything? 

[Flappie]

3 hours ago, markturner1960 said:

Does that suggest anything? 

I don't know, I don't use VR. Is your powered USB hub a good one? I know some users had issues with some models. A friend of mine bought this one and he's happy with it: https://icybox.de/en/product.php?id=119

Edited June 27, 2023 by Flappie

[markturner1960]

The hub was recommended by someone using it with no problems……..I was also using it for 2 weeks without issue, before last weekends patch…..this only started happening then? I also have a powered cable, which also does not work, but did before…… 

Thanks for the suggestions and advice though!

[markturner1960]

Where would I look to check about the onboard GPU settings please? 

 

[Flappie]

There are several ways to do it. Here's a nice guide showing 3 different ways:

• Disable your internal GPU in the BIOS (my favorite method, because neither Windows nor your NVIDIA software will know about the internal GPU, which means no possible interference).
• Disable your iGPU in Windwos Device Manager (although it would work, I don't recommend you to do this).
• Tell Windows to use your discrete GPU when running DCS.

The fourth way is to ask NVIDIA to use your discreet GPU when running any game (the second best solution in my opinion).

What is your motherboard model? Maybe it has no iGPU.

[markturner1960]

Hi mate, its a: ASUS ROG STRIX X570-E

[Flappie]

OK. This motherboard does have an internal GPU. From what I can read, you can disable the iGPU from your BIOS here:

• Advanced> AMD CBS > NBIO Common Options > GFX Configuration > iGPU Configuration >Set to iGPU Disabled

or maybe here:

• Advanced> System Agent (SA) Configuration > Graphcis configuration >Primary display > PCIE

Then ensure in Windows Device Manager that the iGPU is absent from the "Display adapters".

Edited June 30, 2023 by Flappie

[markturner1960]

thanks, will try that

BTW, its not showing in device manager ATM....? just shows my 3090 and 3 x winwing USB display  They are run using display link adapter which is software

Edited June 30, 2023 by markturner1960

[Flappie]

6 minutes ago, markturner1960 said:

thanks, will try that

BTW, its not showing in device manager ATM....? just shows my 3090 and 3 x winwing USB display  They are run using display link adapter which is software

If it's already absent, I guess you don't need to do anything.

Then we must find another designated culprit for your issue.

[markturner1960]

I checked in the bios, I dont have any GFX options under NBIO , so maybe there is no onboard graphics? 

I am still getting crashes on start up even with not using a powered link cable or hub. If I re start, this seems to clear whatever was preventing the start up...do you want latest crash log? 

[Flappie]

6 minutes ago, markturner1960 said:

I checked in the bios, I dont have any GFX options under NBIO , so maybe there is no onboard graphics?

Strange. Your mobo is supposed to have an HDMI input in the back.

7 minutes ago, markturner1960 said:

I am still getting crashes on start up even with not using a powered link cable or hub. If I re start, this seems to clear whatever was preventing the start up...do you want latest crash log? 

If you restart DCS, you mean?

I'm interested in both your logs: the one when it fails, and the one when it starts with no issue.

[markturner1960]

it does have an HDMI port on the back, up near the USB ports. I looked through all the options in the bios and could see nothing as shown in that graphic though that indicated any onboard graphics settings options. And defo nothing in device manager either.....

By the way, this is a one week old install of windows with only DCS and my oculus stuff installed. 

I have noticed another anomoly though which may be relevant....I referred above to the winwing displays ( I have the MP1 displays and bezels UFC system) They usually show in windows display properties as 3 separate displays. when i checked just now, they show as one display, numbered 213 ( they are normally 2,3&4) In the sim, they work, but are all showing what is usually on the first one. Thats a recent change. Do you think its tied in ? By the way, any idea how to get windows to see them properly again? maybe re install that driver software? 

I enclose a log from this morning wherer it crashed on start. Will generate one where it starts. 

dcs.log-20230630-071003.zip

[Flappie]

I don't know much about WinWing devices, sorry. The only thing I know is that their script can cause low FPS in DCS, that's all.

But I'm pretty sure your problem comes from GPU driver detection.

I've just read this thread showing the exact same issue, from 2022. Mustang was using 522.25 NVIDIA driver, the one you have installed recently. When he switched to 522.30, his issue was gone. Can you try?

Edited June 30, 2023 by Flappie

[markturner1960]

Hi, yes, although 522.30 is a studio driver.......? I uninstalled teh winwing display link software drivers, so may see if that changes anything first before swapping drivers, or we wont know where we are! 

Edited June 30, 2023 by markturner1960

[Flappie]

54 minutes ago, markturner1960 said:

I uninstalled teh winwing display link software drivers, so may see if that changes anything first before swapping drivers, or we wont know where we are!

Good thinking.

I'm using NVIDIA 531.41. You can try it instead of 522.30 if you want.

[markturner1960]

Update Flappie: Since I have removed the wrongly detected display from windows ( They are still plugged in, but when I uninstalled the display link drivers, they dont show anymore) I have not had any more crashes.

However, I have had these peripherals installed and working fine alongside my VR for months now, so whatever conflict etc is causing it, its tied to something recent and this did start happening with the last update....so I do think that while its great I am not getting the crash, there is still an issue for ED to look at somewhere below the surface.......I have not changed the driver yet, still 522.25

Thank you for your assistance so far! 

Edited July 2, 2023 by markturner1960

[silverdevil]

sorry to jump in late to this. i have a suggestion. we use displaylink drivers at the office for docking stations. lots of different products use displaylink. the manufacturers will provide displaylink software with their products which many people use. you can also use the latest from the displaylink site. i have found that the displaylink OEM drivers can have problems with windows updates and display drivers updates. i would suggest unplugging the winwing devices. then download and install the latest displaylink from this site.

https://www.synaptics.com/products/displaylink-graphics

then re-plug the winwing. latest nvidia is 536.40 from 6/29/2023 in case you want to try this.

i personally think it is important to always try the newest drivers for all the hardware if possible.