171 replies to this topic

[Wyzak]

how much should you OC the North Bridge. My NorthBridge is at 2200 MHz. HyperThreading at 2.6Ghz. I have gotten the base clock of the CPU up to 4.4GHz stable and the turbo core 4.8+. Also, the RAM is stuck at 1333, any upwards deviation is much disliked. Do I need to make the northbridge 2300MHz to get the CPU stable past 4.4GHz? temperature is not a factor. Brr.


PS system specs

GA-990FXUD3
FX8150
12GB 1600MHz rated Crucial RAM (3 stick 4GB)
Corsair H110 pump with dual radiator
Gigabyte GHz 7970 Windforce 4GB
Windows 7 Pro x64
OCZ 850W PSU

Edited by Wyzak, 11 October 2014 - 10:27 AM.

[Lordred]

The sweetspot on the FX chip is to get the Northbridge to 2400-2600
The sweetspot on the older Thubans was 2900-3100 Northbridge.

What ram are you using, 1333 is pretty slow.

[ninjitsu]

Wyzak, on 11 October 2014 - 10:20 AM, said:

how much should you OC the North Bridge. My NorthBridge is at 2200 MHz. HyperThreading at 2.6Ghz. I have gotten the base clock of the CPU up to 4.4GHz stable and the turbo core 4.8+. Also, the RAM is stuck at 1333, any upwards deviation is much disliked. Do I need to make the northbridge 2300MHz to get the CPU stable past 4.4GHz? temperature is not a factor. Brr.


PS system specs

GA-990FXUD3
FX8150
12GB 1600MHz rated Crucial RAM (3 stick 4GB)
Corsair H110 pump with dual radiator
Gigabyte GHz 7970 Windforce 4GB
Windows 7 Pro x64
OCZ 850W PSU

Running 3 sticks of ram is just hurting your performance. Forces you in to single channel.

[Thorqemada]

AMD wants you to use 2 or 4 sticks of RAM for Dual Channel bcs 1 or 3 sticks will force you into Single Channel - 2 similar sticks need to be put into the right Slots (RTFM).

Edited by Thorqemada, 11 October 2014 - 06:24 PM.

[Golrar]

Every OC guide I have seen recommends disabling the Turbo Core when doing an OC on any FX chip, even on Liquid. Just saying.

[Wyzak]

Ok I took 4GB out from slot 2 (1 and 3 are required to be filled for dual channel, but I had not previously noticed a benefit from dropping 4GB)

The ram which will not go past 1333 despite being rated 1600 is Kingston HyperX 1600C903X1K2/8GX 1.65v
Keep in mind I am using stock voltage and timings and just setting MHz to 1600 when it crashes. Has no 1600 SPD profile.
I turned off CPB, and raised Northbridge to 2.4GHz, and am posting from that. We'll see if it remains stable or if I can raise core speed.

Later tonight I hope to test MWO stability

[ninjitsu]

Wyzak, on 15 October 2014 - 01:37 PM, said:

Ok I took 4GB out from slot 2 (1 and 3 are required to be filled for dual channel, but I had not previously noticed a benefit from dropping 4GB)

The ram which will not go past 1333 despite being rated 1600 is Kingston HyperX 1600C903X1K2/8GX 1.65v
Keep in mind I am using stock voltage and timings and just setting MHz to 1600 when it crashes. Has no 1600 SPD profile.
I turned off CPB, and raised Northbridge to 2.4GHz, and am posting from that. We'll see if it remains stable or if I can raise core speed.

Later tonight I hope to test MWO stability

Do you know if you're on the most recent bios update? Sometimes updating bios helps.

[Golrar]

Just so you know, OCing is all about finding that sweet spot and really every individual CPU has the potential to be different. What works for some may not work for others. Always start small, test, and increase in small increments. You just have to see what works for you. There is no specific settings to get what you want. Some would say that is the fun of it.

[Thorqemada]

Do you have the latest Mothrboard Bios and do you have chosen the right "Profile" like "DDR1600" or "Profile01" or something in your Bios Settings?

Edited by Thorqemada, 25 October 2014 - 06:40 PM.

[Lordred]

I am going to have to perform new tests, the PostAA fix freed up a lot more performance then I was expecting.

[Goose]

Lordred, on 22 October 2014 - 06:01 PM, said:

I am going to have to perform new tests, the PostAA fix freed up a lot more performance then I was expecting.

Pardon?

[Lordred]

Goose, on 22 October 2014 - 08:52 PM, said:

Pardon?

The PostAA fix they applied on the Oct 21st patch has made the games I've played feel 'smoother'. I am going to do a few re-tests to see if I can back up the feeling with empirical data.

Even Alexander Garden has noted that he is seeing greater returns in performance from the fix then he though, and is also getting such reports.

So, my quest continues.

[Goose]

My bad …

So you say it's unloading your GPU by more then a point or two?

[Lordred]

Goose, on 23 October 2014 - 04:47 PM, said:

My bad …

So you say it's unloading your GPU by more then a point or two?

Other direction, I think it is unloading the CPU by a point or two, allowing it to result in more FPS.

Though it appears that using my sys_maxfps=70 is broken, I keep getting 50fps cap, working to resolve.

[Goose]

… Don't take this the wrong way, but are you shore you are working on the file in the right subdirectory? I'd just last week figured out how badly I was derping on my HTPC tests …

[Lordred]

Yes, it is quite odd, if I remove the command, my FPS become unlimited, however if I use the command, I get stuck on 50fps.

I may just do the test with adaptive V-sync at this rate.

[Morang]

Wyzak, on 15 October 2014 - 01:37 PM, said:

The ram which will not go past 1333 despite being rated 1600 is Kingston HyperX 1600C903X1K2/8GX 1.65v
Keep in mind I am using stock voltage and timings and just setting MHz to 1600 when it crashes. Has no 1600 SPD profile.

1600 MHz settings are in XMP profile for this memory. What stock timings do you use? Perhaps try to force voltage and timings manually too, with 1.65v and 9-9-9-27 timings?

Edited by Morang, 23 October 2014 - 11:33 PM.

[Flapdrol]

Lordred, on 23 October 2014 - 10:29 PM, said:

Yes, it is quite odd, if I remove the command, my FPS become unlimited, however if I use the command, I get stuck on 50fps.

I may just do the test with adaptive V-sync at this rate.

I had exactly the same problem with those fps limits, has something to do with the fps limiter in the mechlab, at least it started when they added that

Another strange thing is the fps limit changes when you run teamspeak or mumble, in the menu I'm at 30, if I start teamspeak I'm at 60.

[Goose]

I set mine to 70, but I get 60 in Teh 'Lab; When Teh Devs first set that limiter, I was getting 35 there.

If I chose an AA other then Post, I get stuck at 35 …



On a related note: Are any of y'all setting your limits with something other then user.cfg?

[Golrar]

I noticed the cap in the lab as well this week. And I also noticed a slight bump in max FPS in matches. My max is also set to 70. Noticed I would start matches at around 68 instead of solid at 60. Still haven't upgraded my GPU.