TR Forums

My laptop's config:

Laptop mode: Acer TravelMate TMP645-MG-9419
OS: Windows 10 Professional 64 bit
GPU: Radeon HD 8750M

The first attempt I merely attempted to upgrade the graphic driver from the 16.7.3 version (I think), and that caused the laptop to hard lock. It completely froze the laptop halfway through the installation and the OS would no longer respond to any keyboard inputs, including alt-ctrl-del. When I force power down the laptop and restart it, a black screen appeared during the boot process and nothing else happened. I took a nap, and four hours later, the laptop still displayed a black screen.

I then used a USB stock with the Win 10 ISO to start the system restore process. The 16.7.3 driver was corrupted afterwards and apparently had parts of the 16.12.1 driver.

Before the 2nd installation process attempt, I ran DDU in safe mode. When I attempt to install the Radeon Crimson ReLive 16.12.1 driver, it froze the laptop again. I started the installation process at midnight, went to bed, and woke up about 8 hours later for the computer to still be frozen.

Forcefully restarting the laptop still renders the black screen.

I'm trying to figure out why the driver is causing the entire laptop to lock up.

EDIT, This is what Event Viewer showed during the 2nd driver installation attempt, however, with the volume of error and warning messages during the driver installation, I am not sure which one to look at to try to diagnose the issue. The laptop froze at 11:53pm: http://imgur.com/a/jIvMp

EDIT2: SFC/Scannow and Check Disk did not find any issues.

Have you tried AMD's clean install utility, which is separate from DDU? http://support.amd.com/en-us/kb-article ... ility.aspx

By the by, I had the blank screen/freeze install issue on a friend's PC. He got an RX 470 about two weeks before ReLive came out and when he updated at Radeon Settings' behest, it froze and locked. AMD's clean install utility fixed it for us.

derFunkenstein wrote:

Have you tried AMD's clean install utility, which is separate from DDU? http://support.amd.com/en-us/kb-article ... ility.aspx

AMD's clean uninstall utility download link has been broken since August (according to a forum post that I found):
https://support.amd.com/en-us/download/incomplete

I have also tried 16.11.5 and 16.11.4. Both failed to install, and both also bricked all of my restore points in System Restore.

EDIT: 16.10.3 failed to install

Never had any problems with it, but you can do a clean install right from the driver installer with 16.12.1

I haven't had an Intel laptop in a long time, but generally I'd suggest updating any Intel kit drivers in there (chipset and active graphics chips if there are any.)

UnfriendlyFire wrote:

AMD's clean uninstall utility download link has been broken since August (according to a forum post that I found):
https://support.amd.com/en-us/download/incomplete

Did you actually try the download? I did it earlier fine, and I tried it again just now, and it works. The link I posted works.

derFunkenstein wrote:

UnfriendlyFire wrote:

AMD's clean uninstall utility download link has been broken since August (according to a forum post that I found):
https://support.amd.com/en-us/download/incomplete

Did you actually try the download? I did it earlier fine, and I tried it again just now, and it works.  The link I posted works.

The link you posted lead to an error message saying that "We’re sorry, but we were unable to complete your download. There could be several reasons for this:"

The link posted pulls an exe fine for me...

Not really sure what's going on with it for you UFF.

edit: Try this - http://www2.ati.com/drivers/amdcleanuputility.exe

I've found on a couple of Windows 10 systems that I needed to let Microsoft's automatic driver download system install the AMD video and HDMI audio drivers of its choosing, and I need to keep them installed, otherwise I get black screens.

This means when uninstalling an AMD-provided driver set, I have to change things to uninstall only that version -- not all versions -- and reboot.

Trying a clean-up of all drivers got mucky fast, and pain ensued, though that was on Threshold 2 earlier in the year.

Edit: BTW 16.12.2 is out

Topinio wrote:

Edit: BTW 16.12.2 is out

Very relevant.

AMD wrote:

Radeon ReLive may fail to install during installation on some system configurations.

http://support.amd.com/en-us/kb-article ... Notes.aspx

Not sure if that means the 16.12.1 driver (ReLive edition) or the add-on package. Maybe the latter. Still, if this fixes any install issues, it's worth grabbing the new package.

Initial attempt for me (same system mentioned earlier) didn't go so well.

https://twitter.com/TVsBen/status/811339203841839104

Just like last time, running the cleaner fixed it and 16.12.2 went right on without a hitch. It's extremely aggravating that apparently the only problem is AMD's software and I have to do this to try to install a new driver.

So, uh, this problem just snowballed out of control for me.

I'm on my backup laptop, and now I'm dealing with a very different problem regarding the Acer laptop: viewtopic.php?f=6&t=118962

Windows 10 clean install is no longer working. I didn't see the newer posts until I decided to check them on my phone while attempting the clean install. I don't think 16.12.2 is going to be much of a help now that I deleted the OS and is unable to install a fresh copy.

I appreciate your guys' help though. Maybe if I had waited a few more hours before attempting the nuclear option...

derFunkenstein wrote:

Initial attempt for me (same system mentioned earlier) didn't go so well.

https://twitter.com/TVsBen/status/811339203841839104

Just like last time, running the cleaner fixed it and 16.12.2 went right on without a hitch. It's extremely aggravating that apparently the only problem is AMD's software and I have to do this to try to install a new driver.

I attempted to install 16.12.2 on a newly reinstalled Windows 10 with AV disabled.
Using Custom installation caused the laptop to reboot, and according to the logs, the installer aborted the installation process.
Using the Express method now caused my laptop to freeze again.
I can provide you guys the installation logs when I get the laptop responding again.

Does Acer have drivers on their website? Probably pretty old at this point, but it might be a start to get it functional again.

derFunkenstein wrote:

Does Acer have drivers on their website? Probably pretty old at this point, but it might be a start to get it functional again.

Windows installed a 2015 version driver from the update service. Newer than what Acer currently has on their website.
I guess I'll just work my way backward through the versions. I was really hoping for the new features.

Express install that froze the laptop and caused a black screen on reboot:

PMJobExecuter::executer======= AMD Software installed successfully!!! =======



PMJobExecuter::executer::[23-12-2016 08:38:16]  : reutrn value: 1  

CInstallMgr::OnEnd::[23-12-2016 08:38:16] INSTALL_DETAIL

PMJobExecuter::Install::[23-12-2016 08:38:16]  : reutrn value: 1  

CInstallMgr::OnEnd::[23-12-2016 08:38:16] INSTALL_DETAIL

PMJobExecuter::executer::[23-12-2016 08:38:16]
: execute package: AMD Display Driver : productcode: {24081A9C-8411-4541-AE31-86E1BBF5FE02}

PMJobExecuter::executer::[23-12-2016 08:38:16]  Check if older version of this AMD Display Driver package installed



PMJobExecuter::executer ======= Starting installation of: AMD Display Driver =======



WrapDIFx::[23-12-2016 08:38:16] Turn ON DGPU fail

PMJobExecuter::executer::[23-12-2016 08:38:16]  Install Sub-Packages first for AMD Display Driver



DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER:  DriverPackageGetPathW


DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, RETURN: DriverPackageGetPathW  (0xE0000302)


[ERROR] - ERROR_DRIVER_PACKAGE_NOT_IN_STORE::[00000017DC7F93E0] There does not exist an INF file in the driver store that corresponds to the INF file specified by DriverPackageInfPath.

DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER:  DriverPackageGetPathW


DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, RETURN: DriverPackageGetPathW  (0xE0000302)


[ERROR] - ERROR_DRIVER_PACKAGE_NOT_IN_STORE::[00000017DC7F9520] There does not exist an INF file in the driver store that corresponds to the INF file specified by DriverPackageInfPath.

WrapDIFx::[23-12-2016 08:38:16] Preinstalling package AMD AUDIO filter driver with flag Difx=12

DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER:  DriverPackageInstallW


DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, Looking for Model Section [AMD_KMAFD.NTAMD64]...


DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, No matching devices found in INF "C:\Users\VICTOR~1\Desktop\NON-WH~1.2-D\Packages\Drivers\amdkmafd\WT64A\amdkmafd.INF" on the Machine.


DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, RETURN: DriverPackageInstallW  (0xE000020B)


WrapDIFx::[23-12-2016 08:38:16] Preinstalling package AMD AUDIO filter driver to overwrite existing one with flag Difx=0

DIFxAPI::[23-12-2016 08:38:16] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER:  DriverPackagePreinstallW


DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 0, C:\Users\VICTOR~1\Desktop\NON-WH~1.2-D\Packages\Drivers\amdkmafd\WT64A\amdkmafd.INF is preinstalled.


DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, RETURN: DriverPackagePreinstallW  (0x0)


DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER:  DriverPackageGetPathW


DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, RETURN: DriverPackageGetPathW  (0x7A)


DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER:  DriverPackageGetPathW


DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, RETURN: DriverPackageGetPathW  (0x0)


PMJobExecuter::executer::[23-12-2016 08:38:17]  : Subpakcage installed:         AMD AUDIO filter driver

 

PackageManager::[23-12-2016 08:38:17] ExeInstaller::executeProc initiating installation of C:\Users\Victor Sun\Desktop\Non-WHQL-Win10-64Bit-Radeon-Software-Crimson-ReLive-16.12.2-Dec19\Packages\Apps\VulkanRT64\VulkanRT\VulkanRT.exe.

PackageManager::[23-12-2016 08:38:17] ExeInstaller::executeProc exit code of process returned 0.

PMJobExecuter::executer::[23-12-2016 08:38:17]  : Subpakcage installed:         VulkanRT

 

DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER:  DriverPackageGetPathW


DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, RETURN: DriverPackageGetPathW  (0xE0000302)


[ERROR] - ERROR_DRIVER_PACKAGE_NOT_IN_STORE::[00000017DC7F93E0] There does not exist an INF file in the driver store that corresponds to the INF file specified by DriverPackageInfPath.

DIFxAPI::[23-12-2016 08:38:17] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER:  DriverPackageInstallW


DIFxAPI::[23-12-2016 08:38:18] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, Looking for Model Section [ATI.Mfg.NTamd64.10.0]...


DIFxAPI::[23-12-2016 08:38:31] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, Installing INF file 'C:\Users\VICTOR~1\Desktop\NON-WH~1.2-D\Packages\Drivers\Display\WT6A_INF\C0309792.INF' (Plug and Play).


DIFxAPI::[23-12-2016 08:38:31] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, Looking for Model Section [ATI.Mfg.NTamd64.10.0]...


DIFxAPI::[23-12-2016 08:38:31] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, Installing devices with Id "PCI\VEN_1002&DEV_6600&SUBSYS_082B1025&REV_00" using INF "C:\Windows\System32\DriverStore\FileRepository\c0309792.inf_amd64_16fba8c07200efae\C0309792.INF".


DIFxAPI::[23-12-2016 08:38:31] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, Will force install because driver is not better and force flag is set.


DIFxAPI::[23-12-2016 08:38:31] -->> DIFxAPI CALLBACK --->>>LOG Event: 1, ENTER UpdateDriverForPlugAndPlayDevices...

UnfriendlyFire wrote:

derFunkenstein wrote:

Does Acer have drivers on their website? Probably pretty old at this point, but it might be a start to get it functional again.

Windows installed a 2015 version driver from the update service. Newer than what Acer currently has on their website.
I guess I'll just work my way backward through the versions. I was really hoping for the new features.

Um, unless I am doing this wrong today, the only drivers Acer provides for that model on Windows 10 64b are Bluetooth and Wi-Fi, the stated supported path for all other drivers is to use Windows Update and run whatever Microsoft (and Acer, together?) gives you.

https://www.acer.com/ac/en/GB/content/s ... t/5032?b=1

I also saw that the Travelmate P645-MG is supported for upgrade to Windows 10... but not for the Windows 10 Anniversary Update.

(Conspiracy theory: Is this what Microsoft meant (and some suspected) by the new ** conditions for Windows 10 on the Windows Lifecycle page?

A device may not be able to receive updates if the device hardware is incompatible, lacking current drivers, or otherwise outside of the Original Equipment Manufacturer’s (“OEM”) support period.

)

End conspiracy theory: Possibly the Anniversary Update doesn't play nice with those systems yet and Microsoft and Acer are holding it back?

Topinio wrote:

UnfriendlyFire wrote:

derFunkenstein wrote:

Does Acer have drivers on their website? Probably pretty old at this point, but it might be a start to get it functional again.

Windows installed a 2015 version driver from the update service. Newer than what Acer currently has on their website.
I guess I'll just work my way backward through the versions. I was really hoping for the new features.

Um, unless I am doing this wrong today, the only drivers Acer provides for that model on Windows 10 64b are Bluetooth and Wi-Fi, the stated supported path for all other drivers is to use Windows Update and run whatever Microsoft (and Acer, together?) gives you.

https://www.acer.com/ac/en/GB/content/s ... t/5032?b=1

I also saw that the Travelmate P645-MG is supported for upgrade to Windows 10... but not for the Windows 10 Anniversary Update.

(Conspiracy theory: Is this what Microsoft meant (and some suspected) by the new ** conditions for Windows 10 on the Windows Lifecycle page?

A device may not be able to receive updates if the device hardware is incompatible, lacking current drivers, or otherwise outside of the Original Equipment Manufacturer’s (“OEM”) support period.

)

End conspiracy theory: Possibly the Anniversary Update doesn't play nice with those systems yet and Microsoft and Acer are holding it back?

I was referring to the GPU drivers for Windows 7 and 8.1, as that has been very out of date.

UnfriendlyFire wrote:

I was referring to the GPU drivers for Windows 7 and 8.1, as that has been very out of date.

Ah, okay.

From your previous post:

UnfriendlyFire wrote:

Will force install because driver is not better and force flag is set.

Is that a clue?

Something to note about AMD drivers that I haven't seen in this thread yet:  They frequently depend upon a particular Windows Update. 

I've had all sorts of problems going directly to a newer driver on a Windows 10 x64 system that was fresh-installed from USB (and therefore wasn't updated). Bluescreens, lockups, many kinds of crashes. You might want to wait until the system has gotten at least the Anniversary Edition stuff before installing the AMD drivers.

Vhalidictes wrote:

Something to note about AMD drivers that I haven't seen in this thread yet:  They frequently depend upon a particular Windows Update. 

I've had all sorts of problems going directly to a newer driver on a Windows 10 x64 system that was fresh-installed from USB (and therefore wasn't updated). Bluescreens, lockups, many kinds of crashes. You might want to wait until the system has gotten at least the Anniversary Edition stuff before installing the AMD drivers.

I have Anniversary Edition and all of the updates installed.

I managed to get the AMD clean uninstall utility by downloading it through the mobile data plan and onto my phone, and then copied the file from the phone to the laptop. Strangely, connecting the laptop to the hotspot or using a different computer still didn't work.

I ran the AMD uninstall utility, rebooted to safe mode, and then ran DDU.

Right after the 16.12.2 driver installed, the laptop hanged, and I rebooted it.

Running DDU and the AMD clean uninstall utility separately did not work, I had to use both of them to be able to install the driver.

Just an update about the 16.12.2 driver installation process for anyone running into something similar to this in the future.

The previous method had a tendency of breaking the generic driver for the monitor and thus preventing me from being able to adjust screen brightness.

A workaround for me was to install 16.5.3 driver and then upgrade in steps in order to properly install 16.12.2. I upgraded the 16.5.3 tp 16.7.3, then to 16.8.3, then to 16.9.2, then to 16.10.3, then to 16.11.5, and then to 16.12.2.

Installing any other drivers above 16.5.3 first will trigger similar black screen or freezing issues, or somehow fail Windows' driver signature enforcement. I'm not sure why upgrading in steps was the only way to install the drivers properly.

Is anybody here solved the problem yet? by any means? If so please tell me how coz iam now facing the same problem.

abelroy30 wrote:

Is anybody here solved the problem yet? by any means? If so please tell me how coz iam now facing the same problem.

I faced the same issue. I've tried literally everything. Only this worked for me... This issue is so annoying but it's Windows which is causing this problem for sure. 

UnfriendlyFire wrote:

Just an update about the 16.12.2 driver installation process for anyone running into something similar to this in the future.

The previous method had a tendency of breaking the generic driver for the monitor and thus preventing me from being able to adjust screen brightness.

A workaround for me was to install 16.5.3 driver and then upgrade in steps in order to properly install 16.12.2. I upgraded the 16.5.3 tp 16.7.3, then to 16.8.3, then to 16.9.2, then to 16.10.3, then to 16.11.5, and then to 16.12.2.

Installing any other drivers above 16.5.3 first will trigger similar black screen or freezing issues, or somehow fail Windows' driver signature enforcement. I'm not sure why upgrading in steps was the only way to install the drivers properly.

abelroy30 wrote:

Is anybody here solved the problem yet? by any means? If so please tell me how coz iam now facing the same problem.

Black Screen, the only way I know of around the issue is Safe Mode, but due to the geniuses at MS you need to enter a menu system and reboot to use it (F8 shortcut is disabled/broken in Win10).

As a result I used the iGPU to boot and fix the drivers as described (wipe the AMD drivers and install 16.5.3 and then the newest).

RDP/VNC in to enable and enact the reboot to safe mode, obvs a colossal PITA and thanks Microsoft, but it's the quickest way to do it IME.

Thanks everyone bt my problem didn't get solved that easy. even 16.5 not get installed, display adapter tab in device manager was missing, and some errors occurred(I happened to delete the recovery partition accidentally) during restore and refresh, so only re- installing windows ( to an old build) and then installing the software, fixed the issue.But what i think about the problem is when I tried clean uninstalling of previous drivers using amd's tool and  installing the graphics drivers ( old one) , they didn't show display driver in their installation list, means the installer thinks a latest display driver is already installed. May be the registry entries made by previous software not removed ( this is a thing happens with many software ). May be removing such registry entries manually can fix the problem. However AMD released another version of crimson software today ..........

UnfriendlyFire wrote:

Just an update about the 16.12.2 driver installation process for anyone running into something similar to this in the future.

The previous method had a tendency of breaking the generic driver for the monitor and thus preventing me from being able to adjust screen brightness.

A workaround for me was to install 16.5.3 driver and then upgrade in steps in order to properly install 16.12.2. I upgraded the 16.5.3 tp 16.7.3, then to 16.8.3, then to 16.9.2, then to 16.10.3, then to 16.11.5, and then to 16.12.2.

Installing any other drivers above 16.5.3 first will trigger similar black screen or freezing issues, or somehow fail Windows' driver signature enforcement. I'm not sure why upgrading in steps was the only way to install the drivers properly.

Does it matter if I installed 16.5.3 first and then skip until 16.12.2?

grudge2516 wrote:

Does it matter if I installed 16.5.3 first and then skip until 16.12.2?

No that shouldn't matter. I did the same thing and it should be fine. Although I do get the black screen sometimes.