OldE24 Posted March 8, 2016 Posted March 8, 2016 # -------------- 20160308-002346 -------------- # C0000005 ACCESS_VIOLATION at 3D9F8435 00:00000000 00000000 00000000 0000:00000000 3D9F8435 0014F0F0 0000:00000000 3DB7576C 0014F400 0000:00000000 3DB11F5E 0014F450 0000:00000000 3DBF30B0 0014F480 0000:00000000 BFA66CEF 0014F500 0000:00000000 BFA67235 0014F550 0000:00000000 3DD37948 0014F5C0 0000:00000000 3DD3C315 0014F620 0000:00000000 3DD51F94 0014F650 0000:00000000 3DD51EE4 0014F680 0000:00000000 3DDFA93C 0014FD30 0000:00000000 3DDFDF95 0014FD70 0000:00000000 D7A48102 0014FDA0 0000:00000000 BaseThreadInitThunk()+22 D819C5B4 0014FDF0 0000:00000000 RtlUserThreadStart()+34 i currently get this crash with MIG 29S when i starting on the ground. if you flip to BVR mode to soon or something with switching nav to BVR modes when you first spawn in causes the game to CTD. if i wait untill i am all loaded and engine spool to change to BVR i do not get a crash i still havt not figured out EXACTLY what causes it it just happens on ground as i am loading up getting ready. 8700k@4.7 32GB ram, 1080TI hybrid SC2
Jinks Posted March 19, 2016 Posted March 19, 2016 (edited) Consistent CTD in multiplayer. Not a matter of if but when - sometimes it won't happen for an hour which is the longest I've seen it work without issue. 00417.813 INFO EDCORE: # -------------- 20160319-010911 -------------- 00417.813 INFO EDCORE: 00417.813 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 3FCC8415 00:00000000 00417.815 INFO EDCORE: 00000000 00000000 0000:00000000 00417.815 INFO EDCORE: 3FCC8415 0024ECD0 0000:00000000 00417.816 INFO EDCORE: 3FE459CC 0024EFE0 0000:00000000 00417.816 INFO EDCORE: 3FDE21BE 0024F030 0000:00000000 00417.816 INFO EDCORE: 3FEC3520 0024F060 0000:00000000 00417.816 INFO EDCORE: F7896CEF 0024F0E0 0000:00000000 00417.816 INFO EDCORE: F7897235 0024F130 0000:00000000 00417.816 INFO EDCORE: 40008068 0024F1A0 0000:00000000 00417.817 INFO EDCORE: 4000CA35 0024F200 0000:00000000 00417.817 INFO EDCORE: 400226A4 0024F230 0000:00000000 00417.817 INFO EDCORE: 400225F4 0024F260 0000:00000000 00417.817 INFO EDCORE: 400C756C 0024F910 0000:00000000 00417.818 INFO EDCORE: 400CABC5 0024F950 0000:00000000 00417.820 INFO EDCORE: 779059ED 0024F980 0000:00000000 BaseThreadInitThunk()+D 00417.820 INFO EDCORE: 77B3B371 0024F9D0 0000:00000000 RtlUserThreadStart()+21 CTD Message: Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.5.3.51218 Application Timestamp: 56e4490c Fault Module Name: DCS.exe Fault Module Version: 1.5.3.51218 Fault Module Timestamp: 56e4490c Exception Code: c0000005 Exception Offset: 0000000000028415 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: f3ac Additional Information 2: f3ac2eba13701109f6bdac83aba074c3 Additional Information 3: 43f9 Additional Information 4: 43f9c822ec54b4f61c54645af8eb153b Windows 7 64bit, i5-4670k, 16gb ram, gtx760.crashdump.zip Edited March 19, 2016 by Jinks иɪɢнтмдяᴇ http://www.51st.org/
Jinks Posted March 19, 2016 Posted March 19, 2016 Meant to include, seems to happen during some type of button pressing. Have noticed a couple times that it's happened when switching to BVR after take-off. иɪɢнтмдяᴇ http://www.51st.org/
OldE24 Posted March 21, 2016 Author Posted March 21, 2016 Mutiple people get this i'll get logs again next time i play it...stuck on M2000. i'm not the only person it also happens in the SU-27 but not as often it's alawys on the ramp when you spawn in you Rearm repair and if you button push to much turn power on and hit BVR mode to see missiles and somewhere in there it crashes. I7 2600k@4.5 24GB ddr3 1600 ATI 390 Strix win 10 8700k@4.7 32GB ram, 1080TI hybrid SC2
OldE24 Posted March 22, 2016 Author Posted March 22, 2016 ok here is this one.....i spawned in turned power on closed/closed canopy waited a min hit BVR mode then CRASHED as soon as i pushed my key to changed HUD color CTD.migcrash.rar 8700k@4.7 32GB ram, 1080TI hybrid SC2
OldE24 Posted March 23, 2016 Author Posted March 23, 2016 it's not a repair issue...it sometimes even happens in the SU-27 and i'm not the only person who is having this issue, as others in the 104th who fly SU and MIG have complained about this recently. 8700k@4.7 32GB ram, 1080TI hybrid SC2
HiJack Posted March 23, 2016 Posted March 23, 2016 Make sure all your links to DCS.EXE starts in Administration mode!
OldE24 Posted March 24, 2016 Author Posted March 24, 2016 someone moved this so does that mean that SOMEONE HAS SEEN THIS? If you all want i'll get others to post it's not hard to reproduce. 8700k@4.7 32GB ram, 1080TI hybrid SC2
Jinks Posted April 6, 2016 Posted April 6, 2016 Make sure all your links to DCS.EXE starts in Administration mode! Tried that. Also repairing doesn't fix it. Uploaded two UNLISTED videos to youtube that show what happens, relevant log files already attached. First [ame] [/ame] Second (after repair and starting in administrator mode) [ame] [/ame] иɪɢнтмдяᴇ http://www.51st.org/
holimoli Posted April 6, 2016 Posted April 6, 2016 someone moved this so does that mean that SOMEONE HAS SEEN THIS? If you all want i'll get others to post it's not hard to reproduce. yes constantly crashing on awacs missions. And it seems to be worse if there is awacs + overcast... I cannot even fly on the 104th anymore.. Other ppl in my squad have the same issue. We mainly fly Su-27... [100☭] holimoli #13, 100-й КИАП
Svend_Dellepude Posted April 6, 2016 Posted April 6, 2016 Meant to include, seems to happen during some type of button pressing. Have noticed a couple times that it's happened when switching to BVR after take-off. Get this too but so far only in the quickstart ''intercept'' mission if I respawn and then switch to BVR (2). Also the only mission i did recently with AWACS. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
Recommended Posts