Project Reality Forums

First of all to get 3.5ghz or higher on that processor you need to know about voltage tweaking.
Your processor has a locked multiplier so you simply cant raise the multiplier and overclock it,thus you have to overclocking using raising the fsb,I would suggest you to start with minor increase at first because overclocking is something that you will learn step by step,first target the 3.4ghz mark.
To achieve it fist turn off all the power saving features in BIOS,disable cpu spread spectrun and AMD cool & quiet. Disable offset overclocking and do the oc part manually. Raise the FSB by a notch (the default is 200,you make it 220 mark) in the motherboard bios,once you increase FSB your ram frequency will also increase so you can adjust the ram frequency using ram multiplier.Don't change anything else,save the settings and reboot,if you can enter windows then run prime 95 for around two hour and see you don't get any BSOD (blue screen of death).
If you get a BSOD you need to raise the cpu vcore by a notch from the stock voltage and set the LLC (Load line calibration) to High.
Now again boot back and see if you get any BSOD,if it survives two hours of stress tesing (prime95) you are fine with overclock.
Once you achieve a stable overclock you need to fine tune it with North Bridge overclockig and ram overclocking.
Stduy about it over net,overclocking is something you'd not learn in a day,its a vast thing,so start with small overclock and experiment with the cpu frequency further once you get used to overclocking.
Hope this helps you,if you face any sort of problem do reply we are here to help you,good luck.

Best solution
Z1NONLY OVERCLOCKING MASTER March 16, 2012 6:06:11 PM
Here's a cut and paste from my post on another 1045t thread the names tha gigabyte uses may differ slightly from your Asus BIOS:

I have my 1045t OC'd to 3.4 Ghz with all 6 cores running. It could go higher but, I'm limited by heat because I can't fit a bigger cooler in my case.

I recommend getting some free software first. CPU-Z and HWmonitor, and prime95.

CPU-Z will show you frequencies, voltages and ram timings.

HWmonitor will show you temps. *Be warned* HWmonitor was showing my core temps 10 degrees lower than they actually were. The temp labeled "TMPIN2" was actually tracking perfectly with the core temps shown in AMD Overdive. So look for the highest temperature other than your video card. (many video cards can safely run at hotter temps than your CPU.) The hottest one on my Gigabyte 990 fxa ud3 (other than the video card) is the core temp. Try to keep it below 55C under full load.

Prime95 is the program that will stress test your computer to see if it can remain stable and cool under load. 2hrs of the blend test with no errors and no overheating is a general rule of thumb for a stable OC.

Now for the fun stuff.

Go into your BIOS and lower the multiples for your CPU and your Ram by a few steps. (The 1045t won't let you increase the multiplier above stock)
Then disable turbo (aka "core performance boost" )
Then find your CPU Host clock control and set it to "manual"
Then You should be able to change the "CPU Frequency" (I'll call it FSB) (This is before the multiplier, so it will be low. Mine started at 200)
Now increase that variable by a bit.

I recommend balancing your FSB and your "memory clock" (RAM) multiplier to a point where your ram is back down to stock speeds after you bump the FSB. So raise your FSB to something like 250 then adjust your RAM multiplier down so that your RAM us running at or near stock speeds.

Now move on to your CPU clock ratio. With the faster FSB, you will be able to run your CPU at higher frequencies with a lower-than-stock multiplier. I eventually took mine all the way back up to 13.5 with a final frequency of 3.4 Ghz.

I would recommend starting with a lower multiple that gets you just a couple hundred Mhz boost over stock at first. Then test for stability and heat. Run prime 95 for at least 30 minutes if you want to see your hottest temps. The blend doesn't get things hot until about the third bank of tests.

If things look good, go back into the BIOS and bump the multiplier some more and re-test.

My MB got rather ambitious with the voltages when I left it in auto, so use CPU-Z to keep an eye on core voltages. Many recommend just staying under 1.45 volts. I recommend not going any higher than you need to for a given clock speed. This will help keep heat down. I ended up using a negative offset "CPU voltage control" of -0.075 volts. This brought my core voltages down to about 1.344v at full load.

*note* I'm scraping the floor on voltage with my particular chip/speed. One notch lower and I get BSOD. You may be able to go a little lower or you may need a little more voltage for your chip and clock speed.

Now just test and adjust and repeat.

Generally speaking:

BSOD means you need more voltage, and/or less speed.

Overheating means you need less voltage and/or less speed. (or a better cooler for your CPU.)

If you get to the point where your temps are good and your computer is sable, and you still want to go faster (than ~3.4Ghz), you can go back and bump up the FSB. But remember to adjust your RAM multiplier back down to stock-ish speeds.

You can OC your RAM later, but that gets a little more complicated as you may have to adjust CAS timings and RAM voltages to make it work. Keeping your RAM at stock speeds should give you one less thing to worry about while you probe the limits of your CPU.

Good luck!

Download Bitsum ProcessLasso Free. Make sure you download the correct version, Free 32 bit or Free 64 bit, Process Lasso - Automate and optimize process priorities, CPU affinities, power profiles, and more!
-- Start PR, alt tab to desktop, open ProcessLasso window, right click on PRLauncher.exe, PRBF2.exe and and give them default priority status of High, set the PRBF2.exe to gaming mode, and give both of them high or higher access to RAM.

Unpark your CPU Cores in ProcessLasso->Options->Configure CPU Core Parking->UNpark your cores. explanation of how and why to do this: ParkControl - Tweak and monitor core parking in real time!

Zyco187 wrote:so would this mean that 2 7770s would be worthless ??? and bottleneck the cpu