Download AMD Radeon Software Crimson 15.12 Driver

Published by

Click here to post a comment for Download AMD Radeon Software Crimson 15.12 Driver on our message forum
https://forums.guru3d.com/data/avatars/m/238/238369.jpg
Hype! So, they are the same as the 15.11.1 ?
https://forums.guru3d.com/data/avatars/m/260/260826.jpg
Now it's up for me. Changelog/release note: AMD Radeon Software Crimson Edition 15.12
This release provides users with a Microsoft WHQL certified version of the AMD Radeon Software Crimson Edition 15.11.1 Update driver. Resolved Issues [83112] Radeon Settings driver update check is not available for minor driver versions [83111] System has higher idle power usage on Windows® 7 when running with Radeon Settings [82050] Star Wars™: Battlefront - Snow flickers in a few locations in the game [82240] Star Wars™: Battlefront - Sky rendering may be broken in some game locations [82645] Fallout 4 - The compass may flicker during gameplay on AMD Radeon R9 390 series products. We continue to investigate the issue with AMD Radeon R9 290 and AMD Radeon R9 295X2 series products [82667] Star Wars™: Battlefront - Shadowy textures are visible around hills/structures/caves [81890] Just Cause 3 - Texture corruption may be experienced during gameplay [54874] Call of Duty: Black Ops 3 - Poor AMD Crossfire™ performance may be experienced [82338] The driver installation may fail while installing the ACP component [82426] The font size in Chinese language installations may be too small [82438] The label range values in some AMD Freesync™ installations may be incorrect [82536] The Radeon Settings dropbox does not close when it is clicked on a second time [82603] The AMD Overdrive™ fan settings is always set to ON after first edit on reboot [82586] Language shows up as Chinese Simplified when Chinese Traditional is selected in Windows® 7 [82656] Radeon Settings crashes on the Display tab when cloning a display via HDMI on some notebooks [82671] Overdrive™ fan speed is reset to Manual on exiting from a 3D game or application [82766] Radeon Settings does not get upgraded in some install scenarios [82691] AMD Overdrive™ cannot revert to default settings in some situations Known Issues [82789] Total War™ : Rome II : Choppy gameplay may be experienced [82788] Call of Duty: Black Ops 3 - Frame freezing during gameplay may be experienced [82794] Just Cause 3 - The system may hang when task switching on systems with AMD CPUs and GPUs [82775] Just Cause 3 - Flickering may be experienced during gameplay and on menu screens [82778] Anno 2205 - Water splatter may flicker during in Ultra high mode on 4K displays [82779] Fallout 4 - Gameplay may be choppy in AMD Freesync™ mode in Ultra mode at 1440p resolution [58978] Dirt Rally - A crash may be experienced starting a new race with AMD Crossfire™ and AMD Freesync™ enabled [59475] Elite: Dangerous - Poor performance may be experienced in SuperCruise mode under Windows® 10 [78139] PowerDVD - 3D playback may fail on some configurations using an HDMI 2.0 dongle [79428] Starcraft 2: Flickering may be observed in the 'Episode 3' campaign [80251] Fable Legends: The DirectX® 12 benchmark may fail to launch on some configurations [80836] Call of Duty: Black Ops 3 - Flickering or poor performance may be experienced when running in AMD Crossfire™ mode [81402] Assassin's Creed Syndicate - A crash may be experienced when setting game to Ultra-High graphics mode [81403] Flickering may be observed on some Freesync monitors while playing Wolfenstein - The New Order and Battlefield™: Hardline with Vsync disabled [81448] A system restart may be experience when waking the system from sleep mode on some systems with Intel processors [81489] Unable to create 4x1 or 2.1 portrait mode SLS with 4K displays [81651] Star Wars™: Battlefront - texture corruption may be experienced if the game "Field of View" setting is > 100 [81736] Call of Duty Online - the game may crash if the Printscreen key is pressed on a 4K monitor [81777] Launching a game from the Game Manager may launch on a single display after enabling and disabling AMD Crossfire™ in a 3x1 AMD Eyefinity™ setup [81809] A crash may be experienced if an HDMI™ display is a cloned display device on an HP Envy 15 notebook [81844] Unable to change resolution if a wireless display is the only connected display [81856] Marginally increased power consumption may be observed during video playback [81859] Flickering may be experienced on some monitors when AMD Freesync™ is enabled [81915] Assassin's Creed Syndicate - Building textures may be missing on some AMD Freesync™ displays with Vsync enabled [82083] Ark Survival Evolved - Poor performance may be experienced when running in AMD Crossfire™ mode [82093] Star Wars™ : Battlefront - Some flickering may be experienced in shaded areas of the screen while game levels are loading [82213] Star Wars™ : Battlefront - Some users may experience minor flickering or corruption at different game location or while viewing the in-game cinematics [82387] Assassin's Creed Syndicate - The game may crash if the Gaming Evolved "In Game Overlay" is enabled. A temporary workaround is to disable the AMD Gaming Evolved "In Game Overlay"
http://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-Software-Crimson-Edition-15.12.aspx This list is horrible. It's april's fool today? :puke2:
data/avatar/default/avatar39.webp
It's not offline for me. It's 308MB in size.
https://forums.guru3d.com/data/avatars/m/55/55855.jpg
Hype! So, they are the same as the 15.11.1 ?
Yes, they are the 15.11.1 BETAs WHQL'd, with 2 new fixes added, which are :-
Radeon Settings driver update check is not available for minor driver versions System has higher idle power usage on Windows® 7 when running with Radeon Settings
That Dirt Rally issue of crashing with Xfire and FreeSync must have been going a while, as i get that with the 15.9.1 BETAs. :P
https://forums.guru3d.com/data/avatars/m/90/90882.jpg
I haven't had any issues with the Crimson Drivers so far but I don't really mess around with them. As long as everything works ok that's fine by me.
https://forums.guru3d.com/data/avatars/m/260/260826.jpg
Yes, they are the 15.11.1 BETAs WHQL'd, with 2 new fixes added, which are :-
Well at least the update function in drivers is able now to update drivers to fixed versions and not only to borked WHQL ones. I guess the forced power saving functions in Crimson compensate by a large margin the higher power consumption of the settings GUI. So we are still waiting for the re-fix, i mean the fix for the Crimson fix. :D
https://forums.guru3d.com/data/avatars/m/248/248994.jpg
Two years from now "Elite: Dangerous - Poor performance may be experienced in SuperCruise mode" will still be an ongoing issue. Quite funny. Luckily I don't play that game.
data/avatar/default/avatar19.webp
Yup, the 15.12 Crimson Installer comes with the same display driver that was in 15.11.1, unfortunately.
https://forums.guru3d.com/data/avatars/m/238/238369.jpg
Two years from now "Elite: Dangerous - Poor performance may be experienced in SuperCruise mode" will still be an ongoing issue. Quite funny. Luckily I don't play that game.
It will be fixed in the next driver 15.3.... something 🙂 as i read on the reddit recently (yesterday i think)
https://forums.guru3d.com/data/avatars/m/55/55855.jpg
Least i now know when Dirt Rally sometimes crashes for me, its a driver issue :P
https://forums.guru3d.com/data/avatars/m/260/260826.jpg
It will be fixed in the next driver 15.3.... something 🙂 as i read on the reddit recently (yesterday i think)
15.3? That will be funny. They need to release a time machine for each customer to use updated March drivers. 15.13 is not an option aswell too bad luck and the year is a month short. :D
https://forums.guru3d.com/data/avatars/m/198/198862.jpg
So what is this, WHQL certified 15.11.1 betas? Meh, gonna install it anyway.
https://forums.guru3d.com/data/avatars/m/260/260826.jpg
So what is this, WHQL certified 15.11.1 betas? Meh, gonna install it anyway.
Yes. I hope there is something more to be released in December apart the already provided 15.11.1 Beta (Crimson fix) now "WHQL'ed" as 15.12. This fix really need a fix with a shorter know issues list. :bang:
https://forums.guru3d.com/data/avatars/m/209/209146.jpg
Yes, they are the 15.11.1 BETAs WHQL'd, with 2 new fixes added, which are :- That Dirt Rally issue of crashing with Xfire and FreeSync must have been going a while, as i get that with the 15.9.1 BETAs. :P
Pretty much what it looks like, I'm on Windows 10 and not 7 and I'm not using the Cnext / CCC's update function so I'll probably not upgrade as any unlisted changes are probably minimal at best and I doubt there's any profile tweaks, basically 15.11.1 WHQL. Sadly the list of known issues likely affects the entire "Crimson" series in general and not just 15.11.1 / 15.12 but it's at least good that AMD has recognized these as issues and hopefully come 2016 (Ideally early 2016) they can focus on fixing up the Crimson drivers thoroughly and maybe bring back the missing features and such. (But it's probably going to take time so I won't expect any miracles from a January driver if there is one.)
https://forums.guru3d.com/data/avatars/m/260/260826.jpg
These drivers are distinctly different to the 30 November hotfix Crimson driver. The file sizes are very noticeably different so there shouldn't really be an argument about whether these are newer or not 🙂. Don't read into the version numbers too much, the same version number in AMD could belong to a different build.
Something like this occured in the last (or previous?) drivers release. The size difference was related to 32 bit drivers version integrated in the same exe or not if i remember correctly.
https://forums.guru3d.com/data/avatars/m/249/249985.jpg
Same stupid bug of 15.11.1 , the clock locks to 500/1300 when touch the clocks .
data/avatar/default/avatar31.webp
Same stupid bug of 15.11.1 , the clock locks to 500/1300 when touch the clocks .
it happens only if you touch memory clock
https://forums.guru3d.com/data/avatars/m/260/260826.jpg
No wonder this problem still present been the same drivers WHQL'ed. Staying away from Overdrive (don't enable it!) and using Afterburner as "timings manager" is a possible workaround. Clockblocker probably work also.
https://forums.guru3d.com/data/avatars/m/220/220734.jpg
Looks like they removed support for the older HD series cards again...