solved DCS OB Crashes my whole computer causing restart- seems to be only in MP

[Soul-TRAIN]

Hi im really frustrated it seems like every time i get on the Growling Sidewinder MP server after a few sorties, my whole PC crashes with a high pitched squeaky noise through the audio as it freezes then restarts my whole machine. Any ideas? I have attached my DCS logs.
My setup is 12700k 64gb ram 3080 12gb running basic programs while dcs is running, track IR, winwing simapp, pagefile set to 32 gb, deleted metashaters and fxo not sure what else i should try.  

I believe the crash that I am referring to is located in the Dcs.log OLD file somewhere around the 19.37 mark from what I can tell.

Does anyone know how to review these files and tell me what may be happening to my pc?
 
dcs.20230105-182627.dmp dcs.log dcs.log.old dcs.20230105-182627.crash

[Flappie]

Hi. Your dcs.log file does not show any crash. However, reading your .crash file makes me think that your middle mouse button may be the source of your crash ("cockpit::ccMouseHandler::onMiddleButtonDblclk"):

# -------------- 20230105-182627 --------------
DCS/2.8.1.34667 (x86_64; Windows NT 10.0.19045)
D:\DCS World OpenBeta\bin\WorldGeneral.dll
# C0000005 ACCESS_VIOLATION at 4F1CA1EA 00:00000000
SymInit: Symbol-SearchPath: '.;D:\DCS World OpenBeta;D:\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'msoti'
OS-Version: 10.0.19045 () 0x300-0x1
0x00000000000EA1EA (WorldGeneral): Mission::Track::addEvent + 0x5A
0x00000000000AB626 (WorldGeneral): ActionDispatcher::writeToTrack_ + 0xB6
0x00000000000AB513 (WorldGeneral): ActionDispatcher::process_ + 0x113
0x00000000000AAE26 (WorldGeneral): ActionDispatcher::dispatch + 0x16
0x00000000001DA43F (CockpitBase): cockpit::ccMouseHandler::dispatchAnalog_ + 0x4F
0x000000000037F9A2 (CockpitBase): cockpit::c_draw_debug_cockpit_tripod + 0x4F72
0x00000000001DAD68 (CockpitBase): cockpit::ccMouseHandler::onMiddleButtonDblclk + 0x1B8
0x000000000001C340 (dxgui): gui::GUI::onMouseMoveMessage + 0x40
0x000000000001CA1B (dxgui): gui::GUI::processMessages + 0xDB
0x000000000081185D (DCS): SW + 0x3D1C3D
0x00000000008116AE (DCS): SW + 0x3D1A8E
0x00000000008320B9 (DCS): SW + 0x3F2499
0x00000000007F16F4 (DCS): SW + 0x3B1AD4
0x00000000007F25C4 (DCS): SW + 0x3B29A4
0x000000000227561A (DCS): AmdPowerXpressRequestHighPerformance + 0xF48616
0x0000000000BDFBA2 (DCS): SW + 0x79FF82
0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
0x00000000000526A1 (ntdll): RtlUserThreadStart + 0x21

 

I guess the next question is: do you use your middle mouse button in DCS, and if so, what does it do?

[Soul-TRAIN]

I really don’t use any mouse button other than the left clicker. My mouse is a redragon wireless guy with a huge array of buttons and I’m sure I am accidentally pressing them mid flight inadvertently. How can I find out which button is that one? Picture of my mouse attached


Sent from my iPhone using Tapatalk

[Flappie]

I'd say your "middle mouse button" is the one that acivates when you press the scrollwheel.

If this issue really is caused by a mouse button double click, chances are you can easily reproduce the crash. Try running an instant action mission starting in the air with the aircraft you usually fly when DCS crashes, then try double-clicking each one of your mouse buttons.

Edited January 6, 2023 by Flappie

[Soul-TRAIN]

i cant really seem to recreate with the mouse buttons either in SP or MP modes. And i was pressing everything on a busy server. Anything else i can check? other logs from windows etc? i just updated nvidia graphic driver today and not sure if this was part of the issue or not.

Edited January 7, 2023 by Soul-TRAIN

[Flappie]

I'm pretty sure it's not a graphics issue. Let's take a closer look.

In a crash stack, the latest event is on top. To make it easier, I reversed the crash stack (latest event is at the bottom).

0x00000000000526A1 (ntdll): RtlUserThreadStart + 0x21  --> Gibberish for us, mere mortals
0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14  --> Beep, boop
0x0000000000BDFBA2 (DCS): SW + 0x79FF82  --> Boop, beep, beep
0x000000000227561A (DCS): AmdPowerXpressRequestHighPerformance + 0xF48616 --> I see this all the time, for all kind of crashes, don't pay attenton to it
0x00000000007F25C4 (DCS): SW + 0x3B29A4  --> Beep, boop
0x00000000007F16F4 (DCS): SW + 0x3B1AD4  --> Beep, boop
0x00000000008320B9 (DCS): SW + 0x3F2499  --> Boop, beeeeeeep
0x00000000008116AE (DCS): SW + 0x3D1A8E  --> Oh, hello R2!
0x000000000081185D (DCS): SW + 0x3D1C3D  --> Beautiful day, isn't it?
0x000000000001CA1B (dxgui): gui::GUI::processMessages + 0xDB  --> It's getting interesting. It's about GUI (the sim interface) and messages.
0x000000000001C340 (dxgui): gui::GUI::onMouseMoveMessage + 0x40  --> Now it's GUI + mouse movement. We're getting there.
0x00000000001DAD68 (CockpitBase): cockpit::ccMouseHandler::onMiddleButtonDblclk + 0x1B8  --> Very precise: the sim is dealing with a double-click event on a middle mouse button which seems to interact with the cockpit.
0x000000000037F9A2 (CockpitBase): cockpit::c_draw_debug_cockpit_tripod + 0x4F72  --> No idea what this is.
0x00000000001DA43F (CockpitBase): cockpit::ccMouseHandler::dispatchAnalog_ + 0x4F  --> Still dealing with mouse event.
0x00000000000AAE26 (WorldGeneral): ActionDispatcher::dispatch + 0x16  --> We went from CockpitBase to WorldGeneral and it's about some action.
0x00000000000AB513 (WorldGeneral): ActionDispatcher::process_ + 0x113  --> The action is being "processed".
0x00000000000AB626 (WorldGeneral): ActionDispatcher::writeToTrack_ + 0xB6  --> The action gets written in the mission track
0x00000000000EA1EA (WorldGeneral): Mission::Track::addEvent + 0x5A  --> The latest thing DCS was doing before the crash was adding an event data to the mission track
...
# C0000005 ACCESS_VIOLATION at 4F1CA1EA 00:00000000   --> The most frequent cause for crashes, it won't help us.
D:\DCS World OpenBeta\bin\WorldGeneral.dll   --> DCS, not Windows, nor your GPU driver.

OK, so maybe it's not really about your middle mouse button, but rather abour track recording. If you never use DCS tracks, try this:

Go to "Saved Games/DCS.../Config".

Look for a "autoexec.cfg" file and add this line into it : disable_write_track = true

If you don't have an "autoexec.cfg" file, dowload this one:

autoexec.cfg

Edited January 7, 2023 by Flappie

[Soul-TRAIN]

Ok I will try disabling the tracks as recommended. Will disabling it prevent Tacview files from working?


Sent from my iPhone using Tapatalk

[Flappie]

3 hours ago, Soul-TRAIN said:

Ok I will try disabling the tracks as recommended. Will disabling it prevent Tacview files from working?

No, Tacview has its own recorder.

[Soul-TRAIN]

Following back up here, updated nvidia driver and removed Tacview recording (I rarely use tacview anyways in MP) before i decided to go into the track recording modification and I flew for hours on Sunday with no issues on bigger servers. Thx for the help Flappie.


Sent from my iPhone using Tapatalk

[Flappie]

Thanks for your feedback. I'm glad I could help. It is strange though that the track recording could cause DCS to crash. It's quite unusual.

[Soul-TRAIN]

Flappie- well i thought the track recording is what the culprit was and then the last couple of days the crashing happens again after 30-40 min of multiplayer session. 2 different servers. All is fine was doing carrier opps and crashed during landing right when i was picking up the hornet ball. Whole system restart. I have Tacview installed but recording for SP/MP turned off in the options menu. I do notice that DCS is still recording my MP tracks somehow. The crash seems to always happen in MP and reboots the entire system. Windows event viewer log doesnt state anything that i can see is helpful, other than a critical Power Kernel Failure or something like that. Attached is the recent DCS event log. This issue has seemed to pop up again since the last update. Any ideas?

dcs.log

[Flappie]

Hi. If your system reboots, it's somethnig beyond DCS. It's either a hardware fault or a driver issue.

Try this:

• "sfc /scannow" (guide) to repair your drives
• "DISM /Online /Cleanup-Image /RestoreHealth" (guide) to repair Windows
• Reinstall your SSD drivers
• Try another PSU if you have a spare

[Soul-TRAIN]

Ok I’ll try those steps. Thanks. I just noticed my Nvidia game driver wasn’t up to date either so updating that also. Do you find the Nvidia drivers sensitive to DCS at all?


Sent from my iPhone using Tapatalk

[Flappie]

7 hours ago, Soul-TRAIN said:

Ok I’ll try those steps. Thanks. I just noticed my Nvidia game driver wasn’t up to date either so updating that also. Do you find the Nvidia drivers sensitive to DCS at all?

On my end, not really since I own an old 1080Ti. I see you're using a 3080, which is way more recent. Some driver versions are not that stable with DCS, it's true.

But in your case, I'm seeing DCS file errors in your log, and since broken DCS files cannot in anyway reboot your PC, I'm thinking maybe one of your drive is faulty. The commands above should fix any potential drive issue, any potential Windows file issue.