Constant crash of 4.35 U2 after using TGP or LANTIRN
-
I have a setup of Warthog plus Saitek rudder pedals with one 4K Samsung TV as the main screen and a touchscreen Dell for Helios. I could fly around with normal airline stuffs with no problem but when ever I turn the TGP on the sim gonna crash in like around 5 mins. I tried it with Helios and without, changing resolution and graphic settings but still the crash persisted. I’ve uploaded the last for logs here and let me know if you need the full dump as well.
I was up to flying TFR and LGB training missions and this was when the crash became unbearable. I could hardly finish setting up and it already crashed. It was very frustrating … :uham::uham::uham:
-
Got a .dmp file to share? Please read the following topic item 1. if you failed to get on from BMS: https://www.benchmarksims.org/forum/showthread.php?42473-Enabling-dump-files-at-all-times-MS-Application-Verifier-and-Frozen-dump-files
-
These 4 stack traces are different but 3 of them are fairly close, and all are on main sim-loop thread… interesting.
Hardware (CPU, GPU) and OS? Any overclocking?
Apart from helios … any mods or thirdparty theatres, or textures – does this happen with clean install of 4.35.2, stock KTO theater?
-
I setted up this rig years ago but haven’t got time to invest until recently. It was an i7 with Nvidia GTX 970, 16G of ram, Windows 10, with no overclocking whatsoever.
And I’m learning Falcon as well so no mod at all, clean install of 4.35.2, stock KTO theater.
And Tumbler, I’ve uploaded all 4 of these dump files:
2021-08-16_215319_crash: https://www.mediafire.com/file/1nw8631k9q0jyvx/2021-08-16_215319_crash.dmp/file
2021-08-17_230934_crash: https://www.mediafire.com/file/jmskrp1e2nxnvi1/2021-08-17_230934_crash.dmp/file
2021-08-16_210114_crash: https://www.mediafire.com/file/mcls55wpa41r987/2021-08-16_210114_crash.dmp/file
2021-08-16_154019_crash: https://www.mediafire.com/file/e2pzh5l7avejgl6/2021-08-16_154019_crash.dmp/fileThx for your help !
-
Just to be clear – which training mission(s) does this repro? TR#8 (TFR) or TR#11 (LGB) or both?
I think TRs #12, 13, 14 also have TGP mounted by default. Same issues there?
TR#13 allows you to change the loadout, before committing. Does the crash happen if you remove TGP and fly without it?
Just trying to help narrow down the repro case and possible root causes…
-
Please try and run “dxdiag” to provide details on your graphics setup. I noticed that some reported issues with DirectX11 and the GTX970 and BMS has moved to DX11.
To run dxdiag: Press Win+R, then type dxdiag and press Enter.
Could you post what it says on the first page that shows ?
-
Hi Jacques, Tumbler and I took a look at the DMPs, they don’t make much sense. Code is crashing in places that nothing complex is happening and there does not seem to be a race condition, just one thread doing its job.
We have some options for further debugging this. But first, we need to rule out a hardware issue. Does your system have an integrated GPU? Maybe you can switch to it and see if the error happens there too?
As jayb pointed out, this could be a problematic driver. Are your system and drivers up to date? Also, running a memory check would be helpful to rule out memory errors (memtest86).
-
Sorry for the long delay, I spent all the time I have to find a new graphic card and a new GTX 3070 will arrive tmrw. I couldn’t go higher on the rank otherwise I’ll have to change everything including the motherboard and the Power unit. It’s 600 Watts right now.
Before posting this thread I actually did the memory check and it said I have hardware problem so I actually replaced one of my 8G DDR 3 ram, and the problem persisted that’s why I decided to post
But on the other hand my DCS, Arma is also crashing after like 10 mins or so in game so I’m thinking there must be something wrong with the rig… Something got eaten up and my computer had given up
https://www.mediafire.com/file/fm4fxpfwhzi1ow8/DxDiag.txt/file
And here is the whole DxDiag file be the way, it did say everything was normal though
PS for Airtax I’m doing the training mission in order, I just haven’t been in those later missions yet, but I suspect it would be the same
-
Thanks for checking your system. It now passes memtest86 without errors? Noting your Arma crashes, it seems something is still wrong. Does your system survive a stress test by running eg 3Dmark (time spy or fire strike are both free)?
-
Before posting this thread I actually did the memory check and it said I have hardware problem so I actually replaced one of my 8G DDR 3 ram, and the problem persisted that’s why I decided to post
The DxDiag does not reveal anything particular, in fact your card supports DX12, so that’s probably not the culprit.
It is most likely the RAM, even though you replaced one stick. Now I remember from doing a system build once that RAM does not particularly like being mixed so the best approach is usually to replace all RAM in one go with the same new type. In my case we had 16 gigs in the system already and wanted to add another 16. We bought the exact same type which was already in, but we could not make the system boot up. Due to subtle differences in the old and new RAM sticks, we had to lower the frequency of all RAM slightly and then the PC was happy to accept all the 32 Gb of RAM present.
So in short, you should run the memtest as Tumbler31 suggests. If that causes issues, try the memtest with one stick at a time. If they each pass the memtest, both are fine but incompatible. Then you could try to lower the RAM frequency when they are both in.
-
Thanks for the reply. I was aware of the different RAM problem so I actually was looking for the exactly same second hand DDR3 brand (Kingston Fury Hyper X) and the memory test after the change was all good, I did it three times in a row.
But now my RTX 3070 had arrived, I thought I could do more testing and just Holy XXXX the new graphic card was so BIG that my old rig couldn’t fit it in ……
I ended up changing a new casing and I’ll report back on my new results.
-
First flight of BMS with the new card 3070: TE training mission LGB, after turning back for the second bomb, Blue screen of death then forced restart. Normal setup like before with TrackIR and Helios on the second monitor. I was much faster and fluid but Helas …
I’ve attached the new crash log here.
P.S. Oops that was still the old one… This crash didn’t managed to generate it’s own crash log yet …
-
Please verify memtest86 runs without errors and see if 3Dmark runs without issues.
Also check the thread below to check dump files are being created at all times
https://www.benchmarksims.org/forum/showthread.php?42473-Enabling-dump-files-at-all-times-MS-Application-Verifier-and-Frozen-dump-files -
First flight of BMS with the new card 3070: TE training mission LGB, after turning back for the second bomb, Blue screen of death then forced restart. Normal setup like before with TrackIR and Helios on the second monitor. I was much faster and fluid but Helas …
I’ve attached the new crash log here.
P.S. Oops that was still the old one… This crash didn’t managed to generate it’s own crash log yet …
Also if you got a blue screen you can use a program called bluescreenview from nirsoft to examine the mini-dump file created from the blue screen and see the code of that blue screen. The code of the blue screen is a helpfull evidence to determine what causing instability in your system.
-
https://www.resplendence.com/whocrashed is also quiet good.
-
Thanks for the reply. I was aware of the different RAM problem so I actually was looking for the exactly same second hand DDR3 brand (Kingston Fury Hyper X) and the memory test after the change was all good, I did it three times in a row.
Alright, you have been very thorough on the RAM test it would seem. Next thing to check could be temperature. You are not in a very warm room by any chance? One easy low-tech approach to check for temperature issues is to run the LGB mission with the case cover off and see if that makes a difference.
-
Ok, I finally found the culprit. It was indeed the RAM stick. I removed both of the RAM stick and test them one by one and I found out that my other old stick was reporting error right at the end of phase 2 Windows Memory Test. I was staring at the screen and haven’t been anywhere and was able to confirm this. My first old one was report error right at the start of the test so I thought if it was broken all RAM sticks would behave like the same but nop. So I plugged the good one in and flew around with TGP and the LGB mission with no issue at all this time. I ordered another same brand of DDR3 stick online and flew with 2 DDR3 of 8GB RAM Stick right now, which is also fine without any crash whatsoever.
So it was indeed a Memory Stick problem. Thanks for all your attention and I’m glad that it was a false alarm in the end, the problem is on my hardware side and the program itself is fine in this regard.
-
thanks for following up … it’s useful and interesting to hear what these modes of failure look like, in real life.
eg. interesting that it seems to happen only/mostly under heavy load. I would have expected memory problem to cause random bluescreens, even just sitting idle or browsing the web.
-
So it was indeed a Memory Stick problem. Thanks for all your attention and I’m glad that it was a false alarm in the end, the problem is on my hardware side and the program itself is fine in this regard.
It’s great you got it sorted. It can be a real pain and a time-sink to chase down issues such as these.
