• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Student looking for Teacher(s)! FX-6300 / Sabertooth R2.0

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

IHaveNoEffort

Registered
Joined
Jul 10, 2015
Location
Okinawa
INTRO: Briefly about me.  I have finally built my first computer after about nine (yes, 9) years of dreaming.  The closest i ever got on my first build was some AMD 2.0GHz dual core processor that i bought around 2006.  Never made it much further.  At the moment i am looking to see what i can get out of this CPU / MOBO combo and to learn more about overclocking in general.  I can read everything on the internet but never really understand it until i apply it, and accomplish all the reading i just did to help interpret the results.  This is where i ask for some guidance in the whole process.

SETUP:

Case: NZXT Phantom 410
Motherboard: Asus Sabertooth 990FX R2.0
CPU: AMD FX-6300 (Arctic Silver 5 paste)
CPU Cooler: Noctua NH-D15
Memory: G.Skill Ares 2x4G 1866 (F3-1866C9D-8GAB)
GPU: Asus Strix GTX960 4Gb
PSU: Corsair CX 600M
HDD: Samsung Evo 840 250Gb
Optical: Asus DVD-RW
Cooling: 2 front 120mm, 1 rear 120mm, 2 top 140mm
OS: Windows 7 HP 64

<img src="http://www.overclockers.com/forums/attachment.php?attachmentid=166269&stc=1" attachmentid="166269" alt="" id="vbattach_166269" class="previewthumb">

Here are the results of the first run with Prime95. I know what you guys want to see. This is stock with HWMonitor and CPU-Z for CPU and memory.

Stock.PNG


I have already OC'd to 4.4 by upping the multiplier to 22 and running P95 for two hours with no hiccups on small FFTs.

22.5 Multiplier won't boot windows, But if i lower back to 22 and then reboot and use the ASUS TurboV, it'll run but P95 will crash quickly even with upping the voltage to 1.375 and LLC to High which brought the voltage up to 1.404.

Enough with what i've tried, where should i go from here at stock?
 

Attachments

  • Case.jpg
    Case.jpg
    302.4 KB · Views: 200
More Vcore.........and keep an eye on the temp. You're currently up against the voltage wall. Totally normal. You're going to need a big hike in Vcore to break down that wall. The side effect will be much higher temps. You're on the right track. :thup:
 
More Vcore.........and keep an eye on the temp. You're currently up against the voltage wall. Totally normal. You're going to need a big hike in Vcore to break down that wall. The side effect will be much higher temps. You're on the right track. :thup:


I was playing around with things today and if my memory serves me correct, i got the clock up to 4.7 with FSB at 210 and i was getting failures in P95 quick but i was at 1.45V with medium LLC. Should i go more? Temps seemed fine with around CPU at 55C and socket at 58C give or take. When i upped FSB to 215, i got Blue screen memory dump... Memory undervolted or NB undervolted ?
 
I was playing around with things today and if my memory serves me correct, i got the clock up to 4.7 with FSB at 210 and i was getting failures in P95 quick but i was at 1.45V with medium LLC. Should i go more? Temps seemed fine with around CPU at 55C and socket at 58C give or take. When i upped FSB to 215, i got Blue screen memory dump... Memory undervolted or NB undervolted ?
More likely ram speed too far out of spec. Relax the timings or put it on a divider. You need to slow the ram down a little. When you up the FSB, everything else goes up with it. Ram speed, NB frequency, HT frequency, Ect. All these need to be held in check.
 
In your bios, set the DRAM frequency down one click. You're at 1600 right now, so 1333.
 
I'll be here. :)

Dropped down the ram to 1333 and p95 failed. Upped voltage and the same thing happened. In the UEFI i set the OC from D.O.C.H.P to manual and set CPU ratio to 22 and FSB to 210 then upped it in TurboV and i got Blue screen. Dropped the FSB to 213 and Blue screen. So i upped the LLC and it hovered around 1.5V and then the whole computer shut down.

It seems like this is all i can get.

4.6stable.PNG

That was just a quick start and screen shot, so don't mind the times or temps.

Temps now are 46C CPU package and socket at 54C.
 
AI Suite on its own can induce instability. Highly recommended you OC from your bios and uninstall what you don't need. Like Mr.Scott said add some voltage to your CPU.... you can try to bump your CPU NB volts a bit to say 1.25v should be a nice starting place. At some point 4.5 - 4.7 there will be a big jump in VCORE needed to get your next step...... keep an eye on your temps 72*C socket and 62*C for your core kax, one step at a time.
 
I agree with the gents above and I'll add try setting the Cpu LLC to Ultra high, I find that is usually the best setting for the Sabertooth. The goal with the LLC is to have it maintain the voltage as close to the set voltage without it overshooting by too much and also keeping it from drooping. Raising the Cpu Nb voltage is also a good suggestion as per Bassnut.
 
AI Suite on its own can induce instability. Highly recommended you OC from your bios and uninstall what you don't need. Like Mr.Scott said add some voltage to your CPU.... you can try to bump your CPU NB volts a bit to say 1.25v should be a nice starting place. At some point 4.5 - 4.7 there will be a big jump in VCORE needed to get your next step...... keep an eye on your temps 72*C socket and 62*C for your core kax, one step at a time.

Indeed this is what I've heard. I find that HWinfo64 can read the asus temp sensors that ai suite outputs so there really is no need for it.

I agree with the gents above and I'll add try setting the Cpu LLC to Ultra high, I find that is usually the best setting for the Sabertooth. The goal with the LLC is to have it maintain the voltage as close to the set voltage without it overshooting by too much and also keeping it from drooping. Raising the Cpu Nb voltage is also a good suggestion as per Bassnut.

When i set the llc to extreme in ai suite it held at 1.5v for a few seconds before the computer shutdown. Ill have to play around with it all some more when i get a chance again since ai suite is an unfavorable variable.

I tried doing a blend p95 test over night and one core stopped less than 30 minutes after start and another stopped 3 hours later. Vcore 1.45, multi at 22 and FSB at 210. All other settings are set to auto.
 
Remember a thing...

...typing without pictures to describe and let US see what is going on does not help US to help YOU.

Okay there is a puzzle to which I do NOT have the answer at all. How in h*ll does the cpu speed jump UP nearly 200Mhz when the cpu is only capable of moving the multiplier UP and DOWN and NOT the FSB. If you had used HWINFO and monitored the Voltages and Temps instead of HWMonitor Free you would have likely seen the BUS aKa FSB aKa HT Ref Freq jump UP by five full MHz. This should NOT happen. Or not so by any information I have to judge things by, but we are seeing it more and more without answer. I am beginning to wonder if there is not some sort of issue with the motherboards. An issue where the bus defining oscilaltor is changing when it should NOT.

Onward. I captured your image. I took your image of HWMonitor and moved the listing of Vcore down to just above the CPU MHz shown and in red I said I doubt that the Vcore indicated can support the CPU MHz with stability. AND then I am going to place an Image of an FX-6300 that is about an average of five (5) FX-6300s a friend of mine owned and I tested. You can see the Vcore that I had to use with testing FX-6300 early models.

FX6300.jpeg

Now an image of average Vcore of earlier FX-6300 cpus I tested. FX-6300 Vcores I found necesary are on the right side of the image. My Vcore was higher than your HWMonitor shows.

attachment.php


I am trying to show WHAT I see so that there can be a consensus reached as to WHAT is so odd lately about the Asus big boy boards and jumping upward FSB that does not do so on my own CHV or CHV-Z motherboards. Like I said you can see the FSB jump by using HWINFO for monitoring and capture its' image spread out down the screen and see the BUS speed jump up.

I can find NOTHING indicating that the Sabertooth 990FX R2.0 should be doing such FSB hopping nor the CHV-Z boards. Certainly the Cpu MHz jumping by 200MHz could be bringing on INstability. In my mind it seems possible. Even if only for a split second of time to cause dropping of a core.

RGone...
 
I believe that FSB hopping is a byproduct of AiSuite. If you use Overdrive or just the bios, it doesn't do that.
 
...typing without pictures to describe and let US see what is going on does not help US to help YOU.

Okay there is a puzzle to which I do NOT have the answer at all. How in h*ll does the cpu speed jump UP nearly 200Mhz when the cpu is only capable of moving the multiplier UP and DOWN and NOT the FSB. If you had used HWINFO and monitored the Voltages and Temps instead of HWMonitor Free you would have likely seen the BUS aKa FSB aKa HT Ref Freq jump UP by five full MHz. This should NOT happen. Or not so by any information I have to judge things by, but we are seeing it more and more without answer. I am beginning to wonder if there is not some sort of issue with the motherboards. An issue where the bus defining oscilaltor is changing when it should NOT.

Onward. I captured your image. I took your image of HWMonitor and moved the listing of Vcore down to just above the CPU MHz shown and in red I said I doubt that the Vcore indicated can support the CPU MHz with stability. AND then I am going to place an Image of an FX-6300 that is about an average of five (5) FX-6300s a friend of mine owned and I tested. You can see the Vcore that I had to use with testing FX-6300 early models.

View attachment 166309

Now an image of average Vcore of earlier FX-6300 cpus I tested. FX-6300 Vcores I found necesary are on the right side of the image. My Vcore was higher than your HWMonitor shows.

attachment.php


I am trying to show WHAT I see so that there can be a consensus reached as to WHAT is so odd lately about the Asus big boy boards and jumping upward FSB that does not do so on my own CHV or CHV-Z motherboards. Like I said you can see the FSB jump by using HWINFO for monitoring and capture its' image spread out down the screen and see the BUS speed jump up.

I can find NOTHING indicating that the Sabertooth 990FX R2.0 should be doing such FSB hopping nor the CHV-Z boards. Certainly the Cpu MHz jumping by 200MHz could be bringing on INstability. In my mind it seems possible. Even if only for a split second of time to cause dropping of a core.

RGone...


I understand what you are saying and it is not helping anyone just describing this from memory. So here is what i got when i tried to go with 4.8GHz at 1.48Vcore with medium LLC. It ended with core 4 dropping immediatly and then getting blue screen before i could take a screenshot.

Here are the details:

4.8idletest.PNG 150711235329.jpg 150711235341.jpg

If this does not make any sense to you, let me know where you would like me to start. I could be completely misunderstanding what i've read in other posts where you have helped others. The 4.6Ghz that i am on now is what i got from your help with GhostP late last year.
 
I believe that FSB hopping is a byproduct of AiSuite. If you use Overdrive or just the bios, it doesn't do that.

I wonder about that AiSuite thing and it has never been installed on this CHV-Z I have and do all my overclocking of early FX-8350 from Bios so I have not experienced this jump up by 5 MHz of the Bus clock. You can see it is a 5 MHz jump UP if using HWINFO 64 which I seldom use and not in the forum or hardly at all. You can use math to know it is 5 MHz when seeing the CPU Speed jump up and it calculates to 5 MHz.

But how a jump UP of what seems exactly 5 MHz? And for how long at a low voltage? I cannot get my CHV-Z to do it so I cannot look and watch for how long it remains at the 5 MHz higher clock at what surely seems too little Vcore.

As far as I know it seems to do it 'lately' (2-3Mos) with the two big boys from Asus and maybe because more are not coming in with the lesser boards anymore, which is a good thing. I have wondered if it is something to do with the later run of FX processors, but can find nothing in the specs or literature about FX architecture that indicates the cpu itself can raise its' bus clock by just about dead on 5 MHz for any reason.

I have seen this behavior lately with CHV-Z and FX-9590. Seen such with CHV-Z and newer FX-8320. And now with FX-6300 on what I assume is Sabertooth FX990 R2.0. Those are the three I can remember off the top of my head but I do believe that there have been others within the last few months of 2015. Don't remember seeing this in 2014 at all. And I think we would have noticed it even in HWMonitor. Well maybe not if the + for Clocks was not broken out in HWMonitor.

Cool N Quiet and TurboCore and just about any of the other methods for 'saving' a cpu are able to drop the *multliplier* to drop cpu speed and Vcore to lower temps or load on the VRM circuit. But I can find nothing that seems to have the ability to UP the Bus Clock by a smooth 5 MHz. It is a freeken mystery to me. AND being a mystery, makes it hard to know for sure if it can cause the core drop outs in P95 or other scenarios of instability seen lately.

Been a few years since I tried any of my contacts I had with mobo companies, while I was with DFI but will have to see if any of my old contact infomation is still valid. All I know to do since I am not much interested in installing AiSuite since I will not use it because of how it has acted with AMD boards. Seems to do pretty fair with Intel rigs. It is a mystery to me for sure.

RGone...
 
I wonder about that AiSuite thing and it has never been installed on this CHV-Z I have and do all my overclocking of early FX-8350 from Bios so I have not experienced this jump up by 5 MHz of the Bus clock.

Your only half experienced running only bios overclocks. Perhaps you should try some software overclocking now and then?

Also, AISuite is just a GUI cover for running TurboV EVO, Digi+ power control, sensor recording (could be the problem) , and USB 3.0 Boost.

All very handy features to play with..... I prefer AMD OverDrive because it lets you handle many settings for the Ram and Turbo feature.
 
Back