1 hour ago, Dominique_K said:

No simbrief plans, no navigraph, no Onair, nothing 😉 ?

No overheating (dust on the graphic card !) ? 

No shaky connection of a controller/heaset ?

No to all of the above.

4 hours ago, Swe_Richard said:

Only default. 

Latest Dev version of the FBW A320NX had no issues other than ILS off to the left on approach. I am going to try the same with the WT CJ4, and see what result i get.

I am having trouble with simbrief and the CJ4 (more likely me, than the program) so have been unable to try it yet.

Edited August 10, 20214 yr by Car147

Hi Swe-Richard,

 

Do you use your PC for other processing intensive things / games without issues?

I'm not sure how comfortable you are with removing hardware etc, what about trying;

removing one stick of ram at a time, and then re testing

swapping the ram around between their existing slots (i know this sounds pointless, but has cured some strange ram related issues)

is the ram in the correct slot for the number of sticks you are using? I've seen PC's used for years with the ram in the wrong slots, and run perfectly 99.9% of the time, but experience some weird crash once in a while, or under certain conditions in a software package, because of the wrong slots used.

Resetting your bios back to defaults and re testing, even if it's using less than your hardware's capable timings and the game runs slower

Installing the motherboard's latest chipset drivers

I understand that you're most likely not overclocking anything, so please ignore the following if that's the case; 🙂

 

I'd imagine this has already been mentioned many times in the past   -    people often think they have a stable overclocked system because they can run software like Prime95 for many hours or days or weeks, (and I have tried too with success), but often a game under full load seems to stress the hardware a little differently and will then reveal CTD's etc, and then people begin to think the the software is the cause because their overclock appeared to be stable in their tests.

 

 

Edited August 10, 20214 yr by dogmanbird

30 minutes ago, dogmanbird said:

Hi Swe-Richard,

Do you use your PC for other processing intensive things / games without issues?

 

Yup. There is no issues at all with anything else. 

5 hours ago, Swe_Richard said:

Quite ordinary stuff. 3900x. 2080TI 32GB ram. Sim on M.2 SSD. Saitek Yoke and pedals with quadrant. Nothing fancy or exotic. 

Well that's a top spec computer from 1-2 years ago, should run circles around 90% of the rigs out there. 

1. Do you have any overclocks?
2. Do you run your RAM in XMP/DOCP mode? (might help)
3. Have you updated your motherboard BIOS lately?
4. Have you tried updating your chipset drivers?

I am actually going to take my RAM out of XMP mode tonight.  It is a 3 and a half year old PC and things can deteriorate over time. 

Other applications might be fine, but MSFS pushes PC hardware to the limit sometimes.

Tried with the default CJ4 without the WT upgrade and i am afraid everything went well. I don't know what else to check (I guess you have done the usual and tried different graphics drivers, no over clock etc, etc)

59 minutes ago, Republic3D said:

Well that's a top spec computer from 1-2 years ago, should run circles around 90% of the rigs out there. 

1. Do you have any overclocks?
2. Do you run your RAM in XMP/DOCP mode? (might help)
3. Have you updated your motherboard BIOS lately?
4. Have you tried updating your chipset drivers?

No overclocks. The RAM is 2 x 16 Gb running at 3600MHz. CL16 (XMP profile).

The chipset is fully updated, likewise Bios.

28 minutes ago, Car147 said:

Tried with the default CJ4 without the WT upgrade and i am afraid everything went well. I don't know what else to check (I guess you have done the usual and tried different graphics drivers, no over clock etc, etc)

Thanks for checking for me, appreciate it!

Yeah, no OCs. Haven't messed around too much with drivers. Never use bleeding edge drivers ("don't fix that which is not broken"). 

 

7 minutes ago, Swe_Richard said:

Thanks for checking for me, appreciate it!

Yeah, no OCs. Haven't messed around too much with drivers. Never use bleeding edge drivers ("don't fix that which is not broken"). 

 

The only reason i mentioned drivers as i had a really bad time with constant CTD's during flights, and was very close to just calling it a day. It turned out the Radeon RX 5700XT card i run, and others at the time were having real issues with the drivers, i found out accidently one day when seraching the net for clues to what was going on and a guy had posted about reverting back to a certain driver (which is over a year old now ) and it cured his issues.

Well i thought, why not? i have got nothing to lose. I rolled back the drivers, and surprise, surprise no more CTD's. There have been a number of updates since, and the latest gives more no issues so far, but if it does i wont wait to roll back again.

Hopefully you get back to flying.

Edited August 10, 20214 yr by Car147

On 8/9/2021 at 5:46 AM, Swe_Richard said:

So, I have been massively disappointed about crashes since SU5 and HF 1 and 2. HF 2 made no difference what so ever regarding my CTDs, in fact it felt almost worse. Three out of three attempts at flying ended in a CTD (after HF2) and I was seriously contemplating a LONG hiatus from this hobby.

I rarely use dev-mode but figured I'd try it out (I was clutching at straws as I'd read somewhere that this one individual got no CTDs after running said mode). One thing stood out to me when I run the dev mode and that was a notification in the upper right corner about the existence of newer versions of the SDK. I figured I'd nothing to loose so I installed the latest version of the SDK. After which I tried the route that had CTD:d on me three times in a row: LEPA to LEBB in the DC-6 (about 750:ish NM).

No crash. Could hardly believe it. So I did four more flights in the WT CJ4 of which no crash occurred. The sixth CTD:d on me though, but the previous five was without restarting the computer so I restarted and tried the sixth again. No issues.

I think I understand, or at least have some kind of theory, what caused this. I used to crash despite empty Community folders. However, every single flight I do in MSFS (or at least 99%) I am at the same time running OnAir. Could it be that this particular program tries to access some function or other that simply has been altered as the SDK has been updated, triggering this? When I get clr.dll and ntdll.dll crashes it is always due to memory access violations. I was sceptical at first but still, I went from almost 100% CTDs to significantly less. It simply can't be coincidental.

As I side note, I was kind of expecting that the SDK gets updated as well when the rest of the sim is updated but this seems to not be the case. So, for you still having CTDs and an older SDK; update it.

So.. Mine says there is an update available for the sdk as well.  I click the download button, but nothing seems to happen.  It seems pretty straight forward, but isn't downloading anything that I can tell.  Anyone else have this issue?

1 minute ago, billkirk888 said:

So.. Mine says there is an update available for the sdk as well.  I click the download button, but nothing seems to happen.  It seems pretty straight forward, but isn't downloading anything that I can tell.  Anyone else have this issue?

Yeah, it was like that for me as well, so I googled the installer and installed it that way. 

I'll try that.  Thanks.  Don't give up!

Troubleshooting PC installs in this forum is like nailing jelly to a tree! 🤮🤤

Cheers

 bs