2 hours ago, Car147 said:

Good news, glad its working. I had the one ctd last night on the latest driver, but at least it was'nt the normal driver timed out error. Tonights was a Vcc Runtime error, removed them, and re installed so far so good.

Likewise, glad things are working for you. Proof, if it were needed, that there's rarely a "one solution suits everyone" scenario where computers are concerned! The rule of thumb is use the most recent driver (or program update) which works for you, only updating past that point if the older version has security issues.

Just had a 2nd 'display driver timeout' error message.

I will say that looking at the Windows Error Reporting logs, MSFS crashing shows up first, followed by a Windows Kernel error, followed the Radeon Software crashing (at which point the 'display driver timeout' error gets displayed).

It's not 100% clear to me where this crash originates, it's entirely possible the sim is causing it and leaving the display driver in some un-recoverable state as a result, and then Radeon Software shows the 'timeout error'.  So it might not be AMDs fault.

I filled out AMDs bug reporting tool, with links to 2 forum threads, and the windows error report files.  Maybe they care more about how their product is perceived than MS/Asobo do.

Edited January 31, 20215 yr by marsman2020

I wonder is it worth comparing hardware?

MSI M570 Pro M/Board

32gb DDR4 Ram

Power colour RX5700XT 8gb

AMD RYzen 3800X

No OC

I'm on an X570 Aorus Master, with 64GB of DDR3600 (XMP settings), a reference 5700XT, and a 3950X (no OC).

I'm going to go fly the same flight plan again and see if it might be a repeatable scenery related crash.

My specs are in my signature. I did try XMP for my RAM but found it caused problems with my PC in general so I haven't used that since shortly after installing MSFS. No overclocking and I undervolted my card as per the link further up the thread, but that's the only non-stock settings I have.

2 hours ago, Car147 said:

I wonder is it worth comparing hardware?

MSI M570 Pro M/Board

32gb DDR4 Ram

Power colour RX5700XT 8gb

AMD RYzen 3800X

No OC

 

WIN10 Pro

ASUS B550 Gaming F WIFI

AMD 3700X (PBO enabled)

Powercolor AMD 6800XT Red Devil / AMD Radeon Software ver 21.1.1  NON WHQL (Overcooked to 2500mhz core / 2140 Mhz Memory)

GSKILL 32 GB DDR4 @ CAS 16

ADATA 8200PRO 512GB NVME FOR OS DRIVE / ADATA 8200PRO 1 TB NVME for MSFS

 

New to the AMD graphics scene / No CTD's so far.

3 hours ago, marsman2020 said:

I filled out AMDs bug reporting tool, with links to 2 forum threads, and the windows error report files.  Maybe they care more about how their product is perceived than MS/Asobo do.

I hope you hear back from AMD. I agree I do not believe it is an AMD issue.

Ryzen 5 3600, Gigabyte 5700XT No OC, 32GB ram, B450 Tomahawk Motherboard, 1TB M.2 SSD

I had the Timeout issues every flight, until I rolled back to the late Sept Drivers. Now, not one. 

On 1/29/2021 at 4:14 PM, 109Sqn said:

Are the more recent AMD drivers less stable in MSFS?

Hi,

got my Radeon RX 6900 XT about a week ago, therefore I cannot judge older drivers. Since then I had a few flights about 200 nm long without crash. Yesterday I flew 2-times about 500-600 nm and at both flights I got a CTD at the end of the trip. Don‘t know wether my gpu, the Working Title cj4 mod, LittleNavMap or the FsEconomy client is to blame for?

Tom

6 hours ago, KSATRoadWarrior said:

I hope you hear back from AMD. I agree I do not believe it is an AMD issue.

I hope your right, the only thing i see so far is everyone is AMD  based for CPU, M/Board , And GPU

ASRock B550 Steel Legend

ASRock RX 6800 XT Phantom Gaming OC

AMD 5800X

G.Skill Ripjaws 32GB DDR4 3200 MHz

VPN 1TB M.2 NVME SSD

PSU 750W

Timeout CTDs here (sometimes, even once on the flight setup selection screen!?!) with my new RX6800 and Intel processor (10900).

I was leery of AMD but couldn’t see investing in a card with 10GB or less (and indeed have used close to 10GB on occasion).

Have not tried this September driver yet as I’m very hazy on how to roll back and forward again with AMD.

It's becoming clear this is a bigger issue than it appeared to be. Presumably most of you had thought you were just unlucky with CTDs as many of us get them at one time or another (only to be expected from a resource hungry and advanced sim), but now, as @Car147 says, there appears to be an all-AMD connection. Whether that's proof that 'fault' (if that's even the right term) lies with them is anybody's guess at this point.

Another day, another ctd. Luckily i had just landed.... This one is different, but has popped up at times..Complete crash and restart.. but at least this time it auto collected the data and has been sent direct to Microsoft.

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          01/02/2021 12:28:12
Event ID:      10016
Task Category: None
Level:         Warning
Keywords:      Classic
User:          DESKTOP-RRQ0PJV\clive
Computer:      DESKTOP-RRQ0PJV
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user DESKTOP-RRQ0PJV\clive SID (S-1-5-21-358272918-150920515-659634225-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10016</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2021-02-01T12:28:12.9817393Z" />
    <EventRecordID>31941</EventRecordID>
    <Correlation ActivityID="{f234f1f7-81af-4a41-947d-ad2b18f615ea}" />
    <Execution ProcessID="1344" ThreadID="2520" />
    <Channel>System</Channel>
    <Computer>DESKTOP-RRQ0PJV</Computer>
    <Security UserID="S-1-5-21-358272918-150920515-659634225-1001" />
  </System>
  <EventData>
    <Data Name="param1">application-specific</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
    <Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
    <Data Name="param6">DESKTOP-RRQ0PJV</Data>
    <Data Name="param7">clive</Data>
    <Data Name="param8">S-1-5-21-358272918-150920515-659634225-1001</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
  </EventData>
</Event>

 

Edited February 1, 20215 yr by Car147

Have an ASUS 5700 XT that started giving me the "driver timeout" approximately after the December update. Went back to the August driver and have had zero issues since. Most of my flying is bush type, low and slow. Really loving it. All AMD setup.

Edited February 1, 20215 yr by BlueGhost
additional comment.