I was thinking of another program. You can uninstall if from Windows Settings if it has a separate listing for it.
forget about that for now and just install the HP AMD Driver again without installing the Nvidia driver and see what happens.
I also suggest afterwards to run HP Diagnostic on your laptop just to make sure there aren't any problems with your computer causing the AMD driver to have issues.
I've had this exact same problem with ASUS Rog Zephyrus G14 laptop - the AMD Ryzen 9 cpu with integrated graphics is running along side Gforce 2060 Q. I get Loadlibrary error 87, and sometimes load library error 126.
I used DDU to completely to uninstall the AMD drivers and software, but still have the problem. There was no error messages on the day I reinstalled the drivers, but the next day it was back. It's very strange how it's intermittent. Once I couldn't even open the AMD software, to run or update, because of 'load library error', then one day I could.
On the ROG Zephyrus forums, I was advised to do a complete factory reset. I thought I'd try just the AMD drivers first. But no luck.
P.S I'm pretty sure AMD Adrenalin software can be a drain on battery life.
I am experiencing exactly same problem on my Lenovo Legion 5 with Ryzen 7. Got it yesterday and performed fresh installation of Windows 10.
Tried to remove all iGPU and dGPU drivers with DDU and then reinstall, without luck. My current suspicions are directed towards external monitor plugged on HDMI which runs directly on dGPU. Need to check that out tho.
I am having the exact same problem on my Asus TUF A15 (Ryzen 9 4900H & RTX 2060) when running Steam.
Removing the driver from Device Manager clears up the issue, however I assume my laptops performance is impacted by not having the driver installed...
I have tried both the Asus AMD driver package and the latest Andrenalin.
Computer is 100% up to date including Bios, windows, all drivers, etc.
May have fixed this... updated the DisplayLink drivers (I use a docking station), reinstalled Adrenalin (w. factory reset) and disabled issue detection. Error message is gone for now... will advise if it comes back.
i have the same problem but on my PC. But it happens when my PC goes out from sleepmode, this does not affect performance in any way, but i want to know. One condition is only different, I have both video cards running at the same time and I have two monitors for both adapters.
I experienced the dreaded "LoadLibrary error 87:parameter error" with program FreeVideoEditor only when accessing via a RDP session.
Apparently others have found issue with Windows RDP trying to use hardware acceleration (OpenGL ?) on older (?) AMD chipsets during a RDP session causing video and photo editing apps to fail with the error 87 message.
I am not here to tout why the most recent cards/drivers should be used, only to describe what I did to resolve my situation using older cards. Your mileage may vary.
I am using 2 AMD FirePro 2270 cards for 4 local displays with AMD driver version 15.200.1045.0 supplied by Windows Update
on a Dell T3600 running Win10 Pro x64 V20H2. AMD's Adrenalin fails (wrong hardware). BIOS is the latest for this PC (2015 A18).
The PC is old and the AMD cards are old. AMD's latest driver V15.201.2401.1010 for these cards generates the same error message.
First discovery was to rename OpenGL and OpenCL DLLs and execs in '...\windows/system32'. Found the correct file names in the registry. Tedious to rename files every time I wanted to edit videos via RDP.
Second discovery was to disable both AMD video display devices via device manager when using RDP. Automated the process via a DOS batch proc, but also tedious for each RDP session.
Final discovery was to keep Windows on the remote host from using video hardware acceleration for RDP sessions. Found an entry online that described how Win10 V1903 and later used WDDM for video drivers and how some older (?) video driver versions now misbehaved with remote sessions after V1903.
Successfully used the following procedure to disable video hardware acceleration during RDP sessions on the remote host:
- Launch gpedit as administrator and go the the following entry: "Local Computer Policy>Computer Configuration>Administrative Templates> Windows Components>Remote Desktop Services>Remote Desktop Host>
Remote Session Environment"
- Disable the following three entries:
'Use hardware graphics adapters for all Remote Desktop Services sessions'
'Use advanced RemoteFX graphics for RemoteApp'
'Use WDDM graphics display driver for Remote Desktop Connections'
- Reboot the remote host
- The dreaded error 87 was resolved when launching FreeVideoEditor via a RDP session.
Hope this is of use to others. I have no comment on whether newer cards should be used, just that my problem began after Win10 V1903 and others may find value if this fix works for them.