Tested my old E5 earlier and I find that the Vega FE works flawlessly (no crashes with freesync enabled displays connected). Yep, it's definitely something specific with my Threadripper build. Sadly seems to still cause the BSOD, however, yet I've found that if I remove the freesync support completely - BSOD's stop on display detection (as in, I can unplug and reconnect the monitors hundreds of times without a crash). (40-144 being the normal range supported) Tried changing the freesync range to 34-90 using CRU, and also to 40-90 and 40-60. It seems strange if it's a dud considering it's load stable, including in low-load games where the clocks bounce all over the place. Lowered the PCI-E slot to 2.0, and also tried different PCI-E slots (physically moving the card).Īny suggestions short of testing the card in other computers? Different DisplayPort cables, and an HDMI cable as well.Īs a last ditch effort, I updated that ASROCK board to the 3.50 bios.
#WHAT THREAD STUCK IN DEVICE DRIVER MEAN INSTALL#
I've also tried the use of DDU, cleaning up between installations, and a fresh install of 1809 before the latest attempt with 19.2.2. Locking clockspeeds at the maximum via wattman or ClockBlocker ( cough) does not improve those odds. The card is otherwise 100% stable in games or on the desktop as long as the monitor connection is not touched and the display is not permitted to enter standby or otherwise turned off. Problem: Anytime that the display enters or exits standby mode (OR is connected to the PC) there's what I'd call a 50/50 chance of having the above BSOD (Thread Stuck in Device Driver). Threadripper 1950X stock, tested stable)īenQ XL2730Z, also tested an Acer display. Since installing that card, I've been having non stop "Thread Stuck in Device Driver" BSOD's. Recently managed to get my hands on a "new" Vega FE Liquid at a steal of a price. Finally upgraded and retired my old Fury.
0 kommentar(er)
