Post by mitchellzone on May 15, 2018 22:07:47 GMT
Hi all,
I’ve just installed Bootcamp on a new 15” MacBook Pro. After installation my LG 4K display (connected via Apple Thunderbolt adapter and HDMI) was correctly recognized and I was using both desktops just fine. I noticed some glitches when running high frame rate apps, and played around with the AMD settings and couldn’t make it work the way I wanted. So, I looked around and saw that I could get the latest AMD drivers for the Pro 560 from this site.
However, after following the instructions, removing the old drivers and installing the newest ones, my second display is no longer detected by Windows 10. Actually, that’s not exactly correct—occasionally when unplugging and replugging the monitor into the computer, it sees it briefly, for about 2 seconds, but then it disappears again and Windows cannot detect that I have a second monitor.
I’m in the midst of reverting to a previous version of the Windows disk image, to see if I can get the system back to a state it was working in. However, I’d much rather just be able to troubleshoot this and figure out how to make it work. Any ideas?
Thanks,
/mike
I’ve just installed Bootcamp on a new 15” MacBook Pro. After installation my LG 4K display (connected via Apple Thunderbolt adapter and HDMI) was correctly recognized and I was using both desktops just fine. I noticed some glitches when running high frame rate apps, and played around with the AMD settings and couldn’t make it work the way I wanted. So, I looked around and saw that I could get the latest AMD drivers for the Pro 560 from this site.
However, after following the instructions, removing the old drivers and installing the newest ones, my second display is no longer detected by Windows 10. Actually, that’s not exactly correct—occasionally when unplugging and replugging the monitor into the computer, it sees it briefly, for about 2 seconds, but then it disappears again and Windows cannot detect that I have a second monitor.
I’m in the midst of reverting to a previous version of the Windows disk image, to see if I can get the system back to a state it was working in. However, I’d much rather just be able to troubleshoot this and figure out how to make it work. Any ideas?
Thanks,
/mike
