34 minutes ago, Luke said:

FWIW, every single version of MSFS worked fine on this machine before.

I don't want to read back thru 9 pages to see if you're in the current beta, but if you're not in the beta why not join and see what happens. Given your current predicament, what have you got to lose?

1 hour ago, Luke said:

Nothing besides PMDG. It's a fresh, vanilla install.

Just regular Windows processes.

Yes, no overclock beyond standard manufacturer OC on the GPU. No funny sound cards - basic HDMI out via the NV card to a separate AV system.

FWIW, every single version of MSFS worked fine on this machine before.

Cheers

 

I hate to be repetitive , but what PSU do you have? 

2 hours ago, Luke said:

Nothing besides PMDG. It's a fresh, vanilla install.

Are you using supplied chipset drivers from Microsoft or did you download from main board site? 

Also is  BIOS current? 

 

 

5 hours ago, Luke said:

FWIW, every single version of MSFS worked fine on this machine before.

What if you plug out all USB controllers (yoke, throttle, stick) once you fly on autopilot?

Edited January 5, 20233 yr by mrueedi

7 hours ago, Luke said:

Nothing besides PMDG. It's a fresh, vanilla install.

Remove PMDG.  Then try to reproduce the CTD.

On 1/4/2023 at 1:15 AM, jarmstro said:

MSFS is more power hungry than any other game or programme I have. You might try a new PSU to start with. A cheap one used flat out and under maximum load will eventually fail or give these sorts of errors in my experience. (Or you could take the top off yours and look for things like white gunge coming out of a capacitor.) Just a thought. Also bear in mind that the stated power of many cheap PSU's is often grossly overstated. Peak power is very different to sustainable power. Cheap PSU's also have poor regulation and smoothing.

I have asked a couple of times what his PSU is, and seems as if he doesn't want to answer that. My guess is, that is his problem. 

12 hours ago, Luke said:

Nothing besides PMDG. It's a fresh, vanilla install.

Just regular Windows processes.

Yes, no overclock beyond standard manufacturer OC on the GPU. No funny sound cards - basic HDMI out via the NV card to a separate AV system.

FWIW, every single version of MSFS worked fine on this machine before.

Cheers

 

Sheesh. If that's the case I'd suggest the tedious and annoying CTD checklist from Asobo. It involves a bit of work but it might help. The end game is reinstalling the sim. Have you contacted Asobo via Zendesk?

Also, does this occur with a completely default plane, no mods?

 

7 hours ago, Bobsk8 said:

I have asked a couple of times what his PSU is, and seems as if he doesn't want to answer that. My guess is, that is his problem. 

Not a peep about updated drivers or BIOSes either. It's almost as if he came here, typing "garbage" in an all-caps large font, hoping for sympathy from a bunch of users with the same problem. When he heard from a bunch of people with zero issues instead, it's almost as if he doesn't want to admit there is any possibility that his machine is the problem and doesn't want to do any in-depth troubleshooting because P3D works fine. I'm not gonna take the bait, and I empathize for the people giving detailed troubleshooting tips only to receive no response. Maybe I'm wrong here, but I just call em as I see em.

What it boils down to is if you want to test your computer for stability use MSFS.  It is the best way to stress your system for gaming to date.

sp

Edited January 6, 20233 yr by Sky_Pilot071

On 12/30/2022 at 9:56 PM, andyjohnston.net said:

I can't speak for everyone, but there are so many CTDs now that this program has become essentially useless.

You don't speak for me, certainly. I had no CTD for a long time. Are you on the Beta?

20 hours ago, Luke said:

Yes, no overclock beyond standard manufacturer OC on the GPU

The only CTDs I remember having with MSFS were caused by exactly this (in my case, using the undervolt feature on my RX5700). Try turning off ALL forms GPU tuning.

1 hour ago, Johan217 said:

The only CTDs I remember having with MSFS were caused by exactly this (in my case, using the undervolt feature on my RX5700). Try turning off ALL forms GPU tuning.

I think you misunderstand - I'm not doing any GPU tuning beyond what the manufacturer does natively.

Cheers!

 

My bad. Hope you get it working soon.

12 hours ago, Funky D said:

Not a peep about updated drivers or BIOSes either. It's almost as if he came here, typing "garbage" in an all-caps large font, hoping for sympathy from a bunch of users with the same problem. When he heard from a bunch of people with zero issues instead, it's almost as if he doesn't want to admit there is any possibility that his machine is the problem and doesn't want to do any in-depth troubleshooting because P3D works fine. I'm not gonna take the bait, and I empathize for the people giving detailed troubleshooting tips only to receive no response. Maybe I'm wrong here, but I just call em as I see em.

Yeah, we have asked a lot of questions and are actively trying to help but we are not getting the answers. 

4 hours ago, Luke said:

I think you misunderstand - I'm not doing any GPU tuning beyond what the manufacturer does natively.

Cheers!

 

We have not misunderstood. We have asked several questions trying to help you and you're not answering them. Again, does this happen without the PMDG plane installed? Are you a part of the beta? Do you have anything installed from the Asobo Marketplace? BIOS updated? 

Does this happen with a 100% default simulator? If so I would just reinstall the simulator because you're getting problems most are not getting at all. 

This simulator has frustrating moments but its not useless. 

Edited January 6, 20233 yr by Sonosusto

On 1/4/2023 at 3:12 PM, ckyliu said:

Could you partition your hard drive and place a fresh install of Windows and MFS on that to see if the problem persists? Don't put anything else on the install at all... run with the minimum of peripherals/controllers to start with... I know the above is an arduous pain in the posterior but sounds like the most time effective option at this point if you've "picked the low hanging fruit"

I think at this point (indeed, some time ago), the above is needed: Installing vanilla MFS on a fresh Windows install. That would answer a lot of questions.