AMD FX OC'ers Club

[eidairaman1]

Amds can handle the volts

 

[suraswami]

Amds can handle the volts

but temps and power usage go thru the roof. yeah I will give it a try.

 

[Johan45]

They can as long as they have the cooling and yes shut the turbo off that was most likely just a spike and not really needed. You can get you stock vid using CPU-z if the machine is at stock settings just use the about tab and send to a text file. My 8350 had a stock vid of 1.375v so I'm not overly surprised at you saying 1.4v which might be a bit high.

 

[suraswami]

They can as long as they have the cooling and yes shut the turbo off that was most likely just a spike and not really needed. You can get you stock vid using CPU-z if the machine is at stock settings just use the about tab and send to a text file. My 8350 had a stock vid of 1.375v so I'm not overly surprised at you saying 1.4v which might be a bit high.

but then when turbo is disabled the vid is set to 1.325 for stock 4 ghz clock, why does the board bump it so low?

 

[Johan45]

These are the stock Pstates for my old 8350

P-State FID 0x1A - VID 0x0A - IDD 13 (21.00x - 1.425 V)
P-State FID 0x19 - VID 0x0B - IDD 13 (20.50x - 1.412 V)
P-State FID 0x18 - VID 0x0E - IDD 12 (20.00x - 1.375 V)
P-State FID 0x12 - VID 0x16 - IDD 10 (17.00x - 1.275 V)
P-State FID 0xC - VID 0x1F - IDD 8 (14.00x - 1.162 V)
P-State FID 0x5 - VID 0x29 - IDD 5 (10.50x - 1.037 V)
P-State FID 0x10C - VID 0x33 - IDD 4 (7.00x - 0.912 V)

At 20.00x it's 1.375v the ones above that are boosted states. That's just the way they're set up. By disabling the turbo you're forcing the board to use the lower Pstate. 1.325v is a decent starting point. That should be a good CPU for you to clock. Now just do what I described earlier and see how far it goes.

 

[suraswami]

These are the stock Pstates for my old 8350

P-State FID 0x1A - VID 0x0A - IDD 13 (21.00x - 1.425 V)
P-State FID 0x19 - VID 0x0B - IDD 13 (20.50x - 1.412 V)
P-State FID 0x18 - VID 0x0E - IDD 12 (20.00x - 1.375 V)
P-State FID 0x12 - VID 0x16 - IDD 10 (17.00x - 1.275 V)
P-State FID 0xC - VID 0x1F - IDD 8 (14.00x - 1.162 V)
P-State FID 0x5 - VID 0x29 - IDD 5 (10.50x - 1.037 V)
P-State FID 0x10C - VID 0x33 - IDD 4 (7.00x - 0.912 V)

At 20.00x it's 1.375v the ones above that are boosted states. That's just the way they're set up. By disabling the turbo you're forcing the board to use the lower Pstate. 1.325v is a decent starting point. That should be a good CPU for you to clock. Now just do what I described earlier and see how far it goes.

When I get home after work, I will post the results from CPUZ.

The thing that puzzles me is sleep and wake. Yes shut it down, power cycle, start the cpu at 4.4 with 1.35v, sleep disabled it will stay on for days, game, run few cycles of IBT no issues. So when after few sleep cycles it starts to behave erratically. I wish this stupid board has the feature that the ECS board has - 'apply OC after few secs when wake up from sleep' (does with EOC software tho).

 

[suraswami]

Couldn't wait till evening, bugged wife to send CPUZ results. Here is what it says for my CPU, Weird it only has 4 P-states!! Can others also please post their results?

Processor 1 ID = 0
Number of cores 8 (max 8)
Number of threads 8 (max 8)
Name AMD FX-8350
Codename Vishera
Specification AMD FX(tm)-8350 Eight-Core Processor
Package Socket AM3+ (942)
CPUID F.2.0
Extended CPUID 15.2
Core Stepping OR-C0
Technology 32 nm
TDP Limit 125 Watts
Core Speed 4118.1 MHz
Multiplier x Bus Speed 20.5 x 200.9 MHz
Rated Bus speed 2611.5 MHz
Stock frequency 4000 MHz
Instructions sets MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, XOP, FMA3, FMA4
L1 Data cache 8 x 16 KBytes, 4-way set associative, 64-byte line size
L1 Instruction cache 4 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 4 x 2048 KBytes, 16-way set associative, 64-byte line size
L3 cache 8 MBytes, 64-way set associative, 64-byte line size
FID/VID Control yes
Min FID 7.0x
# of P-States 4
P-State FID 0x1A - VID 0x0A - IDD 13 (21.00x - 1.425 V)
P-State FID 0x19 - VID 0x0C - IDD 13 (20.50x - 1.400 V)
P-State FID 0x18 - VID 0x12 - IDD 12 (20.00x - 1.325 V)
P-State FID 0xFFFFFFFF - VID 0xFFFFFFFF (-1.00x - -1.000 V)

 

[suraswami]

left VID as Auto and changed multi to 21. Played Bioshock Infinite for about 1.5hrs.

Hopefully sleep and wake up works with no black screens.

 

[Johan45]

You're not the first to have issues with sleep and wake. It happens an just about any board that I have seen so far. I think your best bet to get that solved is to either
1. Don't use it and power off when you're not using it
2. Set the PC's OC up with offset voltages and leave all the power saving features on. I think that's where the issue lies, you're using some of the featires but not all when the pc is set to sleep. Using offset isn't too difficult it's just different. If you know the voltage you need for a certain clock, let's just "say" it's 1.4v @ 4.5. You would set the offset for the CPU to +.075v, if you have added volts to the CPU_NB you'll want to set an offset for it as well. Now you will need to take into account any LLC setting you have implemented. If you have the LLC set to add a bit of voltage under load say .005v then your offset would need to be +.07v which under load gets another .005 for the total .075v. With a setting like this and all green stuff enabled that allows the PC to cycle down to about .9v and 1.4GHz when surfing but it will also ramp up to 4.5 and 1.4v under load. I'm not saying this will fix your issue with sleep sinc I don't use it and have no real hands on experience. But it will allow the PC to run more like it was intended and save you some power and heat to boot.

 

[suraswami]

You're not the first to have issues with sleep and wake. It happens an just about any board that I have seen so far. I think your best bet to get that solved is to either
1. Don't use it and power off when you're not using it
2. Set the PC's OC up with offset voltages and leave all the power saving features on. I think that's where the issue lies, you're using some of the featires but not all when the pc is set to sleep. Using offset isn't too difficult it's just different. If you know the voltage you need for a certain clock, let's just "say" it's 1.4v @ 4.5. You would set the offset for the CPU to +.075v, if you have added volts to the CPU_NB you'll want to set an offset for it as well. Now you will need to take into account any LLC setting you have implemented. If you have the LLC set to add a bit of voltage under load say .005v then your offset would need to be +.07v which under load gets another .005 for the total .075v. With a setting like this and all green stuff enabled that allows the PC to cycle down to about .9v and 1.4GHz when surfing but it will also ramp up to 4.5 and 1.4v under load. I'm not saying this will fix your issue with sleep sinc I don't use it and have no real hands on experience. But it will allow the PC to run more like it was intended and save you some power and heat to boot.

Yes I have all the power savings features on, for now the voltages are Auto and LLC is set to medium. I will watch it for couple of days and try messing with the offset voltages.

Wow!! FX OCing is not simple like I thought!!

 

[TheoneandonlyMrK]

That's why some like them , , there's just so much to mess with

 

[Johan45]

That's why some like them , , there's just so much to mess with

I have to say I still get a LOT more enjoyment out of mt FX when compared to my 4770K. The AMD are still like the old days, I swear anyone could OC a Hazwell, if they have a decent board it'll practically do it for you.

 

[suraswami]

You're not the first to have issues with sleep and wake. It happens an just about any board that I have seen so far. I think your best bet to get that solved is to either
1. Don't use it and power off when you're not using it
2. Set the PC's OC up with offset voltages and leave all the power saving features on. I think that's where the issue lies, you're using some of the featires but not all when the pc is set to sleep. Using offset isn't too difficult it's just different. If you know the voltage you need for a certain clock, let's just "say" it's 1.4v @ 4.5. You would set the offset for the CPU to +.075v, if you have added volts to the CPU_NB you'll want to set an offset for it as well. Now you will need to take into account any LLC setting you have implemented. If you have the LLC set to add a bit of voltage under load say .005v then your offset would need to be +.07v which under load gets another .005 for the total .075v. With a setting like this and all green stuff enabled that allows the PC to cycle down to about .9v and 1.4GHz when surfing but it will also ramp up to 4.5 and 1.4v under load. I'm not saying this will fix your issue with sleep sinc I don't use it and have no real hands on experience. But it will allow the PC to run more like it was intended and save you some power and heat to boot.

I read thru your post again after coming to work and have this question
Waking from Sleep makes sense because when waking up board puts all cores to maximum until stabilizes then windows takes over, so it needs all the juice it can get. So like you mentioned offset voltage helps.

But other problem is Black Screen while idling - the CPU idles at 1.4 ghz with .9v when using green features, this will happen irrespective of if the CPU is OCed or not. It is supposed to work at that settings but why does it go not responding after screen saver kicks in? When the screen saver kicks in does the CPU goes back up for a sec and calms down?

And oh, this annoyance I have seen in many generations of AMD CPUs when coupled with Gigabyte boards alone. Every other manufacturer does it right, ECS, MSI, Biostar and Asus.

Ok seems like the PC just saw a Black Screen of death. So I will have to try the voltage offset method.

Better dump Gigabyte!!

 

[Johan45]

I can't say that it's just Giga that does this, like I said my PC is either off or on but I know from other forums people were having the same issues with Asus boards. I would suggest if this black screening continues from wake up try it in safe mode. This should eliminate a software issue any way

 

[suraswami]

I can't say that it's just Giga that does this, like I said my PC is either off or on but I know from other forums people were having the same issues with Asus boards. I would suggest if this black screening continues from wake up try it in safe mode. This should eliminate a software issue any way

This doesn't happen when the CPU is left at default.

May be I will just give up and put the thing in Auto

 

[Norton]

This doesn't happen when the CPU is left at default.

May be I will just give up and put the thing in Auto

I have one chip that does this stuff (newer chip) and I can't overclock it and one that doesn't (older chip). The one that doesn't is perfectly happy running 4.4Ghz (1.36-1.38v) crunching full load 24/7 or just doing daily tasks. Both are in 1st gen Asus M5Axx Evo boards (M5A99X Evo and M5A97 Evo- identical vrm designs). The problem chip runs 100% fine at stock settings btw.

My solution- downclock the bejesus out of the problem chip- It now runs 3.2Ghz and 1.15v

It seems to me that the earlier 8350's overclock better than the newer ones.... before the binning into 9370's, 9590's, etc...

 

[suraswami]

I have one chip that does this stuff (newer chip) and I can't overclock it and one that doesn't (older chip). The one that doesn't is perfectly happy running 4.4Ghz (1.36-1.38v) crunching full load 24/7 or just doing daily tasks. Both are in 1st gen Asus M5Axx Evo boards (M5A99X Evo and M5A97 Evo- identical vrm designs). The problem chip runs 100% fine at stock settings btw.

My solution- downclock the bejesus out of the problem chip- It now runs 3.2Ghz and 1.15v

It seems to me that the earlier 8350's overclock better than the newer ones.... before the binning into 9370's, 9590's, etc...

Can you post CPUZ dump of P-states of ur FXs?

And if anybody here own 9xxx FX can you also post the P-states?

 

[Norton]

Can you post CPUZ dump of P-states of ur FXs?

And if anybody here own 9xxx FX can you also post the P-states?

These are the P states of the 8350 that runs @4.4Ghz (the other one is running Ubuntu so I will have to find the Win7 HDD for it)
# of P-States 7
P-State FID 0x1C - VID 0x0F - IDD 12 (22.00x - 1.362 V)
P-State FID 0x1A - VID 0x0A - IDD 13 (21.00x - 1.425 V)
P-State FID 0x19 - VID 0x0B - IDD 13 (20.50x - 1.412 V)
P-State FID 0x12 - VID 0x17 - IDD 10 (17.00x - 1.262 V)
P-State FID 0xC - VID 0x20 - IDD 8 (14.00x - 1.150 V)
P-State FID 0x5 - VID 0x2A - IDD 5 (10.50x - 1.025 V)
P-State FID 0x10C - VID 0x34 - IDD 4 (7.00x - 0.900 V)

 

[suraswami]

These are the P states of the 8350 that runs @4.4Ghz (the other one is running Ubuntu so I will have to find the Win7 HDD for it)
# of P-States 7
P-State FID 0x1C - VID 0x0F - IDD 12 (22.00x - 1.362 V)
P-State FID 0x1A - VID 0x0A - IDD 13 (21.00x - 1.425 V)
P-State FID 0x19 - VID 0x0B - IDD 13 (20.50x - 1.412 V)
P-State FID 0x12 - VID 0x17 - IDD 10 (17.00x - 1.262 V)
P-State FID 0xC - VID 0x20 - IDD 8 (14.00x - 1.150 V)
P-State FID 0x5 - VID 0x2A - IDD 5 (10.50x - 1.025 V)
P-State FID 0x10C - VID 0x34 - IDD 4 (7.00x - 0.900 V)

that's weird, P-State for default 20 x multi?

I am just going to leave it at 4 ghz with stock 1.325 V.

May be I am going to see if the chip can run at lower voltage.

 

[Norton]

that's weird, P-State for default 20 x multi?

I am just going to leave it at 4 ghz with stock 1.325 V.

May be I am going to see if the chip can run at lower voltage.

The chip will go to 4.6Ghz pretty easy but heat starts to be a problem since I'm only running a Xig Night Hawk w/2x 1500rpm fans and I crunch with it (4.4Ghz is pretty close to stock for temps at full load)

 

[Johan45]

Here ya go Swami this is my 9370
# of P-States 7
P-State FID 0x1F - VID 0x04 - IDD 18 (23.50x - 1.500 V)
P-State FID 0x1C - VID 0x04 - IDD 18 (22.00x - 1.500 V)
P-State FID 0x1A - VID 0x04 - IDD 18 (21.00x - 1.500 V)
P-State FID 0x16 - VID 0x0D - IDD 14 (19.00x - 1.387 V)
P-State FID 0x12 - VID 0x16 - IDD 12 (17.00x - 1.275 V)
P-State FID 0x8 - VID 0x26 - IDD 7 (12.00x - 1.075 V)
P-State FID 0x10C - VID 0x36 - IDD 4 (7.00x - 0.875 V)
But I can run it at 4.8 with 1.428v on my loop or 1.476v on the AIO

 

[suraswami]

I think its my crap board. I set it all default including turbo. Ran few runs of IBT to compare power usage, went to restart, board wouldn't post. I have to hold the power button to turn it off, turn off the PSU, then turn on and it posted. I thought ok may be one off weird thing, did the same run again, bam no post, have to do the same thing again. Before doing this I set the board to defaults using the bios menu.

When set turbo on, the cpu clock didn't stay at 4, instead kept jumping around, thought the HPC option was turned off, no it was not.

Right now I turned off turbo, will be out for dinner, I will clear the cmos using the jumper and then try it out again.

 

[Johan45]

That's a good idea Swami, that would be my first move is clearing the CMOS.

 

[suraswami]

Yeah Johan, you were right, the CPU needs 1.42v to run stable at 4.2Ghz. Not sure if its lazy chip or the board. The CPU will run at 4 Ghz with low volts - 1.325v and went to 1.28v and was happy. Was able to cut down few degrees and few watts.

But to get to 4.2 it needs a big jump to 1.42. When I turn off Turbo and set the multi to 21, set the voltage to 1.42 (anything other than normal voltage), the weird board will not step down the voltage when cpu is idle and drops to 1.4ghz. I have to leave the voltage at Normal setting and up the offset to get to 1.42 and idle works properly.

So decided to go different way. Left the voltages on auto, turned on Turbo. Set the default clock to 21 and turbo clock to 22. So I get 4.2Ghz all cores and boost clock is at 4.4Ghz. Feels bit quicker and has been stable over the weekend, with several gaming sessions, watching Netflix, sleep and wake cycles.

Seems to be working fine at this setting. When turbo kicks in, the voltage creeps up to 1.45v, temps seems to be in the mid 40C while gaming. During IBT the temps reach upto 52C.

Haven't touched NB frequency or HT clocking to up the ram speed.

I am going to leave this thing for now.

 

[Johan45]

@suraswami
The board won't downdrop voltage unless you set an offset voltage for the V_Core and leave all the power savings features on just turn off turbo or set it to the same clock as your OC. So since your CPU showed a base VID of 1.325v at 20x then to get 1.42v for the 22x I would just set a +.100v offset in bios. If you're happy with it the way it is that's cool but that's how you use offset so the CPU speed and volts will downclock when idle/surfing etc...