Lykurgus Posted July 4, 2023 Posted July 4, 2023 I seem to get a lot of Random CTD and BSOD with Memory Management now which is a new development within the last 2 weeks. Tonight it happened when I went to use the f10 map while in flight. Last night it happened while nearly stopped after landing at nellis. Everything started to get very choppy and then BSOD after about an hour of flight which went great up until then. These have been happening while flying the F15E and I do use MT. i7 12700k, msi mpg z690 edge wifi ddr4, 2x 16gb cl16 gskill ripjaw 3600, gigabyte gtx 3080 gaming oc 10g, samsung 970 evo plus 2tb, corsair aio cooler hi150, hp g2 headset, corsair rm 1000x 80plus gold power supply dcs.log.old dcs.log dcs.log-20230704-015758.zip debrief.log dcs.20230702-040517.crash dcs.20230702-040517.dmp
Flappie Posted July 4, 2023 Posted July 4, 2023 Hi, there's an ongoing freeze issue with Intel CPUs, especially with i7 12700 and i9 13900. It seems to be caused by a "conflict" between current OB and Hyperthreading. Your crash is very unusual, and I keep seeing new crashes in this part of the forum. I'm starting to think these crashes are induced by this Hyperthreading intolerance. I suggest you disable Hyperthreading in your PC BIOS (that would be very interesting to determine whether HT causes DCS to crash or not) or simply use DCS ST. ---
Lykurgus Posted July 4, 2023 Author Posted July 4, 2023 8 hours ago, Flappie said: Hi, there's an ongoing freeze issue with Intel CPUs, especially with i7 12700 and i9 13900. It seems to be caused by a "conflict" between current OB and Hyperthreading. Your crash is very unusual, and I keep seeing new crashes in this part of the forum. I'm starting to think these crashes are induced by this Hyperthreading intolerance. I suggest you disable Hyperthreading in your PC BIOS (that would be very interesting to determine whether HT causes DCS to crash or not) or simply use DCS ST. I will give it a shot. Also do you think I should turn hardware accelerated graphics scheduling off. It does seem like there is some kind of an issue developing with the crashes. Even in the group I fly with there has been a massive uptick. I have been playing dcs on this exact rig for a year and a half without issue until very recently .
Flappie Posted July 4, 2023 Posted July 4, 2023 40 minutes ago, Lykurgus said: I will give it a shot. Also do you think I should turn hardware accelerated graphics scheduling off. It does seem like there is some kind of an issue developing with the crashes. Even in the group I fly with there has been a massive uptick. I have been playing dcs on this exact rig for a year and a half without issue until very recently . Windows HAGS has various results. If you don't see any improvement when turning it on, set it back to off. It does nothing on my rig. Please let me know if disabling HT helps. 1 ---
Lykurgus Posted July 6, 2023 Author Posted July 6, 2023 On 7/4/2023 at 11:21 AM, Flappie said: Windows HAGS has various results. If you don't see any improvement when turning it on, set it back to off. It does nothing on my rig. Please let me know if disabling HT helps. Disabling HT did not help.
Lykurgus Posted July 6, 2023 Author Posted July 6, 2023 On 7/4/2023 at 11:21 AM, Flappie said: Windows HAGS has various results. If you don't see any improvement when turning it on, set it back to off. It does nothing on my rig. Please let me know if disabling HT helps. Also all my temps were all good. Tonight was really weird. I had two Bsod. 1 happened a hard black screen and then my computer restarted. When it turned back on I went in and flew for about 20 mins. This time I had what seemed a micro stutter and then dcs said it had crashed. But I was still flying. So I alt tabbed back in and kept going for about another 5 mins. Then another Dcs has crashed. I kept flying through that one as well for another 20 mins. Then I finally had a BSOD with a crash restart. dcs.log dcs.log-20230706-031310.zip dcs.log-20230706-031049.zip
Flappie Posted July 6, 2023 Posted July 6, 2023 (edited) It says "something went wrong with prefetch virtual memory". 2023-07-06 03:13:09.085 INFO ARF (6432): Unknown NCTR : 1,1,5,340 B_737 2023-07-06 03:13:09.418 WARNING LOG (10864): 7 duplicate message(s) skipped. 2023-07-06 03:13:09.418 ERROR EDCORE (16376): Something went wrong with PrefetchVirtualMemory. 2023-07-06 03:13:09.482 INFO EDCORE (16376): try to write dump information 2023-07-06 03:13:09.496 INFO EDCORE (16376): # -------------- 20230706-031310 -------------- 2023-07-06 03:13:09.497 INFO EDCORE (16376): DCS/2.8.6.41363 (x86_64; MT; Windows NT 10.0.22621) 2023-07-06 03:13:09.498 INFO EDCORE (16376): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\edCore.dll 2023-07-06 03:13:09.499 INFO EDCORE (16376): # C0000005 ACCESS_VIOLATION at 00007ffc1962e4ba 00:00000000 2023-07-06 03:13:09.500 INFO EDCORE (16376): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'emkni' 2023-07-06 03:13:09.500 INFO EDCORE (16376): OS-Version: 10.0.22621 () 0x100-0x1 2023-07-06 03:13:09.501 INFO EDCORE (16376): 0x000000000006e4ba (edCore): mmfMemoryBlockPrefetch + 0xAA 2023-07-06 03:13:09.502 INFO EDCORE (16376): 0x000000000006d47f (edCore): mmfMemoryBlockPreload + 0x2F 2023-07-06 03:13:09.502 INFO EDCORE (16376): 0x0000000000070568 (edterrain4): landscape4::GeometrySource::preload + 0x78 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x000000000007b26b (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x65ECB 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x00000000000d66c5 (edterrainGraphics41): createInstancerRenderable + 0x38895 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x0000000000033c39 (edCore): ed::this_thread::yield + 0xB59 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x0000000000049228 (edCore): ed::this_thread::yield + 0x16148 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x00000000000126ad (KERNEL32): BaseThreadInitThunk + 0x1D 2023-07-06 03:13:09.962 INFO EDCORE (16376): Minidump created. Before and after the "crash", your log keeps saying the F-15E NCTR cannot recognize civilian aircraft from the mods you have (A320, B757...). Can you try and disable the civilian aircraft mod, then see if it keeps crashing? Also, since you had a hard reboot and the log mentions the memory, you should check your RAM using MemTest86. Edited July 6, 2023 by Flappie typo ---
Lykurgus Posted July 6, 2023 Author Posted July 6, 2023 11 hours ago, Flappie said: It says "something went wrong with prefetch virtual memory". 2023-07-06 03:13:09.085 INFO ARF (6432): Unknown NCTR : 1,1,5,340 B_737 2023-07-06 03:13:09.418 WARNING LOG (10864): 7 duplicate message(s) skipped. 2023-07-06 03:13:09.418 ERROR EDCORE (16376): Something went wrong with PrefetchVirtualMemory. 2023-07-06 03:13:09.482 INFO EDCORE (16376): try to write dump information 2023-07-06 03:13:09.496 INFO EDCORE (16376): # -------------- 20230706-031310 -------------- 2023-07-06 03:13:09.497 INFO EDCORE (16376): DCS/2.8.6.41363 (x86_64; MT; Windows NT 10.0.22621) 2023-07-06 03:13:09.498 INFO EDCORE (16376): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\edCore.dll 2023-07-06 03:13:09.499 INFO EDCORE (16376): # C0000005 ACCESS_VIOLATION at 00007ffc1962e4ba 00:00000000 2023-07-06 03:13:09.500 INFO EDCORE (16376): SymInit: Symbol-SearchPath: 'C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'emkni' 2023-07-06 03:13:09.500 INFO EDCORE (16376): OS-Version: 10.0.22621 () 0x100-0x1 2023-07-06 03:13:09.501 INFO EDCORE (16376): 0x000000000006e4ba (edCore): mmfMemoryBlockPrefetch + 0xAA 2023-07-06 03:13:09.502 INFO EDCORE (16376): 0x000000000006d47f (edCore): mmfMemoryBlockPreload + 0x2F 2023-07-06 03:13:09.502 INFO EDCORE (16376): 0x0000000000070568 (edterrain4): landscape4::GeometrySource::preload + 0x78 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x000000000007b26b (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x65ECB 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x00000000000d66c5 (edterrainGraphics41): createInstancerRenderable + 0x38895 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x0000000000033c39 (edCore): ed::this_thread::yield + 0xB59 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x0000000000049228 (edCore): ed::this_thread::yield + 0x16148 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 2023-07-06 03:13:09.503 INFO EDCORE (16376): 0x00000000000126ad (KERNEL32): BaseThreadInitThunk + 0x1D 2023-07-06 03:13:09.962 INFO EDCORE (16376): Minidump created. Before and after the "crash", your log keeps saying the F-15E NCTR cannot recognize civilian aircraft from the mods you have (A320, B757...). Can you try and disable the civilian aircraft mod, then see if it keeps crashing? Also, since you had a hard reboot and the log mentions the memory, you should check your RAM using MemTest86. Wouldn’t virtual memory be the SSD and or the GPU? I didn’t use memtest86 but I did do the HCI memory tester to 300 percent without a single error on the memory.
Flappie Posted July 6, 2023 Posted July 6, 2023 1 hour ago, Lykurgus said: I did do the HCI memory tester to 300 percent without a single error on the memory. I didn't know about this utility. 1 hour ago, Lykurgus said: Wouldn’t virtual memory be the SSD and or the GPU? This function seems to be used to transfer data from pagefile to memory. Look at this thread: Same error. One of the RAM stick was faulty. You should do the test. ---
Lykurgus Posted July 8, 2023 Author Posted July 8, 2023 On 7/6/2023 at 3:20 PM, Flappie said: I didn't know about this utility. This function seems to be used to transfer data from pagefile to memory. Look at this thread: Same error. One of the RAM stick was faulty. You should do the test. I ram memtest86 and one of my sticks had indeed gone bad. I have yet to try with new ram but thank you for pushing me over the edge to do the memtest86. I was just being lazy not wanting to spend a whole night testing it.
Recommended Posts