run afterburner or something that can display your gpu core clock, I found mine ranging from 500mhz to 880mhz when the default is 1010mhz it could never reach it.
this is the only issue I had with the 15.12 crimson drivers
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
The AMD Driver Thread
- Thread starter LtMatt
- Start date
run afterburner or something that can display your gpu core clock, I found mine ranging from 500mhz to 880mhz when the default is 1010mhz it could never reach it.
this is the only issue I had with the 15.12 crimson drivers
I had no issues removing Crimson and rolling back to 15.10s; 15.12s weren't stable for me;
I'd either get bsods or hard locks; rolling back had a couple reboots; bsods and now stable.
I like Crimson; but just not there yet for my 290; hopefully next release it will be.
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,675
- Location
- The KOP
Last edited:
15.12 (Crimson) release notes
Known issues
I know I don't have Freesync but those issues started around the time AMD introduced new Winodws 10 drivers along Crossfire Freesync support. I don't know if something is messed up between AMD eyefinity and AMD Freesync but I get this crash when launching a Dirt rally race, works 1 time out of 5 try.
http://techreport.com/news/28602/catalyst-15-7-drivers-enable-freesync-with-crossfire
I'm pretty sure they might have broke something with Crossfire and Eyefinity when trying to implement Freesync + Crossfire.
Note that Freesync absolutely requires a Display Port connection to work.And that my issue is related directly to display port synchronization.
I think this might be a good clue for you AMD.
Known issues
I know I don't have Freesync but those issues started around the time AMD introduced new Winodws 10 drivers along Crossfire Freesync support. I don't know if something is messed up between AMD eyefinity and AMD Freesync but I get this crash when launching a Dirt rally race, works 1 time out of 5 try.
http://techreport.com/news/28602/catalyst-15-7-drivers-enable-freesync-with-crossfire
I'm pretty sure they might have broke something with Crossfire and Eyefinity when trying to implement Freesync + Crossfire.
Note that Freesync absolutely requires a Display Port connection to work.And that my issue is related directly to display port synchronization.
I think this might be a good clue for you AMD.
Caporegime
- Joined
- 8 Jul 2003
- Posts
- 30,063
- Location
- In a house
I get the crashes in Dirt Rally on Win 7 with Xfire and FreeSync, and im using the 15.9.1 BETAs.
Associate
- Joined
- 7 Mar 2013
- Posts
- 1,633
- Location
- North East
I have just had two hours of the Driver Encountered an Error and recovered ERROR ....
everything has been working fine and I was only playing EVE not exactly A TAXING GAME ..
I am stumped as to why this was happening..
The only thing I did do was enable Eyefinity ......
everything has been working fine and I was only playing EVE not exactly A TAXING GAME ..
I am stumped as to why this was happening..
The only thing I did do was enable Eyefinity ......
Last edited:
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,675
- Location
- The KOP
I also believe it's only for whql versions.
FYI, with my ongoing issue with the 2730Z since the upgrade to 15.12.
The monitor on Christmas day decided that couldn't recognize either DVI nor DP, after starting a bad flickering out of the sudden on Christmas Eve. Clean windows upgrade didn't helped either. So the ancient and trusty 2410T out of the back room and back into service after 7 months.
Downgraded to 15.11.1 (total wipe of 15.12 with uninstall and DDU afterwards).
New cable installed and put the 2730Z on. Nothing initially. Both DVI & DP weren't recognized, while simple restart wasn't working either. Cool boot and at last some "life". However the screen is still flickering like mad with DP, and bad screen quality (and lighter flickering) with the DVI.
The 2730Z is flickering even if I connect the netbook that has an i3 igp only. So looks the monitor is a goner and tomorrow morning going to start the process of returning it for repair.
The monitor on Christmas day decided that couldn't recognize either DVI nor DP, after starting a bad flickering out of the sudden on Christmas Eve. Clean windows upgrade didn't helped either. So the ancient and trusty 2410T out of the back room and back into service after 7 months.
Downgraded to 15.11.1 (total wipe of 15.12 with uninstall and DDU afterwards).
New cable installed and put the 2730Z on. Nothing initially. Both DVI & DP weren't recognized, while simple restart wasn't working either. Cool boot and at last some "life". However the screen is still flickering like mad with DP, and bad screen quality (and lighter flickering) with the DVI.
The 2730Z is flickering even if I connect the netbook that has an i3 igp only. So looks the monitor is a goner and tomorrow morning going to start the process of returning it for repair.
I hope it's for all version. Because otherwise update notification feature is useless.
Check to see if your core clocks are fluctuating widely, there's been lots of people reporting that issue
Soldato
- Joined
- 25 Nov 2011
- Posts
- 20,675
- Location
- The KOP
Not really..
The avg Joe beta drivers isn't something they use. They can come with issues.
For having best driver available whql is the better choice.. For more advanced users wanting to use beta drivers they can by downloading manually.
So I set up a second monitor to check out what was going on (bearing in mind I previously had 3 monitors, so this shouldn't be an issue), and it won't go past 1001Mhz on the core and 1500 on the memory for some bizarre reason. All since Crimson.
It's only in Fallout that it seems to stutter, but then I see it's capped at 60FPS in that game (lame) so the core is going up and down constantly.
It's only in Fallout that it seems to stutter, but then I see it's capped at 60FPS in that game (lame) so the core is going up and down constantly.
Still getting black screen on windows loading with crimson and windows 10.
Think it's just a compatibility issue with afterburner. I assume afterburner actually resets the clocks when it shuts down and applies voltage and clocks when you boot up.
With Crimson afterburner isn't putting the clocks back to stock when you shutdown so it's booting up with the higher clock speeds but without the higher voltage that is causing the black screens.
Think it's just a compatibility issue with afterburner. I assume afterburner actually resets the clocks when it shuts down and applies voltage and clocks when you boot up.
With Crimson afterburner isn't putting the clocks back to stock when you shutdown so it's booting up with the higher clock speeds but without the higher voltage that is causing the black screens.
Soldato
- Joined
- 29 Aug 2010
- Posts
- 8,263
- Location
- Cornwall
Isn't this a feature of PowerPlay or ULPS (or something like that) that reduces the clockspeed to what is needed to maintain the fps required (in your case, 60fps).
I get it in a number of games if I cap my framerate my clockspeeds reduce.
In Dota 2 using the console command I can see my clockspeeds change as I raise or lower the max fps (300fps, 60fps, 45fps, 30fps, 15fps, etc.).
If you disable VSync or increase graphics settings I'd imagine you'd see an increase in clockspeeds (assuming your clocks are set to go higher than 1001Mhz).
Maybe this was something you had disabled previously but installing the new drivers has reset it?
same problem for me
VERY VERY annoying
I normally find out first when booting Fallout 4 and it crashes immediately, as set to a resolution above my monitor res
I am completely aware of it adjusting the clock to meet the frame rate target.
For fallout 4, I see it isn't recommended to disable the V-Sync as it actually affects how the game plays (silly silly game). Not sure if there is a way around the 60FPS cap that doesn't affect in-game play.
Anywho.. I reinstalled the latest beta drivers (15.11.1) and it made no difference. I checked MSI for an Afterburner update and it said there wasn't one available, so I checked the web, and lo and behold, 4.2.0 is out (Mine was 4.1.1). So I uninstalled Afterburner and installed the new version and it now appears to have the clocks showing on the sliding now, and not dropping to zero.
Later I will try re-enabling the reg hack to get 50% power limit on again and see if it works as expected.