Solved Unexpected CTD
-
@SoBad Wow, it’s been a while since I last saw a CTD in this code. I’ll take a look, thanks.
-
@Seifer said in Unexpected CTD:
@SoBad Wow, it’s been a while since I last saw a CTD in this code. I’ll take a look, thanks.
Thanks. Just an update:
I flew the same mission again, and it went very successfully and flawlessly until I was 7 miles from my airbase on a cleared approach. Then it CTD very quickly. (!?!) Like I said, I rarely get crashes. But since Hotfix 2, this is now the third one. (I didn’t report the first one).
I went to the \User\Log folder and to my surprise, there was only a 0-byte dtc_last_flight_faults.ext file, and NO *bmp file, *dmp file, or crash.txt file associated with that CTD. First time I’ve ever seen that happen too.
Hope this info helps.
-
@SoBad please share the mission as well.
-
@Seifer said in Unexpected CTD:
@SoBad please share the mission as well.
Sure–
Stock KTO on local drive, Rolling Fire, Day 2, Single Player -
I controlled the 35th FS out of Gunsan, and created a 3-flight package as follows:
Air Interdiction 4-ship F-16 with me in the lead, preceded by
ESCORT 4-ship F-16, preceded by
TARCAP 4-ship F-15 (another squadron also stationed at Gunsan)TARCAP headed out first, then ESCORT, then my flight. After marshaling, TARCAP was about 25 miles ahead, ESCORT was about 20 miles ahead, and my flight being the last group to ingress.
Target area was at Stp. 5, just north of the DMZ. As my flight reached Stp. 4 (about 50 miles south of Stp. 5) we went FENCE IN. After that, it was quiet for a few minutes. I was in my cockpit, regular view, and I had not touched any buttons, about 40 miles away from the DMZ. Then suddenly and unexpectedly, the screen (and sound) froze and CTD about 3 seconds later.
-
@SoBad said in Unexpected CTD:
@Seifer said in Unexpected CTD:
@SoBad please share the mission as well.
Sure–
Stock KTO on local drive, Rolling Fire, Day 2, Single Player -
I controlled the 35th FS out of Gunsan, and created a 3-flight package as follows:
Air Interdiction 4-ship F-16 with me in the lead, preceded by
ESCORT 4-ship F-16, preceded by
TARCAP 4-ship F-15 (another squadron also stationed at Gunsan)TARCAP headed out first, then ESCORT, then my flight. After marshaling, TARCAP was about 25 miles ahead, ESCORT was about 20 miles ahead, and my flight being the last group to ingress.
Target area was at Stp. 5, just north of the DMZ. As my flight reached Stp. 4 (about 50 miles south of Stp. 5) we went FENCE IN. After that, it was quiet for a few minutes. I was in my cockpit, regular view, and I had not touched any buttons, about 40 miles away from the DMZ. Then suddenly and unexpectedly, the screen (and sound) froze and CTD about 3 seconds later.
I think seifer would like the saved cam so he can try to reproduce the bug
Do you have the saved campaign file ?
-
@SoBad said in Unexpected CTD:
I went to the \User\Log folder and to my surprise, there was only a 0-byte dtc_last_flight_faults.ext file, and NO *bmp file, *dmp file, or crash.txt file associated with that CTD. First time I’ve ever seen that happen too.
Please look here https://forum.falcon-bms.com/topic/20866/
And do share the campaign/TE-files that give the constant CTDs
-
@Mav-jp said in Unexpected CTD:
@SoBad said in Unexpected CTD:
@Seifer said in Unexpected CTD:
@SoBad please share the mission as well.
I think seifer would like the saved cam so he can try to reproduce the bug
Do you have the saved campaign file ?
Oh! Sure. I’ll do it when I get back home this evening.
-
Seems like a memory corruption to me (the pointer is not dangling, it looks like garbage). Really need a repro to understand this better.
-
@SoBad any overclock on your side? Can you check the memory as well?
-
@Seifer said in Unexpected CTD:
@SoBad any overclock on your side? Can you check the memory as well?
------ AMD Radeon RX6700 w/ 12Gb VRAM
------ 32Gb DDR5 RAMI do not ever overclock or otherwise fiddle with any such settings. With my specs, I don’t need to. Everything is default.
Tell me how to “check the memory” and I will do it this evening.
-
@SoBad thanks, just double checking some basic stuff. I usually recommend running https://www.memtest86.com/ for memory testing.
The reason I am asking is because the pattern I see in your CTD looks like a bit flip (a perfectly valid memory address with just one bit flipped wrong). It is very rare for code to screw things like that (usually, a corruption caused by code generates a lot of garbage, which is not the case here).
Do you have other DMP from this crash you could share? I want to see if it’s crashing in the same spot.
-
@Seifer said in Unexpected CTD:
@SoBad thanks, just double checking some basic stuff. I usually recommend running https://www.memtest86.com/ for memory testing.
The reason I am asking is because the pattern I see in your CTD looks like a bit flip (a perfectly valid memory address with just one bit flipped wrong). It is very rare for code to screw things like that (usually, a corruption caused by code generates a lot of garbage, which is not the case here).
Do you have other DMP from this crash you could share? I want to see if it’s crashing in the same spot.
I’ll run the memtest this evening when I get home and let you know.
The second crash didn’t generate a DMP file, so I can’t help you there.
I can run the mission again tonight and if it crashes and creates a DMP, I’ll send it to you.
-
@SoBad sgtm, let us know. Many thanks!
-
@SoBad said in Unexpected CTD:
I do not ever overclock or otherwise fiddle with any such settings. With my specs, I don’t need to. Everything is default.
When it comes to RAM freq and timings, sometimes the “default” is overclocked… check your BIOS for “XMP” or for AMD maybe “EXPO” settings.
Tell us about your RAM … what speed, what timings. (TaskMgr shows the RAM frequency at the bottom of the Memory tab.)
idk if there’s such thing yet as RAM timings that are “too fast” for a 7700X but … maybe?
-
@airtex2019 said in Unexpected CTD:
@SoBad said in Unexpected CTD:
I do not ever overclock or otherwise fiddle with any such settings. With my specs, I don’t need to. Everything is default.
When it comes to RAM freq and timings, sometimes the “default” is overclocked… check your BIOS for “XMP” or for AMD maybe “EXPO” settings.
Tell us about your RAM … what speed, what timings. (TaskMgr shows the RAM frequency at the bottom of the Memory tab.)
idk if there’s such thing yet as RAM timings that are “too fast” for a 7700X but … maybe?
I understand all of your concerns, but I’ve been running over a hundred different missions with this gaming computer since I got it about six months ago, and I’ve never changed any setting, or experienced any crashes (with Falcon BMS or anything else, for that matter) until very recently. So I don’t think it’s an issue of O.C. speeds, timings, etc. because they have NEVER changed.
@Seifer - I have no idea what “sgtm” means. Sorry.
-
@SoBad it means “sounds good to me”.
-
@Seifer said in Unexpected CTD:
@SoBad it means “sounds good to me”.
lolol-- Okay. New to me. I’ll get back with you in a couple of hours when I get home.
-
@Seifer - By any chance, could you tell if it was the 3rd bit of 8 that was flipped?
-
@SoBad the faulty pointer is:
0x10 00 00 06 c1 c4 54 60
the first byte, 0x10 is the faulty one, which is 0 0 0 1 0 0 0 0.
So I guess the answer to your question is that it is the 5th bit, from lower to higher.
-
@Seifer said in Unexpected CTD:
@SoBad the faulty pointer is:
0x10 00 00 06 c1 c4 54 60
the first byte, 0x10 is the faulty one, which is 0 0 0 1 0 0 0 0.
So I guess the answer to your question is that it is the 5th bit, from lower to higher.
Okay. I just ran the MemTest86 for the past 1 hour+.
See the results yourself:
https://drive.google.com/file/d/1e8miZgjijGrabOrDeeeEprGU3PlMfClk/view?usp=sharing
Thousands of single bit errors, either one value lower, or one value higher. In every case, the 3rd bit (or maybe 5th bit depending upon which direction you are counting, right?).
If not for your help, I would have never tracked this down. I’m going to contact the business that built my computer to see if my warranty is good for the RAM, but either way, I’ll get this set right. Thanks again.