Table of Contents
Previously we ran the full review of AMD’s Lynx desktop chip, the A8-3850, which is their Llano architecture for desktops. In that review, regrettably, I was not able to explore overclocking this platform. Thankfully, after a bit more time, that has been remedied.
Overclocking Llano isn’t all sunshine and rainbows, but it’s not too difficult. Very few voltages need adjusting, but it isn’t without its quirks. This is no unlocked multiplier, insanely easy ‘raise multi, raise voltage, repeat ad nauseam until your cooling gives out’ adventure. Rather, it’s a more delicate process that involves a bit of tinkering. In other words – actual overclocking! That’s not to say I don’t enjoy Black Edition or (Intel) K-series CPUs. It’s just different, and tweaking is always fun for an overclocker.
What Happens When You Overclock Llano?
First, let’s start by discussing what you’re doing when you overlcock Llano. To overclock this CPU, you have to use the base clock. There is no other choice. Neither the CPU nor the GPU have unlocked multipliers. Thus, even if your BIOS allows higher multipliers (in this case, it can go up to 47x; the setting will dutifully report in software via Windows too), you can’t overclock that way.
Same goes for the GPU. If your BIOS allows you to manually raise the GPU frequency, ignore it. You can’t do that either.
Which brings us back to the base clock. Unfortunately, as with Intel’s Sandy Bridge, overclocking the base clock can lead to issues. Because the traditional northbridge functions lie on the APU, overclocking the base clock also overclocks everything else. Everything – including storage. Thus, if you boot at the wrong frequency, it might not boot at all, giving you a ‘cannot find boot device’ error because the storage bus is overclocked too far.
Thankfully, that’s not the end of the road. Some boards do it automatically and some do it manually, but most boards (I say most because I have no evidence to say ALL) will give you a storage, et al bus divider. The Gigabyte A75M-UD2H (also featured in the initial A8-3850 review) does it automatically. Regretfully, there isn’t a manual option. Said divider kicks in at 133 MHz bus clock. For overclocking, it would be preferable to have a storage bus lock option.
What about the IGP?
As mentioned before, the IGP is locked down at 6x (stock = 100 MHz base clock x6 = 600 MHz IGP). When you raise the base clock, it raises the IGP frequency x6 (unless you drop that multiplier, but we’re not going there with this article). So, even if you get stuck at the spot where the storage bus divider kicks down, that’s 133 MHz x 6, for a 798 MHz IGP frequency. I can tell you now, most A8-3850s should run that speed, which is fully a third higher than the stock IGP frequency. Told you this was a strong APU, didn’t we?
Memory – What’s Best?
What have we not talked about yet? Memory! System memory and IGP memory on the Llano platform are one in the same. By default, the system dedicates 512 MB of system memory to the IGP. You can manually change that if you’d like, I believe to a maximum 1024 MB.
Sharing memory like this is a mixed bag on a budget platform. Memory timings are very important. AMD told all reviewers not to exchange high frequency for loose timings. When looking for memory for your Llano-based desktop, shoot for the tightest latencies at the highest frequency you can afford. CAS latency 8 is the highest I’d recommend. In the initial review, we used DDR3-1866 with timings of 8-9-8-24. Those timings would be decent for DDR3-1600 too, but a bit tighter would be preferable.
We didn’t explore tight vs. loose timings and we’ll take AMD’s word for that, but we did look at different frequencies at similar timings. The difference in graphics performance was surprising. You’ll see those results below though. First, some items to note when overclocking Llano.
Tips to Make Your Life Easier
So, tip #1 is regarding the storage bus. If you try to overclock your Lynx CPU and it won’t even get five measly bclk past stock 100, try 133 to force your board past its divider breaking point.
Tip #2 and #3 don’t have lengthy explanations. They just, capital W, Work. Tip #2 is that you must use a digital output from your APU. I don’t know why, so don’t ask…it just is.
Lastly, #3 is that you must run your HDD (or SSD in this case) in IDE mode. Running AHCI (and presumably RAID, though I didn’t try that) will give you the ‘no boot disk’ error regardless of base clock, even after the divider changes. Again, no idea why, it just is.
Once you get those three things down, the sky’s the limit. Well, your APU’s the limit. Unless…
Unless you have one of the most annoying BIOS glitches you can think of. You see, evidently (and this is a guess as to its mechanism) the storage bus divider fails to function when you restart the computer. If you’re running, say, 140 MHz base clock and you restart, the system will lose your boot drive. Thankfully there is a solution, however annoying.
In this case, the way to defeat the beast is to restart into BIOS and set the base clock back to 100 MHz. You can leave everything else the same, voltages and all. Boot up into Windows. Then, without logging on even, restart the computer. If it was only when changing something (like pushing the overclock), that would be one thing; but this happens every time you restart and/or shut down the system.
One would assume Gigabyte will address this with a BIOS update, but be forewarned, this may be an issue for anyone that doesn’t leave their system on 24/7 and is definitely an annoyance for anyone testing out maximum overclocks!
Raising the Bar
The results from initial testing of this platform were nothing short of impressive for an IGP. The CPU benchmarks were somewhat unremarkable, but for a Stars core, they did well; especially when you look at the native capability for DDR3-1866 memory.
When pushing this APU and board, first up was the CPU. I raised Vcore 0.1 V from the stock 1.4 V to give 1.5 Vore (idle, vDroop took it down to ~1.475 loaded), which managed a respectable 800 MHz overclock, to 3718 MHz from the stock 2900 MHz. The 26x CPU multiplier was used to bring bclk around the 130-140 MHz mark and the memory multiplier was dropped to keep its speed as close to DDR3-1866 as possible.
Unfortunately the IGP didn’t want to go quite that far. At 143 MHz base clock, the IGP was running 858 MHz, which was just a little too high. For the IGP to pass, the base clock had to be dropped two MHz, bringing the final CPU overclock to 3666 MHz and IGP speed to 846 MHz.
If you didn’t yet, look again at the memory tab in CPUz in the final overclock. That’s right. DDR3-2256, with timings of 8-10-8-24! Simply amazing memory clocking on an AMD chip. This was easier than even Thuban memory overclocking. Whatever they did with the memory controller, let’s hope something with this kind of strength makes it into Bulldozer.
For the curious, here are BIOS shots of the settings used for that overclock. The IGP was left alone, with everything on auto (meaning the default 6x multiplier and default 512 MB memory allocation).
We end up with a solid overclock all around. The CPU finished at 3666 MHz with reasonable temperatures on older air cooling (Thermaltake Big Typhoon), a GPU speed of 846 MHz – more than 30% over stock – and memory clocking in at stout DDR3-2256.
One thing I left out of the initial review was power consumption. At idle, this platform just sips power. The tiniest amount keeps one of these systems going. Loaded, it’s certainly less than I’m used to benching Thuban and Sandy Bridge setups. Anyway, here are the numbers. The CPU was loaded with Prime 95 Small FFTs and the GPU was loaded with Furmark.
|Power State||Power Consumption|
|Stock Idle||33 W|
|Stock Loaded (CPU Only)||131 W|
|Stock Loaded ( CPU & GPU)||157 W|
|Overclocked Idle||35 W|
|Overclocked Loaded (CPU Only)||212 W|
|Overclocked Loaded (CPU & GPU)||263 W|
At stock it doesn’t take much power at all. Overclocked is a different story. Gaining over 100 W with the CPU and GPU overclocked is quite a bit. You’ve got to give something to get something though and overall 263 W isn’t too bad. Comparing that to a higher-end system, an Intel 2600K plus GTX 580 pulls 496 W under load at stock.
When we first looked at the A8-3850, I said the CPU side would perform close to a similarly-clocked Phenom II. The Phenom II x4 965 BE clocks in at 3.4 GHz, so we’ll put that to the test. The Llano APU should be just a smidge better than the 965 BE. The system tested was the same as used previously.
|Disk Drive||Patriot Inferno 100G|
|OS||Windows 7 Professional x64|
For overclocked 2D runs, the APU was clocked at 141 MHz base clock with a 26x multi, for 3666 MHz on the CPU. Memory was using the 6.66x multiplier, clocking in at DDR3-1878 with 8-9-8-24 timings.
Again starting with AMD’s less than favorite benchmark, let’s see how the single core integer performance stacks up overclocked.
We were given healthy increases in both SuperPi benchmarks for sure. Both 1M and 32M gained just under 20%. Not quite a clock percentage for time percentage decrease (the overclock here is 26.4%), but pretty close. If we had clocked the RAM up for these, I’ve no doubt they would be closer to overclock-to-time parity.
WPrime is always better for the AMD camp. They focus a lot of energy on multi-core performance and it pays. The overclocked Llano performance is on par with what you’d expect from a 965 BE clocked up a couple hundred MHz.
Cinebench results are impressive for sure. Both of these benchmarks reached overclock-to-score parity, which is a good feat. Being the more real-world of our 2D testing, this bodes well for everyday use. You know, if you plan on rendering or encoding with a Llano-based build.
Moving on to 3D, there are two overclocks displayed in these and the game test graphs. The base clock was the same as above, at 141 MHz, which means the IGP was running at 846 MHz using the default 6x multiplier. The two different results were the result of changing the RAM multiplier. Results in the graphs designated “A8-3850 – OC” were using the RAM as above in the 2D benchmarking, at DDR3-1878 / 8-9-8-24. To test out just how much strong RAM would help benchmarking, I also threw in a stronger RAM kit, the G.Skill DDR3-2400 kit we looked at over a year ago now. For the results designated “A8-3850 – OC-RAM”, the RAM was run at DDR3-2256 with timings of 8-10-8-24.
Starting us off, we’ll look at all four 3DMarks run in one fell swoop.
This APU is very impressive. The IGP truly does have lower-end discrete performance and when you overclock, it just gets better. Score improvements up to 34% are nothing to sneeze at. What really stunned me was how much of a difference the RAM made when you overclock.
Moving on to Heaven, we see big gains in both DirectX 11 and DirectX 9 versions. Nothing dissappointing here.
Now we’ll move on to the real-world APU performance – how can this platform really perform as an HTPC / home-made console gaming system.
Starting off, we’ll have a look at three iterations of Stalker: Call of Pripyat. The bench was run using the DirectX 11, Enhanced Full Dynamic Lighting setting at three different detail settings.
There are definitely strong gains overclocking this platform, especially when you use strong RAM. That’s the real takeaway from a lot of these results – RAM makes a big difference. If you want to use the high detail setting, you’ll want to consider sticking with 720P and enjoying the increased framerates. Both medium and low settings have playable framerates when overclocked.
Aliens vs. Predator was a tough benchmark. Even overclocked, it struggled here because we were seeing how it performed with AA and tessellation on. The low detail setting turned all of that off and the results reflect the change.
There are definite gains, but not enough to make AvP really playable at 1080P. 720P started off playable and would only get better overclocked.
Two more game benches to go – HAWX 2 and Dirt 2.
There are obvious gains throughout in both of these benches. I mentioned in the original piece that Dirt 2 looked playable even at mid-20’s frames per second. The gains from overclocking made it even more so. HAWX 2 started playable and only got better, getting close to matching the stock 720P numbers.
Final Thoughts & Conclusion
Overclocking takes an already strong integrated graphics platform and makes it even better. The gains are very real and palpable.
Llano clocking was certainly a very quirky experience on this A75M-UD2H. With any luck they’ll fix those quirks with a BIOS update. It’s still a very, very young platform so we won’t hold it against them.
The A8-3850 / UD2H combination initially garnered an Overclockers Approved and shows now that it definitely deserves it, not just for its strength as a platform but for its overclocking ability too. It clocked farther and gained more benchmark and gaming performance than expected, which is always a good thing. Thus, if there was any doubt, overclocking Llano is also Overclockers Approved!
– Jeremy Vaughan (hokiealumnus)