If I run in fullscreen or borderless the game just locks up until I change focus. It runs flawlessly in borderless if its in the background. I have to run it windowed for it to work. This is a fresh install of windows 10 x64. I popped in my old windows 7 HDD, and it ran fine oddly enough, but I'm not downgrading my OS to run this one game correctly. Has anyone else ran into this issue, or have a workaround for me?
Windows 10 x64
AMD FX 9590
AMD RX 480 8gb - Driver version 17.3.3
16 GB RAM
So the issue is Windows 10 Creators Update, upon rolling back to Win 10 1607 everything works fine. As far as I know the issue is not present on Nvidia (tested 1070, 960) hardware, only AMD (tested RX480, and Fury). This may have to do with the new xbox overlay/ game mode work. I'll mess around this weekend and update this thread with anything I find out as this update will be rolling out to more users soon. I've tried turning off Xbox DVR feature and all other features I could find that are related such as game mode etc..
CPU: Ryzen 1700 - 3.9GHz
RAM: 16 GB 3200 DDR4
OS: Windows 10 1703(CU)
Nvidia drivers tested:
381.89 - Works Fine
AMD driver tested:
17.4.1 - doesn't work
17.4.2 - doesn't work
you may wish to shoot off an e mail to AMD support i know they had an issue with their drivers and FC 4 before
it also caused FC 3 to crash on launch
see : http://forums.ubi.com/showthread.php...crashes-FC3-4?
it could just simply be an error in the driver package they need to correct ..again
AMDs recently released 17.5.1 Driver actually solved the problem. I did try toggling Xbox DVR and uplay/steam overlay and all seems to be working fine. Rolling back to to 17.4.2 caused the same problem, Fallout 4 also experienced the same issues but turning off freesync fixed it (again on 17.4.2). It seems odd to me because no where in the change log is anything about either game, or any issues that sound even similar, it's also odd that its only an issue on W10CU. This is NOT an issue with FarCry4 it is in fact with AMDs drivers. If it comes back up with a later driver release I'll make sure to report it to AMD.