Instant TDR when using Ogre samples

[darksylinc]

RGP version: RadeonDeveloperTools-2020-09-11-26
Drivers: win10-radeon-software-adrenalin-2020-edition-20.9.1-sep16.exe
OS: Windows 10 2004 (64 bits)
System:

CPU:       Quad core Intel Core i7-7700 (-MT-MCP-) 
           arch: Skylake rev.9 cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28800
           clock speeds: min/max: 800/4200 MHz 1: 800 MHz 2: 800 MHz
           3: 800 MHz 4: 800 MHz 5: 800 MHz 6: 800 MHz 7: 800 MHz 8: 800 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X]
           bus-ID: 01:00.0 chip-ID: 1002:67ff
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Radeon RX 560 Series (POLARIS11)

MINIDUMP IS AVAILABLE UPON REQUEST (privately)

How to reproduce:

Start RGP service and Control Panel
Download Ogre Vulkan Samples, and open bin/Release/Sample_PbsMaterials.exe

RGP control panel will recognize the app and within a few seconds, before Ogre's config dialog shows up, all screen turn off and either the system restarts after dumping memory contents to disk; or the whole system locks up (even reset button doesn't work)

Please note that TDR happens before Ogre's config dialog is showing up. The only thing we do then is probe D3D11, GL and Vulkan for support. We don't create a window or start rendering yet.

Workaround

Edit bin/Release/plugins.cfg and comment the D3D11 and OpenGL plugins, leaving only Vulkan:

 Plugin=RenderSystem_Vulkan
# Plugin=RenderSystem_Direct3D11
# Plugin=RenderSystem_GL3Plus

[chesik-amd]

The TDR should no longer occur with recent drivers, but there are still some timeouts in Radeon Developer Panel that may occur when profiling Ogre samples. The RDP team is aware and has investigated this issue with the driver team.