Crash Report

[SharpeXB]

Crashed trying to open Hornet instant action mission

dcs.log-20250810-203357.zip DxDiag.txt

[SharpeXB]

another one

dcs.log-20251011-221753.zip DxDiag.txt

[SharpeXB]

another

dcs.log-20251011-224945.zip

[sleighzy]

These all different missions, and all instant missions? Does this occur with any other aircraft, or just F18 instant missions? Stack trace from some of the logs below:

2025-08-10 20:33:57.775 INFO    EDCORE (3036): Minidump created.
2025-08-10 20:33:57.775 INFO    Lua::Config (3036): stack traceback:
	[C]: in function 'Init_edterraingraphics'
	[string "./dxgui/bind/NewMapView.lua"]:107: in function 'initEDTerrainGraphics'
	[string "./MissionEditor/modules/me_map_window.lua"]:875: in function 'initTerrain'
	[string "./MissionEditor/modules/me_mission.lua"]:2215: in function 'load'
	[string "./MissionEditor/modules/me_openfile.lua"]:674: in function 'func'
	[string "./Scripts/UI/ProgressBarDialog.lua"]:154: in function 'updater'
	[string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>

Tried running a slow repair of the game? Would recommend doing that, also rename Saved Games\DCS\MissionEditor to MissionEditor.old so it rebuilds a new one of those when DCS starts up.

The DCS log analyser has identified a few other items with your system. Can provide that further following on from this. You can also drop those log files into the #dcs-log-analyzer channel of Eagle Dynamics DCS Discord server to get all these errors and potential solutions. For example, likely unrelated to this crash but it looks like you have core parking enabled as well.

From the DxDiag report:

Windows Error Reporting (WER)

Your system crashes with Bluescreens.

The following kernel-events have been detected: DPC_WATCHDOG_VIOLATION,KMODE_EXCEPTION_NOT_HANDLED,HYPERVISOR_ERROR,IRQL_NOT_LESS_OR_EQUAL,KERNEL_SECURITY_CHECK_FAILURE

• Remove any overclocking (including XMP).,
• Run SFC and DISM to check your Windows.,
• Check for any updates of your BIOS or chipset drivers.,

Application Errors

DCS.exe: c0000005 (nvgpucomp64.dll)

[SharpeXB]

1 hour ago, sleighzy said:

Does this occur with any other aircraft, or just F18 instant missions?

The two recent crashes were with the F-4

[SharpeXB]

12 hours ago, sleighzy said:

Tried running a slow repair of the game? Would recommend doing that, also rename Saved Games\DCS\MissionEditor to MissionEditor.old so it rebuilds a new one of those when DCS starts up.

I’ll try these

12 hours ago, sleighzy said:

For example, likely unrelated to this crash but it looks like you have core parking enabled as well.

Yes I do but I don’t have any performance troubles with that.

12 hours ago, sleighzy said:

Check for any updates of your BIOS or chipset drivers.,

These are all up to date

12 hours ago, sleighzy said:

Remove any overclocking (including XMP)

I have no OC except XMP. Been running DCS for years with that so I don’t think it’s the cause. 

12 hours ago, sleighzy said:

Run SFC and DISM to check your Windows

If the simple repairs to DCS don’t work I’ll try this next. 
 

Thanks
 

[SharpeXB]

Another one after those fixes above. Loading the F-4 A2A training mission  

dcs.log-20251012-163737.zip DxDiag.txt

Edited Sunday at 04:57 PM by SharpeXB

[silverdevil]

42 minutes ago, SharpeXB said:

Another one after those fixes above. Loading the F-4 A2A training mission

i did not check the other files you posted. however the latest shows the video driver is crashing. the log shows you have parked cores, an error about possible manual shading, and the crash just after attempting to load 'lightPalette.tif'. i do not see in previous parts of this thread. do you have OC on video card?

[SharpeXB]

1 hour ago, silverdevil said:

do you have OC on video card?

No

[sleighzy]

4 minutes ago, SharpeXB said:

No

Is your signature still accurate re: your video card "ASUS TUF GeForce RTX 4090 OC"? The OC means that this is coming with a factory overclock. You can use something like MSI Afterburner to verify and adjust.

The dll referenced in the error log is C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_08efa4f6500ab001\nvgpucomp64.dll . Look into the overclock on the card, and may need to also DDU your video card drivers and install later versions of them.

I see you're not on the latest version of DCS either.

[SharpeXB]

1 hour ago, silverdevil said:

the latest shows the video driver is crashing

I did just update that and it showed some errors. I’ll try rolling back to the prior version. 

19 minutes ago, sleighzy said:

Is your signature still accurate re: your video card "ASUS TUF GeForce RTX 4090 OC"? The OC means that this is coming with a factory overclock.

Yes but as a factory OC it’s probably reliable enough and has been running DCS for years. I don’t think that’s the culprit. 

21 minutes ago, sleighzy said:

I see you're not on the latest version of DCS either.

I did update after that first crash.

[silverdevil]

36 minutes ago, SharpeXB said:

Yes but as a factory OC it’s probably reliable enough and has been running DCS for years. I don’t think that’s the culprit. 

its only a test. things do go bad. i believe you can go into the nvidia driver and enable debug from menu. that will temporarily disable factory OC. again. just a test. it could be an indication of cooling issues.

null

Edited Sunday at 08:31 PM by silverdevil

[SharpeXB]

Tried rolling back driver, still crashed. Also had one quit to desktop

DxDiag.txt dcs.log-20251012-204252.zip dcs-quit.log

[SharpeXB]

Turned off the OC but it still quit to the desktop after running a while

Events251012-1.evtx DxDiag.txt dcs-quit.log dcs.log

[SharpeXB]

quit to desktop again

DxDiag.txt Events251012-2.evtx dcs.log

[sleighzy]

The last couple of logs haven't been DCS game crashes per se (there's no stack trace and list of dlls, it just stops logging), and the previous stack traces which were throughout all the others aren't showing up. This indicates that Windows itself is killing this. Ran the latest DxDiag report back through the log analyzer. Similar to previous with some notable changes, i.e. it is no longer highlighting that dll error that had showed up before.

Windows Error Reporting (WER)

Your system crashes with Bluescreens.

The following kernel-events have been detected: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY,VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP,HYPERVISOR_ERROR,IRQL_NOT_LESS_OR_EQUAL,KERNEL_SECURITY_CHECK_FAILURE

• Remove any overclocking (including XMP).,       (you've said you've tried this already)
• Run SFC and DISM to check your Windows., 
• Check for any updates of your BIOS or chipset drivers.,    (you've said you've checked these already)

Application Errors

DCS.exe: c00000fd (edCore.dll)

 

For the SFC and DISM commands open a command prompt as administrator and run the below two commands separately and then restart your PC.

dism /online /cleanup-image /restorehealth

sfc /scannow

 

The DxDiag report shows the last 10 crashes/issues on your system. Most of these are BlueScreen events with codes 139 or 20001. Can be Googled to see what they related to, e.g. 20001 mentioned hypervisor, which aligns with the HYPERVISOR_ERROR in the above list. The two commands above may possibly help with some items if corrupt system files.

Edited 21 hours ago by sleighzy

[SharpeXB]

11 hours ago, sleighzy said:

Run SFC and DISM to check your Windows

I ran these and they did indeed find some corrupted file and repaired successfully. Was about to consider this solved after running it for almost 2 hours.

But then got this quit.

dcs.log DxDiag.txt Events251013-1.evtx

[silverdevil]

1 hour ago, SharpeXB said:

I ran these and they did indeed find some corrupted file and repaired successfully. Was about to consider this solved after running it for almost 2 hours.

But then got this quit.

your dcs.log only shows 1 hour of flight and ends prematurely. this means windows ended the dcs process; as indicated by the windows events you posted. and the gpu driver is still being called out as failing.

2025-10-13 15:13:28.621 WARNING EDCORE (Main): hypervisor is active
2025-10-13 15:13:28.621 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores)
 

Edited 9 hours ago by silverdevil

[SharpeXB]

4 hours ago, silverdevil said:

2025-10-13 15:13:28.621 WARNING EDCORE (Main): hypervisor is active

I’m asking my PC support what that hypervisor crash was

4 hours ago, silverdevil said:

2025-10-13 15:13:28.621 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores)

Never had any performance trouble from this. 

4 hours ago, silverdevil said:

and the gpu driver is still being called out as failing

I ran a stress test on the GPU which passed. Rolling back the driver earlier didn’t help. 

Edited 4 hours ago by SharpeXB