The AMD Driver Thread

[EastCoastHandle]

Saying that the TDR issues are purely non GPU h/w related is not entirely accurate imo.

From AMD's own release notes...

Fixed Issues

When Instant Replay is enabled, a TDR or black screen may occur when launching games or applications.
Metro Exodus™ may experience an application hang or TDR when choosing some specific dialogue prompts in the Sam’s Story DLC.
Battlefield™ V may experience an application hang or TDR after extended periods of play.

So they acknowledge they have addressed some TDR issues.

Also under know issues....

Enhanced Sync may cause a black screen to occur when enabled on some games and system configurations. Enhanced Sync has been temporarily disabled from the gaming profile and any users who may be experiencing issues with Enhanced Sync enabled should disable it as a temporary workaround.

Playing Endless Legends with a browser open on the seconds screen playing video I can pretty much guarantee a TDR bugcheck reboot with Enhanced Sync enabled, I don't when it is disabled.

Also from the Microsft support doc posted above...

You may need to install the latest updates for your display driver, so that it properly supports the TDR process.
Visual effects, or too many programs running in the background may be slowing your PC down so that the video card can not respond as necessary.

Both of which are software, not hardware, fixes and include updating display drivers.
Not that a lot of support docs are 100% accurate a lot of the time, more a here's a list of everything kind of related we can get you to waste time checking.


TDR's can and do result in black screens, depending on how far it manages to get through the TDR process. I also wonder how long people are waiting to let their PCs properly bugcheck and reboot and how often they check their event logs or mem dumps afterwards for the bugcheck code.
Rather than just hitting the power button each time the screen goes blank ?

Just saying that this particular VIDEO_TDR_FAILURE is just a driver problem is not accurate imo when there are other factors. I think we need to get an understanding on that first. Which is the content of confusion. We arent talking about enhanced sync/instant replay. We know thats the problem. However, he was rebooting, for example, when he encountered a problem. So the two dont relate.

Secondly, he has posted problems with his motherboard. In which there was no real fix. Be that as it may it could very well be a driver problem. However, I seriously doubt it knowing this information. Which shouldn't be ignored or just glossed over as just a unknown, random TDR. We know what the error is (VIDEO_TDR_FAILURE).

Using the term TDR to imply that the condition is unclear is a tad specious. In this case we know what is contributing to the issues. So we can pinpoint it. It's not a hard process. However I think you're convoluting the issue to be more cumbersome then necessary to call a VIDEO_TDR_FAILURE as a blackscreen, driver issue when its documented that there are other factors to consider.

 

[Techen]

So having a mess around on my navi rig, Anyone else getting these issues?

Framerates drop when steam messages pop up mainly in rocket league, It drops the FPS to 1 during the pop up and pop down. Can confirm does not happen on my nvidia rig.

Battlefield 5 still sees really bad issues with gpu usage, With lows of 60fps and highs of 140fps in someplaces compared to a 1660 super that can get 80-90fps on the same settings/res.

Overlay crashes the control panel often, I don't have MSI installed or anything but after awhile the overlay will die and then control panel breaks.

I've reported all three to AMD anyway so I'll be curious to see if they appear on the known list next patch but while these new drivers are good, I haven't had any blackscreen issues since updating the other issues are a real shame.

 

[chaosophy]

Just saying that this particular VIDEO_TDR_FAILURE is just a driver problem is not accurate imo when there are other factors. I think we need to get an understanding on that first. Which is the content of confusion. We arent talking about enhanced sync/instant replay. We know thats the problem. However, he was rebooting, for example, when he encountered a problem. So the two dont relate.

Secondly, he has posted problems with his motherboard. In which there was no real fix. Be that as it may it could very well be a driver problem. However, I seriously doubt it knowing this information. Which shouldn't be ignored or just glossed over as just a unknown, random TDR. We know what the error is (VIDEO_TDR_FAILURE).

Using the term TDR to imply that the condition is unclear is a tad specious. In this case we know what is contributing to the issues. So we can pinpoint it. It's not a hard process. However I think you're convoluting the issue to be more cumbersome then necessary to call a VIDEO_TDR_FAILURE as a blackscreen, driver issue when its documented that there are other factors to consider.

You appear to have completely misread and completely misread into, both the meaning and motive of my post.

I merely pointed out that those errors can be both software and hardware related.

To tell someone that they should only be looking to replace their hardware and that there was nothing AMD (or the end user) could, or should be looking at to see if these issues can be fixed in software is just wrong.

Which you seem to both agree and disagree with in your reply.

 

[EastCoastHandle]

To tell someone that they should only be looking to replace their hardware and that there was nothing AMD (or the end user) could, or should be looking at to see if these issues can be fixed in software is just wrong.

This is a figment of your own doing. I did not tell him to 'replace hardware'. I did tell him that what fixed the issue for someone else was the psu. The error is VIDEO_TDR_FAILURE, not just a TDR.
The information about the error can be found from Microsoft, not from AMD: https://docs.microsoft.com/en-us/wi.../debugger/bug-check-0x116---video-tdr-failure
I didn't mis-read your post, you speciously claim that I said it wasn't just an AMD driver problem when there are other factors to consider.
Furthermore, he's had issues with his motherboard already. None of which you mentioned nor considered in your reply to me.
"You appear to have completely misread.. both the meaning and motive of my post."...is an understatement from my prospective when you admit (unwillingly):

Which you seem to both agree and disagree with in your reply.

Which clearly demonstrates that I've pointed out a larger prospective into the VIDEO_TDR_FAILURE then just amd bug list that you posted...which had nothing to do with the problems posted. Furthermore, I wouldn't get someone hopes up thinking that "the next driver" is going to solve their problem either.

 

[gpuerrilla]

Must admit I have seen that generic error on many a system and even laptops, its on nvidia systems too so diving deeper to find the culprit paints a better picture than sweeping statements.

 

[chaosophy]

This is a figment of your own doing. I did not tell him to 'replace hardware'. I did tell him that what fixed the issue for someone else was the psu. The error is VIDEO_TDR_FAILURE, not just a TDR.
The information about the error can be found from Microsoft, not from AMD: https://docs.microsoft.com/en-us/wi.../debugger/bug-check-0x116---video-tdr-failure
I didn't mis-read your post, you speciously claim that I said it wasn't just an AMD driver problem when there are other factors to consider.
Furthermore, he's had issues with his motherboard already. None of which you mentioned nor considered in your reply to me.
"You appear to have completely misread.. both the meaning and motive of my post."...is an understatement from my prospective when you admit (unwillingly):

Which clearly demonstrates that I've pointed out a larger prospective into the VIDEO_TDR_FAILURE then just amd bug list that you posted...which had nothing to do with the problems posted. Furthermore, I wouldn't get someone hopes up thinking that "the next driver" is going to solve their problem either.

ok whatever. It's clear you're not open to any kind of discussion and just want to twist and misunderstand things to get an argument out of it.
I have no interest in going down that road.

 

[TNA]

ok whatever. It's clear you're not open to any kind of discussion and just want to twist and misunderstand things to get an argument out of it.
I have no interest in going down that road.

Waste of time talking to him. Surely you would have noticed that with my exchange with him a few pages ago. Nothing is AMD’s fault, always something else or the users apparently

 

[chaosophy]

Waste of time talking to him. Surely you would have noticed that with my exchange with him a few pages ago. Nothing is AMD’s fault, always something else or the users apparently

Yeah, I think it dawned on me after the second reply. Then I recognised the name and thought nah not worth it.

 

[EastCoastHandle]

ok whatever. It's clear you're not open to any kind of discussion and just want to twist and misunderstand things to get an argument out of it.
I have no interest in going down that road.

Waste of time talking to him. Surely you would have noticed that with my exchange with him a few pages ago. Nothing is AMD’s fault, always something else or the users apparently

Yeah, I think it dawned on me after the second reply. Then I recognised the name and thought nah not worth it.

You make it very obvious that you are trolling/having a go in the AMD driver thread. There is no technical troubleshooting skills exhibited by either of you that would truly help a user try to resolve the issues they are having. All you want parrot and harp on is to say it's amd's fault.

Thus showing no previous experience, technical know-how, nor critical thinking into the problems that would exhibit any technical help to the issues at hand. You will ignore technical papers, links to documentation, prior history of PC problems, Etc. that clearly show examples to those issues which I have provided.

No one can talk to you because you ignore all evidence contrary to your own personal belief that it must be an AMD issue and AMD only. Therefore the only accusations that you can make when refuted is I'm somehow defending them. Which is comical to say the least because you have nothing else to say.

If there is a driver issue it would behoove you (anyone really) to report it directly to AMD and/or ask the community for help. So it can be address instead of using someone's personal PC problem as a talking point not to buy AMD in an attempt to discourage other people. I'm sure those who actually want help don't want to be used like that.

 

[TNA]

You make it very obvious that you are trolling/having a go in the AMD driver thread. There is no technical troubleshooting skills exhibited by either of you that would truly help a user try to resolve the issues they are having. All you want parrot and harp on is it say amd's faults.

Thus showing no previous experience, technical know-how, nor critical thinking into the problems that would exhibit any technical help to the issues at hand. You will ignore technical papers links to documentation, prior history of PC problems, Etc that clearly show examples to those issues which I have provided.

No one can talk to you because you ignore all evidence contrary to your own personal believe that it must be AMD and AMD only. Therefore the only accusations that you can make towards me is I'm somehow defending them. Which is comical to say the least.

If there is a driver issue it would behoove you to report it directly to AMD. So they can address it instead of using it as a talking point not to buy AMD.

What a load of rubbish from you as usual

 

[chaosophy]

You make it very obvious that you are trolling/having a go in the AMD driver thread. There is no technical troubleshooting skills exhibited by either of you that would truly help a user try to resolve the issues they are having. All you want parrot and harp on is to say it's amd's faults.

Thus showing no previous experience, technical know-how, nor critical thinking into the problems that would exhibit any technical help to the issues at hand. You will ignore technical papers links to documentation, prior history of PC problems, Etc that clearly show examples to those issues which I have provided.

No one can talk to you because you ignore all evidence contrary to your own personal believe that it must be AMD and AMD only. Therefore the only accusations that you can make towards me is I'm somehow defending them. Which is comical to say the least.

If there is a driver issue it would behoove you to report it directly to AMD and/or ask the community for help. So it can be address instead of using it as a talking point not to buy AMD in an attempt to discourage people.

ok I said I'd stay out of it but I'll bite as you seem to be completely misunderstanding me to the point of now totally misquoting me.

re: the bits in bold of your above message, show me where and how any of this is true?

Again... (seeing as you're either ignoring it or having trouble understanding it)

"I merely pointed out that those errors can be both software and hardware related."

You appear to have taken this as me somehow blaming or attacking AMD?
Not everything is is 100% one way or the other, not every post is an argument or an attack. You need to chill out and actually take the time to read what people are saying, rather than instantly going on the defensive and thinking about what rambling response you're going to come up with next.



Also, not that I should need to justify myself to you and have no way - or inclination - to prove it to you, I feel I should tell you that I have only ever owned ATi/AMD graphics cards (to list a few that I can remember 9800 aiw, X800, X1950, 2900, 4870x2, 5870, 7970, Fury, Vega64), the only nVidia h/w I have ever owned was an nForce chipset on an old mobo and the chip in the Nintendo Switch. I've also worked in IT support for about the last 25 years for two of the biggest companies in their field. I'm certainly not going to take any kind of technical advice from you, hell half the time I'd not take it from MS support and just fix the issue myself before we could get it escalated to someone who had half a clue as to what the issue was.

 

[TNA]

ok I said I'd stay out of it but I'll bite as you seem to be completely misunderstanding me to the point of now totally misquoting me.

re: the bits in bold of your above message, show me where and how any of this is true?

Again... (seeing as you're either ignoring it or having trouble understanding it)

"I merely pointed out that those errors can be both software and hardware related."

You appear to have taken this as me somehow blaming or attacking AMD?
Not everything is is 100% one way or the other, not every post is an argument or an attack. You need to chill out and actually take the time to read what people are saying, rather than instantly going on the defensive and thinking about what rambling response you're going to come up with next.



Also, not that I should need to justify myself to you and have no way - or inclination - to prove it to you, I feel I should tell you that I have only ever owned ATi/AMD graphics cards (to list a few that I can remember 9800 aiw, X800, X1950, 2900, 4870x2, 5870, 7970, Fury, Vega64), the only nVidia h/w I have ever owned was an nForce chipset on an old mobo and the chip in the Nintendo Switch. I've also worked in IT support for about the last 25 years for two of the biggest companies in their field. I'm certainly not going to take any kind of technical advice from you, hell half the time I'd not take it from MS support and just fix the issue myself before we could get it escalated to someone who had half a clue as to what the issue was.

He will either stop responding now that you have put him in his place or get even more defensive/angry and type more childish rubbish. I myself like you have probably owned more ATI/AMD GPU's than he has been alive based on his immature posts.

 

[Darujhistan]

Anyone help?

New drivers have totally broken my desktop, can't run 2nd monitor @ native 1080p anymore, everything else stuck at 60FPS despite changing things in the POS app, and in game.

What's the best way to run an AMD GPU card on its own (currently playing with MSI AB) and to set up games individually without having to use the garbage bundled AMD software?

 

[Bacalhau]

He will either stop responding now that you have put him in his place or get even more defensive/angry and type more childish rubbish. I myself like you have probably owned more ATI/AMD GPU's than he has been alive based on his immature posts.

He's also making friends at guru3d...

 

[Curio]

He will either stop responding now that you have put him in his place or get even more defensive/angry and type more childish rubbish. I myself like you have probably owned more ATI/AMD GPU's than he has been alive based on his immature posts.

My first video card was an ATi 3D Xpression based on the Rage II chipset. I suspect that was at least 5 years before he was even born

 

[TNA]

He's also making friends at guru3d...

My first video card was an ATi 3D Xpression based on the Rage II chipset. I suspect that was at least 5 years before he was even born

 

[LtMatt]

Men, take a deep breath. There is more to life than arguing on a forum.

 

[TNA]

Men, take a deep breath. There is more to life than arguing on a forum.

Tell that to EastCoast. His types do more damage to AMD than help imo.

 

[EastCoastHandle]

Men, take a deep breath. There is more to life than arguing on a forum.

No problem Matt.

 

[LtMatt]

Tell that to EastCoast. His types do more damage to AMD than help imo.

Let it go TNA.