2.7 Memory violation

[Wiz]

This is something new since the big cloud update.  I can log in the first time and fly forever but any reloads or track watching forces a CTD with the following logs.  I have sent enough logs to wallpaper all the offices in DCS. 

 

I was hoping the last update would resolve.

 

Sys is 7700K with a 2080ti

 

DCS/2.7.0.5659 (x86_64; Windows NT 10.0.19042)
C:\WINDOWS\SYSTEM32\d3d11.dll
# C0000005 ACCESS_VIOLATION at F4766BAE 00:00000000
SymInit: Symbol-SearchPath: '.;F:\Eagle Dynamics\DCS World OpenBeta;F:\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'wiz'
OS-Version: 10.0.19042 () 0x300-0x1
0x0000000000016BAE (d3d11): (function-name not available) + 0x0
0x00000000000169F9 (d3d11): (function-name not available) + 0x0
0x0000000000029EE3 (d3d11): D3D11CoreCreateDevice + 0x9823
0x0000000000028C25 (d3d11): D3D11CoreCreateDevice + 0x8565
0x00000000000295A6 (d3d11): D3D11CoreCreateDevice + 0x8EE6
0x000000000004B65B (d3d11): D3D11CoreCreateDevice + 0x2AF9B
0x0000000000043525 (d3d11): D3D11CoreCreateDevice + 0x22E65
0x000000000000CC16 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x7B46
0x000000000000CD82 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x7CB2
0x0000000000031612 (NGModel): model::ModelMaterial::draw + 0x5DE2
0x0000000000034FB4 (NGModel): model::ModelMaterial::draw + 0x9784
0x0000000000020ED3 (NGModel): model::graph::GraphNodesFactory::bootstrap + 0x473
0x0000000000037DC2 (NGModel): model::ModelMaterial::draw + 0xC592
0x0000000000041F3D (NGModel): init_graphics_plugin + 0x2F6D
0x0000000000042088 (NGModel): model::NGModelLods::~NGModelLods + 0x48
0x000000000004291E (NGModel): model::NGModelLods::~NGModelLods + 0x8DE
0x0000000000036B73 (GraphicsVista): Graphics::Models::gc + 0x1B3
0x0000000000032970 (GraphicsVista): Graphics::Renderer::FreeUnusedResources + 0x20
0x0000000000801E54 (DCS): SW + 0x5114A4
0x00000000007E9349 (DCS): SW + 0x4F8999
0x000000000011786A (edCore): Common::FSM::sendOutputSymbol_ + 0x4A
0x0000000000116F02 (edCore): Common::FSM::enterToState_ + 0xC2
0x00000000001176E9 (edCore): Common::FSM::onSymbol_ + 0x1A9
0x00000000007FF491 (DCS): SW + 0x50EAE1
0x00000000007D0234 (DCS): SW + 0x4DF884
0x00000000007D060D (DCS): SW + 0x4DFC5D
0x0000000001C38FBD (DCS): AmdPowerXpressRequestHighPerformance + 0xE49FB9
0x0000000000A071BE (DCS): SW + 0x71680E
0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
0x0000000000052651 (ntdll): RtlUserThreadStart + 0x21

Edited May 8, 2021 by Wiz

[Gumbie]

I had a similar issue I had to completely do a clean install of the game to get it to stop good luck!

 

[BIGNEWY]

1 hour ago, Wiz said:

This is something new since the big cloud update.  I can log in the first time and fly forever but any reloads or track watching forces a CTD with the following logs.  I have sent enough logs to wallpaper all the offices in DCS. 

 

I was hoping the last update would resolve.

 

Sys is 7700K with a 2080ti

 

DCS/2.7.0.5659 (x86_64; Windows NT 10.0.19042)
C:\WINDOWS\SYSTEM32\d3d11.dll
# C0000005 ACCESS_VIOLATION at F4766BAE 00:00000000
SymInit: Symbol-SearchPath: '.;F:\Eagle Dynamics\DCS World OpenBeta;F:\Eagle Dynamics\DCS World OpenBeta\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'wiz'
OS-Version: 10.0.19042 () 0x300-0x1
0x0000000000016BAE (d3d11): (function-name not available) + 0x0
0x00000000000169F9 (d3d11): (function-name not available) + 0x0
0x0000000000029EE3 (d3d11): D3D11CoreCreateDevice + 0x9823
0x0000000000028C25 (d3d11): D3D11CoreCreateDevice + 0x8565
0x00000000000295A6 (d3d11): D3D11CoreCreateDevice + 0x8EE6
0x000000000004B65B (d3d11): D3D11CoreCreateDevice + 0x2AF9B
0x0000000000043525 (d3d11): D3D11CoreCreateDevice + 0x22E65
0x000000000000CC16 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x7B46
0x000000000000CD82 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x7CB2
0x0000000000031612 (NGModel): model::ModelMaterial::draw + 0x5DE2
0x0000000000034FB4 (NGModel): model::ModelMaterial::draw + 0x9784
0x0000000000020ED3 (NGModel): model::graph::GraphNodesFactory::bootstrap + 0x473
0x0000000000037DC2 (NGModel): model::ModelMaterial::draw + 0xC592
0x0000000000041F3D (NGModel): init_graphics_plugin + 0x2F6D
0x0000000000042088 (NGModel): model::NGModelLods::~NGModelLods + 0x48
0x000000000004291E (NGModel): model::NGModelLods::~NGModelLods + 0x8DE
0x0000000000036B73 (GraphicsVista): Graphics::Models::gc + 0x1B3
0x0000000000032970 (GraphicsVista): Graphics::Renderer::FreeUnusedResources + 0x20
0x0000000000801E54 (DCS): SW + 0x5114A4
0x00000000007E9349 (DCS): SW + 0x4F8999
0x000000000011786A (edCore): Common::FSM::sendOutputSymbol_ + 0x4A
0x0000000000116F02 (edCore): Common::FSM::enterToState_ + 0xC2
0x00000000001176E9 (edCore): Common::FSM::onSymbol_ + 0x1A9
0x00000000007FF491 (DCS): SW + 0x50EAE1
0x00000000007D0234 (DCS): SW + 0x4DF884
0x00000000007D060D (DCS): SW + 0x4DFC5D
0x0000000001C38FBD (DCS): AmdPowerXpressRequestHighPerformance + 0xE49FB9
0x0000000000A071BE (DCS): SW + 0x71680E
0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
0x0000000000052651 (ntdll): RtlUserThreadStart + 0x21

 

 

 

Hi, welcome to the forum

 

Advice

 

Remove all unofficial mods and edits ( if any )

run a slow repair or verify in steam

ensure windows is up to date

ensure all drivers are up to date. 

If you are overclocking it maybe the cause of the crash. 

 

if you continue to crash please attach the whole log so we can take a closer look.

 

thank you

[Wiz]

Good morning team!

 

I have updated all drivers, no overclocking, Did a CP repair and my version of Open has always been vanilla

 

I flew a mission this morning, exited and went to reload another and CTD.

 

I have been flying the prod version all day with zero issues.

 

I have enclosed the crash zip and the help is appreciated!

 

 

 

dcs.log-20210509-110008.zip

Edited May 9, 2021 by Wiz

[Hawkeye_UK]

update?

 

[Wiz]

Known issues resolved by ED teams.  No issues since patches.