- #Windows 10 thread stuck in device driver r9 390 drivers
- #Windows 10 thread stuck in device driver r9 390 driver
- #Windows 10 thread stuck in device driver r9 390 software
- #Windows 10 thread stuck in device driver r9 390 series
#Windows 10 thread stuck in device driver r9 390 drivers
Which also means that driver-level optimizations have to be done twice, once for the VLIW drivers and once for the GCN drivers, every single time.
#Windows 10 thread stuck in device driver r9 390 driver
And if you want one driver to continue to support the still-new VLIW cards out there and ALSO support the brand-spanking-new GCN cards, then what you really have is two separate driver paths for two separate architectures, packed into one driver. When AMD went from VLIW to GCN, that was a complete ground-up architecture shift, which requires ground-up driver design.
#Windows 10 thread stuck in device driver r9 390 series
It's not that hard to continue supporting the 400 series in drivers when it's still basically the same as the 1000 series, scaled down. They shrink it down with each node shrink, and then copy-paste cuda cores into all the extra space they have.
"The point is that Nvidia has been using the same design on an architectural level since the 8800GT at least. Some good read, about why ATI drivers are not maturing instantly Have you read our Radeon RX Vega 64 review already?