- Forum
- FLEM Forum
- Welcome to Digital FLEM - General discussions
- Missing "Display Driver" option in AMD setup
You can post your comments and experiences about using Digital FLEM here.
Missing "Display Driver" option in AMD setup
- AmiloMan
-
- Offline
- Administrator
-
- Creator of Digital-FLEM
Great post on the Success with the log file and spreadsheet with the attempts that failed and succeeded.
Please Log in or Create an account to join the conversation.
- Avinide
- Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 1
After many combinations, it worked with 13.9 base and 16.1.1. Previously I've tried the same combination, but with only 7 base files, and enabled option no. 1 and 3. It gave me those glitches, and almost immidiately code 43. It seems, that adding remaining files (ex. for OpenGL) and selecting option no. 2 and 4 was necessary. I'm attaching my final log from FLEM.
Also, I'm attaching my spreadsheet with driver results. 16.1.1 had similar behaviour as 14.4, which means this driver version might also work.
My question for now is this: am I forced to use 14.4 CCC? Is there an option to use newer/modded one?
Attachments:
Please Log in or Create an account to join the conversation.
- Avinide
- Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 1
I'm always using clean packages, and I have untouched backup, made to save a bit of time.
One interesting thing happened with 16.1.1 Hotfix + 13.9 base (I'm trying now different versions, will make a full report later on). Windows accepted those drivers, my screen reported 1080p resolution, overscan disappeared, so installation was successful. After one second, it went back to normal and reported error 43. However, I've got a notification, which says:
"Cannot launch this display driver.
Instead of this one, use the Basic Microsoft Display Driver. Search for the newer driver by using Windows Update service [...]"
I'm attaching the screenshot of it. Unfortunately I don't run Windows in english, however the translation of that message is above. Maybe there's something else which causes issues? I'm running Windows 10 Pro 1803 x64 btw.
Attachments:
Please Log in or Create an account to join the conversation.
- AmiloMan
-
- Offline
- Administrator
-
- Creator of Digital-FLEM
Actually in DDU there is an option to select boot into safe mode, it will reboot into safe mode for you and do a thorough clean from there.
Always Mod a driver before cleaning out the driver and always use a freshly extracted driver package not one that you have already attempted to mod.
Please Log in or Create an account to join the conversation.
- Avinide
- Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 1
Please Log in or Create an account to join the conversation.
- AmiloMan
-
- Offline
- Administrator
-
- Creator of Digital-FLEM
Keep trying at least now you can install from device manager and see which one works, always clean-out the old drivers before trying to install new ones.
Please Log in or Create an account to join the conversation.
- Avinide
- Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 1
Please Log in or Create an account to join the conversation.
- Avinide
- Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 1
I'll try, give me a few minutes.
Please Log in or Create an account to join the conversation.
- AmiloMan
-
- Offline
- Administrator
-
- Creator of Digital-FLEM
- Extract a fresh copy the 15.11 and use the 13.1 legacy for base files, use all 8 files to be sure.
- Uninstall the current driver wiith DDU, link provided: Display Driver Uninstaller (DDU) download version 18.0.6.8
- After complete cleanout, install the driver using the method I posted above.
Please Log in or Create an account to join the conversation.
- Avinide
- Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 1
Please Log in or Create an account to join the conversation.
- AmiloMan
-
- Offline
- Administrator
-
- Creator of Digital-FLEM
Right click the gpu in device manager and select "update driver",
"Browse my computer for driver software"
"Let me pick from a list of available drivers on my computer"
Please Log in or Create an account to join the conversation.
- Avinide
- Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 1
14.4 also worked, and I can install the display driver via the setup.exe, but I'm getting the driver error code 52. I have test mode enabled, and disabled system integrity check.
Would you be able to try to mod those drivers remotely, ex. via TeamViewer?
Please Log in or Create an account to join the conversation.
- AmiloMan
-
- Offline
- Administrator
-
- Creator of Digital-FLEM
If the 2018 drivers don't work after being modded try an older version like from 2017 or 2016 and see if it works.
Please Log in or Create an account to join the conversation.
- Avinide
- Topic Author
- Offline
- New Member
-
- Posts: 9
- Thank you received: 1
Drivers I've tried to mod:
18.4.1, but it gave me a lot of .NET(?) errors, so I knew it wouldn't work.
16.2.1 - the latest legacy driver for 5xxx and up
15.7.1 - the latest stable legacy driver for 5xxx and up
Base drivers I've used:
13.9 for Windows 7
13.1 for Windows 8
I've selected the necessary files according to the Guide, ones for OpenCL, *dxx.dll and *cfx.dll from 13.9 or 13.1. FLEM did say, that there were missing strings in C*****.inf file (don't exactly remember how it was with 18.4.1, apart from mentioned errors). Process finished in ~4 seconds. Then I'm trying to install it with the Setup.exe file, but as I said, I don't have the option for Display Driver or CCC.
Could someone tell me, what am I doing wrong?
EDIT: Also, manual installation of modded drivers via Device Manager doesn't go through - "Windows decided, that current drivers are optimal" or something like that, tried with no drivers installed (Basic Microsoft GPU, I don't have Windows in english so I'm translating it on the fly). However, manual installation of 13.9 or 13.1 is working, and I can install CCC from one of those drivers, but it doesn't work - "no options available to configure". I'm attaching my logs, in case that would help.
Attachments:
Please Log in or Create an account to join the conversation.