AnsweredAssumed Answered

ANY custom Wattman settings causing "thread_stuck_in_device_driver" BSOD

Question asked by nunklen on Jan 11, 2019
Latest reply on Apr 14, 2019 by ssin

Hello,
Problem:
When adjusting any custom wattman settings, (adjusting fan curve, increasing power limit, setting clocks, etc..) or even just turning on virtual resolution, the system hangs and i receive BSOD "thread_stuck_in_device_driver".

 

My set up:

GPU: 2x reference air VEGA 64

CPU: 1x Ryzen 7 2700x

MOBO: X470 Gaming Wifi 7

RAM: 32GB 3200 cl14

DISPLAY 1: 1x 4k Display 60hz

DISPLAY 2: 1x 4k Display 60hz (tested both TV -HDMI- and monitor -DP/HDMI-)

DISPLAY 3: 1x 2560x1440 display 144hz

 

Observations:
-Disconnecting one of the connected displays allows wattman settings to be manipulated and applied as expected.
or
-Lowering resolution of one of the 4K monitors to 1080p allows wattman settings to be manipulated and applied as expected.


-No change in behaviour is seen when connecting 1 monitor through hdmi instead of DP.

 

-Turning off Crossfire has no effect if all 3 displays are connected to the same Vega.

 

-Crossfire disabled: i can connect 1 Display to the second card and both will function as expected independently.

I've tried with both December adrenaline driver and the latest Jan update. (SAFE mode DDU in between)

 

I know its a very uncommon occurrence, i just wanted to see if anyone has seen this or know of an easy way to fix.


Thanks!

Outcomes