My Crash Log

[flick]

# -------------- 20170107-155524 --------------

�

# C0000005 ACCESS_VIOLATION at B776D787 00:00000000

00000000 00000000 0000:00000000

B776D787 008FF0B0 0000:00000000 ?isGroup@wControl@@QEBA_NXZ()+7

BDBDD2C7 008FF0E0 0000:00000000 ?regLuaEnv@Scripting@@YAXPEAUlua_State@@_N@Z()+7A7

C2F97254 008FF120 0000:00000000 luaD_growstack()+7A4

C2FA6FB5 008FF2A0 0000:00000000 luaS_newlstr()+49C5

C2F97541 008FF2D0 0000:00000000 luaD_growstack()+A91

C2F9684F 008FF450 0000:00000000 lua_getinfo()+11AF

C2F9785E 008FF490 0000:00000000 lua_yield()+9E

C2F92440 008FF4E0 0000:00000000 lua_pcall()+60

BDBEA8BD 008FF510 0000:00000000 ?regLuaStaticObject@Scripting@@YAXPEAUlua_State@@@Z()+37D

E393642F 008FF590 0000:00000000

E3936975 008FF5E0 0000:00000000

B51E6CF8 008FF650 0000:00000000

B51EE4C1 008FF6B0 0000:00000000

B51DC354 008FF6E0 0000:00000000

B51DC2A4 008FF710 0000:00000000

B4EB743F 008FFDC0 0000:00000000

B52F2ABD 008FFE00 0000:00000000

EB0D8364 008FFE30 0000:00000000 BaseThreadInitThunk()+14

EEBC70D1 008FFE80 0000:00000000 RtlUserThreadStart()+21

[BIGNEWY]

Hi

 

we can see from the above info it has something to do with static objects and scripting

 

but we need more to try and help you

 

I have a guide in my signature for attaching logs, it is preferable to have the whole log folder zipped and attached straight after the crash, it will give us more information.

 

If you could also tell is what aircraft and mission and what is your system specification.

 

also if you have any unofficial modifications please remove them and run a repair

 

thanks

Edited January 7, 2017 by BIGNEWY