Flappie

Thank you. Your track works for me: you did call the radio and the JTAC answered. I then take control over the track and resume the conversation and it keeps working. I tried both with and without Easy comms: it worked with both. We need to find what's wrong with your DCS. Try this: Browse to "Saved Games". Rename your "DCS" folder into "DCS.backup" (do NOT delete anything). Start DCS and enter your credentials. Replay your track or my track and see if there is any change. Once the test is over: Exit DCS. Rename the new "DCS" folder to "DCS.virgin". Rename the "DCS.backup" folder to "DCS. (of course, if your folder is called "DCS.openbeta", rename "DCS.backup" to "DCS.openbeta" once the test is over)

I'm trying hard to reproduce the cut out tail on the Anton, to no avail for now. Was it MP or SP?

Yes, please.

The next update should fix this issue. The date is not known yet.

It's perfectly OK! Especially since you return here with the solution.

I've read users saying the same thing: the CPU apparently behaves perfectly even during intense benchmarking, but as soon as it is asked to run a game, it becomes unstable.

Apparently, Intel pledged to grant RMA to all impacted users.

Please attach a DCS track of this issue.

Do you have a DCS track showing this issue? Or a simple way to reproduce the bug?

@jfri The issue is reported. Here's a workaround in the meantime:

OK, then I'm afraid you need to mess with BIOS settings. What is your motherboard model? Is that an ASUS Z790? We'll try and find solutions from users with the same issue with the same hardware. EDIT: you should try this step by step guide:

Try updating your motherboard:

For some reason, I couldn't see it in your track because the views are wrong, but I understood you wanted me to look under the missiles. Now I can see the issue, thanks. I'm not sure devs will fix this quickly since it's very hard to see, but the video of your mod should help. Issue reported.

That is a very good idea. There was a precedent in the forum where the surge protector was causing CTDs because it limited the power drained by the PC.

I suggest you uninstall then reinstall the AJS37 module. Maybe a Viggen file is damaged, causing all of this. You can also give the DCS cleanup and repair a try.

Your feedback is appreciated.

Hi. The crash stack scream "Viggen bug" (you can see the name of the module DLL in the crash stack, or in the last called functions). Each crash mentions the AJS37 radar. Yet, I've looked at Heatblur's forum and couldn't find any Viggen crash epidemy. Do you have any mod altering the Viggen? #1 2025-02-07 11:44:59.669 ERROR VIGGEN (Main): HeatBlur: Assert failed: - @ C:\repo\trunk\ViggenNew\Sources\Flightmodel\BackupInstruments.cpp:95 2025-02-07 11:46:21.003 WARNING LOG (6732): 1 duplicate message(s) skipped. 2025-02-07 11:46:21.003 WARNING EFFECTS2 (Main): OParticleSystem: preset 'missile' not found in 'volumetricPointLight.lua', using default 2025-02-07 11:46:41.404 WARNING LOG (6732): 1 duplicate message(s) skipped. 2025-02-07 11:46:41.404 ERROR VIGGEN (Main): HeatBlur: Assert failed: - @ C:\repo\trunk\ViggenNew\Sources\Flightmodel\BackupInstruments.cpp:95 2025-02-07 11:47:04.958 WARNING LOG (6732): 15 duplicate message(s) skipped. 2025-02-07 11:47:04.958 WARNING FLIGHT (Main): airdrome release Airdrome 2025-02-07 11:47:04.961 INFO EDCORE (9260): try to write dump information 2025-02-07 11:47:05.281 INFO EDCORE (9260): # -------------- 20250207-114705 -------------- 2025-02-07 11:47:05.282 INFO EDCORE (9260): DCS/2.9.12.5336 (x86_64; MT; Windows NT 10.0.22631) 2025-02-07 11:47:05.283 INFO EDCORE (9260): M:\Eagle Dynamics\DCS World\Mods\aircraft\AJS37\bin\AJS37-Avionics.dll 2025-02-07 11:47:05.283 INFO EDCORE (9260): # C0000005 ACCESS_VIOLATION at 00007ffaa1d84041 00:00000000 2025-02-07 11:47:05.284 INFO EDCORE (9260): SymInit: Symbol-SearchPath: 'M:\Eagle Dynamics\DCS World\bin;', symOptions: 532, UserName: 'JM Costa' 2025-02-07 11:47:05.285 INFO EDCORE (9260): OS-Version: 10.0.22631 () 0x300-0x1 2025-02-07 11:47:05.286 INFO EDCORE (9260): 0x0000000000134041 (AJS37-Avionics): cockpit::AJS37::RadarDevice::initialize + 0x3311 2025-02-07 11:47:05.286 INFO EDCORE (9260): 0x0000000000138f23 (AJS37-Avionics): cockpit::AJS37::RadarDevice::initialize + 0x81F3 2025-02-07 11:47:05.287 INFO EDCORE (9260): 0x0000000000029333 (ucrtbase): _recalloc + 0xA3 2025-02-07 11:47:05.288 INFO EDCORE (9260): 0x000000000001259d (KERNEL32): BaseThreadInitThunk + 0x1D 2025-02-07 11:47:05.925 INFO EDCORE (9260): Minidump created. #2 2025-02-07 22:38:21.761 INFO VIGGEN (Main): External fuel tank jettison button 2025-02-07 22:38:49.696 WARNING LOG (9624): 1 duplicate message(s) skipped. 2025-02-07 22:38:49.696 INFO VIGGEN (Main): Wings over-G 2025-02-07 22:38:49.696 INFO VIGGEN (Main): OUTPUTTING DAMAGE 1.000000 36 2025-02-07 22:38:49.696 INFO VIGGEN (Main): OUTPUTTING DAMAGE 1.000000 35 2025-02-07 22:38:49.708 INFO VIGGEN (Main): Wings over-G 2025-02-07 22:38:49.708 INFO VIGGEN (Main): OUTPUTTING DAMAGE 1.000000 36 2025-02-07 22:38:49.708 INFO VIGGEN (Main): OUTPUTTING DAMAGE 1.000000 35 2025-02-07 22:38:49.713 INFO VIGGEN (Main): Wings over-G 2025-02-07 22:38:49.713 INFO VIGGEN (Main): OUTPUTTING DAMAGE 1.000000 36 2025-02-07 22:38:49.713 INFO VIGGEN (Main): OUTPUTTING DAMAGE 1.000000 35 2025-02-07 22:38:49.773 WARNING FLIGHT (Main): airdrome release Airdrome 2025-02-07 22:38:49.775 INFO EDCORE (2692): try to write dump information 2025-02-07 22:38:49.880 INFO EDCORE (2692): # -------------- 20250207-223850 -------------- 2025-02-07 22:38:49.881 INFO EDCORE (2692): DCS/2.9.12.5336 (x86_64; MT; Windows NT 10.0.22631) 2025-02-07 22:38:49.881 INFO EDCORE (2692): M:\Eagle Dynamics\DCS World\Mods\aircraft\AJS37\bin\AJS37-Avionics.dll 2025-02-07 22:38:49.882 INFO EDCORE (2692): # C0000005 ACCESS_VIOLATION at 00007ffa78454041 00:00000000 2025-02-07 22:38:49.883 INFO EDCORE (2692): SymInit: Symbol-SearchPath: 'M:\Eagle Dynamics\DCS World\bin;', symOptions: 532, UserName: 'JM Costa' 2025-02-07 22:38:49.884 INFO EDCORE (2692): OS-Version: 10.0.22631 () 0x300-0x1 2025-02-07 22:38:49.884 INFO EDCORE (2692): 0x0000000000134041 (AJS37-Avionics): cockpit::AJS37::RadarDevice::initialize + 0x3311 2025-02-07 22:38:49.885 INFO EDCORE (2692): 0x0000000000138f23 (AJS37-Avionics): cockpit::AJS37::RadarDevice::initialize + 0x81F3 2025-02-07 22:38:49.886 INFO EDCORE (2692): 0x0000000000029333 (ucrtbase): _recalloc + 0xA3 2025-02-07 22:38:49.886 INFO EDCORE (2692): 0x000000000001259d (KERNEL32): BaseThreadInitThunk + 0x1D 2025-02-07 22:38:50.278 INFO EDCORE (2692): Minidump created. #3 2025-02-11 20:41:32.490 WARNING LOG (14280): 21 duplicate message(s) skipped. 2025-02-11 20:41:32.490 INFO EDCORE (6784): signal caught: 'Abnormal termination' 2025-02-11 20:41:32.492 INFO EDCORE (6784): try to write dump information 2025-02-11 20:41:32.673 INFO EDCORE (6784): # -------------- 20250211-204133 -------------- 2025-02-11 20:41:32.673 INFO EDCORE (6784): DCS/2.9.12.5336 (x86_64; MT; Windows NT 10.0.22631) 2025-02-11 20:41:32.674 INFO EDCORE (6784): C:\WINDOWS\System32\KERNELBASE.dll 2025-02-11 20:41:32.675 INFO EDCORE (6784): # FFFFFFEA (Unknown exception code) at 00007ffaf7a2fb4c 00:00000000 2025-02-11 20:41:32.676 INFO EDCORE (6784): SymInit: Symbol-SearchPath: 'M:\Eagle Dynamics\DCS World\bin;', symOptions: 532, UserName: 'JM Costa' 2025-02-11 20:41:32.677 INFO EDCORE (6784): OS-Version: 10.0.22631 () 0x300-0x1 2025-02-11 20:41:32.684 INFO EDCORE (6784): 0x000000000005fb4c (KERNELBASE): RaiseException + 0x6C 2025-02-11 20:41:32.685 INFO EDCORE (6784): 0x0000000000006b59 (edCore): ed::current_exception_stack_trace + 0x279 2025-02-11 20:41:32.686 INFO EDCORE (6784): 0x000000000007e6d5 (ucrtbase): raise + 0x1E5 2025-02-11 20:41:32.687 INFO EDCORE (6784): 0x000000000007f6e1 (ucrtbase): abort + 0x31 2025-02-11 20:41:32.687 INFO EDCORE (6784): 0x00000000000059ea (VCRUNTIME140): _purecall + 0x1A 2025-02-11 20:41:32.687 INFO EDCORE (6784): 0x0000000000131622 (AJS37-Avionics): cockpit::AJS37::RadarDevice::initialize + 0x8F2 2025-02-11 20:41:32.687 INFO EDCORE (6784): 0x00000000001340e4 (AJS37-Avionics): cockpit::AJS37::RadarDevice::initialize + 0x33B4 2025-02-11 20:41:32.687 INFO EDCORE (6784): 0x0000000000138f23 (AJS37-Avionics): cockpit::AJS37::RadarDevice::initialize + 0x81F3 2025-02-11 20:41:32.687 INFO EDCORE (6784): 0x0000000000029333 (ucrtbase): _recalloc + 0xA3 2025-02-11 20:41:32.688 INFO EDCORE (6784): 0x000000000001259d (KERNEL32): BaseThreadInitThunk + 0x1D 2025-02-11 20:41:33.228 INFO EDCORE (6784): Minidump created.

@Istari6 I've just found this solved thread for another user with the same issue. You both have a 14900 CPU. Can you try what is suggested?

I don't have many ideas because your crash isn't written in the log file. It ends abruptly. But I've just come across this interesting thread: same symptom, same CPU. You should take a close look. Have you already tried what @sleighzy has suggested, especially these below? Disable Game Mode Disable Hardware accelerated GPU scheduling Disable Core Isolation You can also try these, which helped users with the same symptom: In the BIOS, set Min/Max Cache Ratio to "Auto", if you have such an option. Ensure Windows Power mode is set to High Performance. Ensure no drive is full or nearly full (especially your system drive and your DCS drive). Disable HPET. autoexec.cfg By the way, here's another user with the same issue, and the same CPU. Not solved yet.

I've just found an internal report. The issue was reported internally a few months ago.

Crash reproduced. Issue reported.

Thanks for your feedback. Chances are the MB-339 module tries to read/write in this folder, "Saved Games\DCS\Config\MB339", but cannot handle special characters. I'll give it a try then report the issue to the third party if I'm able to reproduce the crash.

Then I have no idea what's happening. Maybe a custom script (from Saved Games/DCS.../Scripts) is messing with your settings while you play? (you can rename this "Scripts" folder to "Scripts_bak" before starting DCS in order to neutralize it temporarily).

The exception code found in your Event viewer is "0xc00000fd", stack overflow, which means your system ran out of memory. Your PC has 64GB of RAM, which should be enough for DCS. Try lowering DCS Preload Radius value (it's 150 000 - make it 60 000 which is default), and it this help, start looking at your memory OC settings.

There is no tracks attached to this thread. Please provide short tracks, one from the server, another from a client. Missile desync is often caused by latency. Tracks will help determine the cause of the issue.