Jump to content

DCS Randomly Freezes PC

Shimakaze514

By Shimakaze514
in Game Crash

 Share

Recommended Posts

Shimakaze514

Shimakaze514

Posted
Posted

When I enter the main game interface, select the Multiplayer tab, and let it refresh itself, DCS freezes the entire system several times. It seems that it always freezes for tens of seconds when a new server is refreshed and the UI is updated. When all servers are refreshed and the refresh arrow on the top stops spinning, it will freeze for several minutes. When it freezes, I can't move the mouse, can't switch windows, and the monitor screen is frozen. I first encountered this problem a few days ago and tried reinstalling DCS, reinstalling the graphics driver, doing a windows update, and reinstalling the motherboard and CPU firmware, but none of them improved it. I used Process Monitor to observe and analyze and saw the CPU usage during the frozen time is 435%

QHD)U4`0UJ94~F1V2(R9N8W.png

Shimakaze514

Shimakaze514

Posted
  • Author
Posted

The timing of the freeze seems completely random, it could be triggered at the main menu, during the server fresh and after the server refresh is completed. The duration of the freeze is not fixed, from seconds to minutes. I can't do anything with DCS opened in the background, it will freeze my PC randomly. Even when I was typing here, my PC was frozen 4 times, each lasted about 2 minutes. Here is a video recording the situation:

Shimakaze514

Shimakaze514

Posted
  • Author
Posted

When DCS is off, my PC never freezes. It is running smoothly with other games such as WarThunder, World of Warships, Microsoft Flight Simulator 2020, and Squad. All of those games are as or more CPU consuming as/than DCS, so I don't think it is a hardware issue of my PC.

 

My PC spec (Lenovo Legion Y7000p 2024 Laptop):

  • Operating System: Windows 11 (Build 22631.5189)
  • CPU: Intel i7-14700HX
  • GPU: Nvidia RTX 4070 Laptop
  • RAM: 16GB

Repaird DCS, still randomly freezes

image_50.png

silverdevil

silverdevil

Posted
Posted
7 minutes ago, Shimakaze514 said:

When DCS is off, my PC never freezes. It is running smoothly with other games such as WarThunder, World of Warships, Microsoft Flight Simulator 2020, and Squad. All of those games are as or more CPU consuming as/than DCS, so I don't think it is a hardware issue of my PC.

 

My PC spec (Lenovo Legion Y7000p 2024 Laptop):

  • Operating System: Windows 11 (Build 22631.5189)
  • CPU: Intel i7-14700HX
  • GPU: Nvidia RTX 4070 Laptop
  • RAM: 16GB

Repaird DCS, still randomly freezes

hello. you should post your DCS.LOG from saved games. also, if true, 16 GB is likely your issue. it is low end, if not under minimum requirements. also check to see if you have exception in your AV software.

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

dutchili

dutchili

Posted
Posted

This occurs even with a high-end PC, especially in VR.

Sounds like a classic programming issue where the graphical representation is linked to the actual work (getting server data). If the latter is delayed, so is the UI en 'user input'.

The gameplay has the same issue (so it seems) where FPS and 'mission complexity' are tightly coupled.

  • Like 1
Shimakaze514

Shimakaze514

Posted
  • Author
Posted
21 minutes ago, Pillowcat said:

Most probably: core parking issue, second: had run with admin rights, else: yet some variants exists

Thanks for the info, it is kind of a relief to see I'm not alone in having this annoying freezing issue. I have installed Process Lasso and Park Control, but random freeze still occurs after I set the core affinity of DCS to 0-15 in Process Lasso and disable core parking in Park Control. I don't have DCS running in administrator mode, it is launched via the default shortcut created on the desktop at installation. However, I did find 2 CPU cores with a 100% usage rate when I'm running DCS, and I have now disabled them. Sadly, right after a few minutes, I encountered another freeze.

sleighzy

sleighzy

Posted
Posted (edited)
50 minutes ago, Shimakaze514 said:

Thanks for the info, it is kind of a relief to see I'm not alone in having this annoying freezing issue. I have installed Process Lasso and Park Control, but random freeze still occurs after I set the core affinity of DCS to 0-15 in Process Lasso and disable core parking in Park Control. I don't have DCS running in administrator mode, it is launched via the default shortcut created on the desktop at installation. However, I did find 2 CPU cores with a 100% usage rate when I'm running DCS, and I have now disabled them. Sadly, right after a few minutes, I encountered another freeze.

You need to attach a DCS log file for review as it may provide more insights as to the root cause. I also wouldn’t just start disabling CPU cores if you see them at 100% as you’re reducing the amount of processing power of your PC. The menu etc. is also not multithreaded so results will vary.

If disabling half your CPU with Process Lasso didn’t solve your problem then I would revert that change for now. It may mask further underlying problems. Revisit it if needed. Provide a log first. 

Edited by sleighzy

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Mr_sukebe

Mr_sukebe

Posted
Posted

Can I please suggest that you take a scan here:

 

7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat 

Wizard_03

Wizard_03

Posted
Posted
17 hours ago, Shimakaze514 said:

Thanks for the info, it is kind of a relief to see I'm not alone in having this annoying freezing issue. I have installed Process Lasso and Park Control, but random freeze still occurs after I set the core affinity of DCS to 0-15 in Process Lasso and disable core parking in Park Control. I don't have DCS running in administrator mode, it is launched via the default shortcut created on the desktop at installation. However, I did find 2 CPU cores with a 100% usage rate when I'm running DCS, and I have now disabled them. Sadly, right after a few minutes, I encountered another freeze.

I'm experiencing full PC freeze when DCS starts. A solution that has been working for me is to, before opening the game, delete metashaders2 and FXO files in saved games folder, perform a short repair of DCS and finally perform a cleanup from the launcher, and then DCS runs great for me. I

 

Its only a workaround though, the last major update (the one that introduced save functionality) clearly borked something, that or its some kind of driver issue or both, the new NVIDIA driver has lots of issues with multiple games. My latest log is attached which is from a session where the game froze shortly after starting, shows no errors. The log analyzer in DCS discord recommends rolling back GPU drivers.

dcs.log

  • Like 1

DCS F/A-18C :sorcerer:

Shimakaze514

Shimakaze514

Posted
  • Author
Posted

After the 2.9.15 update, the freezing problem is more serious. Before, there was only a chance of freezing on the main menu page, and if you continued to operate quickly, you could still enter the multiplayer server and play. Now there is a high probability of continuous freezing on the main menu page, and even if you click directly into the multiplayer page, it will freeze when refreshing the server. I just encountered a freeze on the multiplayer page, which lasted for dozens of minutes, and then the computer automatically restarted with a black screen. This is the first time that the computer cannot automatically recover from a freeze. I checked the event log, maybe this will help. It says DCS raised an error called "Top level window is idle".

image_54.png

Thanks to this automatic reboot, it generated a minidump file, after I analyzed it using windbg, it showed that the driver UsbHub3.sys caused the computer to crash, I think this may be the reason. I will try to fix it now and post the fix method later 

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffc704420b8c40, Physical Device Object of the stack
Arg3: ffffd88d2ec9f738, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc7044a081810, The blocked IRP

Debugging Details:
------------------

Implicit thread is now ffffc704`356cc040
*** WARNING: Check Image - Checksum mismatch - Dump: 0x20b7be, File: 0x20b850 - C:\ProgramData\Dbg\sym\BTHport.sys\7A9A74EE202000\BTHport.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1203

    Key  : Analysis.Elapsed.mSec
    Value: 55878

    Key  : Analysis.IO.Other.Mb
    Value: 15

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 47

    Key  : Analysis.Init.CPU.mSec
    Value: 281

    Key  : Analysis.Init.Elapsed.mSec
    Value: 62131

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 181

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27793.1000

    Key  : Analysis.Version.Description
    Value: 10.2410.02.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2410.2.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 0x1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x9F_3_UsbHub3!HUBPDO_EvtDeviceD0Exit

    Key  : Failure.Hash
    Value: {00e27064-02f5-d601-a099-ac4f455b9037}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffc704420b8c40

BUGCHECK_P3: ffffd88d2ec9f738

BUGCHECK_P4: ffffc7044a081810

FILE_IN_CAB:  041825-11859-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc704356cc040

DRVPOWERSTATE_SUBCODE:  3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffd88d`2ea16640 fffff805`3544883d     : 00000000`00000000 00000000`00000000 ffffa300`14d91180 ffffa300`14d91180 : nt!KiSwapContext+0x76
ffffd88d`2ea16780 fffff805`354b881f     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc704`356cc040 : nt!KiProcessDeferredReadyList+0x29d
ffffd88d`2ea16af0 fffff805`354b67ac     : ffffa300`00000000 00000000`00000000 ffffa300`14d91180 fffff805`354ce347 : nt!KeSetSystemGroupAffinityThread+0xff
ffffd88d`2ea16b60 fffff805`354fdd5b     : 00000000`00000104 ffffd88d`00000000 00000000`00000000 00000000`00000104 : nt!KeGenericProcessorCallback+0x114
ffffd88d`2ea16d30 fffff805`3a7d47ae     : ffffc704`420e58f0 00000000`00000000 ffffc704`420e5a40 00000000`00000000 : nt!KeFlushQueuedDpcs+0x10b
ffffd88d`2ea16fb0 fffff805`3a7c577e     : ffffc704`46c3b001 00000000`00000500 ffffd88d`2ea170b9 00000000`00000000 : Wdf01000!FxTimer::Stop+0xf022 [minkernel\wdf\framework\shared\core\fxtimer.cpp @ 757] 
ffffd88d`2ea17010 fffff805`64809f12     : ffffc704`420e58f0 ffffd88d`2ea170b9 00000000`00000003 ffffffff`dc3cba00 : Wdf01000!imp_WdfTimerStop+0x3e [minkernel\wdf\framework\shared\core\fxtimerapi.cpp @ 294] 
ffffd88d`2ea17040 fffff805`3a82cc73     : ffffd88d`2ea17460 ffffc704`47137d98 ffffc704`46cd2060 ffffc704`47137820 : UsbHub3!HUBPDO_EvtDeviceD0Exit+0x352
ffffd88d`2ea17120 fffff805`3a7cff2a     : ffffc704`47137d98 00000000`00000004 ffffc704`47137a00 00000000`00000300 : Wdf01000!FxPnpDeviceD0Exit::InvokeClient+0x23 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 285] 
ffffd88d`2ea17180 fffff805`3a82ef6c     : 00000000`00000000 00000000`00000003 00000000`00000003 ffffc704`47137820 : Wdf01000!FxPrePostCallback::InvokeStateless+0x32 [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 408] 
ffffd88d`2ea171b0 fffff805`3a82edab     : ffffc704`47137820 ffffd88d`2ea17350 fffff805`3a84dd60 ffffd88d`2ea17460 : Wdf01000!FxPkgPnp::PowerGotoDxIoStoppedCommon+0x178 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3100] 
ffffd88d`2ea17220 fffff805`3a82e9c0     : ffffc704`47137820 ffffd88d`2ea17350 00000000`00000420 00000000`00000000 : Wdf01000!FxPkgPnp::PowerGotoDxIoStoppedArmedForWake+0xb [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3195] 
ffffd88d`2ea17250 fffff805`3a82f997     : 00000000`00000000 ffffc704`47137a00 00000000`00001000 00000000`00000420 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x194 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1699] 
ffffd88d`2ea17390 fffff805`3a82f7c4     : ffffc704`47137820 00000000`00000000 ffffd88d`2ea17500 ffffa300`14d91180 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x177 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1613] 
ffffd88d`2ea17410 fffff805`3a840499     : 00000000`00000000 00000000`00000001 ffffd88d`2ea17580 ffffd88d`2ea17590 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1c0 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1394] 
ffffd88d`2ea174a0 fffff805`3a8409d1     : ffffc704`47137820 ffffc704`46cd21d0 00000000`00000004 00000000`00000000 : Wdf01000!FxPkgPdo::DispatchDeviceSetPower+0xe5 [minkernel\wdf\framework\shared\irphandlers\pnp\pdopower.cpp @ 216] 
ffffd88d`2ea174f0 fffff805`3a7c7a94     : ffffc704`47137820 ffffc704`46cd21d0 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPdo::_DispatchSetPower+0x21 [minkernel\wdf\framework\shared\irphandlers\pnp\pdopower.cpp @ 91] 
ffffd88d`2ea17520 fffff805`3a7fe02e     : ffffc704`4a081810 ffffc704`4a081810 ffffc704`46cd2060 ffffc704`4a081c88 : Wdf01000!FxPkgPnp::Dispatch+0xd4 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 771] 
ffffd88d`2ea17590 fffff805`3a7fdf75     : ffffc704`4a081810 ffffc704`46cd21d0 ffffc704`46cd2060 00000000`00000000 : Wdf01000!DispatchWorker+0x9a [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1590] 
ffffd88d`2ea175c0 fffff805`3a7f455f     : ffffc704`41fb69a0 ffffc704`46c3b0d0 ffffc704`4a081810 00000000`00000000 : Wdf01000!FxDevice::DispatchPreprocessedIrp+0xa1 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1652] 
ffffd88d`2ea17600 fffff805`64807d75     : ffffc704`46cd2060 ffffc704`4a081810 000038fb`b932df98 fffff805`35646f06 : Wdf01000!imp_WdfDeviceWdmDispatchPreprocessedIrp+0xef [minkernel\wdf\framework\shared\core\km\fxdeviceapikm.cpp @ 258] 
ffffd88d`2ea17640 fffff805`3a7fe7b8     : ffffc704`4a081810 00000000`00000016 00000000`00000001 ffffc704`46cd2060 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPnPPowerPreprocess+0x435
ffffd88d`2ea17690 fffff805`3a7cb964     : ffffc704`4a081810 ffffc704`46cf5860 00000000`00000001 00000000`00000000 : Wdf01000!PreprocessIrp+0x58 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1519] 
ffffd88d`2ea176c0 fffff805`35525ba7     : ffffc704`4a081810 00000000`00000000 00000000`00000000 ffffc704`4a081cd0 : Wdf01000!FxDevice::DispatchWithLock+0x3ea4 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1445] 
ffffd88d`2ea17710 fffff805`3541e30d     : ffffc704`47624e10 fffff805`00000000 00000000`00000000 00000000`00000000 : nt!IopPoHandleIrp+0x3b
ffffd88d`2ea17740 fffff805`3556b029     : ffffc704`504799e0 ffffc704`58c735a0 00000000`00000000 fffff805`35e3d0f0 : nt!IofCallDriver+0x6d
ffffd88d`2ea17780 fffff805`3a9d9728     : ffffc704`356c08b0 ffffc704`6623cb30 ffffc704`58c73580 ffffc704`4a065820 : nt!PoCallDriver+0x9
ffffd88d`2ea177b0 fffff805`3a9b749a     : ffffc704`47624e10 fffff805`35525c70 ffffc704`356c08b0 fffff805`6493a008 : ACPI!ACPIFilterIrpSetPower+0x338
ffffd88d`2ea17810 fffff805`35525ba7     : 00000000`00000007 ffffc704`4a081810 ffffc704`58c73580 00000000`00000000 : ACPI!ACPIDispatchIrp+0x648a
ffffd88d`2ea17890 fffff805`3541e30d     : ffff655a`6b654fdf fffff805`00000000 00000000`00000000 fffff805`64933ba8 : nt!IopPoHandleIrp+0x3b
ffffd88d`2ea178c0 fffff805`3556b029     : fffff805`6493a008 fffff805`64914f8e 00000000`00000016 00000000`00000002 : nt!IofCallDriver+0x6d
ffffd88d`2ea17900 fffff805`8cbb28db     : ffffc704`4a081810 ffffc704`58c73580 ffffc704`58c73430 00000000`00000000 : nt!PoCallDriver+0x9
ffffd88d`2ea17930 fffff805`6491445f     : ffffc704`58c735a0 ffffc704`58c73430 00000000`80000000 ffffc704`4a081810 : hidusb!HumPower+0xab
ffffd88d`2ea17970 fffff805`64912007     : ffffc704`58c73580 00000000`00000016 fffff805`6493a008 fffff805`35526018 : HIDCLASS!HidpFdoPower+0x42f
ffffd88d`2ea179f0 fffff805`355259ea     : ffffa300`14da0000 ffffc704`356cc040 ffffd88d`2ea17b00 fffff805`00000000 : HIDCLASS!HidpMajorHandler+0x227
ffffd88d`2ea17a80 fffff805`354ded97     : ffffc704`356cc040 00000000`00000000 fffff805`35525790 00000000`00000000 : nt!PopIrpWorker+0x25a
ffffd88d`2ea17b30 fffff805`35619a24     : ffffa300`14d91180 ffffc704`356cc040 fffff805`354ded40 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffffd88d`2ea17b80 00000000`00000000     : ffffd88d`2ea18000 ffffd88d`2ea11000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  UsbHub3!HUBPDO_EvtDeviceD0Exit+352

MODULE_NAME: UsbHub3

IMAGE_NAME:  UsbHub3.sys

IMAGE_VERSION:  10.0.22621.5192

STACK_COMMAND:  .process /r /p 0xffffc70435764040; .thread 0xffffc704356cc040 ; kb

BUCKET_ID_FUNC_OFFSET:  352

FAILURE_BUCKET_ID:  0x9F_3_UsbHub3!HUBPDO_EvtDeviceD0Exit

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {00e27064-02f5-d601-a099-ac4f455b9037}

Followup:     MachineOwner
---------

 

  • Like 1
Shimakaze514

Shimakaze514

Posted
  • Author
Posted

Just encountered another freeze and auto restart, third time opening DCS after the update and third time freeze auto restart now. Here's the log, but I think it is useless:

dcs.log

  • Like 2
sleighzy

sleighzy

Posted
Posted (edited)
5 hours ago, Shimakaze514 said:

Just encountered another freeze and auto restart, third time opening DCS after the update and third time freeze auto restart now. Here's the log, but I think it is useless:

dcs.log 40.14 kB · 0 downloads

This log shows a few interesting things:

  • You only have 16Gbs of RAM....kind of. It shows 14043Mb which is a weird number. Might be worth looking into that to ensure no problems there, e.g. run RAM tests. Don't know what kind of performance you're getting in multiplayer.
  • You have your preload radius set to 100000 which is quite high for your specs. Given you only have 8Gb VRAM on your GPU and 16Gb RAM (kind of) I'd drop that right down to 30000
  • You have a 58Gb page file set. That's larger than the general recommendations, e.g page file being roughly double (and a half) of physical RAM. Is this on your fastest SSD with at least 10% free space remaining?
  • Disable TacView as well
  • Enable fullscreen.
Edited by sleighzy

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

BuLLeT.ZA

BuLLeT.ZA

Posted
Posted

I'm getting the same issue with intermittent freezing. DCS locks up my whole system for 30 seconds or so at a time while in the menu or editor - not during gameplay though thankfully.

I'll try all the mentioned fixes above and keep watching this topic with great interest.

Saitek X52 | 4770k@4.3GHz | MSI 1080GTX Armor OC | TrackIR 5

Pillowcat

Pillowcat

Posted
Posted
2 hours ago, sleighzy said:

preload radius set to 100000

2 hours ago, sleighzy said:

Disable TacView

MAIN MENUs, guys, are you think it is preload of kilometers of 2D GUI and so cause freezing or what?! it is not 'performance' issue in the meaning of system being insufficient in drawing 2D picture..

sleighzy

sleighzy

Posted
Posted (edited)
2 hours ago, Pillowcat said:

MAIN MENUs, guys, are you think it is preload of kilometers of 2D GUI and so cause freezing or what?! it is not 'performance' issue in the meaning of system being insufficient in drawing 2D picture..

Correct, the main menu freeze is weird and cause is still unknown. However, if somebody drops a log here with additional stuff that should be addressed then I’ll call it out so they don’t have issues further down the road. 

9 hours ago, Shimakaze514 said:

Just encountered another freeze and auto restart, third time opening DCS after the update and third time freeze auto restart now. Here's the log, but I think it is useless:

dcs.log 40.14 kB · 3 downloads

Can you run the Windows DxDiag tool, save the report, and then attach that here also.

also when you say “auto-restart” do you mean that your Windows reboots itself automatically?

Edited by sleighzy
  • Like 1

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

MAXsenna

MAXsenna

Posted
Posted
MAIN MENUs, guys, are you think it is preload of kilometers of 2D GUI and so cause freezing or what?! it is not 'performance' issue in the meaning of system being insufficient in drawing 2D picture..
In the OP its stated it happens when DCS refreshes the server list. That means MP not main menu, and the thread should be moved. If OP has a different problem now, a new thread should be made.
Others that have similar issues in the ME should also make their own threads in the relevant subforums.

Cheers!

Sent from my SM-A536B using Tapatalk


sleighzy

sleighzy

Posted
Posted

This log was also after the multiplayer servers listed. TacView recorder was also loaded at this point hence also mentioning it.

@Shimakaze514 , this log shows that it took roughly a minute from launching DCS to getting the list of servers up. This does not seem unreasonable. The fact that your PC froze and then rebooted itself following this (if this is what is meant by autorestart) would potentially point at some deeper Windows issue. Hopefully the DxDiag report contains more info. 

  • Like 1

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Dginn69

Dginn69

Posted
Posted

Freezing here to after the update last night. I can post a log fie when I get home later. But my issue seems to be core parking. 

 

BuLLeT.ZA

BuLLeT.ZA

Posted
Posted
On 4/18/2025 at 3:37 PM, MAXsenna said:

In the OP its stated it happens when DCS refreshes the server list. That means MP not main menu, and the thread should be moved. If OP has a different problem now, a new thread should be made.
Others that have similar issues in the ME should also make their own threads in the relevant subforums.

Cheers!

Sent from my SM-A536B using Tapatalk

 

Not sure about the OP, but my freezes happen anywhere that isn't ingame. Main menu, server browser and editor all lock up my system.

Saitek X52 | 4770k@4.3GHz | MSI 1080GTX Armor OC | TrackIR 5

MAXsenna

MAXsenna

Posted
Posted
Not sure about the OP, but my freezes happen anywhere that isn't ingame. Main menu, server browser and editor all lock up my system.
Best way is to post your DCS.log then.

Cheers!

Sent from my SM-A536B using Tapatalk

MoleUK

MoleUK

Posted
Posted
On 4/18/2025 at 4:41 AM, Shimakaze514 said:

Just encountered another freeze and auto restart, third time opening DCS after the update and third time freeze auto restart now. Here's the log, but I think it is useless:

dcs.log 40.14 kB · 6 downloads

I am seeing the same freezes on server select screen at least, as well as some other freeze and CTD issues.

Mine don't last entire minutes, but that may be due to the CPU recovering quicker.

 

Slippa

Slippa

Posted
Posted

Came here to see I'm not alone too. Since the update (incl Germany) DCS is crashing, freezing, CTD, it even Rebooted altogether.

I've wiped the FXO and Metashaders folders at various times to no avail. MP servers even lightly populated are crippling. Anywhere near Berlin I'm in a flickshow of horrors. I need a PC but as usual DCS is all that gives it any trouble. I wouldn't mind but I wanna fly all the maps in all my modules all of the time 😄.

Hope an update helps but it's not looking good unless someone wants to build me a super-dooper-computer.

 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...