Sadly this has changed and there doesn't seem to be any other explanation that something one microsoft's update server or dumped into the creators updates have royallyed screwed things up. The reason i bring this up is that one of my occupations is IT for several companies and personal computers, and over the weekend i've been inundated with numerous calls and complaints after many of these machines running HD4000/3000/2000 series graphics cards without issues at all since windows vista/7 and majority of which received the update to windows 10 and took it without a problem since it first launched, using their HDMI connected tvs and multiple displays in some situations without a problem and even playing many games without fault.
Those with HD5000 series or newer are entirely unaffected and life continues on without fault. The problem is associated with the 1703 or more recently the 1709 update that appears to attempt to install an invalid driver, fails, and then prevents the user from forcefully installing the previously working driver or even uninstalling the existing one properly because windows reports that "no driver is currently installed" but also reports in the driver tab that a valid AMD WHQL'd driver is in fact installed with version "version=22.19.128.0" listed when it SHOULD be "version=8.970.100.9001" that was used prior to the update.Īdditionally, if one attempts to remove the ATI/AMD High definition audio device from the device manager manually, so far, at least for me, on numerous machines, will result in an IRQ_LESS_THAN_EQUAL BSOD even in safe mode, to which the graphics card has to be physically removed, an alternative installed prior to being able to remove it. On top of that, the refresh rates will be permanently locked to 64hz. Some exceptions appear to allow for a wild range of obscure and rather odd additional non-compliant (out or range) resolutions. Numerous windows 10 users, general users that tend to focus on web page browsing, office work, and nothing really gpu intensive may start experiencing problems regarding losing their resolution options, being stuck at 1024x768 as a maximum "recommended" resolution or perhaps worse.
I'd like to point out something that only seems to be ramping up as of last week and over the weekend occurring in mass.
0 kommentar(er)
