Tuesday, December 1, 2015

Say hello to the TITAN Strangler + some benching data and thoughts on the Fury X.


Well that's how I dealt with having to cram 3 radiators onto an open air test bench. They are literally just sitting there All the pipes are twisted 1 time over and then held together by some velcro straps to make sure that none of the radiators falls of the bench. It looks pretty bad but it works just fine so I have 0 plans to change it.

Here's the parts list off the top of my head so some name may be incorrect:
i7 5960X
4x4GB Geil Super Luce 3400 16-18-18-36 1.35V DDR4
Rampage V Extreme
3 way Power Color Fury X
EVGA G2 1600W PSU
Dimastech Easy V3.0 Metallic grey
3TB Western Digital Black
480GB Crucial BX200(The first time I have an SSD in a desktop)
Thermalright TY143 fans
Phanteks PH-TC14PE (with the 2.5K RPM fans it handles IBT even at 1.25V core voltage)

My only regret right now is the RAM. The default XMP doesn't work with the RVE at all. I have managed to manually time and clock it to a variety of settings however due to this being my first time with DDR4 and X99 I spend more time trying to get all 4 sticks to boot up than actually running benchmarks(dual channel vs quad channel is a big deal).

My IKEA furniture was supposed to arrive today but due to a mess up on my part I didn't actually get any of it and so I'm continuing with benching from the kitchen counter. The monitor is an AOC G2460VQ6. As far as I know it's the cheapest Free Sync 24" monitor. The colors and viewing angles are pretty good and it starts up way faster than any of my ASUS monitors so I'm happy with it. It also came with a very complete accessory pack including a DP HDMI and VGA cable. However the DP cable turned out to be really dodgy once I started to push over 1200mhz core clocks and ended up running the rest of my benching with HDMI. I don't particularly need Free Sync on this monitor because it is my secondary to the 2560X1080 LG 29UM67 which I'm using because I hate the curve that the 3440x1440p Free Sync monitors come with.

From behind






When I go for my serious attempts I will be running all 3 cards without the shrouds and this fan will be helping with keeping the VRMs cool.

And this mess of wires and tubing is where the system gets the Strangler name from. I do have an idea how to clean this up however my budget for computer parts has reached an O.

!DONATE NOW TO RELIEVE THESE POOR POOR FURY XS OF THEIR SUFFERING!
(don't actually do that. 155 people donating 5$ would just lead to me buying another Fury X causing further suffering)

Now seriously the cards are running just fine like this however it is an awful mess. Now then lets get to the part where I talk overclocking.

Some overclocking of the Fury X
First thing first the Cooler on the Fury X is a freaking beast. The room had an ambient temperature of 20C according to the heating controller and these cards were running sub 40C even after I fed them +174mv (how to get more voltage in Trixx using a hex editor by /u/Meretrelle). I was running all 3 cards in Crossfire the whole time I was overclocking but I was overclocking them one card at a time.
All 3 cards were running +174mv on the core with +50% power limit and 100% fan speed. The first card is running PCI-e 3.0 X16 from the CPU, the second is running PCI-e 2.0 X4(this does not affect scores at all!) through the chipset and the third is running PCI-e 3.0 X8 from the CPU. This configuration has the lowest possible heat density and puts less strain on the CPU's system agent than running all 3 cards from the CPU's PCI-e.
The primary managed 1250mhz core 572mhz HBM it finished 3Dmark Fire Strike without going over 37C°. This card also ran without any artifacts until I started overclocking the other 2.
The secondary did 1200mhz core 555mhz HBM and ran at the same temps as the first.
The third card did 1210mhz core and 566mhz HBM and ran at the same temps as the other 2.

My best score for the session was 31 761 points because of a huge CPU bottleneck caused by  losing 2 channels of RAM and running only 4.67Ghz. To be fair I wasn't really focusing on getting a high score and was more interested in the maximum GPU clocks.


My other observations so far are:
At 4.67GHz the 5960X can't keep up with the FuryXs which led to absolutely terrible FPS scaling.

Running more than 1GPU from the CPU PCI-e lanes limits the RAM overclocking capabilities.

The RVE's retry button is god send allowing me to get RAM settings that I would otherwise abandon to boot.

Booting all 4 sticks of RAM is really hard. To get my best settings to start with all 4 stick I had to use 1.935V RAM voltage. I also confirmed that the RAM is indeed Samsung based.

To get the best FPS scaling the HBM clocks of all 3 cards need to be somewhat similar running 572/500/500 and 572/555/500 was a disaster but there was a nice jump when I clocked them all up to 572/555/566. I hope to find a way to get all 3 cards to run 600mhz HBM.

I need to test the new AMD Crimson drivers to see if they don't lower the CPU bottleneck that I have right now.

35.2K Fire Strike is definitely within reach of 3 Fury Xs however the CPU power needed is way higher than what a 3 way TITAN-X setup needs. (4.7GHz on T-X vs ~5Ghz on Fury X)

There is a possibility that the apparent stability of the system during testing was caused by the CPU bottleneck leading to the GPUs not being used 100%. Testing with Fire Strike Ultra will either confirm or refute this theory.

Running low temps on the Fury X seems to be the key to high clocks and getting good voltage scaling.

I might be able to rip up some single GPU scores if one of the cards will hit 1300mhz on air


My Opinions(may change as time passes)

IMO the Fury X is a budget/ambient overclocker's dream. However an overclocker's dream and should not be mistaken with a gamers dream. This is because card is incredibly fun to overclock. It is however not "easy" to overclock unlike the GTX 980Ti where the ASIC is everything and you either hit 1550mhz or you don't. The Fury X scales with everything. If you can run it colder. It clocks higher. If you give it more voltage. It clocks higher. Now there are many cards that do this. However the Fury X is the first card where the card already comes with pretty much everything you need.
Voltage Scaling
Temperature Scaling
Beastly VRM
Great Cooling
Basically Unlimited Software Voltage Control

The only things missing are low CPU overhead and high core clocks. However if you just look at percentages the average 980Ti does 25% over stock. My best Fury X did 19% and I didn't think I maxed it out yet(I didn't try more than 1250mhz). 25% or 1312mhz core is probably doable on a Fury X and if it is I'll do it. I approach GPU like games. It's no fun without any challenge. However too much challenge is also bad. The Fury X hits the happy medium. 

Well the Fury Xs blew me away and left me with a great big stupid smile on my face I think I got my moneys worth. Now I just need to get the RAM to behave and the CPU to not die in 3Dmark Physics.

BTW: None of this is "gaming" style overclocking. I consider an overclock good if it finishes the benchmark I really don't care that it might crash if I run it for an hour or 2 because I only need it to work for the 2ish minutes that 3Dmark needs to run. I will do a proper 24/7 overclocking guide for the Fury X some time soon. I will also be helping with some modded BIOSs for the Fiji cards with the goal to run higher HBM voltage and power limits along with more stability oriented power play tables.

Monday, November 9, 2015

R9 380 Nitro Volt mod guide

As you all know I wanted to make an Sapphire R9 380 Nitro(review of the card) volt mod guide. However me being me I royal messed up my R9 380 and had to leave for the UK before I fixed it. However a kind gentleman on Facebook has provided PCB pictures. They aren't exactly what I need however they are good enough to do the guide with. Lets get to it.

DISCLAIMER: Everything past this point will void your warranty! If the GPU stops working due to you doing any of the things described bellow I am at no fault what so ever.

So first lets breakdown that PCB into what's important.










































There isn't much to modding the card. Hook some sensing wires to the memory and core voltage VRMs and pull a GND from where ever you want to. I highlighted some good candidates in brown.

First up core voltage and core current limits. The current limit is simple to disable just cut the 2 traces highlighted in green. Now your card will think it's pulling 0W regardless of what the powerdraw actually is. So power related throttling is history. However it does make it easy to blow up the VRM by running Furmark since there is nothing to stop the card from pulling too much power. This should only be a risk when going over 1.45V core voltage. To cut the traces I suggest digging into them with a needle. This picture also shows how you could try modding core voltage however I recommend that you avoid soldering onto a pin or trace because it is really hard to not screw up. 

Instead solder a 22K(+/-5K) ohm variable resistor from the red point to ground. This will give you free control over core voltage. I recommend not going over 1.35V on air cooling for daily usage. For benching 1.45V is my ceiling. More than that seems to rapidly degrade 28nm GPUs.

The VRAM is an easy mod. All you do is hook a 220K(+/-50K) ohm variable resistor from the pin highlighted in orange to ground and you'll have VRAM voltage on manual control. There is no power limit for the VRAM so you don't have to worry about that. I don't rember the stock voltage of the VRAM on the 380 but don't go over 1.7V for daily usage. On sub zero 1.85-1.95V should be optimal.

Practical Tips
Use a fine chisel tip for all the soldering. A needle tip will make everything much harder because the tip of the pen won't actually melt anything.

If you have a temperature regulated iron set it to 240-250C for everything.

When you finish soldering one of the connections to an SMD component I recommend using plastidip to hold it in place. Hot glue is harder to apply without breaking a weak soldering joint and is very bulky which might prevent you from fitting the heatsink back on the card.


Please donate if you want to see more guides! I can't do mods on GPUs I don't have and unfortunately I'm not important enough to get free samples yet...
If just 200 of you were to donate 5$ I would be able to do almost any GPU you're interested in.

Saturday, November 7, 2015

Overclocked Power Draw Calculator

Back in 2012 when I first started this blog(there aren't any posts left from then because it was literally just me ranting about everything in existence) I figured out how to calculate overclocked power draw. Over the years I have tested the equation and tried to perfect it. I failed to perfect it. However I have found all it's flaws and so I feel safe in releasing a program that does the calculation for you. The usage should be self explanatory. However I recommend you read the README.txt to understand the flaws. Like everything else I make it's still written in Java. Java 7 might run it but you will most likely need Java 8.

Download Link

Pic of it in action:























Donate if you want to see the app get better! With enough funds I can make this take operating temperature and architecture into account and possibly extend the functionality to include some degradation rate estimates. I could also make it a whole system power draw calculator but I think that's unnecessary because there are plenty of those on the net already.

Wednesday, October 7, 2015

It's official I'm gonna build a 4 way Fury-X system.

 Prepare for reviews statistics guides and more importantly me going to town on the 4 way GPU rankings at HWbot.

This system will be fulling two of my dreams:
- Use a system with 4 GPUs
- Use a system with 2 PSUs

I like to give pet names to my permanent systems. The 3960X is called CPU Cannon. The FX 6350 is called MASSFX(I want to put an 8 core in it one day). I wonder what I'll call this one because I only give the names after I'm done with the build. Octopus seems like a candidate because of the CPU and all the water tubing for the Fury Xs.

Either way I'm not dead uni is going fine and this blog will be back in a several weeks(admittedly these are buidlzoid weeks so they share similarities with months).

In other news I now write gaming peripheral reviews for TechPowerUp.com so the monthly blog budget just got more substantial and I will not run into stupid problems like: doesn't have the right value potentiometer.

Saturday, September 19, 2015

Stream is delayed... and some more

Due to unforeseen issues I'll be streaming on Sunday. Sorry for the delay.

EDIT: More delay on the stream. I start it randomly when I have time some time soon. After the 24th I will go silent as far as blogging goes because I'll be in the UK with no access to any of my stuff. Hopefully I will figure out some way to transport all my stuff and store it.

Friday, September 11, 2015

R9 Fury Tri-X and Fury X Vmod Guide.

Wow am I sloooooow. I promised a Fury Vmod guide in August. It is now September. But hey better late than never. This guide will work for ALL reference PCB Furys. That means any Fury X and the Sapphire Fury Tri-X and the Powercolor Fury. If you have the ASUS STRIX use this guide from Xtreme Addict. Another way to get some extra performance out of the Fury is to try unlock extra cores on it.

VRM overview
The Fury has 4 VRMs. The HBM and Vcore are controlled by the IR 3567B the AUX and 0.95V voltage are controlled by other controllers which I can't find because none of part numbers for the ICs that could be voltage controllers return anything. That also means that I won't be covering how to mod the AUX and 0.95V voltage. If you're on air or water cooling this doesn't matter. For LN2 users you'll have to figure out how to get 1.05V on the 0.95V VRM output your selves because I don't have the resources to figure it out.


DISCLAIMER: Everything past this point will void your warranty! If the GPU stops working due to you doing any of the things described bellow I am at no fault what so ever.

Modding
 Before starting with any volt mods you need a way to measure you voltages. So hook up one wire to any of the GND points, one wire the Core voltage points and one wire to the HBM voltage points. This will allow you to use a multimeter to check the voltages because software does not pick up on the increase in voltage due to volt mods. Also there is no software voltage reading for the HBM or AUX voltages. For AUX it doesn't matter. The stock voltages are 1.2V core and 1.35V HBM.


Now for the actual volt modding. The 3567B is a very very smart voltage controller. It's so smart that if you try to hard mod the power limit you end up with this and run the risk of burning the VRM. Instead just max the power slider in you overclocking software(Sapphire Trixx 5.0.0 goes upto +50% and supports HBM overclocking). To get core voltage under control hook up a 100ohm variable resistor(potentiometer or trimmer) to any of the red points and to ground. To limit the maximum core voltage to 1.8V put a 7ohm resitor in series with the variable resistor. If you want a maximum voltage of 1.5V use a 14ohm resistor. For the HBM hook up a 220ohm variable resistor use a 50ohm resistor to limit the maximum voltage to 1.62V.



Practical tips
Use a fine chisel tip for all the soldering. A needle tip will make everything much harder because the tip of the pen won't actually melt anything.

If you have a temperature regulated iron set it to 240-250C for everything except when trying to solder onto the GND pins of the PCI-e connector. Those act like massive heatsinks so I suggest you raise your pen temperature to 300C.

When you finish soldering one of the connections to an SMD component I recommend using plastidip to hold it in place. Hot glue is harder to apply and very bulky which might lead to you not be able to fit the heatsink back on the card.

Route wires from the 3567B between the PCI-e power connectors. This will hold them in place without the need for more glue/plastidip.

Some results.

Due to budget constraints I do not have 100ohm nor 220ohm potentiometers. So I improvised a dipswitch voltage controller. However they seem to be much higher resistance than the values of the resistors I used to make them. My maximum core voltage is 1.3V and with it I can run 1165mhz core clock this is a 65mhz increase over the 1100mhz that I was getting on stock volts. My maximum HBM voltage is only 1.37V and it didn't improve the HBM overclocking capabilities of my card in the slightest I'm still stuck at 570mhz HBM. So I think HBM doesn't scale with voltage on air cooling or I'm just not giving it enough voltage. Keep in mind that SK Hynix specs HBM to run at 1.2V so over volting it much more than 1.35V might not be the best idea. For the core you can run 1.3V if you keep it sub 80C and if you keep the core sub 60C you can run it at 1.4V. If you set the fans on the Tri-X to 60% you should have no problem keeping the card sub 60C. For benchmarking you can run an extra 100-150mv on top of the safe 24/7 voltage for a given temperature.


Some tips for Tri-X owners
Sapphire used some weird thermal paste on the VRM heatsinks and core. For the core do whatever you usually do when you repaste a GPU but for the VRM heatsinks you can use 0.5mm thermal pads. They will contact the MOSFETs just fine and are cheaper than the 1mm and 1.5mm thermal pads.

Tip to lower or even eliminate coil whine.

Apply hot glue or plastidip on the marked sides of the inductors. If the first time you still get coilwhine you can apply more plastidip/hotglue.

I would like to thank techpowerup.com for allowing anyone to use their PCB pics. My attempts at PCB pictures are better for making desktop backgrounds than Vmod guides:







Thank you to Cooler Master for powering this blog.

Wednesday, September 9, 2015

Sapphire R9 Fury Tri-X OC Physical review.


It's hard to see but Sapphire put a small piece of plastic over the interposer to protect it. It isn't perfect since you can still break the interposer but much better than nothing.



Buildzoid's GPU reviews explained

Specs
3584 stream processors clocked at 1040mhz
4GB of HBM clocked at 500mhz on a 4096bit bus
2 8pin power connectors officially supporting up to 375W
Core clock throttling temperature: 85C°
1 HDMI port3 DisplayPort

Physical Specs
length: 320mm
width: 110mm
height: 2.5 slots

Cooling: 10/10
 When I first played a game on this card I knew I was gonna end up giving away points like they grow on trees. And why wouldn't I the cooling on this card can get the same temperatures as a custom water block. I currently don't have the equipment necessary to do proper noise testing but just ot give you an idea of the fan noise I'll tell you this. With the GPU at 0RPM my sound meter reads about 51.5dB sitting 8cm from the GPU. With the fans at 40% it reads 52 dB. At 55% it gets 59dB. At 75% it reads 66dB and at 100% it reads 73dB. I'd recommend running the card around 55-65% fan speed since that's when the noise temperature trade off is quite reasonable.

VRM: 9/10
Core
- 6 true phases provided by an IR 3567B
- 1 low side IR 6894 MOSFETs providing 105A per phase at 100C case temperature
- 1 high side IR 6811 MOSFET providing 44A per phase at 100C case temperature
- 200KHz up to 2MHz
VRAM
- 1 phase
- 1 low side IR 6894 MOSFETs providing 105A per phase at 100C case temperature
- 1 high side IR 6811 MOSFET providing 44A per phase at 100C case temperature
VAUX
- 1 phase
- 1 low side IR 6894 MOSFETs providing 105A per phase at 100C case temperature
- 1 high side IR 6811 MOSFET providing 44A per phase at 100C case temperature
The low side on this VRM is a beast. However like on the R9 290X the high side here is iffy. If you keep it cool you'll be fine but if you let the VRM get hot you can't let the card pull much more than 500W because you'll be risking burning out the high side. There are plenty of cases of people doing this on the R9 290X. The Fury uses much less power so it's not as much of a risk but keep it in mind if you're going heavy on the voltage and not using LN2 because the VRM can easily overheat. Also do note that in certain situations the card has coil whine. Not enough to be as annoying as say loud fans but enough to be noticeable so keep that in mind. I will try somethings with the card to get rid of the coil whine and will put that into my Fury volt modding post which is coming soon.

Extras:
+1 Dual BIOS
+1 0RPM fans in idle 
+1 VRAM cooling
+1 Backplate
+1 Silicon Interposer protector

Overclocking
The highest I've managed to push this card to was 1144/566mhz using Sapphire Trixx. These were not 100% stable clocks. My 100% stable clocks are 1100/550mhz and require a custom fan curve to keep the GPU sub 55C core temperature. The GPU does not clock well and instabilities are hard to catch. I had the card running perfectly OK at 1135mhz core clock for several hours and then it black screened out of no where when playing a relatively light game. This leads me to believe that the dynamic power management is holding the card back.

Conclusion: 24/20 Why is the score so high?
I love this card. It is by far the best GPU I have ever had. It is way way quieter and cooler than all my past GPUs. It's so good a card that I'm terrified of volt modding it(also because the 3567B has the weirdest voltage sensing circuit I've ever dealt with). Which I'm working on as I finish up this review. I don't really have much to say. I love this card it provides an excellent platform for volt modded overclocking.

The voltmod guide for this GPU is now up

Thank you to CoolerMaster for providing the V1000 PSU that was used for this review.

Tuesday, September 8, 2015

No more Twitch streams

Unfortunately twitch has been a massive pain for my last 2 live stream attempts. So I've switched to Youtube and I'm currently streaming here.

Monday, September 7, 2015

Something Quickly: How to calculate overclocked current and power draw for CPUs and GPUs.

This is what you use to calculate power draw:
(MHzOC/MHzstock)* (VOC2*(TDP/Vstock2))
Just plug in the numbers and you'll get the power draw of the CPU or GPU you're overclocking once it's overclocked. It does have a few issues it only works for specific temperatures and TDP doesn't always give accurate values it's best if you measure the initial power draw rather than relying on the TPD to be accurate. However if you do you power draw and stock voltage measurement when under load and your temperature when overclocked isn't different this will be accurate. A power draw value isn't all that useful when you're trying not to kill a VRM. To get current draw you just use this version of it:
(MHzOC/MHzstock)* (VOC*(TDP/Vstock2))
The power draw value is good for when you're designing a chiller or trying to choose coolers the current draw value is for not killing a VRM. The equation has a +/- 10% margin of error so keep that in mind when using it(AFAIK it does not work with Nvidia Maxwell GPUs at all). It can be much more accurate if I could do more research into it but that requires that I can get my hands on a bunch of CPUs to test it with and several liters of LN2 so I can keep very specific temperatures.

Just for the sake of doing a quick proof: 
 My 3960X measured 353W at 5Ghz using 1.56V running IBT. It has a stock voltage of 1.18V, TDP of 130W and stock clock of 3.3Ghz. Lets plug them in:

(5/3.3)*(1.562(130/1.182))= 344W
So it a little bit of but hey better than nothing.

Friday, September 4, 2015

R9 Fury Unlocking Simplified

As you probably already know it is possible to unlcok the R9 Fury from it's normal 3584 stream processor to 3776 processor, 3840 processor or even 4096 processors at which point it's basically a Fury X.

This guide is a simplification of this guide. When I was doing the process for the first time it took me close to an hour to get through it all. So this is my take on how to make the guide simpler.


First of all download this file  (dropbox mirror) and python 2(Python 3 does not work!). The filecontains all the programs and scripts that you need to unlock your Fury. You need Python to run one of the applications that makes flashing possible.
I hope that none of the software creators have a problem with me putting everything together and re-uploading it. If you do you can just leave a comment and I'll take it down again.

Unzip the folder to where ever you want. Then go to the folder CUinfo and run the program "cuinfo16".
And you'll get to see something like this:
If the last line says something like "X CUs are disabled by HW lock, override is possible at your own risk." You can try flash the card.

In order to flash the card first go into the ATiFlash folder and run the script called "BackupBIOS". This will create a file called: FuryBIOS.rom. Copy and paste this file(DO NOT CUT AND PASTE! THIS IS YOUR WORKING VANILLA BIOS IF THINGS GO SOUR YOU WILL NEED IT!) to the AtomTool folder. Then go back to ATiFlash rename the FuryBIOS.rom to FuryBIOS1.rom and then flip the BIOS switch on the top edge of your Fury. Now run the "BackupBIOS" script again. Once it's done flip your BIOS switch back to it's original position. Now go into the AtomTool folder and run the "makeroms" script. This will creat 3 files called:
3776spBIOS.rom
3840spBIOS.rom
4096spBIOS.rom

Copy these to the ATiFlash folder and run the script called "Flash XXXXSP BIOS" the XXXX stands for how many cores will be unlocked. First run the 3776 core script then restart the computer and check using GPU-z that you now have 3776 cores. If you do stress test the GPU by playing some games or running a stress test. If it's stable you can run the "Flash 3840SP BIOS" script. Then do the same that you did to check that the 3776 BIOS worked. If it does great and you can run the "Flash 4096SP BIOS" script. Then check that it worked the same way you check that the 3776SP and 3840SP BIOS worked.

If at any point the GPU is not stable just go into the ATiFlash folder and run the script that applies the previous BIOS that worked using the corresponding script. If the 4096SP BIOS didn't work flash the 3840SP BIO. If the 3840SP BIOS didn't work flash the 3776SP BIO. If the 3776SP BIOS didn't work run the "Flash Backup BIOS" script.

If the system fails to boot up after a BIOS flash flip the BIOS switch on your R9 Fury and boot up. Once windows is loaded flip the BIOS switch back to the broken BIOS and flash the last working BIOS the same way I explained in the previous paragraph.

If you run into any issues leave a comment down bellow. If you liked this guide please like and share this post potentially sign up for email updates about the blog.

The R9 Fury and Fury X volt modding guide is now up!

Thank you to Cooler Master for powering this blog with their amazing V series power supplies.

Tuesday, September 1, 2015

Gigabyte 78LMT-USB3 Review

Grey and black a color scheme almost as good as black and black. I like it. The board has two 4 pin fan headers one for the CPU and one for a chassis fan. There are six SATA 2.0 ports on the board and 1 IDE connector. Also one internal USB 3.0 port and two USB 2.0 ports.




















four USB2.0, one VGA, one DVI, one HDMI, and two USB3.0 along with basic audio.






















VRM
CPU VCore
- Richtek RT8868 4+1 phase controller
- 4 true phases
- 2 Renesas K0393 Low side MOSFETs rated for 40A at 25C 
- 2 Renesas K03B7 High side MOSFETs rated for 30A at 25C 
- 680nH inductors
- 38.4g Heatsink
- 270KHz to 330Khz 
- 5K rated capacitors however they are very low capacity
- LLC Auto/Regular/Extreme 
- OCP(around 90A) OVP  
CPU NB
- 1 true phase
- 1 Renesas K03B7 High side MOSFETs rated for 30A at 25C 
- 1 Renesas K03B7 Low side MOSFETs rated for 30A at 25C
- 270KHz to 330Khz
- OCP OVP 
RAM
- 1 true phases
- Same MOSFETs as CPU core - No heatsink
- Unknown minimum to unknown maximum KHz
Verdict: 5/10
40A at 25C is very very little. So to be safe it's best to assume a de-rating of 50% at 100C meaning that there is a total of 160A available on the low side. Luckily the RT8868 features OCP so this motherboard shuts down before it catches fire if you push it too far. When under load the capacitors and inductors get into the 110C area without a fan over them. The MOSFETs them selves are kept in the 75-85C area by the heatsink. I'd recommend putting some heatsinks on the inductors and capacitors and a fan over the entire VRM in order to extend life span. Even a basic 50x50mm fan at 2000RPM would help significantly.

BIOS
Voltages:
- Max VCC: 1.4375V
- VCC LLC Extreme(I+75mv/L+150mv) Regular(I+0/L-30mv) 
- Max VNB: 1.475V
- Max VDDR: 1.9V
CPU:
- 35x maximum CPU multi 
- 20x maximum CPUNB multi
- Full active core cuntrol with support 1 core per CU mode
DRAM:
- No XMP Support
- Missing tertiary sub timings
- No support for asymmetrical timings
- All timings are either automatic or manual 
- Up to 2400mhz support 
EXTRAS
- No Extras 
Verdict: 4/10
This BIOS has many flaws. First of all the CPU voltage setting shows incorrect values until you get the OCP to trip. So when you first boot the board and want to overclock the CPU you will see the option to run 1.7125 Vcore however if you actually set that you only get 1.43V when idling and 1.4V while running regular LLC. Extreme LLC is what it says on the box. It's EXTREME LLC. Giving a ridiculous 75mv Vboost at idle and an even more insane 150mv Vboost under load. I suggest you just don't use Extreme LLC because setting up to not trip the OCP the moment you go under load is really really hard and the low idle voltage will mean stability will always be very very iffy when using it. There are also no OC profiles. The postives of the BIOS are the 1 core per CU mode and the relatively easy navigation and the good responsiveness that some of the overly graphical BIOSs these days lack.


That's 214W on the CPU power line. I tried to push more than that but the terrible LLC options and low maximum voltage setting meant that my attempts always pushed well over 240W(was aiming for 220-230W) to the CPU and tripped the OCP. So if you were really brave and patient you cold maybe get a 9000 series FX to run on this board. But you most likely won't and I don't think it's worth the effort.

Testing Results:
The following hardware ran stable, using Intel Burn Test (IBT) for stress testing.
- G,skill ECO 2x2GB 1333 7-7-7-24 1.35V/max clock: 1866mhz 9-10-9-27-2T 1.65V
- Max CPU clock 8 core: 4444mhz at 1.4375V
- Max FSB clock: 217mhz
Verdict: 5/10
My FX 8320E is not a very good chip. And this boards weak VRM will not give you more 
The OCP on the VRM does it's job however it makes rebooting a pain because it doesn't shut the system down it just kills the CPU VRM which leaves the rest of the system still running. When that happens you need to cut AC power from the system because holding the power button doesn't seem to do anything.

Conclusion: 14/30 Points, 0.233pts/$
Between this board and the 970M Pro3 I think the key to choosing the right one is knowing what you want to do. This board is easy to use and very safe. The Pro3 on the other hand offers much more CPU voltage freedom and can definitely push higher clocks but the only safe guard it has is the temperature related throttling. If you just want a basic AM3+ MATX board to get 4.4-4.6Ghz depend on your CPU this board is enough. The VRM has enough cooling to not catch fire and the OCP will stop you before you kill the MOSFETs. You also have an integrated GPU that can save you if you dedicated doesn't want to work. This board also offers better RAM overclocking however that's not really worth talking about with a board that is limited to 1.4375 Vcore. Either way it's a good board and if you want to run an AMD 8 core in an MATX system but don't plan to overclock very much this board has you covered.

If you want to support what I do here please hammer the various share buttons down below. If you want to keep up with the various things I do follow me on Facebook. I will also be putting a video review up on the Youtube channel sometime soon. It is less for being informative and more for comedic value because I think there aren't enough motherboard jokes on the internet.

As always thank you to CoolerMaster for powering the blog.

Sunday, August 30, 2015

OC stream aftermath

I managed 6.8Ghz on the 8320E using 1.8V.
The whole system managed this and this.

Here's a pic of the system from the end of the stream:

This was my longest stream ever at a whopping 6 hours and 43 minutes. Unfortunately the sound failed twice during the stream. You can find the entire beast in its 2 3 hour long segments up on my Youtube channel.

Thank you to Cooler Master for supporting the blog.

Sunday, August 23, 2015

Live Stream on Monday

If you follow AHOC on Facebook you probably know that I've figured out what I did wrong with the R9 380. I've decided that I'm going to clean the card up and make it what I would call my ideal card. I'll be streaming this on Monday and hopefully I'll get the card to scale with voltage an I'll hopefully get it to hit 1.2Ghz like I originally wanted.

Thursday, August 20, 2015

The road to voltage Fury.

So I just made major step towards making the R9 Fury volt mod guide. I have revived the R9 290X Windforce which I killed and managed to get it's VRM under manual control.

Now most of you might be sitting there going DAFUQ How does volt modding an R9 290X have anything to do with volt modding the Fury?
It's simple. The Fury and R9 290X use the same exact voltage controller. If I manage to control the IR 3567B on the 290X it makes taking control of the IR 3567B on the Fury that much simpler.

The first thing I learned about the IR 3567B is that it's pretty smart. So smart, that the damn thing will not let the card run if it doesn't sense current on the VRM phases. With most GPU voltage controllers you cut the power sensing lines and they just ignore the fact that the current reading of 0.8A is wrong and continue running the VRM like nothing's changed. Not the IR 3567B, no the IR 3567B shuts the card down if it sense 0A on the phases. So after I tore all the SMD 300ohm ISEN resistors off the card in hopes that I would remove all power limits. I ended up resoldering every single one of the damn things. However I don't have SMD 300ohm resistors and so I improvised to end up with an R9 290X that looks more like a modern art piece than a GPU.



I also managed to under volt mod the card so it ended up running at 0.56V idle instead of the 0.968V that it should idle and boot at and so naturally it didn't work. I managed to fix that too and the card now boots and runs. At least on stock voltage I haven't tried overvolting it yet because the Windforce cooler no longer fits and I've run out of Seidons to ziptie on to it(it might sound like a terrible idea but the Seidon 120V rev2.0 can keep the 290X sub 70C even with 1.4V and at 55C when running stock volts and clocks).
Either way after this volt modding adventure modding the Fury will be a walk in the park.... I hope.

PS I'm very much aware that the AMD 125W CPU heatsink can't cool an R9 290X however I needed a cooler that could keep the GPU running long enough for me to get to the BIOS and it did that so you can keep the comments about me being an idiot to yourselves thank you very much.


Thank you to Cooler Master for powering this blog by giving me a V1000 PSU.