question over crimson drivers

R

roadiek9

New member
Hello,

I've just recently registered to the forums, even though I've looked at them for many years.

I've recently purchased a msi r9 380 ( ample since i have a single 1080p monitor) and of course went straight to get the latest drivers. at the time these were the crimson 15.12. I was having problems such as slow speed and stuttering. On monitoring things i noticed the gpu clock was under clocking a lot. I tried the last catalyst driver set and everything was fine.

I noticed something else however. I had to go back and forth and take print screens to be sure.

crimson
crimson1.png


crimson2.png


catalyst



I hope the photos work in the post.( if they're too big let me know)

Can you see how the crimson is not rendering certain things.

Anyone else getting this?
Are the newer 16.1 the same?
 
Last edited by a moderator:
I would try the newer 16.1 Hotfix drivers if you do like the interface of the Crimson drivers.

However, if things don't work well, I'd be happy to use the 15.11.1 Beta drivers until things are sorted out. (That's been my preference on my R9 390 for quite a while now.)
 
Dyre Straits said:
I would try the newer 16.1 Hotfix drivers if you do like the interface of the Crimson drivers.

However, if things don't work well, I'd be happy to use the 15.11.1 Beta drivers until things are sorted out. (That's been my preference on my R9 390 for quite a while now.)
Click to expand...

From past experience, it may be your preference for good.
:huh:
 
is this tool safe?
I think I might have to give this a try.
since using crimson drivers I'm noticeing strange Crossfire behaviour such as MGPU not working, frame rate literally halving and second card occasionally idling when playing games fullscreen. Should add that disabling ULPS seems to make no difference.
 
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.
 
Lurk said:
is this tool safe?
I think I might have to give this a try.
since using crimson drivers I'm noticeing strange Crossfire behaviour such as MGPU not working, frame rate literally halving and second card occasionally idling when playing games fullscreen. Should add that disabling ULPS seems to make no difference.
Click to expand...

Yes it's totally safe, i've been using this for well over a week and have encountered zero problems with it (there is a thread over at guru3d forums so you can verify the integrity of it http://forums.guru3d.com/showthread.php?t=404465)
 
tried the tool last night and the difference in EVE online is night and day.
For some reason a few days ago I tried the vsync cap option in the Crimson interface and for some other strange reason (which I don't want nor need to know), from that moment the second card wouldn't clock to 3D anymore. Even tried reinstalling the driver.

I downloaded ClockBlocker and I immediately noticed the game running smoother an in some situations the stutters disappeared (opening the ship fitting window showing a 3D rotating model of your ship).
More than this, the built-in fps counter in EVE went from showing a wobbly 32, 35, 44, 36 to an almost stable 70 (my refresh rate is 72).

The obligatory question: how long before AMD solves this problem with GPU clocks? When I game I want my cards to smoke!

Why can't we have an option to prevent all of the power savings features from getting in the way of our gameplay in such an intrusive manner?

Why is it always that some bright folk has to fix it for them, FFS?

yay for ClockBlocker!
 
You must log in or register to reply here.
Back
Top