FWIW Hendrik has also said on multiple occasions that he solely tests on nVidia/Intel, and in less words isn't a big fan of AMD drivers.
I test and develop with the hardware I own and use. None of us here own a big lab full of hardware to test things on, its just what we have and use. There is practically no hardware specific work ever going into anything, that is not a level we even work on. We develop against the specifications provided by Microsoft for Direct3D or similar things for cross-platform. If we work on features that might require particular hardware capabilities, I'll always consider all 3 major brands, and ensure they work or have a fallback.
As for AMD, its just experience from doing hardware video for 15 years that has me not buy their hardware (quite a while before I even joined JRiver). There is a long history of problems specifically with video use (across many software products, not just LAV or MC), and a culture of not really being reachable for developers. This is just to illustrate where I'm coming from, and of course that won't help you if you have their hardware.
These kind of bugs, just from a development perspective, for example if a graphics driver crashes, or it disconnects the audio when we turn HDR mode on (to name another problem being brought up in another thread), there is really very little we can even attempt to do about that. There is no information in these crashes to really act on, and even less if its just a behavior problem without a crash.
For the crash above, it would already help if you determine if this was in Theater View, or in Video Playback. Both of those use quite different ways to interact with the hardware.