Long story short , since june 2019 i have a new videocard (MSI Vega 56 Air boost OC) , which I am trying to get stable for the past 3 months now . I have been trying everything , swapping hardware in and out , changing fansettings , adding fans , DDU drivers , updating all programs/drivers on my pc and what not . Every time the PC crashes , i have to do a CMOS reset to get the pc to boot again . Just a restart or power down is not enough .
The "Thread stuck in device driver" blue screen analysis points towards DX and AMD drivers , hence me being focused on those things at first .
So in the end nothing helped and I decided to try to run stability tests in a completely new windows 10 x64 installation . Only installing chipset driver , sound drivers and videocard drivers . Suddenly no more crashes ... Since in a clean windows install stopped the crashes (meaning the hardware is fine) , i went back to my old windows installation to try and find out what software was causing these BSOD's .
In the end I had a stable run of several hours .Yay ! Where the only program i closed was AIDA64 . So I decided to stop the stability test . After closing the stability run (Heaven benchmark) I opened AIDA64 back up .
What do you think , mere 2 minutes after opening I get BSOD with thread stuck in device driver again . And this was just on the desktop , with no stresstests running .
So the next day i closed 3 monitoring programs to be sure : AIDA64 , Rivatuner statistics server and Remote panel . I fired up a gpu stresstest and let it run all day and night . No crash ... . It was still running when i woke up the next day . This never happened before !
Software versions :
- AIDA64 (I always used latest beta's since june 2019 . currently using 6.00.5161)
- Rivatuner statistics server 7.2.2
- Remote panel 1.16
- AMD driver always latest optional since june (currently 19.9.2)
The output of my monitoring currently goes towards a Samsung Galaxy s5 connected through usb) . But before I used a G19 keyboard , which was causing the same BSOD .
To this post I also attached a bluescreen analysis with WhoCrashed .
BSOD thread stuck in device driver analysis.txt