Jump to content

Unexpected crash stable since 2.7.16.28157


Go to solution Solved by Flappie,

Recommended Posts

Posted

Hi,

Since the latest Stable Update, DCS crashes unexpectedly. A10C - also Windows 11 reports a program crash. Can someone look over the log file. Also, 2 bug reports were sent out automatically. Microsoft and ED.

 

Log in the attachment.

dcs.log

  • Solution
Posted

Here is your crash stack:

2022-08-05 21:05:05.702 INFO    APP: Invalid pilotid, initiator pilotid: 26, target pilotid: 0
2022-08-05 21:05:10.994 WARNING LOG: 2 duplicate message(s) skipped.
2022-08-05 21:05:10.994 INFO    EDCORE: try to write dump information
2022-08-05 21:05:10.994 INFO    EDCORE: # -------------- 20220805-210511 --------------
2022-08-05 21:05:10.995 INFO    EDCORE: DCS/2.7.16.28157 (x86_64; Windows NT 10.0.22000)
2022-08-05 21:05:10.995 INFO    EDCORE: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe
2022-08-05 21:05:10.995 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 0A748C15 00:00000000
2022-08-05 21:05:10.998 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World;C:\Program Files\Eagle Dynamics\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: '2278-'
2022-08-05 21:05:10.998 INFO    EDCORE: OS-Version: 10.0.22000 () 0x100-0x1
2022-08-05 21:05:11.231 INFO    EDCORE: 0x0000000000488C15 (DCS): SW + 0x162DD5
2022-08-05 21:05:11.231 INFO    EDCORE: 0x0000000000487469 (DCS): SW + 0x161629
2022-08-05 21:05:11.231 INFO    EDCORE: 0x0000000000476572 (DCS): SW + 0x150732
2022-08-05 21:05:11.231 INFO    EDCORE: 0x0000000000476673 (DCS): SW + 0x150833
2022-08-05 21:05:11.231 INFO    EDCORE: 0x000000000012DD26 (WorldGeneral): AI::MultiTaskState::onEvent + 0x56
2022-08-05 21:05:11.232 WARNING LOG: 1 duplicate message(s) skipped.
2022-08-05 21:05:11.232 INFO    EDCORE: 0x00000000000C8F38 (WorldGeneral): wControl::onDamage + 0xE8
2022-08-05 21:05:11.232 INFO    EDCORE: 0x00000000000C8ECD (WorldGeneral): wControl::onDamage + 0x7D
2022-08-05 21:05:11.232 WARNING LOG: 1 duplicate message(s) skipped.
2022-08-05 21:05:11.232 INFO    EDCORE: 0x00000000008CA846 (DCS): SW + 0x5A4A06
2022-08-05 21:05:11.232 INFO    EDCORE: 0x0000000000098A90 (Transport): woCar::takeDamage + 0x1C0
2022-08-05 21:05:11.232 INFO    EDCORE: 0x000000000008589E (Transport): woCar::PostCollisionProcessing + 0x46E
2022-08-05 21:05:11.232 INFO    EDCORE: 0x00000000008A9262 (DCS): SW + 0x583422
2022-08-05 21:05:11.232 INFO    EDCORE: 0x00000000008A825F (DCS): SW + 0x58241F
2022-08-05 21:05:11.233 INFO    EDCORE: 0x00000000002038D8 (WeaponBlocks): wVStartAutopilot::simulate + 0xEB48
2022-08-05 21:05:11.233 INFO    EDCORE: 0x00000000000425D2 (WeaponBlocks): wPNCoeffCalcBlock::operator= + 0xC832
2022-08-05 21:05:11.233 INFO    EDCORE: 0x000000000011DA3A (WeaponBlocks): wClusterStarter::simulate + 0x5DEA
2022-08-05 21:05:11.233 INFO    EDCORE: 0x00000000000200FA (blocksim): wSimulationSystem::simulate + 0x14A
2022-08-05 21:05:11.233 INFO    EDCORE: 0x000000000006AFA9 (WeaponsBase): wAmmunition::simulate + 0x149
2022-08-05 21:05:11.233 INFO    EDCORE: 0x00000000001356DB (Weapons): wAmmunitionDecoy::spawnSnare + 0x7CB
2022-08-05 21:05:11.233 INFO    EDCORE: 0x000000000013D4F8 (Weapons): wAmmunitionSelfHoming::simulate + 0x158
2022-08-05 21:05:11.233 INFO    EDCORE: 0x0000000000067DCA (WeaponsBase): wAmmunition::Class + 0x9A
2022-08-05 21:05:11.233 INFO    EDCORE: 0x0000000000003AD6 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x466
2022-08-05 21:05:11.233 INFO    EDCORE: 0x0000000000003F3D (World): wSimCalendar::DoActionsUntil + 0x1FD
2022-08-05 21:05:11.234 INFO    EDCORE: 0x0000000000841155 (DCS): SW + 0x51B315
2022-08-05 21:05:11.234 INFO    EDCORE: 0x0000000000840EAE (DCS): SW + 0x51B06E
2022-08-05 21:05:11.234 INFO    EDCORE: 0x00000000008568FB (DCS): SW + 0x530ABB
2022-08-05 21:05:11.234 INFO    EDCORE: 0x00000000008276C4 (DCS): SW + 0x501884
2022-08-05 21:05:11.234 INFO    EDCORE: 0x0000000000827A9D (DCS): SW + 0x501C5D
2022-08-05 21:05:11.234 INFO    EDCORE: 0x0000000001D472DC (DCS): AmdPowerXpressRequestHighPerformance + 0xED62D8
2022-08-05 21:05:11.234 INFO    EDCORE: 0x0000000000A7150E (DCS): SW + 0x74B6CE
2022-08-05 21:05:11.234 INFO    EDCORE: 0x00000000000154E0 (KERNEL32): BaseThreadInitThunk + 0x10
2022-08-05 21:05:11.234 INFO    EDCORE: 0x000000000000485B (ntdll): RtlUserThreadStart + 0x2B
2022-08-05 21:05:11.379 INFO    EDCORE: Minidump created.

 

I don't see anything obvious in it. Have you tried a DCS repair yet? Choose the "slow" method.

---

Posted (edited)

The device mapped to 0A748C15 did not give the program access to the memory, or process.

GPU Driver likely crashed or memory is unstable. (DCS Resolution is also above DX11's limit of 8192)

Edited by SkateZilla

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Posted

I have a similar crash after the latest update.  I am narrowing it down.  It happens when trying to exit a mission, single or multiplayer and a FW190-A has to be selected and occupied at some point.  If a Bf109 or/and FW190-D is occupied there has not been a crash yet.  I will keep on trying to narrow down but the "FW190-A" parameter seem to be consistent.

PS. Stable ver. 2.7.16.28157, win 10 pro, Intel  i9-11900K, Asus RTX 3090

Once problem occurred, Nvidia drivers updated and a Repair was performed, just in case.  No change 

Posted (edited)

I was making sure that the issue was reproducible and what you suggest would have been my next move.  Then,  I saw your post on running the repair in "Slow" method.  I have only done in the "fast" method before.   After I did run the repair with the slow method, the problem disappeared.  I have been trying to recreate it but, and thankfully, I cannot 🙂

For now, I will have to assume that it got fixed by running the repair like that, although there was no mention in the buffer that any corrupt files were spotted. 

Thank you for your help!

PS: I might be wrong on the spotting of corrupt files.  There was one file in a FW190A folder (id_6_N.dds) that was replaced.   Anyway, Everything is still properly functioning.

Edited by Kadin
  • Like 1
  • Thanks 2
  • Recently Browsing   0 members

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