For those who may not know it, the current 16.1's are 100% compatible with the CCC Interface. Follow these instructions and you can have your cake and eat it, too...
1)Uninstall Crimson 16.1's, then install the most recent Catalyst driver release of your choice
2) Open Device manager
3) find "Display adapters"
4)right-click on the name of your display adapter and select "update driver software"
5) select "browse for driver software"
6) select "let me pick from a list of device drivers on my computer"
7)on the "select driver you want to install for this hardware" tab, select the "have disk" button
8)hit the "browse" button and point it to C:\AMD\WHQL-Radeon-Software-Crimson-edition-16.1-64-bit-Win10-Win8.1-Win7-Jan7\Packages\Drivers\Display\WT6A_INF\C0297971.inf
and hit the "open" button and sit back as your Crimson drivers populate the CCC shell.
All the standard CCC features work 100%...and, unlike in the Crimson Interface, are 100% reliable. Surprise: you can change resolutions from inside the driver interface again! The only feature that does not translate into the CCC is the shader cache function, but I'm not actually sure if this feature does anything at all for Crimson performance as it is. You will not miss it. You also will not miss the plethora of Crimson Interface bugs--like settings that will not save, etc.
This gives you the latest drivers plus the rock-solid CCC driver interface.
Another bug (which I just reported) in the Crimson 16.1 Interface concerns GPU scaling. In the CI when GPU scaling is turned on, all of the resolutions in the Win10 registry >60Hz disappear; when GPU scaling is turned off, all of the Windows resolutions >60Hz that your monitor supports, including any custom resolutions you have created that are > 60Hz, reappear. As if by magic. Works every time.
Anyway, with the CCC this is not a problem either way and all of your resolution refresh rates are available regardless of your scaling settings. Additionally, the custom res utility works 100% reliably from the CCC interface, too.
I have no earthly idea why AMD is not offering this as an alternate driver for people unhappy with the Crimson Interface--until they can get the CI fixed. It's ideal, it works, and they have all of the components--but they'd rather force people into the buggy Crimson interface whether they like it or not. That just makes no sense to me.