To be honest the build difference was the LAST thing I checked. and once my fellow vExpert had ditched the 1703 build of Windows10 the problem went away. I’d not seen the problem because my lab uses 1709…. In nutshell 1703 is “bad” for VMware Admins, but 1709 is fine. Turned out it was a problem with with Windows itself. We went ALL around the houses looking at the usual suspects – DHCP, Administrator credentials, DNS and so on. And I’m keen to expose myself new problems and issues, and I like trying to fix issues. STORAGE: SSD ADATA 240GB and WESTERN DIGITAL 1TB Blue.This week I decided to try and help out a fellow vExpert who was having an issue with carrying out guest customisation on a Windows10 system. PSU: CoolerMaster Extreme Power Plus 700w RAM: 2x8GB DDR4 Corsair Vengeance 3000Mhz GPU: XFX RX 580 8GB GTR Black Edition Crimson (RX-580P8DBRR) Sorry for grammar errors, English is not my primary language. I'll do it if the next windows version does not solve the problem. I have not tried the gpu on another PC either, but I'm pretty sure the problem is related to Windows 10. If not, I will roll back to anniversary update. This will probably solve the issue, but in the future, I can’t sell a GPU that only works well with a specific Windows 10 version, or that need a downclock to work properly, so I need to find a coherent solution.Īnyway, I'll wait for the next major Windows 10 update (1809) and see if it solves the problem. The only thing that I haven’t tried yet, is to roll back to Wind(Anniversary Update). Updated mobo BIOS (then and now with my new rig). When the problem started, I had a different system (FX 6300, MOBO ASUS M5A97 Plus, 8GB DDR3 1600mhz). Changed rig and installed Windows 10 from version 1703. Tried a different PSU (a new one from a friend). Uninstalled all programs like msi afterburner, rivatuner, etc. Installed every new AMD driver since the problem began, hoping that the new ones will fix it. Updated Windows to the latest version 1803.
Fresh install of Windows 10 versions 17. I don't think the GPU is faulty, because the problem starts with just +1 Mhz off clock, and the temps never reach 70☌. The GPU is almost new, I bought it on june 2017, and I have never overclocked it. It seems that after Creators update, the system doesn’t support any kind of GPU overclock, even its factory overclock (1405 mhz clock). But I need my GPU to work properly in case of selling it. The only fix so far, is to downclock the GPU clock to 1340 mhz (reference clock). Since then, my GPU FACTORY OVERCLOCK has been unstable, and it has caused artifacts, crashes (display driver stop and recovery), flickering, flashings in some GPU intensive games like Battlefield 1, Hellblade Senua's Sacrifice, Shadows of War, etc. The problem started almost a year ago when I updated from Windows 10 version 1607 (Anniversary Update) to 1703 (Creators Update).
0 kommentar(er)
