newtekie1
Semi-Retired Folder
- Joined
- Nov 22, 2005
- Messages
- 28,473 (4.15/day)
- Location
- Indiana, USA
Processor | Intel Core i7 10850K@5.2GHz |
---|---|
Motherboard | AsRock Z470 Taichi |
Cooling | Corsair H115i Pro w/ Noctua NF-A14 Fans |
Memory | 32GB DDR4-3600 |
Video Card(s) | RTX 2070 Super |
Storage | 500GB SX8200 Pro + 8TB with 1TB SSD Cache |
Display(s) | Acer Nitro VG280K 4K 28" |
Case | Fractal Design Define S |
Audio Device(s) | Onboard is good enough for me |
Power Supply | eVGA SuperNOVA 1000w G3 |
Software | Windows 10 Pro x64 |
Microsoft doesn't test the drivers with cards if that's what you're thinking, they just look at the code to see if it conforms to WDM.
WHQL doesn't even do that, all Microsoft does is look at a bunch of logs generated from the manufacturers testing. Microsoft doesn't do anything for WHQL really, they basically just take the manufacturers word for it.
Yes, I was thinking that they actually tested it with sample hardware. Clearly WHQL certification has its limits and a junky driver can still sail through.
Easily sail through.
Since when software damages hardware like this is intended to show... in a driver update?
It's happened before, nVidia messed up a driver update back in the G92 era, the driver wouldn't spin up the fan and the card would overheat extremely quickly.
It could be a similar issue happening here.