ags Posted January 7, 2021 Share Posted January 7, 2021 I'm experiencing repeated crashes with 2021-01-07 21:30:18.619 ERROR DX11BACKEND: failed to create structed buffer. Reason: E_OUTOFMEMORY 2021-01-07 21:30:18.619 ERROR DX11BACKEND: CreateShaderResourceView FAILED. Reason: E_INVALIDARG I'm on a not-overclocked 5950x, using a G1, and a non-overclocked MSI 3090. Current OS, drivers and DCS openbeta. Logs attached, and an gpu-z log as well, that shows memory usage growth. Windows is a fresh install (Sunday, 3rd Jan). Help appreciated. gpuz_log2020g.7z dcs.7z dcs.log.old.7z VR, i9, Winwing, TM and VKB. 2, 4, ban, ban, 2 Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted January 7, 2021 ED Team Share Posted January 7, 2021 Hi seeing a few issues. first NET: Failed to decode network.vault: either hardware ID or OS username are different. Saved login data will be reset. It maybe worth renaming your dcs folder in saved games, create a backup, then restart DCS login, and redo settings. Also ensure you have removed your unofficial mods, some of them are creating errors. then run a full cleanup and repair of dcs ensure windows and your display driver are also up to date. let us know if it helps, if not please attach your fresh dcs log thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
ags Posted January 7, 2021 Author Share Posted January 7, 2021 (edited) hardware ID mismatch is easily explained by a bios update. Edited January 7, 2021 by ags VR, i9, Winwing, TM and VKB. 2, 4, ban, ban, 2 Link to comment Share on other sites More sharing options...
ags Posted January 8, 2021 Author Share Posted January 8, 2021 Cleaned mods, played online, VRAM kept growing, crashed around <21GB occupied. Track, dcs.log, and gpu-z log https://www.dropbox.com/sh/7yh244grqsbel1e/AAC2t023eaOoZXgPP0SgCxhLa?dl=0 VR, i9, Winwing, TM and VKB. 2, 4, ban, ban, 2 Link to comment Share on other sites More sharing options...
Flappie Posted January 8, 2021 Share Posted January 8, 2021 (edited) Hi ags. It seems DCS had write permission issues during the crash. This associated with the memory issue the firs time makes me think of a storage/pagefile issue. 2021-01-08 00:58:44.511 INFO EDCORE: CreateFile failed. Error: 32 2021-01-08 00:58:44.512 INFO EDCORE: CreateFile failed. Error: 32 2021-01-08 00:58:44.513 INFO EDCORE: MiniDumpWriteDump failed. Error: 2147943855 2021-01-08 00:58:44.773 ERROR VFS: VFS_open_write: CreateFile(C:\Users\ags\Saved Games\DCS.openbeta\Tracks\Multiplayer\Gildiansky_Range_v1_7_3_lite-20210107-233947.trk): The process cannot access the file because it is being used by another process. 2021-01-08 00:58:44.774 ERROR VFS: VFS_open_write: CreateFile(C:\Users\ags\Saved Games\DCS.openbeta\Logs\dcs.log-20210108-005843.zip): The process cannot access the file because it is being used by another process. 2021-01-08 00:58:44.774 ERROR DCS: can not create zip 'C:\Users\ags\Saved Games\DCS.openbeta\Logs\dcs.log-20210108-005843.zip' Please send the result of this command (open the "cmd" utility and run the command into it) : wmic pagefile list /format:list Also please attach your dxdiag log. Here's how to obtain one. Edited January 8, 2021 by Flappie Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
ags Posted January 17, 2021 Author Share Posted January 17, 2021 (edited) C:\Users\ags>wmic pagefile list /format:list AllocatedBaseSize=32768 CurrentUsage=227 Description=C:\pagefile.sys InstallDate=20210108133840.734843+000 Name=C:\pagefile.sys PeakUsage=1476 Status= TempPageFile=FALSE And dxdiag is attached. VRAM usage still keeps climbing. DxDiag.7z Edited January 17, 2021 by ags added chart VR, i9, Winwing, TM and VKB. 2, 4, ban, ban, 2 Link to comment Share on other sites More sharing options...
Flappie Posted January 17, 2021 Share Posted January 17, 2021 Thank you. I see you have a 32 GB pagefile stored on an NVMe disk, which has 550 GB of free space, and DCS is stored on that same disk: there shouldn't be any bad file access timings. I'm still trying to figure out what caused the file access error messages. Maybe it's something with your antivirus. Please add these folders as exceptions in your antivirus: C:\Users\your-name\Saved Games\DCS.openbeta C:\dcsOpenBeta\ Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
ags Posted January 18, 2021 Author Share Posted January 18, 2021 I am running Defender only, and these folders are already defined as exceptions. VR, i9, Winwing, TM and VKB. 2, 4, ban, ban, 2 Link to comment Share on other sites More sharing options...
Flappie Posted January 18, 2021 Share Posted January 18, 2021 OK. I see in your dcs.log DCS only detects 8 GB of pagefile. Please try manually setting your pagefile size: initial size: 32768 (32 GB) max size: 65536 (64 GB) Now, your dcs.log file should always show at least a 32 GB pagefile. If DCS keeps crashing after this, it won't be because of a lack of memory (except if it's a hardware RAM issue of course). Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
ags Posted January 18, 2021 Author Share Posted January 18, 2021 0. First dcs.log correctly picks up an 8GB pagefile, this has been increased to 32GB. 1. Running long-lasting tests for CPU, memory, and ovearall stress is something I have already done, no faults. I’ve increased amount of pagefile since the original post, it is now set at 32GB permanenty - what would you expect to change if dynamic sizing would be allowed? I’ll start logging these values from other software then. To my eye, which lacks insight into DCS under the hood, scenario to trigger an overflow is rather simple - fly in a vanilla (as in, no mods) multiplayer server, keep shooting at things, die multiple times. DCS crash ensues. I so far hold my opinion DCS is too aggressive in how VRAM is being used, and releasing this resource is not happening as expected. As a sidenote, log sometimes mentions polygon gc cycles going into 10s of ms. I’d say this is „long”, and should be faster, or ceased after a smaller threshold value. VR, i9, Winwing, TM and VKB. 2, 4, ban, ban, 2 Link to comment Share on other sites More sharing options...
Flappie Posted January 18, 2021 Share Posted January 18, 2021 Look into the Windows Event Manager, in the "Application" section, at the time of your latest crash. You should find an error message dealing with both DCS.exe and VCRUNTMIME140.dll (see here). Can you please paste here the full error message? Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
ags Posted January 22, 2021 Author Share Posted January 22, 2021 Funny enough, now that you have requested a message from Error Log, my DCS started being more stable. VR, i9, Winwing, TM and VKB. 2, 4, ban, ban, 2 Link to comment Share on other sites More sharing options...
BrzI Posted January 24, 2021 Share Posted January 24, 2021 Today I also started getting DCS DX11 crashes. Seeing this : Faulting application name: DCS.exe, version: 2.5.6.59625, time stamp: 0x5fe21078 Faulting module name: dx11backend.dll, version: 2.5.6.59625, time stamp: 0x5fdb3463 Exception code: 0xc0000005 Fault offset: 0x000000000000c145 Faulting process id: 0x1f350 Faulting application start time: 0x01d6f29e195c181a Faulting application path: C:\DCS World\bin\DCS.exe Faulting module path: C:\DCS World\bin\dx11backend.dll Report Id: d1745cc7-5eff-4ad1-8b9b-ede1a4724c47 Faulting package full name: Faulting package-relative application ID: Any ideas... ? Link to comment Share on other sites More sharing options...
BrzI Posted January 24, 2021 Share Posted January 24, 2021 After doing a base repair I got this : Version=1 EventType=APPCRASH EventTime=132560015895659818 ReportType=2 Consent=1 ReportIdentifier=26caddc7-2746-4fe7-bf8e-ffd58a89d822 IntegratorReportIdentifier=048aa2e2-8ed2-430d-aeec-88599ce97d67 Wow64Host=34404 NsAppName=DCS.exe AppSessionGuid=0000ae58-0003-0066-a44c-a7a3a1f2d601 TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!DCS.exe TargetAppVer=2020//12//22:15:27:52!0!DCS.exe BootId=4294967295 ServiceSplit=1 TargetAsId=20762 UserImpactVector=271593744 IsFatal=1 EtwNonCollectReason=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=DCS.exe Sig[1].Name=Application Version Sig[1].Value=2.5.6.59625 Sig[2].Name=Application Timestamp Sig[2].Value=5fe21078 Sig[3].Name=Fault Module Name Sig[3].Value=DCS.exe Sig[4].Name=Fault Module Version Sig[4].Value=2.5.6.59625 Sig[5].Name=Fault Module Timestamp Sig[5].Value=5fe21078 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=0000000000981855 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.19041.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=4105 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0000 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=00000000000000000000000000000000 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=0000 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=00000000000000000000000000000000 UI[2]=C:\DCS World\bin\DCS.exe OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=19041 OsInfo[3].Key=ubr OsInfo[3].Value=746 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=4105 OsInfo[7].Key=geoid OsInfo[7].Value=39 OsInfo[8].Key=sku OsInfo[8].Value=48 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=256 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=220930675 OsInfo[15].Key=osinsty OsInfo[15].Value=3 OsInfo[16].Key=iever OsInfo[16].Value=11.630.19041.0-11.0.220 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=32706 OsInfo[19].Key=svolsz OsInfo[19].Value=237 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=191206 OsInfo[22].Key=bldtm OsInfo[22].Value=1406 OsInfo[23].Key=bldbrch OsInfo[23].Value=vb_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.19041.746.amd64fre.vb_release.191206-1406 OsInfo[30].Key=buildflightid OsInfo[30].Value=5AFFFB9B-FB87-4242-B66A-4ECEEB1CF75F.1 OsInfo[31].Key=edition OsInfo[31].Value=Professional OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[33].Value=RS:6E74 OsInfo[34].Key=fconid OsInfo[35].Key=containerid OsInfo[36].Key=containertype OsInfo[37].Key=edu OsInfo[37].Value=0 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=DCS AppPath=C:\DCS World\bin\DCS.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=CCCFD963E1407416B8929A00528B4AF6 MetadataHash=-742622831 Link to comment Share on other sites More sharing options...
Flappie Posted January 24, 2021 Share Posted January 24, 2021 Hi Brzl. Can you please attach your most recent crashlog. It's a zip file located in your "C:\Users\your-name\Saved Games\DCS...\Logs" folder. Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
BrzI Posted January 25, 2021 Share Posted January 25, 2021 dcs.log-20210124-225909.zip Here you go. What I also did was to download the latest NVidia drivers. It seems to have fixed the issue. It is a bit weird because the old drivers were from December 2020. The only thing I can think of is that somehow those driver files got corrupted somehow. Thanks Link to comment Share on other sites More sharing options...
Flappie Posted January 25, 2021 Share Posted January 25, 2021 Thanks for your feedback. For the record, the driver causing the issue was "NVIDIA 460.89" from December 15th 2020. Here's the crashlog: 2021-01-24 22:59:08.862 INFO VISUALIZER: StartSimulation 2021-01-24 22:59:08.868 ERROR DX11BACKEND: Failed assert `false && "failed to create texture"` at Projects\render\dx11backend_win8\Source\DX11TextureManager.cpp:703 2021-01-24 22:59:08.869 INFO EDCORE: try to write dump information 2021-01-24 22:59:08.871 INFO EDCORE: # -------------- 20210124-225909 -------------- 2021-01-24 22:59:08.872 INFO EDCORE: DCS/2.5.6.59625 (x86_64; Windows NT 10.0.19041) 2021-01-24 22:59:08.874 INFO EDCORE: C:\DCS World\bin\dx11backend.dll 2021-01-24 22:59:08.875 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 6C39C145 00:00000000 2021-01-24 22:59:08.882 INFO EDCORE: SymInit: Symbol-SearchPath: '.;C:\DCS World;C:\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'gogi' 2021-01-24 22:59:08.883 INFO EDCORE: OS-Version: 10.0.19041 () 0x100-0x1 2021-01-24 22:59:10.099 INFO EDCORE: 0x000000000000C145 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x6035 2021-01-24 22:59:10.099 INFO EDCORE: 0x000000000000B991 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x5881 2021-01-24 22:59:10.100 INFO EDCORE: 0x000000000001272F (dx11backend): RenderAPI::DX11Renderer::createFrameBuffer + 0x8F 2021-01-24 22:59:10.100 INFO EDCORE: 0x0000000000008934 (GraphicsCore): enlight::Atmosphere::computeSkyRadianceChunk + 0x9F4 2021-01-24 22:59:10.100 INFO EDCORE: 0x000000000001A1EF (GraphicsCore): deferredShading::DepthResolver::copy + 0x85F 2021-01-24 22:59:10.100 INFO EDCORE: 0x000000000001B74F (GraphicsCore): deferredShading::DeferredComposer::init + 0xBF 2021-01-24 22:59:10.100 INFO EDCORE: 0x0000000000164476 (Visualizer): smSceneManager::CreateSceneManager + 0xFA66 2021-01-24 22:59:10.100 INFO EDCORE: 0x0000000000164DFD (Visualizer): smSceneManager::CreateSceneManager + 0x103ED 2021-01-24 22:59:10.100 INFO EDCORE: 0x000000000015EE37 (Visualizer): smSceneManager::CreateSceneManager + 0xA427 2021-01-24 22:59:10.101 INFO EDCORE: 0x00000000007C4C9C (DCS): CoreUtils::TempFilesManager::operator= + 0x3D2F2C 2021-01-24 22:59:10.101 INFO EDCORE: 0x00000000007AFB70 (DCS): CoreUtils::TempFilesManager::operator= + 0x3BDE00 2021-01-24 22:59:10.101 INFO EDCORE: 0x000000000011BCEA (edCore): Common::FSM::sendOutputSymbol_ + 0x4A 2021-01-24 22:59:10.101 INFO EDCORE: 0x000000000011B382 (edCore): Common::FSM::enterToState_ + 0xC2 2021-01-24 22:59:10.101 INFO EDCORE: 0x000000000011BB69 (edCore): Common::FSM::onSymbol_ + 0x1A9 2021-01-24 22:59:10.101 INFO EDCORE: 0x00000000007C3A85 (DCS): CoreUtils::TempFilesManager::operator= + 0x3D1D15 2021-01-24 22:59:10.101 INFO EDCORE: 0x0000000000794834 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A2AC4 2021-01-24 22:59:10.101 INFO EDCORE: 0x0000000000794BF9 (DCS): CoreUtils::TempFilesManager::operator= + 0x3A2E89 2021-01-24 22:59:10.102 INFO EDCORE: 0x00000000018572FC (DCS): AmdPowerXpressRequestHighPerformance + 0xBEA2F8 2021-01-24 22:59:10.102 INFO EDCORE: 0x000000000098462E (DCS): CoreUtils::TempFilesManager::operator= + 0x5928BE 2021-01-24 22:59:10.102 INFO EDCORE: 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14 2021-01-24 22:59:10.102 INFO EDCORE: 0x000000000004D0D1 (ntdll): RtlUserThreadStart + 0x21 2021-01-24 22:59:10.462 INFO EDCORE: Minidump created. Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
BrzI Posted January 25, 2021 Share Posted January 25, 2021 Just to educate myself : This was a failry new driver and I am sure a lot of people still have it. Why would it crash on me ? Any ideas ? Thanks Link to comment Share on other sites More sharing options...
Flappie Posted January 25, 2021 Share Posted January 25, 2021 (edited) Apparently, this driver version was plagued with a lot of issues with other games (flickering, mostly). Also, I've helped another user who had a lot of crashes lately. He was using the same driver version. He thought dusting off his CPU had fixed the issue, but maybe his driver was automatically updated at the same time. Last but not least: each PC is different, hardware-wise (CPU, RAM, OC...) and software-wise (some W10 updates are not mandatory, pagefile size, installed DCS modules, DCS settings, shader cache ...). Edited January 25, 2021 by Flappie Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Recommended Posts