Each graphics card is different reacts differently with an OC not a driver problem. Still it will show up as a driver issue in the logs
The whole system is complex, many variables as you said. Updates happen frequently. On one it works on the other it crashes. Even log will always say application crashed due to a driver issue. Not saying what caused the driver to crash. it may be not a driver issue but system has a problem. You can't expect a driver to fix system's bad config or a problem in the newly released driver.
Example: Look at the problems with the 1903 (i suppose it was that one for windows 10). (CPU usage on certain machines surges to 30%) Is that CPU's driver problem?
In general sense you want to say driver issue and that AMD screws that up because it is easy. You have no data about all the individual incidents and it is easier to blame AMD for driver issues.
Feature issues newly implemented in some games may occur (driver updates for AMD adrenaline) switch the feature off no driver issues. The feature needs tweaking because it is damn new and that is why.
Games problem. Windows event log will still say application crash due to a driver issue. Not a driver issue but still application caused the driver to crash.
I hope you see where I'm going with this. The actual driver issues are rare but it will always show up in the logs as a driver issue. Your perspective changes when you do actually realize, like you said, that there's 100 (or more) variables that can cause the issue but the driver will be the one to blame always. (or at least most cases). Graphics drivers are not for fixing other variables' wrong doings or fails but the driver is to display pictures.
There is an abstraction layer, or several, between driver/GPU and the rest of the system for all the data it gets. There goes your story... the GPU is supposed to feed off that, and not all other sorts of requirements in the system. In the end, thát is really what is happening here, and drivers are really an assortment of compatibility bits to cater for a wide range of situations. The quality of the driver is expressed like that: how compatible is it, to all those situations. How does it handle them in case of a problem. Will it CTD, will it give you a TDR (Timeout/Device removed; as is Nvidia's way of keeping the system operational with the GPU in safe mode), or will it already guide the user to recommended / restricted settings. Or will you get a BSOD with some random error string.
So yes, I get you, but I still disagree we should not blame the driver
The driver is the most fundamental piece of the puzzle here, for all software running on a GPU.
After that it is up to Nv/AMD to fight the battle with devs over who should change what. NOT my problem and once it becomes one, said company is on my shitlist. When Nvidia did not bring SLI support for Elder Scrolls Online back in the day, it was clear as day to me: this is the last SLI setup ever, go screw yourselves. Trust is hard to gain, and instantly lost. And in hindsight, that was a very good decision, Look where multi GPU is at today.
That is exercising customer power. Act on your findings and support quality. Being lenient on companies for screwing up only allows them to repeat it.
I think you completely miss understood what I was trying to explain. And this isn't me experimenting, this is several comments from others off Reddit and forums. If you have overclocked UNSTABLE MEMORY or CPU, then install a Radeon Graphics Card, and you get Blue Screens, how is that the GPU's fault?? The suggestion was to default stock your CPU & RAM, install your graphics cards, only to Eliminate an ALREADY unstable CPU & RAM overclock, so they wouldn't blame the GPU, then once you have your GPU Drivers installed, go at it with the CPU & RAM OC if you choose.
Yes I'm a total geek & can assemble a gaming PC with my eyes closed if need be. lol
Oh and a FYI, there was plenty of Nvidia drivers that bricked or fried GPUs almost every year, some even pulled out of circulation by Nvidia.
Point taken, and great, so let's cross that one off then. But it does seem odd that the insertion of a GPU is cause to make a reddit topic about BSODs due to your non GPU OC, is it not? But if that was the case, how was it even relevant to begin with? Its clear that such a thing is not a GPU issue, so why even use it as an example...
I mean yes, I fully understand the point you and
@ratirt are making here that not all problems
originate from the GPU. But in every single case, the truth comes to light and the trend is that the vendor is very, very slow and rather weak at providing fixes for the problems that DO originate from the GPU. And the fixes are also not always good ones. But the biggest question mark to me is why AMD is still using a waterfall principle for its releases of drivers. Big releases instead of cutting them up in many smaller ones, working iteratively... definitely something Nvidia approaches in a much more modern way.
In case you're like WTF is he on about...:
What's the difference between Agile vs Scrum vs Waterfall vs Kanban? Here's everything you need to know about these project management methodologies.
www.smartsheet.com
And ehm... you're gonna have to back up that 'almost every year' of bricked GPUs
due to drivers with some sources, because as far as I know, there has been one truly documented instance of it, maybe two.