Zergburger Posted May 4, 2023 Share Posted May 4, 2023 log files attached, similar circumstances, in server for prolonged period on MP. dcs.log-20230503-125311.zip dcs.log-20230504-155217.zip Link to comment Share on other sites More sharing options...
-Scrat- Posted May 4, 2023 Share Posted May 4, 2023 Since the last update I also experienced a lot of crash on MP. Link to comment Share on other sites More sharing options...
Flappie Posted May 5, 2023 Share Posted May 5, 2023 @Zergburger Although this doesn't seem to be the first source of your crash, you're having an awful lot of error messages like these in your log: 2023-05-04 14:48:29.934 INFO ASYNCNET (Main): Current ping: 77.2ms 2023-05-04 14:48:30.793 ERROR DX11BACKEND (12100): Failed assert `shader != nullptr && technique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1243 2023-05-04 14:48:30.793 ERROR DX11BACKEND (12100): Failed assert `this->wantedShader != nullptr && this->wantedTechnique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1319 2023-05-04 14:48:30.799 ERROR DX11BACKEND (12100): Failed assert `shader != nullptr && technique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1243 2023-05-04 14:48:30.799 ERROR DX11BACKEND (12100): Failed assert `this->wantedShader != nullptr && this->wantedTechnique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1319 2023-05-04 14:48:30.805 ERROR DX11BACKEND (12100): Failed assert `shader != nullptr && technique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1243 2023-05-04 14:48:30.805 ERROR DX11BACKEND (12100): Failed assert `this->wantedShader != nullptr && this->wantedTechnique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1319 2023-05-04 14:48:30.812 ERROR DX11BACKEND (12100): Failed assert `shader != nullptr && technique != render::INVALID_HANDLE` at Projects\render\dx11backend_win8\Source\DX11Renderer.cpp:1243 Are you using core mods, such as ReShade? If so, disable them and see if DCS keeps crashing. Here's your crash: 2023-05-04 15:52:00.349 INFO ASYNCNET (Main): Current ping: 77.3ms 2023-05-04 15:52:16.762 INFO EDCORE (Main): try to write dump information 2023-05-04 15:52:16.789 INFO EDCORE (Main): # -------------- 20230504-155217 -------------- 2023-05-04 15:52:16.791 INFO EDCORE (Main): DCS/2.8.4.39731 (x86_64; MT; Windows NT 10.0.22621) 2023-05-04 15:52:16.793 INFO EDCORE (Main): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\edObjects.dll 2023-05-04 15:52:16.794 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff9c855f244 00:00000000 2023-05-04 15:52:16.796 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'oihjQ' 2023-05-04 15:52:16.798 INFO EDCORE (Main): OS-Version: 10.0.22621 () 0x100-0x1 2023-05-04 15:52:16.800 INFO EDCORE (Main): 0x000000000001f244 (edObjects): RegStorage::setHostID + 0x11D4 2023-05-04 15:52:16.802 INFO EDCORE (Main): 0x0000000000020449 (edObjects): RegisterManager::Create + 0x8C9 2023-05-04 15:52:16.802 INFO EDCORE (Main): 0x000000000011cb11 (Visualizer): smSceneManager::regLua + 0x32D1 2023-05-04 15:52:16.802 INFO EDCORE (Main): 0x0000000000117720 (Visualizer): smSceneManager::DestroySceneManager + 0xEB70 2023-05-04 15:52:16.802 INFO EDCORE (Main): 0x000000000011c54c (Visualizer): smSceneManager::regLua + 0x2D0C 2023-05-04 15:52:16.802 INFO EDCORE (Main): 0x0000000000874676 (DCS): SW + 0x3DDF66 2023-05-04 15:52:16.803 INFO EDCORE (Main): 0x00000000008959aa (DCS): SW + 0x3FF29A 2023-05-04 15:52:16.803 INFO EDCORE (Main): 0x0000000000853dc4 (DCS): SW + 0x3BD6B4 2023-05-04 15:52:16.803 INFO EDCORE (Main): 0x0000000000854c95 (DCS): SW + 0x3BE585 2023-05-04 15:52:16.803 INFO EDCORE (Main): 0x0000000002359163 (DCS): AmdPowerXpressRequestHighPerformance + 0xFB315F 2023-05-04 15:52:16.803 INFO EDCORE (Main): 0x0000000000c52412 (DCS): SW + 0x7BBD02 2023-05-04 15:52:16.803 INFO EDCORE (Main): 0x00000000000126ad (KERNEL32): BaseThreadInitThunk + 0x1D 2023-05-04 15:52:16.979 INFO EDCORE (Main): Minidump created. Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Zergburger Posted May 6, 2023 Author Share Posted May 6, 2023 (edited) no mods, this was a full vanilla install on a PC i built less than a week ago. Also, do you think you could be so kind as to translate the crash jargon to something approaching english? EDIT: I am running win11 N, and have recently run into issues with other games because of a lack of "Media Feature Pack". Since installing that i have not had another crash @Flappie, it may be a fix........unsure as of now. Edited May 6, 2023 by Zergburger 1 Link to comment Share on other sites More sharing options...
Flappie Posted May 7, 2023 Share Posted May 7, 2023 That is the first time ever I read about the Media Feature Pack solving game issues, yet I see many other games are affected by its absence. Let's wait a few more days before we add the "solved" tag to this thread. 1 Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Hoirtel Posted May 7, 2023 Share Posted May 7, 2023 @Zergburgeraside from the crashing, what's the performance like? Link to comment Share on other sites More sharing options...
skypickle Posted May 7, 2023 Share Posted May 7, 2023 @ZergburgerI assume you know the issue with Ryzen 7000 cooking themselves? It seems that even at default auto settings, the bios sends too much voltage to the memory controller (VSOC). This results in a slow death of the memory controller. the earliest 'safe bios' was just released last week. If you manually set your voltages you could also be safe on earlier bioses. The default memory timings (JEDEC) are slow-something like 4800. I have been using buildzoid's memory timings and they are bullet proof. I tried to push above 6000 using other timings I ended up getting crashes in DCS about 3-5 minutes into any flight. You can read here: https://www.overclock.net/threads/amd-ddr5-oc-and-24-7-daily-memory-stability-thread.1800926/page-150#post-29186749 There is a lot of craziness currently. People are stress testing their memory and it passes only to crash to desktop on idle or in a game. Since I got my chip stable it's been a dream. 140 FPS on a 4k monitor. 4930K @ 4.5, 32g ram, TitanPascal Link to comment Share on other sites More sharing options...
kerlcat Posted May 8, 2023 Share Posted May 8, 2023 Just saw author got this fixed. And realized there is N version of Win11/10 specially for Europe. Also using 7800X3D since it’s launched on day 1. So far it’s great. I won’t try OC and keep it updated with MB so to avoid any risk of burning out. 7800X3D /3090 /64GB /SSD 2T+4T /Quest3<-(Pico4<-Rift S <-Rift CV1) /Orion F18 /DOFReality P6; Win11 Link to comment Share on other sites More sharing options...
Zergburger Posted May 11, 2023 Author Share Posted May 11, 2023 (edited) On 5/7/2023 at 1:41 PM, Hoirtel said: @Zergburgeraside from the crashing, what's the performance like? i have an rtx 4090, 64gb ram @ 6ghz cl30, everything except motion blur is turned to max including 1.5x supersampling. I'm getting 180 fps pinned on multithreading on enigma's coldwar syria, every once in a while it will dip to 170. On 5/7/2023 at 4:31 PM, skypickle said: @ZergburgerI assume you know the issue with Ryzen 7000 cooking themselves? It seems that even at default auto settings, the bios sends too much voltage to the memory controller (VSOC). This results in a slow death of the memory controller. the earliest 'safe bios' was just released last week. If you manually set your voltages you could also be safe on earlier bioses. The default memory timings (JEDEC) are slow-something like 4800. I have been using buildzoid's memory timings and they are bullet proof. I tried to push above 6000 using other timings I ended up getting crashes in DCS about 3-5 minutes into any flight. You can read here: https://www.overclock.net/threads/amd-ddr5-oc-and-24-7-daily-memory-stability-thread.1800926/page-150#post-29186749 There is a lot of craziness currently. People are stress testing their memory and it passes only to crash to desktop on idle or in a game. Since I got my chip stable it's been a dream. 140 FPS on a 4k monitor. yes im fully aware of the issue, I am actually working with GN on the stuff. I am testing the asus 1303 bios, the latest "production" bios Edited May 11, 2023 by Zergburger Link to comment Share on other sites More sharing options...
Zergburger Posted May 11, 2023 Author Share Posted May 11, 2023 On 5/7/2023 at 5:12 PM, kerlcat said: Just saw author got this fixed. And realized there is N version of Win11/10 specially for Europe. Also using 7800X3D since it’s launched on day 1. So far it’s great. I won’t try OC and keep it updated with MB so to avoid any risk of burning out. I am in north america, i just didnt want the windows bloatware on my install. Link to comment Share on other sites More sharing options...
kerlcat Posted May 11, 2023 Share Posted May 11, 2023 43 minutes ago, Zergburger said: I am in north america, i just didnt want the windows bloatware on my install. I see. Anyway non mainstream version would potentially bring some issue we developer not likely to test on is upon release. Good you pinged the root cause anyway. 7800X3D /3090 /64GB /SSD 2T+4T /Quest3<-(Pico4<-Rift S <-Rift CV1) /Orion F18 /DOFReality P6; Win11 Link to comment Share on other sites More sharing options...
Hoirtel Posted May 12, 2023 Share Posted May 12, 2023 8 hours ago, Zergburger said: i have an rtx 4090, 64gb ram @ 6ghz cl30, everything except motion blur is turned to max including 1.5x supersampling. I'm getting 180 fps pinned on multithreading on enigma's coldwar syria, every once in a while it will dip to 170. yes im fully aware of the issue, I am actually working with GN on the stuff. I am testing the asus 1303 bios, the latest "production" bios Good to know, and now the crashing is fixed? I have an x607e-f and 7800X3D, bit worried about what to do! I am on 1303 and no EXPO, system hasn't been running long so haven't tried DCS yet. Thinking of shelving it until things get fixed. Link to comment Share on other sites More sharing options...
kerlcat Posted May 12, 2023 Share Posted May 12, 2023 @Hoirtel If you don't OC or EXPO, then you have nothing to worry about. Some people OC with 1.3v or above...led the burning. I 've being using same CPU from day 1 w/ EXPO & PBO on, rest as default. It's pretty mild OC. If you have concern, then keep everything as it is and you only might miss 2-3% of gain. 7800X3D /3090 /64GB /SSD 2T+4T /Quest3<-(Pico4<-Rift S <-Rift CV1) /Orion F18 /DOFReality P6; Win11 Link to comment Share on other sites More sharing options...
Hoirtel Posted May 12, 2023 Share Posted May 12, 2023 (edited) 1 hour ago, kerlcat said: @Hoirtel If you don't OC or EXPO, then you have nothing to worry about. Some people OC with 1.3v or above...led the burning. I 've being using same CPU from day 1 w/ EXPO & PBO on, rest as default. It's pretty mild OC. If you have concern, then keep everything as it is and you only might miss 2-3% of gain. Kinda need to run expo really or else it's in the toilet perf wise. I haven't yet but considering the only bios that is permitted is dangerous I guess I'll stick to my 9900k until Asus sort themselves out. Might just sell my board and chip cheap on eBay and cut my losses. Knew I should of got 13700k, could of had it months ago too. Edited May 12, 2023 by Hoirtel Link to comment Share on other sites More sharing options...
Flappie Posted May 19, 2023 Share Posted May 19, 2023 @Zergburger Hi, can you confirm your issue was definitely solved by installing the Media Feature Pack? Don't accept indie game testing requests from friends in Discord. Ever. Link to comment Share on other sites More sharing options...
Zergburger Posted May 25, 2023 Author Share Posted May 25, 2023 On 5/19/2023 at 12:31 AM, Flappie said: @Zergburger Hi, can you confirm your issue was definitely solved by installing the Media Feature Pack? I think this is what solved my issue. On 5/12/2023 at 4:42 AM, Hoirtel said: Kinda need to run expo really or else it's in the toilet perf wise. I haven't yet but considering the only bios that is permitted is dangerous I guess I'll stick to my 9900k until Asus sort themselves out. Might just sell my board and chip cheap on eBay and cut my losses. Knew I should of got 13700k, could of had it months ago too. yes i was having a separate blue screen issue outside of DCS that completely went away when i turned expo back on. (this was after i solved the issue that was causing these specific crashes) 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now