So that's trivial, the main problem is that the AMD graphics driver crashes, causing other effects. It has no "render target" (or valid output device) when the driver crashes and before the Basic driver is loaded, causing it to crash. Because applications that rely on the driver to be properly loaded, may crash when it fails: just like dwm.exe presumably does, as seen in my screenshot above. This can explain why some people are complaining about related things (like RadeonSoftware.exe or interface crash): it's a side-effect of the graphics driver (momuntarily or entirely) crashing. Note: if your entire driver crashes per this issue, a bunch of WER error reports will be generated of independent AMD-related or reliant processes, in the folder C:\ProgramData\Microsoft\Windows\WER\ReportArchive (or ReportQueue, if checked too early) it will look like this: This state is one where if you close the game, your AMD driver will still be loaded and there is no need to restart your PC entirely to make use of it again.
or the flickering lasts a while and you can continue, albeit, in some games, the visuals will look pixelated and low-resolution if your driver doesn't forcibly crash. That means you will need to restart your PC, since the Device Manager will show an error code for your GPU.ġ) At any random moment, often shortly after launching the game, screen will start to flicker (black and back to your screen output, so forth, so forth).Ģ) Depending on how bad the case is (in my experience, varies per game that is affected) your GPU driver may either crash as seen in below screenshot ("Display driver failed to start", AMD driver crashed mid-game so Windows falls back on it)
So after i updated to the latest driver version (win10-radeon-software-adrenalin-2020-edition- 19.12.2-dec12.exe), some games will make my screen flicker a few times and then the graphics driver crash in such a way that Windows will load the Basics graphics driver.
0 kommentar(er)
