- Dec 1, 2018
- 2,169
- 2,080
At least it seems no AMD user is experiencing the strange mesh distortion problem anymore didn't heard anything about that anymore 
The other issue now seems to be caused by the Volumetric Lights used in that exact spot to get a certain wow effect
It helped 1 AMD user reportedly so far to disable the Volumetrics in the Video Setup to avoid the crash on his RX580 (Polaris GCN 4), but it could be random as another one reported it didn't avoid the crash when he disabled the Volumetrics and that makes it now super strange, though it's still unclear if he really disabled it correctly.
It could be also that those cards are overly wrong Overclocked or get just to Hot and the Volumetrics stress it to a timeout, this is especially problematic on the Windows 10 Hardware Security Architecture.
If a Device isn't reacting fast enough Windows 10 assumes a instability or attack on the Hardware and brakes the drivers connection to avoid damage or a low level intrusion.
This also happens on pre Windows 10 but on Windows 10 the stability checks are deeper and it's reacting faster to very small deviations from what it expects to be a normal state.
You can higher the timeout before a so called TDR (Timeout Detection and Recovery) happens to give the driver/hardware more time to react but there are more indeepth Kernel checks in Windows 10 those you can't change.
Windows 10 will be pickier when it doesn't like what it sees and also try to protect itself with higher force, it reacts very fast to instabilities
And most of the times it sees OC as a instability or even a attack and goes very fast into Red Alert Mode.
The other issue now seems to be caused by the Volumetric Lights used in that exact spot to get a certain wow effect
It helped 1 AMD user reportedly so far to disable the Volumetrics in the Video Setup to avoid the crash on his RX580 (Polaris GCN 4), but it could be random as another one reported it didn't avoid the crash when he disabled the Volumetrics and that makes it now super strange, though it's still unclear if he really disabled it correctly.
It could be also that those cards are overly wrong Overclocked or get just to Hot and the Volumetrics stress it to a timeout, this is especially problematic on the Windows 10 Hardware Security Architecture.
If a Device isn't reacting fast enough Windows 10 assumes a instability or attack on the Hardware and brakes the drivers connection to avoid damage or a low level intrusion.
This also happens on pre Windows 10 but on Windows 10 the stability checks are deeper and it's reacting faster to very small deviations from what it expects to be a normal state.
You can higher the timeout before a so called TDR (Timeout Detection and Recovery) happens to give the driver/hardware more time to react but there are more indeepth Kernel checks in Windows 10 those you can't change.
Windows 10 will be pickier when it doesn't like what it sees and also try to protect itself with higher force, it reacts very fast to instabilities
And most of the times it sees OC as a instability or even a attack and goes very fast into Red Alert Mode.
Last edited:
