A few people and myself was telling him it was his word not allowed amd gpu that was the cause of his ctd. I'm glad he listened and decided to change it. I'm happy for you you @Bobsk8@Bobsk8 🤣

I think if you learn anything from this process is just because it is new doesn't mean it can't cause problems. I got an EVGA 3080 FTW and it actually ran MSFS fine, no crashes. But then when I tried to play a different game it would constantly crash to desktop. Turns out that the OC that EVGA did wasn't quite able to handle the temps in A my case, and B this particular game that constantly hammers the GPU (somehow more so than MSFS).

Of course once I found that out I went the extreme route and went to water cooling. No more CTDs!

Lesson... Electronics today are finicky as we are pushing the limits of Moore's law and power consumption, heat dispersion it will only get worse. 

 

Glad you got it sorted.

Hmm, my close to 6 year old AMD gpu never caused me any issues, and I've been using AMD for all my gaming for over 12 years. But, whatever.

19 hours ago, Bobsk8 said:

Now comes the bad part, almost immediately I started having CTDs. I would go sometimes for a few days, and then a rash of CTDs would start, sometimes every other flight. Most of these would happen on approach and landing. The other thing that would happen is AMD driver timeouts. I would get one of these about every 8-10 CTDs. I tried every suggestion that people made, on getting rid of these CTDs, and sometimes they would stop for a few days, and then start again with a vengeance. Now when I posted my problems, a few people said " There must be something wrong with your system"...Now the money I spent for this brand new PC, was alot for me, being semi retired and on SS plus a small part time consulting. So I denied that my new PC was a fault, it must be bugs in MSFS2020 because others were reporting identical problems. 

So where does the apology come in, well that is because I argued with several people telling that the issue must be my PC, and not MSFS2020, and I would deny that this couldn't be true, because I had a brand new PC. So they were right, and I was wrong.  Anyway, I am so grateful for CLX fixing my problem, and now MSFS is a joy to fly.  

The fact the many thousands were running the software without the CTD was a strong indication that the problem might be with your hardware.  Glad it all worked out!!

Edited June 29, 20214 yr by Tierborn

Now I know which GPU’s to stay away from. 

19 hours ago, Bobsk8 said:

Yeah, I have thought about that. All voltages seemed normal, but an intermittent like that is rough to diagnose without just swapping it out with another part. 

This is why I never cheap out on the PSU. It's the single easiest failure point or headache generator. Not saying you  did but a lot don't think investing in a high end, name brand PSU is worth it because "Its just the electricity!!!" 

Happy flying, and always nice to see someone have some humble pie and own up to something. 

Edited June 29, 20214 yr by styckx

1 minute ago, styckx said:

This is why I never cheap out on the PSU. It's the single easiest failure point or headache generator. Not saying you  did but a lot don't think investing in a high end, name brand PSU is worth it because "Its just the electricity!!!" 

Happy flying, and always nice to see someone have some humble pie and own up to something. 

There is one popular manufacturer of Pre Builts that uses a PSU that is so bad, in the majority of their PCs, that reddit advices people that bought one from them to not turn it on until they replace the PSU. Apparently, when the PSU in their products goes bad, it sometimes smokes the rest of the unit. 

I'd bet on the PSU as well. I used different AMD cards for years and never had issues with any of them. I'm on Nvidia now because when I needed a GPU there was no offering from AMD with the necessary computing power. I will definitely check them out when buying the next one though.

Also in my experience there will not be driver issues with AAA games on AMD that last longer than the initial days. They fix those just like Nvidia does.

I just switched from a RTX2080Ti to a Radeon 6900XT and no issues at all with FS2020.

 

sam

Glad you were persistent in finding a solution. MSFS is truly amazing when it works right, but when it doesnt it makes me want to throw my PC out of a Cessna 172.

On 6/28/2021 at 7:38 PM, Bobsk8 said:

Now comes the bad part, almost immediately I started having CTDs. I would go sometimes for a few days, and then a rash of CTDs would start, sometimes every other flight. Most of these would happen on approach and landing. The other thing that would happen is AMD driver timeouts. I would get one of these about every 8-10 CTDs.

Hi Bob,

when I started to read your post, I thought, hey, he is talking about me!!! Because I had  a new PC shipped to my home two weeks ago (specs in my signature) with everything AMD for the first time. I could never finish a flight that lasted longer than 15 minutes before I had a CTD. But in my case it wasn't the power supply, it was the GPU driver. The worst case was, after I had started to load the payware Caudron Rafale plane. I had a CTD within 5 minutes, guaranteed. And each time, I sent a report in to AMD. They must have received some 15 from me. At one point I sent them a pretty angry e-mail, telling them that this new MSFS thing is not one of these tiny niche market flightsims, but the real thing. And if they don't get their act together quickly, this could hurt their business for some time. 

Yesterday I received a note that the driver had been upgraded from 21.3.1 to 21.6.1. I installed it and hallelujah, my problems were gone. I flew the Caudron for over an hour and nothing happened, MSFS behaved flawlessly. I'm a happy camper again!! 

10 minutes ago, bernd1151 said:

Hi Bob,

when I started to read your post, I thought, hey, he is talking about me!!! Because I had  a new PC shipped to my home two weeks ago (specs in my signature) with everything AMD for the first time. I could never finish a flight that lasted longer than 15 minutes before I had a CTD. But in my case it wasn't the power supply, it was the GPU driver. The worst case was, after I had started to load the payware Caudron Rafale plane. I had a CTD within 5 minutes, guaranteed. And each time, I sent a report in to AMD. They must have received some 15 from me. At one point I sent them a pretty angry e-mail, telling them that this new MSFS thing is not one of these tiny niche market flightsims, but the real thing. And if they don't get their act together quickly, this could hurt their business for some time. 

Yesterday I received a note that the driver had been upgraded from 21.3.1 to 21.6.1. I installed it and hallelujah, my problems were gone. I flew the Caudron for over an hour and nothing happened, MSFS behaved flawlessly. I'm a happy camper again!! 

Everytime I had an AMD driver timeout, I would fill out the form that popped up which went to AMD.  I must have placed over 20 of them at least. I am sure others are doing the same thing. 

Glad you got it sorted, Bob. Kudos to the PC company for the good support.

You don't need to apologize, it's human nature to equate "new" with "good".

People need to realize that every single component on a MB, GPU, memory stick, or in a power supply was picked out of a bin of hundreds or thousands like it. A simple capacitor or other component can be slightly out of spec and cause problems. Usually the oddball type, where everything works great 99% of the time. Like your situation. For some components, quality control only examine samples of each production run instead of every unit made. Unfortunately, some bad components make their way into new product. The company that used it ends up taking the hit from the customer. The company that made the bad component gets away with it. I think the new, larger p/s fixed your issue.

I am thrilled to see that MS2020 continues the age old Flight Simulator tradition of being one of the best dang pieces of diagnostic software ever made. If a machine will run Flight Simulator, it'll run anything. Bank on it. 

On 7/1/2021 at 2:48 AM, Bobsk8 said:

Everytime I had an AMD driver timeout, I would fill out the form that popped up which went to AMD.  I must have placed over 20 of them at least. I am sure others are doing the same thing. 

AMD GPUs are banned in my workplace for client/workstation  use because over 100's of machines they tend to have more driver issues and bluescreens then nvidia GPUs and that costs us money. 

However by "more driver issues" we are talking 6 or 8 machines having glitches in a 6 month period out of a 100 for maybe 2 or 3 Nvidia machines. However in an enterprise situation where you can lose thousands of dollars an hour with a system down that makes a big difference.

Does that make them bad for gaming ? Not at all   The chances of individual users having an issue with just one or at the most two systems at home is small and generally even if you do get an issue it is just a Saturday afternoons to get it sorted. For personal use go with whatever is the best bang per buck.

As for servers, it would be truly wonderful if our software ran on server class top end AMD processors and GPUs as Xeon Gold's and A100 tesla are worth tens of thousands more than the AMD equivalent but unfortunately our stats software is Intel/nvidia only and getting it recoded for AMD would cost more than we would save.

.