AMD today released Radeon Software Crimson Edition 15.11.1 Update. A follow up to last week's major release, version 15.11.1 addresses a major issue with driver-level VGA fan speed control, which saw the driver either crank fan-speeds up to 100%, or lock them down to 30%, causing GPUs to overheat. In addition, the driver addresses several game-specific bugs related to Just Cause 3, Fallout 4, Star Wars: Battlefront, and Call of Duty Black Ops III.AMD Radeon Software Crimson Edition 15.11.1 for Windows 10/8.1/7 32-bit

55 Comments on AMD Releases Radeon Software Crimson Edition 15.11.1 Update

1 to 25 of 55 Go to Page 123 PreviousNext

#1 Mussels

Moderprator First!

wait this isn't facebook.





Downloading now! Posted on Dec 1st 2015, 3:49 Reply

#2 Hood

Mussels First!

wait this isn't facebook.





Downloading now! Check the charge on your fire extinguishers, and put 911 on speed dial...the AMD driver team came up with this update very quickly: I'm just sayin', their track record merits caution. Check the charge on your fire extinguishers, and put 911 on speed dial...the AMD driver team came up with this update very quickly: I'm just sayin', their track record merits caution. Posted on Dec 1st 2015, 5:00 Reply

#3 manofthem

WCG-TPU Team All-Star! With this news, I'm going to install the Crimson driver on my 2 pcs that haven't been updated yet. I want to see how it affects those gpus (7770 and 270x), if it'll burn one up and force me to get a new card :)



If it does mess it up, I'll update to this new beta. Posted on Dec 1st 2015, 5:08 Reply

#4 GoldenX

The AMD page gives you this driver both por GCN and WLIV based cards, does anyone know if that is correct? Posted on Dec 1st 2015, 5:10 Reply

#5 Aquinus

Resident Wat-man GoldenX The AMD page gives you this driver both por GCN and WLIV based cards, does anyone know if that is correct? Not according to the download release notes. It looks the same as regular Crimson.





It's probably time to throw in the towel so to speak on VLIW GPUs. They've been around for a long time and it's time for support to be dropped in order to focus on the newer and more flexible architecture of GCN. VLIW5 like on my old 6870s has its limitations and it's only holding AMD back from focusing on their newer products by having to support it. We got quite the stint of support for these GPUs though. I bought my first 6870 on release day and got to enjoy over 5 years of support. That's not too shabby in my opinion. Not according to the download release notes. It looks the same as regular Crimson.It's probably time to throw in the towel so to speak on VLIW GPUs. They've been around for a long time and it's time for support to be dropped in order to focus on the newer and more flexible architecture of GCN. VLIW5 like on my old 6870s has its limitations and it's only holding AMD back from focusing on their newer products by having to support it. We got quite the stint of support for these GPUs though. I bought my first 6870 on release day and got to enjoy over 5 years of support. That's not too shabby in my opinion. Posted on Dec 1st 2015, 5:47 Reply

#6 Mussels

Moderprator GoldenX The AMD page gives you this driver both por GCN and WLIV based cards, does anyone know if that is correct?



7670M in my laptop misses out by a whisker 7670M in my laptop misses out by a whisker Posted on Dec 1st 2015, 5:47 Reply

#7 akspa

GoldenX The AMD page gives you this driver both por GCN and WLIV based cards, does anyone know if that is correct? The new driver has definitions in the INF files for cards going as far back as the Radeon HD 2600 XT, so I'd wager a guess and say that the driver files still have the applicable code paths for these cards. The new driver has definitions in the INF files for cards going as far back as the Radeon HD 2600 XT, so I'd wager a guess and say that the driver files still have the applicable code paths for these cards. Posted on Dec 1st 2015, 6:00 Reply

#8 R-T-B

akspa The new driver has definitions in the INF files for cards going as far back as the Radeon HD 2600 XT, so I'd wager a guess and say that the driver files still have the applicable code paths for these cards. That'd be a shocker considering there hasn't been a Radeon 2000/3000/4000 driver code path in these drivers for quite some time outside the legacy branch. That'd be a shocker considering there hasn't been a Radeon 2000/3000/4000 driver code path in these drivers for quite some time outside the legacy branch. Posted on Dec 1st 2015, 6:04 Reply

#9 TheGuruStud

Mussels 7670M in my laptop misses out by a whisker mod the ini mod the ini Posted on Dec 1st 2015, 8:02 Reply

#10 Mussels

Moderprator TheGuruStud mod the ini Somehow i doubt thats going to get me much functionality, or has it been tested? Somehow i doubt thats going to get me much functionality, or has it been tested? Posted on Dec 1st 2015, 8:04 Reply

#11 Esse

New update breaks Battlefront.



After every death my screen flashes black for a split second.



I also can't tab out and back in without clicking multiple times very fast to keep it full screen.



edit; no games can full-screen without lots of clicking. Oh well, back to the older drivers. Posted on Dec 1st 2015, 8:58 Reply

#12 agent00skid





Tried to run it on my laptop, and it installed just fine. Lost OpenCL in the process though. Posted on Dec 1st 2015, 10:12 Reply

#13 Mussels

Moderprator Oh somehow i failed to notice these drivers existed with a seperate download for the legacy devices, derped on that one. downloading the right file for my laptop now. Posted on Dec 1st 2015, 10:50 Reply

#14 Ebo

Yeah and the new driver makes problems in AC Black Flag instead, what a peice of junk. Posted on Dec 1st 2015, 11:38 Reply

#15 progste

Mh... Having liquid cooling the fan profile was not an issue, now I'm not sure if it's worth risking to break stuff by installing this version, I love their cards but wish AMD would test their drivers a bit more. Posted on Dec 1st 2015, 13:06 Reply

#16 Mussels

Moderprator i'm having no trouble with these drivers on my laptop or desktop.



had to use DDU on the laptop, but that was likely due to using modded drivers initially. Posted on Dec 1st 2015, 13:14 Reply

#17 Aquinus

Resident Wat-man Mussels i'm having no trouble with these drivers on my laptop or desktop.



had to use DDU on the laptop, but that was likely due to using modded drivers initially. I've been using DDU ever since I upgraded to Windows 10. There have been more instances than not where drivers haven't updated properly and just cleaning them out before upgrading ensures that doesn't happen. I'm convinced that a lot of issues that crop up are because of this. I've been using DDU ever since I upgraded to Windows 10. There have been more instances than not where drivers haven't updated properly and just cleaning them out before upgrading ensures that doesn't happen. I'm convinced that a lot of issues that crop up are because of this. Posted on Dec 1st 2015, 13:27 Reply

#18 Mussels

Moderprator Aquinus I've been using DDU ever since I upgraded to Windows 10. There have been more instances than not where drivers haven't updated properly and just cleaning them out before upgrading ensures that doesn't happen. I'm convinced that a lot of issues that crop up are because of this. in the past i had lots of issues with various driver cleaner programs, DDU seems to be working well for me. I have windows update disabled and use a third party tool, so i do not have driver issues like that. in the past i had lots of issues with various driver cleaner programs, DDU seems to be working well for me. I have windows update disabled and use a third party tool, so i do not have driver issues like that. Posted on Dec 1st 2015, 13:28 Reply

#19 Aquinus

Resident Wat-man Mussels I have windows update disabled and use a third party tool, so i do not have driver issues like that. I've had the issue using AMD's installer to upgraded drivers. I too have driver updates from Windows Update disabled. I've had the issue using AMD's installer to upgraded drivers. I too have driver updates from Windows Update disabled. Posted on Dec 1st 2015, 13:32 Reply

#20 progste

I'm still on win7, I don't think I'll upgrade any time soon. Posted on Dec 1st 2015, 13:39 Reply

#21 GoldenX

Installed it with no problems on Win10, no need for DDU.

I'm going to try it on my brother's HD5450, the .inf shows all cards, even the DX10 ones. Posted on Dec 1st 2015, 15:01 Reply

#22 m0nt3

I haven't tested these yet, but on the previous crimson drivers while in BF4 when I press the tab I would get big block squares (for lack of a better description) around certain objects on ocassion. I did not suffer from the fan speed bug. My temps stayed around 76C and 45% fan speed in BF4. Posted on Dec 1st 2015, 15:08 Reply

#23 Octopuss

I hate the fact that you can't change the language in this new (Crimson in general I mean) driver. Piece of shit software automatically shows everything in czech on my PC, and I seriously don't know what the hell most of the settings mean. Posted on Dec 1st 2015, 16:22 Reply

#24 r.h.p

I'm getting a flickering Gps marker in Fallout4 even with the new beta update ....not before the crimson drivers Posted on Dec 1st 2015, 19:40 Reply

#25 Mussels

Moderprator r.h.p I'm getting a flickering Gps marker in Fallout4 even with the new beta update ....not before the crimson drivers theres a fix for it on the nexus, involves pasting two .dll files into the game directory. theres a fix for it on the nexus, involves pasting two .dll files into the game directory. Posted on Dec 2nd 2015, 3:36 Reply