problems remain unresolved

problems remain unresolved

If there is something good about AMD, it is undoubtedly its designs in hardware and hence its great products, especially in CPUs. But at the same time, if there's one thing AMD does wrong, it's its software. For years it has lagged behind its rivals and although it has increased its workforce and has taken several steps forward in this section, at the moment it has various problems that are causing many users to consider purchasing their hardware.

And is that the software is as important or more than the hardware, therefore errors like the ones we have seen since the beginning of the year are not doing the company too well. Today we have the latest with the new drivers for its chipset with version 2.04.04.111.

Read This Now:   Coronavirus, Facebook cancels all the big events until June 2021

AMD Chipset drivers 2.04.04.111: the last straw?

We will start first by taking up the problems with the previous version 2.03, which we already covered in a specific article because they were driving many users crazy. The problem was simple, the installer stayed at 0% of that installation and would never advance.

The problem came from two different aspects, where one would have the drivers installed correctly but without realizing it, while the other would face either a null installation, or problems related to overwriting the previous drivers, thereby causing restarts and problems. various.

The error was known as 1720 and with these new drivers 2.04 it has not only been corrected, but there are quite a few new features:

Launch highlights

  • Obsolete device IDs have been removed from the driver IOV.
  • Obsolete device IDs have been removed from the driver USB 3.0.
  • General system stability improvements.

Problems solved

  • The installer may crash during the progress of the installation.
  • The installer can abort with the code Error 1720.
  • The installation will not install in a location other than C:.
  • Screen rotation error resolved with certain AMD mobile processors
  • The system stops at 7th Generation AMD A-Series APUs.
Read This Now:   Buy Galaxy A52s 5G and get PLN 300 return

Known issues

  • The Windows Installer pop-up message may appear during installation.
  • Moving the installer window during the installation process can cause the installer window to flicker / move across the screen.
  • Unable to open installation log file after completion.
  • The installer cannot update a subpackage to the latest version. Workaround: Manually uninstall any previous subpacks, restart, and then reinstall the full chipset package.

So, knowing everything new that this driver brings, what is the new problem that plagues AMD? Very simple, the .zip file from which the driver is downloaded cannot be opened, that is, we downloaded it from the AMD website and when trying to open the compressed file for installation we will get the following message:

AMD-Drivers "width =" 411 "height =" 127 "srcset =" https://www.bitcoinminershashrate.com/wp-content/uploads/2020/04/1586341060_950_problems-remain-unresolved.jpg 411w, https: // hardzone. en / app / uploads-hardzone.es / 2020/04 / AMD-Drivers-300x93.jpg 300w "sizes =" (max-width: 411px) 100vw, 411px "/></p>
<p>No matter what decompression software we use, we will not be able to open it. It seems really incredible that errors like these keep happening in a company as big as AMD. The company should take note, since although in this case the error is minor, the previous one created a great controversy and bad being among its users, among whom we are of course.</p>
<p>We will have to wait for a new version to enjoy the improvements seen, but not before creating at least one system restore point, at least.</p>
</div>
</pre>
<div class=


Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420

Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420