just updated to 16.9.2 (29 sep) thanks amd :< thanks

Yeah same, so make 16.9.2 into WHQL and then release 16.10.1 as beta? Ah well time to install these too. 😀 EDIT: Also uses Vulkan 1.0.26.0 same as the newly re-released WHQL'd 16.9.2 drivers. 🙂 EDIT: atiapfxx.exe -r -sys -s test.xml comparison against 16.9.2-> (This creates a plain .xml so easy to use any comparison tool like WinMerge but I don't have the skill to dig into the actual .dll's for any newer profiles not yet in this "blob", Kn00t used to maintain a very good repository for this earlier.) Crossfire: Battle Field 1 (bf1 and bf1trial.exe so both the game and the EA Access version.) Deus Ex: Mankind Divided F1_2016 Civilization 6 (Both Civ6_Win64_DX11_FinalRelease.exe and CivilizationVI.exe so should be good for the release version.) These were all updated. 🙂 Call of Duty: Infinite Warfare (But it targets 4-iw7_profile.exe so probably not the release version exe?) Shadow Warrior 2 (EDIT: Infinite Warfare also has iw7_ship.exe and iw7uwp_ship.exe - win10 store version?) These were added. 🙂 PXDynamic profiles for "HighPerfGPUAffinity" Dishonored 2 ( Dishonored2_x64.exe and Dishonored2_x64Retail.exe so probably good when it releases.) Mafia 3 (mafia3.exe) Titan Fall 2 (r2_x64.exe and Titanfall2.exe) Rocket League ( rocketleague.exe ) Shadow Warrior 2 (shadowwarrior2.exe) Watch_Dogs 2 (WatchDogs_r64.exe, WatchDogs_rt64.exe and WatchDogs2.exe ) (Man they're just lining up one AAA game after another with these, they've been busy although well these aren't the Crossfire flags.) (Better late than never for Rocket League I suppose but these flags are at least from what I read about the game switching to using the dedicated GPU over a APU or something along those lines.) EDIT: Battlefield 1 seems to have a lot of "Tunguska" based exe files, code name for the game perhaps during development. 😀 Tunguska.Main_Win64_Final.exe Tunguska.Main_Win64_final_DLL.exe Tunguska.Main_Win64_Release.exe Tunguska.Main_Win64_release_DLL.exe EDIT: Actually speaking of Crossfire it seems Watch_Dogs 2 already has a profile? (Probably I listed it when I copy pasted to a earlier driver release but already forgot about it. :P )

Ha I get it now with AMD they have been busy with a secret project...Time travel: Just noticed the date on the download. Non-WHQL-Win10-64Bit-Radeon-Software-Crimson-16.10.1-Oct6.exe

it is the 5th you know, it was probobly just a typo, the 6 is next to the 5.

Well..It's already 6 here..:D

cool. i like how they've been on top of drivers all year.

So next month the new shade of red? just like last year? 15.11.1 Crimson?

So next month the new shade of red? just like last year? 15.11.1 Crimson?

They do like to use that month for releasing new stuff. Just like 12.11 mega driver 😀

Anyhow VSR can be enabled with these drivers on ultrawide screen with my CRU tweaks. My LG 29UM58 ultra wide screen works with the tweaks for VSR however I perfer 3440x1440 manually entered. Also freesync on non freesync at least can be enabled in the control panel. Verdict is still out on exactly what this does.

Tahiti idle clocks bug still present. :\

They do like to use that month for releasing new stuff. Just like 12.11 mega driver 😀

Yup, we can wonder how it will be named 🙂 The Rage Driver Omega Crimson Driver Aniversary Driver But it will be for sure, now i need to check ME:C with Hyper textures (rest on Ultra/Blurrrrr OFFFF)

Same problem remain with this drivers i can't go 4k 60hz with these... I'm using a 4k tv and club 3d diplay port-to hdmi 4k 60hz cable and a 390x gpu Also i can't see the pixel format option... Is there any sort of registry hack for this ?

Here any driver newer than 16.7.3 crashes the system(Windows 10 x64) when playing a video with MPC-BE+LAV Filters+madVR(all x64) and resize the player window or to make full screen(ALT+ENTER). MPC-BE https://sourceforge.net/projects/mpcbe/files/MPC-BE/Release%20builds/1.4.6/ LAV http://forum.doom9.org/showthread.php?t=156191 madVR http://madvr.com/ Here my configuration for MPC-BE https://dl.dropboxusercontent.com/u/4686872/MPC-BE+LAV+madVR.reg but MPC-BE *MUST* be installed at c:\Program Files\MPC-BE\ To configure MPC-BE check https://linustechtips.com/main/topic/233290-high-quality-video-playback-on-windows/

Anyhow VSR can be enabled with these drivers on ultrawide screen with my CRU tweaks. My LG 29UM58 ultra wide screen works with the tweaks for VSR however I perfer 3440x1440 manually entered. Also freesync on non freesync at least can be enabled in the control panel. Verdict is still out on exactly what this does.

This was done many months ago by me after crimson release. VSR only has 16:9 resolutions though. Hence why I never use it on my LG29UM67-P. Its still not fresync that is on cru tweaks. Let that BS die. Its a form of frame pacing done with crossfire.

Here any driver newer than 16.7.3 crashes the system(Windows 10 x64) when playing a video with MPC-BE+LAV Filters+madVR(all x64) and resize the player window or to make full screen(ALT+ENTER). MPC-BE https://sourceforge.net/projects/mpcbe/files/MPC-BE/Release%20builds/1.4.6/ LAV http://forum.doom9.org/showthread.php?t=156191 madVR http://madvr.com/ Here my configuration for MPC-BE https://dl.dropboxusercontent.com/u/4686872/MPC-BE+LAV+madVR.reg but MPC-BE *MUST* be installed at c:\Program Files\MPC-BE\ To configure MPC-BE check https://linustechtips.com/main/topic/233290-high-quality-video-playback-on-windows/

In madVR, enable DX11 renderer. http://image.prntscr.com/image/fa0d78c258e94e7d9fcf73d6cbb2edb9.png All crashes should be gone!

Tahiti idle clocks bug still present. :\

I was waiting for these ones just for that bug fix. Well, maybe for New Year's Eve will get one 🙂

Same problem remain with this drivers i can't go 4k 60hz with these... I'm using a 4k tv and club 3d diplay port-to hdmi 4k 60hz cable and a 390x gpu Also i can't see the pixel format option... Is there any sort of registry hack for this ?

Maby try CRU 🙂 There you can set all Monitor related options + you can Save cfg then just load it when needed (like Driver change)

I was waiting for these ones just for that bug fix. Well, maybe for New Year's Eve will get one 🙂

Please use the report form also, one day they might wake up and do something about. For some reason, I can't report under Chrome (stuck at loading animation), but it's OK in IE.

just found out this whole time that the installer when ran in upgrade mode. wasnt replacing atikmdag.sys in system32/drivers folder. but it did have it in the driverstore folder..... the atikmdag.sys version that was in the system32/driver folder is from august.... probably explains why I been having trouble with some apps not working correctly.

Here any driver newer than 16.7.3 crashes the system(Windows 10 x64) when playing a video with MPC-BE+LAV Filters+madVR(all x64) and resize the player window or to make full screen(ALT+ENTER). MPC-BE https://sourceforge.net/projects/mpcbe/files/MPC-BE/Release%20builds/1.4.6/ LAV http://forum.doom9.org/showthread.php?t=156191 madVR http://madvr.com/ Here my configuration for MPC-BE https://dl.dropboxusercontent.com/u/4686872/MPC-BE+LAV+madVR.reg but MPC-BE *MUST* be installed at c:\Program Files\MPC-BE\ To configure MPC-BE check https://linustechtips.com/main/topic/233290-high-quality-video-playback-on-windows/

7950/7970/280/280x/380/380x (Possibly 270/270x/285?) are all plagued with stability issues - they become severe with Windows 10 14353. Even on a system with a legacy install, and no secure boot, they still crash under load. It can be Google Chrome, madVR, Rainbow Six Siege, whatever. BSODs, amd kernel dll faults, application crashes and driver crashes. And clocks are still stuck. :bang: I've seen these problems on the newer drivers on many people's computers now. A GTX 970 is the perfect solution. They're only about $170-190 on hardwareswap now. Massively reduced CPU overhead, massively reduced power consumption and heat output. (Seriously, my ITX rig now idles at 30w instead of 90w+. Gaming load is 230w peak vs 460w peak). I'd love nothing more than for this to get fixed, but I don't have faith that it will, in fact. I don't even think it's on AMD's radar. If they paid attention and actually tested their drivers themselves, they'd find all sorts of bugs and silly limitations. Having to use CRU to create a custom resolution with AMD drivers but not Nvidia drivers is another example. Why are these problems ignored?