Currently, when I boot into Windows, one monitor stays black (undetected), and the other can only display 800x600 resolution.
When I look at Device Manager > Display Adapters > NVIDIA GeForce GTX 970 > General > Device Status
, it says "Windows has stopped this device because it has reported problems. (Code 43)".
Details > Problem Code
says "00002b". Details > Status
says:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
When I then click into the Events tab, it says "Device PCI\VEN_10DE&DEV_13C2&SUBSYS_29763842&REV_A1\4&25438c51&0&0008 requires further installation."
I have a EVGA Nvidia GeForce GTX 970 graphics card with the latest drivers (376.19 from 12/1/2016).
My Windows 10 Pro has the latest updates and is at Version 1607, OS Build 14393.576.
My ASRock Z170 Pro4 motherboard BIOS is also updated to the latest version (7.00 from 10/4/2016).
I have dual Acer monitors with 1920x1080 resolution.
I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into the Ubuntu operating system instead of Windows. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why my video card has stopped working within Windows.
What I Have Tried
- I've tried using Display Driver Uninstaller from Guru3d in Safe Mode to delete all drivers and try to install fresh.
- I've tried many different versions of the driver dating back more than 12 months.
- I've tried reseating the card.
- I've tried moving the card to a different slot.
- EVGA's phone support told me to reinstall windows (
Windows > Reset this PC > Keep my files
). Unfortunately, I followed their advice (and now don't have any of my programs), and I still get Code 43 with the EVGA Nvidia card.
What I Have NOT Tried
- I would love to try installing this card onto a different Windows 10 computer to see what happens, but I don't have access to any other computers. If you live northeast of Atlanta, let me know. ;-)
I'd appreciate any other ideas you have!.
glxinfo
and look for anything suspicious (Lot of output tho) or just run something that requires 3D acceleration. Maybe the reason it's still working is because it's using safe fallbacks?