Wednesday, December 18th 2013

AMD Releases the Catalyst 13.12 WHQL Graphics Drivers

After months of Catalyst 13.11 betas AMD has now made available a new WHQL-certified graphics driver, the Catalyst 13.12. This release features support for the Radeon HD 5000, HD 6000, HD 7000, Radeon R7 and R9 Series cards and is available for Windows Vista, 7, 8 and 8.1.

Download: Catalyst 13.12 WHQL 32-bit / Catalyst 13.12 WHQL 64-bit

Feature Highlights
​Support for the following new products:
  • AMD Radeon R9 290, 280, and 270 Series
  • AMD Radeon R7 260, 250, and 240 Series
​Improved AMD CrossFire​ scaling for the following game titles:
  • Call of Duty: Ghosts (multiplayer component)
  • Splinter Cell Blacklist
  • Saints Row 4
  • Metro Last Light
​New AMD Enduro Technology profiles for the following game titles:
  • XCOM: Enemy Unknown
  • Need for Speed Rivals
  • Total War​: Rome 2
  • Battlefield 4
  • Saints Row 4
  • Splinter Cell Blacklist
  • FIFA 14
​Support For AMD CrossFire frame pacing
  • Frame pacing ensures that frames rendered across multiple GPUs in an AMD CrossFire configuration will be displayed at an even and regular pace
  • Frame pacing is enabled through the AMD Catalyst Control Center, or on a per application basis
  • Frame pacing is supported on DirectX 10 and DirectX 11 applications using resolutions up to (and including) 2560x1600 on a single display
Resolved Issues
  • May resolve intermittent black screens or display loss observed on some AMD Radeon R9 290X and AMD Radeon R9 290 graphics cards
  • Resolves intermittent crashes seen in legacy DirectX 9 applications
  • AMD Radeon R9 290 Series - Power Tune update to reduce variance of fan speed / RPM
  • PCI-E bus speed is no longer set to x1 on the secondary GPU when running in an AMD CrossFire configuration
  • Resolves incorrect HDMI Audio Driver information being listed in the AMD Catalyst Control Center
  • Resolves AMD Steady Video option being grayed out in the AMD Catalyst Control Center
  • Resolves intermittent flickering seen on some AMD Radeon R9 270X graphics cards
  • Resolves graphics corruption issues found in Starcraft
  • Resolves image corruption seen in Autodesk Investor 2014
  • Resolves flickering water corruption found in World of Warcraft
  • Resolves intermittent black screen when resuming from a S3/S4 sleep-state if the display is unplugged during the sleep-state on systems supporting AMD Enduro Technology
  • Resolves intermittent crashes experienced with Battlefield 4 on Windows 8 based systems
  • Resolves the display turning green when using Windows Media Player to view HD .avi format video in an extended desktop configuration
  • Resolves Metro applications experiencing frame drops during playback of interlaced video content
  • Resolves video playback corruption of .wmv format files in Windows Media Player
Add your own comment

80 Comments on AMD Releases the Catalyst 13.12 WHQL Graphics Drivers

#1
Prima.Vera
They specify clear that the drivers support also include the 5XXX series. A BS lie. If they don't do squat about us with 5xxx generation cards, at least they should remove the support and be done with it. Those drivers offers 0 improvements over previews ones for my CFX cards....
Posted on Reply
#2
Octopuss
You misunderstand the statement. Just because the driver WORKS with those cards doesn't mean they get any improvements. Support in this particular case simply means you can install the driver with such card. That's all.
Posted on Reply
#3
Steevo
Prima.Vera said:
They specify clear that the drivers support also include the 5XXX series. A BS lie. If they don't do squat about us with 5xxx generation cards, at least they should remove the support and be done with it. Those drivers offers 0 improvements over previews ones for my CFX cards....
Specifically if your feet were in a vat of liquid nitrogen and your head on fire your average temperature would be OK too. But specifically we both know that its a bad idea, so when you find a driver that has no issues, stop installing new ones, that is unless you want to try and create issues to complain about.
Posted on Reply
#5
Solaris17
Creator Solaris Utility DVD
Prima.Vera said:
Steevo, you drunk? o_O
have you seen him irl? he could probably drink you under the table
Posted on Reply
#6
Frag Maniac
Can anyone confirm whether the driver number after install is just a read error? I really don't want to install this until I'm sure it's actually a 13.12 driver.
Posted on Reply
#7
Disruptor4
Frag Maniac said:
Can anyone confirm whether the driver number after install is just a read error? I really don't want to install this until I'm sure it's actually a 13.12 driver.
I reckon it is just a read error. It's happened before.
Posted on Reply
#8
Steevo
Prima.Vera said:
Steevo, you drunk? o_O
Not yet. That starts tomorrow night. These drivers do nothing for us other than cause problems, so much like Nvidia doesn't supply drivers on a regular basis for all cards, ATI/AMD doesn't take the time to test drivers with every board, CPU, Memory, OS and service pack and hotfix, and game in that combination, so sometimes you are better sticking with a good stable driver.

http://www.nvidia.com/Download/Scan.aspx

It requires Java on their main download page so you can only install their recommended version, if AMD did this everyone would scream bloody murder and how horrible Java is and the thread would easily reach 10 pages.

If you look at the 400 series cards the 331.93 is listed as Beta for them, as it may cause issues, and plausible deniability when shit does go wrong. Again if ATI/AMD did this there would be a huge fit thrown about how cards aren't supported anymore.

So at the end of the day you are better off sticking with a good known driver unless you want to take the chance to experience issues.
Solaris17 said:
have you seen him irl? he could probably drink you under the table
LOL,
Posted on Reply
#9
de.das.dude
Pro Indian Modder
plz work on my 7790 like its supposed to -.-
Posted on Reply
#10
agent00skid
As their mobility download tool finally worked, I have now installed it on my laptop.

The version number updated correctly.
Posted on Reply
#11
Constantine Yevseyev
agent00skid said:
As their mobility download tool finally worked, I have now installed it on my laptop.

The version number updated correctly.
Really? It did work?! I can't believe that! There's no confirmation on the Internet that this tool actually worked for anybody. Ever.

I was trying to make use of it since having my ATI Mobility Radeon HD 540v. Four different operating systems, three graphic cards - it just didn't work. I was searching for a proof that this tool can at least start downloading process since 2009. Can I have a look at screenshot?
Posted on Reply
#12
Prima.Vera
Steevo said:
These drivers do nothing for us other than cause problems, so much like Nvidia doesn't supply drivers on a regular basis for all cards, ATI/AMD doesn't take the time to test drivers with every board, CPU, Memory, OS and service pack and hotfix, and game in that combination, so sometimes you are better sticking with a good stable driver. ...
So at the end of the day you are better off sticking with a good known driver unless you want to take the chance to experience issues.
I get what you're saying, unfortunately I am playing latest games, and have a CFX config, so if I'm not getting latest crappy drivers, I will have no chance of having CF working on those titles. Heck, BF4 works flawlessly only with the latest betas, while COD crashes like crazy. Also those drivers surprisingly are the only ones that enable proper CF in Ass Creed 3, however the game start to crash often now, and restarting PC....
As you see, I have no choice here, but to keep hoping that the next drivers will be better than previews ones.
Posted on Reply
#13
Melvis
No good, Pegs my second card at 100% GPU usage in games....AGAIN!!!! So back to 13.4's :banghead:
Posted on Reply
#14
SK-1
Fixed BF4. No more texture flashing :) Haven't checked 2nd gpu usage but Id be happy with 100%...
Posted on Reply
#15
Octopuss
SK-1 said:
Fixed BF4. No more texture flashing :) Haven't checked 2nd gpu usage but Id be happy with 100%...
It's not the drivers, it's the recently released BF4 patch :P
Posted on Reply
#16
SK-1
Octopuss said:
It's not the drivers, it's the recently released BF4 patch :p
oops wrong thread lol...
Posted on Reply
#17
agent00skid
Constantine Yevseyev said:
Really? It did work?! I can't believe that! There's no confirmation on the Internet that this tool actually worked for anybody. Ever.

I was trying to make use of it since having my ATI Mobility Radeon HD 540v. Four different operating systems, three graphic cards - it just didn't work. I was searching for a proof that this tool can at least start downloading process since 2009. Can I have a look at screenshot?
As requested.
Posted on Reply
#18
Serpent of Darkness
Melvis said:
No good, Pegs my second card at 100% GPU usage in games....AGAIN!!!! So back to 13.4's :banghead:
If the game doesn't support Crossfire, i.e. World of Tanks, then you'll always see a 100% GPU Load on the 2nd GPU. This is with CrossfireX. This happens especially with the newer R7 and R9 Series. Basically all games and benchmarks that only use single graphic card setups, GPU 2's load will always do 100%, and GPU 1 will be at 0%. This isn't an error or malfunction in the card. It is the nature of AMD Graphic Cards. Even complain to AMD about this on their forum, they will tell you that this is actually a natural function or state for their cards. So whether you use Driver Version 13.4 or 13.12, it won't really make a difference on GPU 2 at 100% load. Second GPU at 100% load is actually normal for AMD Cards. The only major difference between 13.4 and 13.12 is optimization, profiles changes, bug fixes, etc... Yes. You can take ULPS, set it to 0 in the registry, but that just means that both (if you have 2) GPUs will be running 100% loads on a game that only needs 100% loads, or throttles less loads on a single GPU. Both GPUs at 100% loads equate to more power consumption over time. You also need to take into account that GPU Loads are approached differently between NVidia and AMD Graphic Cards. GPU loads on NVidia cards try to mirror one another. If GPU 1 is doing 43% for half section of frames, then GPU 2 will do 43% load for the other half section of the same frames, in SLI. On the other hand, if GPU 2 does 88%, more than twice the first, then you know the SLI configuration is having scaling issue. AMD GPUs throttle 99 to 100% loads amongst the different Graphic Cards. The question then becomes for how long. If it has to do it for a long time, then the GPU load will always cap at 99 to 100%. When it's not required to do those loads for a small instant in time, the GPU Load could throttle down and up again. This occurs more often when ULPS is set to 1 because their is a change in power consumption requirements over time for different loads. While NVidia uses AFR 1 and 2, AMD only uses AFR 1, or whole frames from each Graphic Card. So AMD Graphic Cards always do 99 to 100% loads for whole frames, per GPU, when frames need to be produced.

Basically, when you can only utilize 1 AMD Graphic Card, and you're running a CrossfireX setup, you will always see a 99% to 100% load on GPU 2. What basically happens is that GPU 2, on Graphic Card 2, will produce the frames. Frames will be created by GPU 2, sent to Graphic Card 2's framebuffer, transferred to Graphic Card 1's framebuffer from the CrossfireX Bridge, and then it's sent off to the Display Adapter. We are talking about whole frames being transferred from one framebuffer to another framebuffer, in AMD's case. On the other hand, if you do play a game that does utilize both Graphic Cards, GPU 1 will produce frames on it's frame buffer while GPU 2 does the same. GPU 1 shoots a frame off to the display adapter. Once the Frame leaves the framebuffer from the first card, it will receive the frame from the 2nd Graphic Card's framebuffer, and push that frame off to the display adapter. From there, it's just a repetitive motion. Frame Pacing Software was designed and needed to regulate this process. Before the software, both GPUs would have a potential to produce partial frames instead of whole ones, and try to send it off to the display adapter. When the graphic card realized it didn't produce a whole frame, it would drop the frame. Nothing on a hardware level was regulating that to reduce runt frames from being sent off from the frame buffers. AMD implemented software to control the way those frames were being pushed out. AMD 7000 Series Graphic Cards had a potential to push even smaller Frame Times, but sacrificed the time needed to developed whole frames. That was the tradeoff. This is why AMD 7000 Series Graphic Cards had so much drop-age and bandwidth in their Frame Time Variance Graphs. With the PCIe Based CrossfireX, it's allowed AMD the ability to better control and regulate whole frames with their software, and how it's being transferred from one framebuffer to the other.
Posted on Reply
#19
Melvis
Serpent of Darkness said:
If the game doesn't support Crossfire, i.e. World of Tanks, then you'll always see a 100% GPU Load on the 2nd GPU. This is with CrossfireX. This happens especially with the newer R7 and R9 Series. Basically all games and benchmarks that only use single graphic card setups, GPU 2's load will always do 100%, and GPU 1 will be at 0%. This isn't an error or malfunction in the card. It is the nature of AMD Graphic Cards. Even complain to AMD about this on their forum, they will tell you that this is actually a natural function or state for their cards. So whether you use Driver Version 13.4 or 13.12, it won't really make a difference on GPU 2 at 100% load. Second GPU at 100% load is actually normal for AMD Cards. The only major difference between 13.4 and 13.12 is optimization, profiles changes, bug fixes, etc... Yes. You can take ULPS, set it to 0 in the registry, but that just means that both (if you have 2) GPUs will be running 100% loads on a game that only needs 100% loads, or throttles less loads on a single GPU. Both GPUs at 100% loads equate to more power consumption over time. You also need to take into account that GPU Loads are approached differently between NVidia and AMD Graphic Cards. GPU loads on NVidia cards try to mirror one another. If GPU 1 is doing 43% for half section of frames, then GPU 2 will do 43% load for the other half section of the same frames, in SLI. On the other hand, if GPU 2 does 88%, more than twice the first, then you know the SLI configuration is having scaling issue. AMD GPUs throttle 99 to 100% loads amongst the different Graphic Cards. The question then becomes for how long. If it has to do it for a long time, then the GPU load will always cap at 99 to 100%. When it's not required to do those loads for a small instant in time, the GPU Load could throttle down and up again. This occurs more often when ULPS is set to 1 because their is a change in power consumption requirements over time for different loads. While NVidia uses AFR 1 and 2, AMD only uses AFR 1, or whole frames from each Graphic Card. So AMD Graphic Cards always do 99 to 100% loads for whole frames, per GPU, when frames need to be produced.

Basically, when you can only utilize 1 AMD Graphic Card, and you're running a CrossfireX setup, you will always see a 99% to 100% load on GPU 2. What basically happens is that GPU 2, on Graphic Card 2, will produce the frames. Frames will be created by GPU 2, sent to Graphic Card 2's framebuffer, transferred to Graphic Card 1's framebuffer from the CrossfireX Bridge, and then it's sent off to the Display Adapter. We are talking about whole frames being transferred from one framebuffer to another framebuffer, in AMD's case. On the other hand, if you do play a game that does utilize both Graphic Cards, GPU 1 will produce frames on it's frame buffer while GPU 2 does the same. GPU 1 shoots a frame off to the display adapter. Once the Frame leaves the framebuffer from the first card, it will receive the frame from the 2nd Graphic Card's framebuffer, and push that frame off to the display adapter. From there, it's just a repetitive motion. Frame Pacing Software was designed and needed to regulate this process. Before the software, both GPUs would have a potential to produce partial frames instead of whole ones, and try to send it off to the display adapter. When the graphic card realized it didn't produce a whole frame, it would drop the frame. Nothing on a hardware level was regulating that to reduce runt frames from being sent off from the frame buffers. AMD implemented software to control the way those frames were being pushed out. AMD 7000 Series Graphic Cards had a potential to push even smaller Frame Times, but sacrificed the time needed to developed whole frames. That was the tradeoff. This is why AMD 7000 Series Graphic Cards had so much drop-age and bandwidth in their Frame Time Variance Graphs. With the PCIe Based CrossfireX, it's allowed AMD the ability to better control and regulate whole frames with their software, and how it's being transferred from one framebuffer to the other.
But it doesnt happen with 13.4 drivers, they work perfectly for me, but 13.9 and 13.12 do the same thing, but 13.9 did it as soon as I opened Firefox, so annoying, but at least 13.12 doesnt do that, just in this particular game (payday 2) even if I turn on Vsync it doesnt change, or in menus' nothing, just runs flat out and then overheats my card, where 13.4's run the GPU at what it needs to run at, which is like 30-40% not 100% and runs alot cooler. But i havent tested 13.12 in other games so I dont know. If that issue was fixed then the drivers be great as I do get a performance increase, but how they are at the moment, ill pass.
Posted on Reply
#20
NeoXF
Melvis said:
No good, Pegs my second card at 100% GPU usage in games....AGAIN!!!! So back to 13.4's :banghead:
Isn't 100% usage of a GPU/multi-GPU setup and good thing? :confused:
Posted on Reply
#21
Melvis
NeoXF said:
Isn't 100% usage of a GPU/multi-GPU setup and good thing? :confused:
Not when its not needed. Both GPU's should be working at the same usage but with the newer drivers one will be at 20-30% (top card) and the bottom will be at 100% at all times no matter where you are at in the game, even in menu's :(
Posted on Reply
#22
Serpent of Darkness
NeoXF said:
Isn't 100% usage of a GPU/multi-GPU setup and good thing? :confused:
Yes, you are correct. Having 99% or 100% loads on an AMD Graphic Card is good. It mean that one processing unit is taking up 100% loads to produce frames onto it' framebuffer.

I think he is more concern that GPU 2 is only doing 100% or 99% loads, and not GPU 1. I suspect he strongly feels that they, GPUs 1 and 2, are suppose to divide the load evenly amongst the GPUs. AMD Graphic Cards don't approach producing partial frames for one another like NVidia does with SLI. Simply put, AMD produces whole frames, and NVidia does multiple links of a whole frame, but divides the work amongst any additional graphic card in SLI. If I am not mistaken, the links begin from the upper left of your screen. If GPU 1 - NVidia isn't in SLI, then that Graphic Card does all links, or 100% of the load. If their is a 2nd GPU in SLI, GPU 2 will be in charge of every evenly numbered link, and GPU 1 will be in charge of every odd numbered link. Thus, this is why NVidia call its multi-gpu solution SLI, or Scalable Link Interface. Fragments of a whole images on the NVidia card, are broken down into links on your screen like a grid, before the image is displayed on your monitor. AMD doesn't do this, and that's why they don't share GPU loads.


Melvis said:
Not when its not needed. Both GPU's should be working at the same usage but with the newer drivers one will be at 20-30% (top card) and the bottom will be at 100% at all times no matter where you are at in the game, even in menu's :(
Again, you cannot compare GPU Loads from NVidia cards and AMD cards in the same context. Both companies approach the multi-gpu setup at different angles. If you want your GPU loads to have the same percentage, then you should have invested in NVidia Graphic Cards. AMD Graphic Cards work in a different way, and that work being done is generating "whole" frames. Storing that information into it's framebuffers before the image is sent to your monitor. When the GPU's Load is at 99% or 100%, the uptime indicates that the GPU is producing frames at full capacity. AMD GPU Loads have a tendency to throttle up and down when it isn't necessary to produce whole frames. Probably due to the fact that it's already finished it's load of work, and hasn't received instructions from the CPU.

Now the only scenario where I can see both AMD GPUs having the same load, and it's less than 99%, is when the graphic cards are overkill for the PC Game. Older PC Games are like this where, because newer graphic cards have more streaming processors and higher core frequencies, it will take less latency to accomplish the same goal as older AMD Graphic Cards . It will take less time to push the same amount of work. This also means that less resources are needed to accomplish the same amount of work as an older GPU. So that could translate to lower GPU Load Percentages. If an AMD GPU Load drops down to 30%, then it only needed to utilize 30% of itself to produces frames at that small instant in time. If the percentage goes up, then the GPU % goes up, and this is an indication that it needs to consume more power to produce the next batch of frames.
Posted on Reply
#23
Melvis
Serpent of Darkness said:
Again, you cannot compare GPU Loads from NVidia cards and AMD cards in the same context. Both companies approach the multi-gpu setup at different angles. If you want your GPU loads to have the same percentage, then you should have invested in NVidia Graphic Cards. AMD Graphic Cards work in a different way, and that work being done is generating "whole" frames. Storing that information into it's framebuffers before the image is sent to your monitor. When the GPU's Load is at 99% or 100%, the uptime indicates that the GPU is producing frames at full capacity. AMD GPU Loads have a tendency to throttle up and down when it isn't necessary to produce whole frames. Probably due to the fact that it's already finished it's load of work, and hasn't received instructions from the CPU.

Now the only scenario where I can see both AMD GPUs having the same load, and it's less than 99%, is when the graphic cards are overkill for the PC Game. Older PC Games are like this where, because newer graphic cards have more streaming processors and higher core frequencies, it will take less latency to accomplish the same goal as older AMD Graphic Cards . It will take less time to push the same amount of work. This also means that less resources are needed to accomplish the same amount of work as an older GPU. So that could translate to lower GPU Load Percentages. If an AMD GPU Load drops down to 30%, then it only needed to utilize 30% of itself to produces frames at that small instant in time. If the percentage goes up, then the GPU % goes up, and this is an indication that it needs to consume more power to produce the next batch of frames.
o_O I didn't say I was comparing Nvidia to AMD, just AMD, I get what your saying, but im not talking about anything to do with Nvidia here just the drivers and my set up.

This is what I mean the cards I use are overkill for the game (payday 2) so they dont need to work hard (100%) to get great FPS in this game, but with 13.9 and 13.12 it only pegs the second GPU at 100% when its just not needed. But 13.4 drivers work perfectly and evenly in this game, thats just how it is for me with my Crossfire 7870 XT's.
Posted on Reply
#24
Blín D'ñero
Serpent of Darkness said:
If the game doesn't support Crossfire, i.e. World of Tanks, then you'll always see a 100% GPU Load on the 2nd GPU. This is with CrossfireX.
[...]
Having 99% or 100% loads on an AMD Graphic Card is good. It mean that one processing unit is taking up 100% loads to produce frames onto it' framebuffer.
[...]
Stop spreading nonsense PLEASE! Goddammit what a load of crap you made up.

The 99% usage on GPU2 is a bug caused by ULPS. ULPS is supposed to be a power saving feature for crossfire, but hasn't been working correctly for many Catalyst versions now.
So, Crossfire users must disable ULPS in the registry.

How-to:

  1. In the search field (above the Start Orb) type
    regedit
  2. right-click on the regedit.exe shortcut that appears -> run as admin
  3. In Registry, on the left highlight HKEY_LOCAL_MACHINE.
  4. Hit Ctrl+F, and in the Find field fill in:
    enableulps
    and hit Enter (or click Next) or hit F3 for next.
  5. At Every instance of EnableUlps change the value from 1 to 0
    Don't touch EnableUlps_NA
  6. Close Registry
  7. Reboot the PC
This is the workaround for the "99% usage on GPU2 in 3D applications (games)."- bug.
The downside is that GPU2 is no longer put to sleep mode when idle (in 2D).
Posted on Reply
#25
Serpent of Darkness
[quote="Blín D'ñero, post: 3039021, member: 66551"]Stop spreading nonsense PLEASE! Goddammit what a load of crap you made up.

The 99% usage on GPU2 is a bug caused by ULPS. ULPS is supposed to be a power saving feature for crossfire, but hasn't been working correctly for many Catalyst versions now.
So, Crossfire users must disable ULPS in the registry.

How-to:

  1. In the search field (above the Start Orb) type
    regedit
  2. right-click on the regedit.exe shortcut that appears -> run as admin
  3. In Registry, on the left highlight HKEY_LOCAL_MACHINE.
  4. Hit Ctrl+F, and in the Find field fill in:
    enableulps
    and hit Enter (or click Next) or hit F3 for next.
  5. At Every instance of EnableUlps change the value from 1 to 0
    Don't touch EnableUlps_NA
  6. Close Registry
  7. Reboot the PC
This is the workaround for the "99% usage on GPU2 in 3D applications (games)."- bug.
The downside is that GPU2 is no longer put to sleep mode when idle (in 2D).[/quote]Disabling Ultra Low Power State doesn't stop only GPU 2 from pushing 99 to 100% usage on the new R9-290x versus the old 7970 Cards. World of Tanks, and other PC games that don't utilize CrossfireX still show a 100% load on GPU 2, and 0% load on GPU 1. ULPS is set to 0, and AMD CrossfireX Mode set to AFR. On the other hand, if you used 2 7970 card, it will push 99% loads on both 7970s, in CrossfireX with ULPS set to 0. It will push these loads in any game that does or doesn't support CrossfireX on the 7000 series cards. So whether you think it's a load of crap or not, is irrelevant.

You do realize that the new Beta MSI Afterburner (3.0.0 Beta 17) has a feature that disables it for you. It's convenient, easy, and idiot-proof. Settings --> "AMD compatibility properties" under General --> "Disable ULPS." Check the box, a window pops up asking if you want to restart your computer to let the changes take effect, and you're done.

No offense, but you wasted your time telling me how to turn off ULPS in the registry when I already knew that. I've done it a billion times with my previous AMD 7000 Series Cards in CrossfireX. I've done it from Beta Drivers 13.2 on up...

Did you know in certain games like Planetside 2, before the Oh Make Game Faster Update, if you didn't have ULPS set to 0, the second GPU would bug out, and lock in the frame on the 7970s. When you tabbed out in full screen, and tabbed back in, you'd see a frame display for 2 seconds going as far back as 10 seconds ago to 5 minutes ago. Then if you tried to utilize other programs like Sony Vegas Pro or Photoshop afterwards, the setup would BSOD upon load up of these applications? I forget the BSOD Code, but the message had something to do with the un-sync clock frequencies of the secondary GPU, blah blah blah... Take that into account, and both AMD Graphic Cards weren't OCed at all... The only way to fix this was to set ULPS to 0...

Have you seen the bug were you could tabbed out and back in, to any random PC Game, you could glitch your display. It would show frames overlapping one another from the top, and they would drop to the bottom of your screen with some of the 13.8 and 13.10 Beta Drivers... I bet you haven't... This has occurred with ULPS set to 0 on the 7000 series AMD cards....

Btw, only the 7000 series cards and below push 99% loads. The new R9s push 100% load... So what's so significant about that... I think it shows I've spent quite a lot of time dealing with both cards... If I am not mistaken, the 6990s would only push 98% loads. I'll have to check that out again if I ever get around to making my bitmining rig...
Posted on Reply
Add your own comment