- #Thread stuck in device driver windows 10 acer install#
- #Thread stuck in device driver windows 10 acer drivers#
- #Thread stuck in device driver windows 10 acer windows#
#Thread stuck in device driver windows 10 acer windows#
originally watching video would cause the problem to manifest, but now its only in D3D/gaming and also hardware accelerated google chrome windows and such. memtest shows now errors after 11 hours of testing. replaced my RAM, I have two different sets, but the issue persists when only one pair is in the board. (I now have two, both are behaving the same, together in crossfire and seperately.)
#Thread stuck in device driver windows 10 acer drivers#
uninstalled drivers completely, reinstalled various versions, including stable and beta. This will occur multiple times until it will fail to recover, showing a 0x000000EA (Thread_stuck_in_device_driver) BSOD. Getting freezing in D3D applications, and then a report from windows that the gpu recovered from a serious error (amdkmdap stopped working) event viewer shows the same thing. changed drivers back up to the latest, **WORKS**.Hey guys, i'm at my wit's end with this problem. Still not consistent, missing something here. Goal is to make this "permanent" where a TDR, etc, cannot cause the settings to be wiped.ĮDIT: Changing table indices rather than directly touching voltage of lower states gets Windows to boot.
Is there any way to disable lower VRAM states via softpowerplay? (eg, where the card runs at a constant 945 HBM even in P0) For now I seem limited to the game-mode drivers for ADL. Yet this seems to result in the system hardlocking immediately on startup (doubt that the voltage is actually changed). Played with Soft PowerPlay through registry and tried kicking the speed of the lower HBM states up in addition to adjusting the lower voltages (raising them) to match state 4. May go for an RMA, yet considering it works on the E5 properly with no adjustments, that sounds pointless or that it's not the card persay. Had a read through this thread of which alot of the replies sounded mighty similar to my situation: In more experimenting I've also found (so far) that my locking of clock frequency was insufficient, and that with HBM clocks now locked at 945 - I am unable to cause the BSOD on connecting monitors with the 1950x rig. The strange part is that the Fury-X is completely solid in there (including with freesync active), same with my older Geforce 980 (on GSync). May have to try getting my hands on another brand motherboard. (one drive, 8GB memory, just the videocard) Even with it stripped down to the basics, it's still happening. I've tried swapping their PSU's (so that's been ruled out), and disconnecting everything unnecessary from the 1950X. 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.
#Thread stuck in device driver windows 10 acer 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)
