Return of AMD FX: My OC'd AMD FX 8150 with OC'd 6990 Review - First Results Up!

Neuer_PC_2010_-_SSD_-_Aufkleber_-_small.jpg


Thanks for the sticker OCZ!


So with the money I made from selling my Sapphire 6970 (which I used to have in crossfire with my 6990) and my old OCZ revodrive 120gb I decided to buy OCZ's consumer flagship PCI-X SSD the Revodrive 3 X2 240 Gb.


Just how fast is this thing compared to other SATA 6 SSDs?





RESULTS:


ATTO Disk Benchmark:



OCZ Vertex 3 Max IOPS

ATTO-QD10-OCZ-Vertex-Max-IOPS-SSD.png


OCZ Revodrive 3 X2

atto1.png


Only up until 16Kb read/write , the Rovodrive 3 X2 actually trails its much cheaper brother the OCZ Vertex 3 Max IOPS, however as soon as it hits 32Kb read/write it leaves it in the dust!


Kind of like this Video:


http://www.youtube.com/watch?v=RXqSedWSu2k



PassMark Disk Mark:


disk.png



That's more like it!
 
The Global Foundries maybe made them wrong and there could be also a reason why they are slower and generating extensive heat, maybe they used bit different materials or something and the electrical properties of CPUs are greatly different. Maybe it's not the architecture itself.

But It's still not well understood why BD was out even, what they thought it will happen? It should be rather delayed or something, because now they did something that just supports the fact i5s are selling like hotcakes.

It has been delayed for almost a year by the time they released it. I doubt they could have really delayed any longer.
 
ROUND 5: WinRar Benchmark


So when bulldozer was officially released Winrar was one of the benchmarks where FX raced ahead of the 2600k. (Example1)(Example2)

But due to a newly discovered bug where Windows disables HT for intel processors, CORE Parking must be enabled to get the full potential out of compressing and decompressing with Winrar.

RESULTS:

winrarcomp.png



Bulldozer only barley beats a stock i7 870k with core parking turned off.
Before the bug was discovered AMD FX 8150 appeared to have beat even a 3960x.


source : http://www.xtremehardware.it/


If you have any questions feel free to ask!

Link to Blog:
http://AMDFX.blogspot.com
 
It was a bug that inhibited the performance of the Intels, once again Bulldozer getting completely raped :eek:
 
Keep up the review bro, let's see some res evil 5 and lost planet 2 benchies! Just make sure you use the fixed benchmarks on both of them if you do decide to do them.
 
AID64 benchmarks later today! stay tuned! Also, doing patch benchmark comparison!
 
4.8 Ghz stable is only attainable with a top end air cooler or liquid cooling (h80 and up). With midrange 4.6 Ghz should be attainable, but 4.5 Ghz is much more propbable. The difference between 2600/2700k overclockability and the FX 8150 is within error or delta, so there is no clear cut winner in this sense. This of course is without performance considerations, just sheer ghz overclock.

The delta of my chip is somewhere smack in the middle. I bet with my indigo-extreme and promlatech genesis i could find an FX 8150 cpu that hits 5 Ghz stable. I am speaking only with ALL 8 cores activated. I haven't tried tampering with deactivated cores.

I will post screen-shots of my temps before and after 20 minutes of Hyperpi 32M calculation soon!

If anyone has any questions feel free to ask!

This is a great thread! Also shows when OC this arch scales well and continues to scale well the faster it goes. All the OC tricks for BD I don't think is well know yet which I believe is leading some with less OCing range then possible with their rigs. For example I am limited to 4.8ghz unless I up my fsb, once I do that (of course with other stuff too) I can go to 5.3ghz. Not sure if particular to just the chip I got but for mine that is the case. People stick great water coolers on the cpu and then cause another problem. Those VM's surrounding the cpu also gets cooled by that CPU fan which was just taken away, so those VM's can start getting rather toasty and causing one's OC to be much less then it should be. There are bios settings which left in auto will not take you above 4.8 ghz as well. Other settings which have a huge impact on memory performance and thus impact on memory intensive tasks. I am thinking of starting another thread dealing with all the OCing tricks or techniques that I've found to work with BD which should work for all the BD line and hopefully help others get the most out of their setup. Plus others can share their successes and failures so we can all win.
 
This is a great thread! Also shows when OC this arch scales well and continues to scale well the faster it goes. All the OC tricks for BD I don't think is well know yet which I believe is leading some with less OCing range then possible with their rigs. For example I am limited to 4.8ghz unless I up my fsb, once I do that (of course with other stuff too) I can go to 5.3ghz. Not sure if particular to just the chip I got but for mine that is the case. People stick great water coolers on the cpu and then cause another problem. Those VM's surrounding the cpu also gets cooled by that CPU fan which was just taken away, so those VM's can start getting rather toasty and causing one's OC to be much less then it should be. There are bios settings which left in auto will not take you above 4.8 ghz as well. Other settings which have a huge impact on memory performance and thus impact on memory intensive tasks. I am thinking of starting another thread dealing with all the OCing tricks or techniques that I've found to work with BD which should work for all the BD line and hopefully help others get the most out of their setup. Plus others can share their successes and failures so we can all win.

Do it.

I was able to get my 8150 4.62ghz x 210mhz stable with 1.51 Vcore.
Temps max in high 40's in Overdrive Stability test.

But I can't get it to post @ 4.7. I have to clear Cmos every time.
 
My chip wont go past 1.47V without freezing. Im at 4.81 Ghz with 1.42 V core atm.
 
My chip wont go past 1.47V without freezing. Im at 4.81 Ghz with 1.42 V core atm.

I looked for what motherboard you are using and couldn't find it (what are you using?). Anyways if you havn't, up your fsb and decrease your cpu multiplier, make sure ram speed is OK. I hit a multiplier wall right around 4.8ghz with a 200mhz fsb. This multiplier wall (don't quit remember if it was 23x stays constant) fsb OCing is then needed plus more stability I gained if I was much lower then let say 23x multiplier.

If your motherboard has CPU Power Phase control settings like ASUS, use the extreme setting (ASUS has an optimize setting which is ment for low power and not high OCing and good luck if you can OC over 4ghz with it)

Another setting key, with ASUS is CPU Voltage Fequency if left in auto it will limit OC to like 4.9ghz, manually adjusting the VRM fixed frequency to greater then 450 allows a higher OC.

Turn off all Spread Spectrum settings except maybe PCIx.

There are also current limit settings, voltage droop settings which I can go into but if you don't have an ASUS board it might not make any sense.

Edit: Unfortunately, everything I told you will increase heat load on your computer and VRMs, so cooling not only the cpu is the key.
 
Last edited:
yes I do use asus crosshair V. Thanks for the tips, but i have literally tried almost everything except for maybe manually setting voltage frequency. I found extreme settings for cpu voltage pushes the voltage too high and my comp wont handle it. Past 1.47 v my temps skyrocket as well. I honestly think my chip cant properly oc past 1.47v without over heating or crashing.

AIDA64 benchmarks up!! Patch vs. no Patch comparison!!
 
yes I do use asus crosshair V. Thanks for the tips, but i have literally tried almost everything except for maybe manually setting voltage frequency. I found extreme settings for cpu voltage pushes the voltage too high and my comp wont handle it. Past 1.47 v my temps skyrocket as well. I honestly think my chip cant properly oc past 1.47v without over heating or crashing.

AIDA64 benchmarks up!! Patch vs. no Patch comparison!!

Cool! I can compare bios settings then, I have an ASUS Sabertooth, give you what I have and any findings which may help. Yes when you start getting towards 5ghz heat does become an issue. Monitor your VRM temps using ASUS monitor, when they get above 85c things can go astray. I think I use the Very high setting for CPU voltage droop and not the Extreme since it jumps the voltage up too high when OCing with the Very high setting the CPU voltage goes up very little when at 100% load like .02v. But the phase one is one of the most important setting since it determins how many VRMs are used, four settings (ASUS Optimize, Standard, Extreme, Manual) I use the Extreme with T-Probe sensing, havn't tried the current sensing parameter with that one. The CPU voltage frequency if left in Auto limits me to around 4.9ghz, I run it manually around 470-480.
 
thanks alot for the tips man! im going to utilize this and see what happens! A higher OC and windows 7 patch is a nice boost in performance ^^.
 
Awesome stuff. Thanks for posting these. I keep checking back for more and some of the results are surprising.
 
Wonderful, never thought an FX could be made quite competitive,
Now if they would just release a Piledriver CPU (or APU) that is more power efficient, I'll be jumping onboard.
 
more benchmarks starting tomorrow! Revisiting DIRT 3 by request with FX @ 4 Ghz
 
DIRT 3 revisited ..AGAIN! FX @ 4.0 Ghz. Tomorrow Fritz Chess benchmark, then after Cinebench 10, then SpecviewPerf 11
 
Before you get to Specviewperf 11 I wanted to point something out.
Specviewperf really only runs well if you have a professional video card, in other words Quadro or Firepro.
Take a look at this older review of a Quadro FX 4800 vs a Geforce GTX 280.
http://www.tomshardware.com/reviews/quadro-fx-4800,2258-10.html
The Quadro was 10X faster in the Solidworks portion of the test. This is mainly due to the difference in drivers between the Quadro and Geforce.
Anyway, my point is that since I think you are running a gaming card, then your scores will be low and will not tell you much of anything of value. Specview is so dependent on the gpu that I do not see it as a good cpu test at all.
 
Back
Top