Jump to content

Crash with A-10C on loading screen


Vhzn

Recommended Posts

Hi guys !

 

So i've looked on older thread but found no proper answer, so i will try it here.

 

When i launch any A-10C mission, and A-10C only, the game crash on the loading screen.

I would avoid uninstalling the game, i've done lot of config for bindings...

Here is two crash log:

 

# -------------- 20160430-092245 --------------

 

# C0000005 ACCESS_VIOLATION at D9BE8410 00:00000000

00000000 00000000 0000:00000000

D9BE8410 0014E2D0 0000:00000000

66DAA177 0014E380 0000:00000000

66DF1CC6 0014E410 0000:00000000

66EE9043 0014E470 0000:00000000

66EE9326 0014E4B0 0000:00000000

66EE8D33 0014E4F0 0000:00000000

66EE875A 0014E540 0000:00000000

66EC76CE 0014E620 0000:00000000

66EC58D2 0014E7E0 0000:00000000

66EC72BE 0014E8D0 0000:00000000

66DF0640 0014E960 0000:00000000

66EC05E5 0014E9C0 0000:00000000

66F2ED9B 0014EB30 0000:00000000

66F2D064 0014EBD0 0000:00000000

66F1DBF3 0014ECC0 0000:00000000

66F1CD71 0014EFA0 0000:00000000

66F1580D 0014F100 0000:00000000

DD167D3A 0014F130 0000:00000000 ?sendOutputSymbol_@FSM@Common@@AEAAXI@Z()+2A

DD167CF8 0014F170 0000:00000000 ?enterToState_@FSM@Common@@AEAAXI@Z()+C8

DD167AFB 0014F1B0 0000:00000000 ?onSymbol_@FSM@Common@@AEAAXI@Z()+1CB

66F1B7C6 0014F210 0000:00000000

66F31464 0014F240 0000:00000000

66F313B4 0014F270 0000:00000000

66FD625C 0014F920 0000:00000000

66FD98B5 0014F960 0000:00000000

FB498102 0014F990 0000:00000000 BaseThreadInitThunk()+22

FC89C5B4 0014F9E0 0000:00000000 RtlUserThreadStart()+34

 

# -------------- 20160430-091849 --------------

 

# C0000005 ACCESS_VIOLATION at D9B18410 00:00000000

00000000 00000000 0000:00000000

D9B18410 0014E680 0000:00000000

66DAA177 0014E730 0000:00000000

66DF1CC6 0014E7C0 0000:00000000

66EE9043 0014E820 0000:00000000

66EE9326 0014E860 0000:00000000

66EE8D33 0014E8A0 0000:00000000

66EE875A 0014E8F0 0000:00000000

66EC76CE 0014E9D0 0000:00000000

66EC58D2 0014EB90 0000:00000000

66EC72BE 0014EC80 0000:00000000

66DF0640 0014ED10 0000:00000000

66EC05E5 0014ED70 0000:00000000

66F2ED9B 0014EEE0 0000:00000000

66F2D064 0014EF80 0000:00000000

66F1DBF3 0014F070 0000:00000000

66F1CD71 0014F350 0000:00000000

66F1580D 0014F4B0 0000:00000000

DCED7D3A 0014F4E0 0000:00000000 ?sendOutputSymbol_@FSM@Common@@AEAAXI@Z()+2A

DCED7CF8 0014F520 0000:00000000 ?enterToState_@FSM@Common@@AEAAXI@Z()+C8

DCED7AFB 0014F560 0000:00000000 ?onSymbol_@FSM@Common@@AEAAXI@Z()+1CB

66F1B7C6 0014F5C0 0000:00000000

66F31464 0014F5F0 0000:00000000

66F313B4 0014F620 0000:00000000

66FD625C 0014FCD0 0000:00000000

66FD98B5 0014FD10 0000:00000000

FB498102 0014FD40 0000:00000000 BaseThreadInitThunk()+22

FC89C5B4 0014FD90 0000:00000000 RtlUserThreadStart()+34

Link to comment
Share on other sites

I'm thinking you should just contact support, no? Unless you already went that route.

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

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