Jump to content

Game Crash 2.7


jfnelson0127

Recommended Posts

@Harker The "DXGI_ERROR_DEVICE_REMOVED" can mean something is wrong with your graphics driver or your graphics card, but sometimes it happens for different reasons. Here are solutions that worked to fix this error:

  • Empty "C:\Users\username\AppData\Local\Temp\DCS.Openbeta" (by the way, please check the folder you created gets filled once you've played a mission - if it doesn't, maybe your game uses another folder... but I've never heard of such thing)
  • Disable SSLR
  • Removed dust from CPU coooler
  • Removed GPU overclocking
  • Removed RAM overclocking
  • Replaced PSU

 

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

No xmp? I haven’t tried to disable the oc ram yet. I updated the new NVidia 466.27 

first mission start and destroy I got a crash but that’s it running solid right now going on 2 hours... so weird.

ALIENWARE R11 - I9 10900KF @ 5.1 GHz - M.2 NVMe 2TB - RTX3090  - XFURY 64GB -3400 MHz RAM

Monitor AW3420DW @ 120Hz - Virpil CM3 Throttle - TM TPR Rudder pedals - Virpil CM2 w/TM Hornet Stick Center - Monstertech Deck Mounts 

RealSimulator FSSB-R3 Lightning Base w/ F16SRGRH SideStick - VR user / Varjo Aero - Big Thx to mbucchia

Start Date April 2020 

 

Link to comment
Share on other sites

Users and programmers trying to get a handle on 2.7 crashes:

 

image.gif

11 minutes ago, Flappie said:

I think I've not asked this yet: what happens if the second mission you load is located on another map? Does it crash nevertheless?

It did for me.

  • Like 1

YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg

 

_____

Win 10 Pro x64, ASUS Z97 Pro MoBo, Intel i7-4790K, EVGA GTX 970 4GB, HyperX Savage 32GB, Samsung 850 EVO 250 GB SSD, 2x Seagate Hybrid Drive 2TB Raid 0.

Link to comment
Share on other sites

3 hours ago, Flappie said:
@Harker The "DXGI_ERROR_DEVICE_REMOVED" can mean something is wrong with your graphics driver or your graphics card, but sometimes it happens for different reasons. Here are solutions that worked to fix this error:
  • Empty "C:\Users\username\AppData\Local\Temp\DCS.Openbeta" (by the way, please check the folder you created gets filled once you've played a mission - if it doesn't, maybe your game uses another folder... but I've never heard of such thing)
  • Disable SSLR
  • Removed dust from CPU coooler
  • Removed GPU overclocking
  • Removed RAM overclocking
  • Replaced PSU
 

I stress-tested my components when the crashes started, they're all fine. All my other games play fine without any issues. The driver crashes only occured in DCS and started as soon as it updated to 2.7, so I'd say that the problem is isolated there.

Actually, after updating to the 466.27 driver, I don't get this DXGI_ERROR_DEVICE_REMOVED anymore, but I still get DX11BACKEND errors.

 

Specifically errors like that:
 

2021-04-30 21:21:20.695 ERROR_ONCE DX11BACKEND: render target 'cloudShadows' not found
2021-04-30 21:21:20.695 ERROR_ONCE DX11BACKEND: render target 'CascadeShadowMap' not found
2021-04-30 21:21:20.695 ERROR_ONCE DX11BACKEND: render target 'mainDepthBuffer_copy' not found
2021-04-30 21:21:20.695 ERROR_ONCE DX11BACKEND: render target 'DummyShadowMap' not found

and

2021-04-30 21:06:53.693 ERROR_ONCE DX11BACKEND: texture 'lha_04_wm_map' not found. Asked from 'NGMODEL'
2021-04-30 21:06:53.763 ERROR_ONCE DX11BACKEND: texture 'lha_02_wm_map' not found. Asked from 'NGMODEL'
2021-04-30 21:06:53.827 ERROR_ONCE DX11BACKEND: texture 'lha_01_wm_map' not found. Asked from 'NGMODEL'
2021-04-30 21:06:53.992 ERROR_ONCE DX11BACKEND: texture 'lha_05_wm_map' not found. Asked from 'NGMODEL'

 

Looks like the game is looking for assets it cannot locate. This was in a MP session, without any extra asset mods etc.

The folders I created in User\AppData\Local\Temp\ are empty, I don't think they're used.

And could you please let me know why SSLR would be a problem? I was using it prior to 2.7 without issues. I'll disable it and test anyway, just asking.

Thank you!


Edited by Harker

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

@HarkerThere's no need to disable SSLR if you don't get "DXGI_ERROR_DEVICE_REMOVE" anymore.

 

The 8 "ERROR_ONCE" messages you posted are "normal": we all get them. This is work-in-progress stuff (sometimes even long term WIP... some messages are getting old now).

 

I don't understand why your game doesn't use the C:\Users\username\AppData\Local\Temp\DCS... path. I'll ask ED to know if there's an alternative path.

 

I see in the dxdiag log extract you posted that your EVGA software is related to the DCS crash. Can you try disabling the EVGA software and see if DCS runs fine on its own?

 

Faulting module path: C:\Program Files\EVGA\Precision X1\PXSHW10_x64.dll

 

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

Your %TEMP% variable must have changed, which explains why you cannot find the Temp\DCS... folder.

Try to reach this address with your file browser, you should find the temps DCS folders: %TEMP%

 

image.png

 

Once in here, remove both DCS and DCS.openbeta folders, and see if DCS keeps crashing.

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

16 hours ago, Ironhand said:

Users and programmers trying to get a handle on 2.7 crashes:

 

image.gif

It did for me.

 

:grin:, I'm really starting to feel like all the stars lined up when I set my rig up 2 years ago. I haven't had a crash since... about 2 years ago?  Well, lots of the stars (the whole galaxies) were not required to line up since I only play SP but I do feel lucky. The only quirk I have to deal with has to do with changing anti-aliasing going from VR to pancake to play tracks sometimes. If I don't restart DCS I might get some graphical 'weirdness'.

But, I know how this works...  As soon as I brag, s*** will start happening.


Edited by Gripes323
Link to comment
Share on other sites

46 minutes ago, Gripes323 said:

 

...As soon as I brag, s*** will start happening.

 

 

I'm heading for cover now... Don't want to get hit by the falling debris.

YouTube Channel: https://www.youtube.com/channel/UCU1...CR6IZ7crfdZxDg

 

_____

Win 10 Pro x64, ASUS Z97 Pro MoBo, Intel i7-4790K, EVGA GTX 970 4GB, HyperX Savage 32GB, Samsung 850 EVO 250 GB SSD, 2x Seagate Hybrid Drive 2TB Raid 0.

Link to comment
Share on other sites

7 hours ago, Flappie said:

Your %TEMP% variable must have changed, which explains why you cannot find the Temp\DCS... folder.

Try to reach this address with your file browser, you should find the temps DCS folders: %TEMP%

 

image.png

 

Once in here, remove both DCS and DCS.openbeta folders, and see if DCS keeps crashing.

Found it, that did it! It was on my secondary drive, an HDD I use for storage. I had directed program-related temp and such to be saved there, in Windows. I'll delete it and see if it helps.
 

 

9 hours ago, Flappie said:

@HarkerThere's no need to disable SSLR if you don't get "DXGI_ERROR_DEVICE_REMOVE" anymore.

 

The 8 "ERROR_ONCE" messages you posted are "normal": we all get them. This is work-in-progress stuff (sometimes even long term WIP... some messages are getting old now).

 

I don't understand why your game doesn't use the C:\Users\username\AppData\Local\Temp\DCS... path. I'll ask ED to know if there's an alternative path.

 

I see in the dxdiag log extract you posted that your EVGA software is related to the DCS crash. Can you try disabling the EVGA software and see if DCS runs fine on its own?

 


Faulting module path: C:\Program Files\EVGA\Precision X1\PXSHW10_x64.dll

 

After the latest driver update, I'm not getting that any more, the driver hasn't crashed, yet. This only shows up with driver crashes and I suspect it occurs after the driver crash itself, since Precision is used to monitor the GPU clocks, control fan speeds etc. If I see that error again or if the driver crashes, I'll disable it and try again.

Thanks a lot for the help, I appreciate it!

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

31 minutes ago, Harker said:

Found it, that did it! It was on my secondary drive, an HDD I use for storage. I had directed program-related temp and such to be saved there, in Windows. I'll delete it and see if it helps.

 

Using an HDD for %TEMP% is a bad idea: this folder is used by many apps (including DCS). It means the HDD slows them down.

Hope your issue will be fixed now that you've deleted the old folders.

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

My DCS still sometimes creates a folder in  C:\Users\username\AppData\Local\, as well as in C:\Users\username\AppData\Local\Temp\.

 

Don't know if that is significant in any way at all. :dontgetit:

CPU:5600X | GPU:RTX2080 | RAM:32GB | Disk:860EVOm.2

Link to comment
Share on other sites

Right, but I have deleted both folders repeatedly over the past week, and it sometimes still remakes the old C:\Users\username\AppData\Local\ folder.


Edited by wowbagger

CPU:5600X | GPU:RTX2080 | RAM:32GB | Disk:860EVOm.2

Link to comment
Share on other sites

 
Using an HDD for %TEMP% is a bad idea: this folder is used by many apps (including DCS). It means the HDD slows them down.
Hope your issue will be fixed now that you've deleted the old folders.
Yeah, makes sense. I'll switch to the SSD.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

@FlappieI haven't had any long play sessions since I deleted the DCS folder at AppData/Local/Temp/, but I've had some short ones and had zero crashes. Seems like the driver update to 466.27 and deleting the DCS temp folder worked. Fingers crossed.

I'll probably have a long MP session in a few days, I'll update.

  • Thanks 1

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

Hello. For two days I have been trying hard to solve my friend's problem with the dsc 2.7 crash right after entering the mission, or shortly after. From the disk format and the new Windows and read DCS, to the replacement of the memory bones, etc. Graphics 466 ... But nothing helped. You know what helped in the end: nvidia 388.71 drivers! Eureka. As he took with his hand. Give it a try.

Link to comment
Share on other sites

Hi guys,

 

Still get crashes.

Here is what I have done so far:

Reinstalled the NVIDIA driver 466.27 after uninstalling it completely with DDU (Display Driver Uninstaller) and installed the KB5001391 Cumulative Update Preview for Windows 10 20H2.

I deleted fxo and metashader2 folders and deleted the DCS OpenBeta folders in the Temp folder in C:\Users\UserName\AppData\Local\Temp.

Despite this all I get DCS game crashes, not so often as before, but stil several a day.

Almost never had a crash in DCS Openbeta 2.5, so this is new to me.

When I look into the Event Viewer, I see the crashes tied to the ntdll.dll, the d3d11.dll or the dx11backend.dll.

More strangely, the errors in the Event Viewer get sometimes written when closing the game. During these instances, I don't notice anything.

 

Anyway, here attached is the latest Dcs log ZIP folder.

Let's hope for the best.

dcs.log-20210508-001158.zip

dcs.log-20210508-010352.zip


Edited by casserole
Link to comment
Share on other sites

22 minutes ago, casserole said:

Hi guys,

 

Still get crashes.

Here is what I have done so far:

Reinstalled the NVIDIA driver 466.27 after uninstalling it completely with DDU (Display Driver Uninstaller) and installed the KB5001391 Cumulative Update Preview for Windows 10 20H2.

I deleted fxo and metashader2 folders and deleted the DCS OpenBeta folders in the Temp folder in C:\Users\UserName\AppData\Local\Temp.

Despite this all I get DCS game crashes, not so often as before, but stil several a day.

Almost never had a crash in DCS Openbeta 2.5, so this is new to me.

When I look into the Event Viewer, I see the crashes tied to the ntdll.dll, the d3d11.dll or the dx11backend.dll.

More strangely, the errors in the Event Viewer get sometimes written when closing the game. During these instances, I don't notice anything.

 

Anyway, here attached is the latest Dcs log ZIP folder.

Let's hope for the best.

dcs.log-20210508-001158.zip 145.68 kB · 1 download

 

I am having the same problem. Tons of DX11 errors. I tried same steps, no change. Only started with latest 2.7 update.

Link to comment
Share on other sites

@casseroleYou seem to have a variant of the second mission loading crash, only this time it's triggered by the System::CleanScenes() function.

  1. "Graphics::Renderer::FreeUnusedResources + 0x20"
  2. Lua stack in the end
2021-05-08 00:11:55.072 INFO    TERRAIN: lSystem::exit()
2021-05-08 00:11:55.072 INFO    VISUALIZER: TerrainRenderer::release
2021-05-08 00:11:55.072 INFO    TERRAIN: lSystem::CleanScenes()
2021-05-08 00:11:55.072 INFO    EDOBJECTS: lTypeObjectManagerImpl::clear 13
2021-05-08 00:11:57.873 INFO    EDCORE: try to write dump information
2021-05-08 00:11:57.923 INFO    EDCORE: # -------------- 20210508-001158 --------------
2021-05-08 00:11:57.931 INFO    EDCORE: DCS/2.7.0.5659 (x86_64; Windows NT 10.0.19042)
2021-05-08 00:11:57.940 INFO    EDCORE: C:\Windows\SYSTEM32\d3d11.dll
2021-05-08 00:11:57.948 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 064F77A4 00:00000000
2021-05-08 00:11:57.956 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'PATRICK'
2021-05-08 00:11:57.964 INFO    EDCORE: OS-Version: 10.0.19042 () 0x100-0x1
2021-05-08 00:11:58.498 INFO    EDCORE: 0x00000000000A77A4 (d3d11): D3DKMTWaitForVerticalBlankEvent + 0x53174
2021-05-08 00:11:58.499 INFO    EDCORE: 0x000000000000AAA4 (d3d11): (function-name not available) + 0x0
2021-05-08 00:11:58.500 INFO    EDCORE: 0x000000000004F2AD (d3d11): D3D11CoreCreateDevice + 0x2EBED
2021-05-08 00:11:58.501 INFO    EDCORE: 0x0000000000029580 (d3d11): D3D11CoreCreateDevice + 0x8EC0
2021-05-08 00:11:58.502 INFO    EDCORE: 0x000000000004B65B (d3d11): D3D11CoreCreateDevice + 0x2AF9B
2021-05-08 00:11:58.503 INFO    EDCORE: 0x0000000000043525 (d3d11): D3D11CoreCreateDevice + 0x22E65
2021-05-08 00:11:58.504 INFO    EDCORE: 0x0000000000042D16 (dx11backend): createRenderer + 0x2AFA6
2021-05-08 00:11:58.505 INFO    EDCORE: 0x0000000000042E82 (dx11backend): createRenderer + 0x2B112
2021-05-08 00:11:58.507 INFO    EDCORE: 0x000000000002DDC5 (NGModel): model::ModelMaterial::draw + 0x2595
2021-05-08 00:11:58.508 INFO    EDCORE: 0x00000000000315E0 (NGModel): model::ModelMaterial::draw + 0x5DB0
2021-05-08 00:11:58.509 INFO    EDCORE: 0x0000000000034FB4 (NGModel): model::ModelMaterial::draw + 0x9784
2021-05-08 00:11:58.510 INFO    EDCORE: 0x0000000000020ED3 (NGModel): model::graph::GraphNodesFactory::bootstrap + 0x473
2021-05-08 00:11:58.511 INFO    EDCORE: 0x0000000000037DC2 (NGModel): model::ModelMaterial::draw + 0xC592
2021-05-08 00:11:58.511 INFO    EDCORE: 0x0000000000041F3D (NGModel): init_graphics_plugin + 0x2F6D
2021-05-08 00:11:58.512 INFO    EDCORE: 0x0000000000042088 (NGModel): model::NGModelLods::~NGModelLods + 0x48
2021-05-08 00:11:58.513 INFO    EDCORE: 0x000000000004291E (NGModel): model::NGModelLods::~NGModelLods + 0x8DE
2021-05-08 00:11:58.514 INFO    EDCORE: 0x0000000000036B73 (GraphicsVista): Graphics::Models::gc + 0x1B3
2021-05-08 00:11:58.515 INFO    EDCORE: 0x0000000000032970 (GraphicsVista): Graphics::Renderer::FreeUnusedResources + 0x20
2021-05-08 00:11:58.516 INFO    EDCORE: 0x0000000000008F82 (Terrain): createGlobalLand + 0x272
2021-05-08 00:11:58.517 INFO    EDCORE: 0x0000000000009A09 (Terrain): createGlobalLand + 0xCF9
2021-05-08 00:11:58.518 INFO    EDCORE: 0x00000000000096FB (Terrain): createGlobalLand + 0x9EB
2021-05-08 00:11:58.519 INFO    EDCORE: 0x0000000001C3B5A3 (DCS): AmdPowerXpressRequestHighPerformance + 0xE4C59F
2021-05-08 00:11:58.519 INFO    EDCORE: 0x0000000000001D40 (lua-terrain): (function-name not available) + 0x0
2021-05-08 00:11:58.520 INFO    EDCORE: 0x0000000000007AC5 (lua): luaD_growstack + 0x845
2021-05-08 00:11:58.521 INFO    EDCORE: 0x0000000000018D94 (lua): luaS_newlstr + 0x5254
2021-05-08 00:11:58.522 INFO    EDCORE: 0x0000000000007E04 (lua): luaD_growstack + 0xB84
2021-05-08 00:11:58.522 INFO    EDCORE: 0x0000000000006F7F (lua): lua_getinfo + 0x133F
2021-05-08 00:11:58.524 INFO    EDCORE: 0x000000000000812E (lua): lua_yield + 0x9E
2021-05-08 00:11:58.524 INFO    EDCORE: 0x0000000000002576 (lua): lua_pcall + 0x66
2021-05-08 00:11:58.525 INFO    EDCORE: 0x00000000000F2DA9 (edCore): ED_lua_pcall + 0x59
2021-05-08 00:11:58.526 INFO    EDCORE: 0x0000000000004005 (lua-dxguiWin): (function-name not available) + 0x0
2021-05-08 00:11:58.528 INFO    EDCORE: 0x00000000007D064D (DCS): SW + 0x4DFC9D
2021-05-08 00:11:58.528 INFO    EDCORE: 0x0000000001C38FBD (DCS): AmdPowerXpressRequestHighPerformance + 0xE49FB9
2021-05-08 00:11:58.529 INFO    EDCORE: 0x0000000000A071BE (DCS): SW + 0x71680E
2021-05-08 00:11:58.530 INFO    EDCORE: 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
2021-05-08 00:11:58.531 INFO    EDCORE: 0x0000000000052651 (ntdll): RtlUserThreadStart + 0x21
2021-05-08 00:11:58.732 INFO    EDCORE: Minidump created.
2021-05-08 00:11:58.732 INFO    Lua::Config: stack traceback:
	[C]: in function 'Init'
	[string "./MissionEditor/modules/me_map_window.lua"]:811: in function 'initTerrain'
	[string "./MissionEditor/modules/me_mission.lua"]:1638: in function 'load'
	[string "./MissionEditor/modules/me_openfile.lua"]:633: in function 'func'
	[string "./Scripts/UI/ProgressBarDialog.lua"]:154: in function 'updater'
	[string "./Scripts/UpdateManager.lua"]:64: in function <[string "./Scripts/UpdateManager.lua"]:40>

 

Don't accept indie game testing requests from friends in Discord. Ever.

Link to comment
Share on other sites

On 4/28/2021 at 12:15 PM, Flappie said:

Hi @ShuRugal. Your latest error message is related to me_logbook.lua, line 1118. I think BuzzLine has the fix you're looking for. Please try this:

 

 

Your pagefile is tiny (less than 3GB). You should ask Windows to set an initial size of 16 GB, and max 32GB.

 

 

 

I have the page file disabled deliberately, I should have more than adequate actual RAM and don't care to have windows thrashing my drives.  If you are seeing memory errors, I will look into acquiring more RAM.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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