through the Asus suite overclocking software

 

Did you check your Vcore? You should NEVER use software or any automatic OCing tools, especially with Ivy Bridge that tend to overheat with excessive voltage.

Now if you GPU also overheats without overclock, you may have a cooling problem in your case

Interesting feedback indeed, I would have thought after seeing the Asus video about OC saying that it's "safe for the CPU" to over clock with their software that I was being conservative...!!! And no my GPU is not over clock. The cooler has been checked and is reported working normally by the technician. Thank you for your feedback Dario.

Driver version 301.42 indeed one fps faster than 301.10!

CPU: 4.7 GHz

Mem: 2133 MHz, CAS9 CR2

FSXMark11: 47.56 fps avg

 

HLJAMES

 

Hi.

I get my 3770K and made some test to see that is ok.

the 2800ram a orderd is it long time to get, think to take

Gskill 2666 like HL James instead.

My 3770 clock ok not a golden chip 4.9 -5.0 ok, super pi 32m and aida64 10min @5,1

 

Did this tests with gskill 2133 9-11-10-28-2T @4.7ghz to see that a get the right numbers.

Driver 301.42

 

FSMark11:

Run1: avg 47.7 wide=True

Run2: avg 48.8 " Lucid Virtu MVP mode D

Run3: avg 47.0 " Lucid Virtu MVP on Intigrated DVI port

 

Run4: avg 53,4 wide=False

Run5: avg 53.8 " Lucid Virtu MVP mode D

Run6: avg 53.3 " Lucid Virtu MVP on Intigrated DVI port

 

I am right there , any comments?

 

Hasse

Hi

here you can see the benefits of 3770 to 2700 on slow rams

 

Hasse

 

Hey all. Just want to give a quick thanks to Techguy, James, Ben, Word Not Allowed, and everyone else who has added very valuable information to this thread. I have been following it since day one and just purchased my hardware based largely on what I read here. I hope to get the system up and running in the next week. I will get my FSXMark scores up as soon as I get the system smooth, stable, and hopefully blazing fast.

 

3770K

H100 Liquid Cooling

ASRock X77 Extreme4

3x 120GB Vertex 3 (on sale for $70 each)

8GB Mushkin Enhanced Redline

EVGA GTX670 "FTW" Edition

Corsair 850W PSU

 

 

Hey all,

 

Got the build finished and tested over the weekend and here are the results:

 

Stable OC at 4.7 with a +0.086 Turbo offset. RAM is at 1600 7-9-8-24 at 1.65v, gonna see if I can push that higher. Used EVGA PrecisionX to play with the videocard and have it running smooth at an 1180 clock and hasn't gone above 70C (Fan at 60%) while in the sim with 301.42 drivers.

 

FSMMark11 avg. is 51.1

 

Gonna play with it some more during the week and see if I can fine tune it but overall I am very pleased with the results.

 

Thanks again for all the valuable input!

OK..After thoroughly screwing up my build and a dead CPU, I managed to rebuild everything. Even the Win 7 reactivation went without a glitch (Since its all the same components)

 

This time I didn't mess with the voltage directly. I used the ASUS Turbo EVO to do the OC for me. Initially it oc to 4.2 and then when I used the auto OC extreme, It moved it up to 4.3Hz and the Vcore went to 1.2v but when I run Prime 95, the vcore cpuZ shows me close to 1.3v

 

I then went into BIOS and changed the multiplier/Ratio to 44.and I get 4.433Ghz (Since the FSB=103?)

 

This time when I run Prime95, it shoots to 90deg but when I run FSX, the temp stays around sub 80 but the vcore fluctuates between 1.3-1.4v

 

The vcore bothers me.. The Vcore in BIOS is not manual..its in offsetmode starting at 1.2 (The image shown is not mine) but instead of .988v in the image, mine says 1.2 and then just like in the image its offset mode + or -. What is the amount that its increasing by? and how does it go from 1.2 to 1.4v during full load?

 

IS there a way to set the maximum to not go beyond 1.3v at any point?

 

How do I reduce the starting voltage from 1.2 to say 1.0?

 

I am worried I am going to brick another CPU

 

IF I want to manually set the voltage, What do I do? click on the button offset mode to manual..and then where do I actually set the voltage?

 

 

 

 

Manny

 

 

 

 

 

I did read Word Not Allowed's page where the OC articles are...but Its not clear. That one good link he has

 

http://www.xtremesys...Guide-Included)

Instead if offset use fixed voltage mode. This will always run at the voltage you specify though, even when it's not under load. This could have an adverse affect on lifespan of the chip.

Another q.

 

Since we basically turn off the MT and use fsx.cfg parameter to 14 (To use the second core in a quad core), why not just OC the second core to the max and leave the other core around say 4.2 or even less?

 

Is that a good idea? for FSX we don't have to OC all the cores to the max. would that help?

 

Manny

 

Instead if offset use fixed voltage mode. This will always run at the voltage you specify though, even when it's not under load. This could have an adverse affect on lifespan of the chip.

 

Hi Tech guy, do you have the ASUS MB or something else?

 

I thought I had entered the fixed voltage of 1.3 the first time I bricked the CPU. Not sure why 1.3v would have bricked my CPU. Now I am questioning everything I am doing.

 

As far as life span, I need it to last 2 or 3 years..after that who cares. :)

 

Manny

voltage is not your problem, heat is. I've got my 3770k at 4.7 with ~1.380V. For that you need a good cooler. I changed my old corsair H50 with at 4.5 ghz, I was getting 90o to a corsair H80 and the temps are 65o at 4.7ghz.

Instead if offset use fixed voltage mode. This will always run at the voltage you specify though, even when it's not under load. This could have an adverse affect on lifespan of the chip.

 

Another solution I use is a dual boot-one for FSX, the other for non-FSX. I run my CPU at stock for the non-FSX uses, and over clocked for FSX.

Another q.

 

Since we basically turn off the MT and use fsx.cfg parameter to 14 (To use the second core in a quad core), why not just OC the second core to the max and leave the other core around say 4.2 or even less?

 

Is that a good idea? for FSX we don't have to OC all the cores to the max. would that help?

 

Ya know, that's actually an intriguing idea. If you find the "good" core in your chip and overclock to the max you might just get better FPS than sticking to a lower overclock applied to all cores, given the largely serial processing nature of FSX. It might also increase longevity of the chip if only dressing a single core. One potential downside could be slower texture loading, though, with the other cores running slower.

 

 

Hi Tech guy, do you have the ASUS MB or something else?

 

I thought I had entered the fixed voltage of 1.3 the first time I bricked the CPU. Not sure why 1.3v would have bricked my CPU. Now I am questioning everything I am doing.

 

As far as life span, I need it to last 2 or 3 years..after that who cares. :)

 

Manny

 

I have the Asrock Z77 Extreme 4 board. I like it, but it has some USB device compatibility issues that they're still working out the bugs in the BIOS (UEFI).

 

A fixed voltage of 1.3 shouldn't fry your chip, Ivy Bridge is good up to 1.52V according to Intel, modern cooling systems just can't handle the heat.

Well, I received my single most expensive upgrade ever today - EVGA GTX 680 Superclocked Signature 2 (yesh, that's a mouthful)

 

I'm looking forward to trying it out :) I know FSX is almost totally CPU bound but I should still see some improvement coming from a reference GTX 470.

Hi

Dont try to hit big numbers with AUTO clock tools!!!

I run a Gigabyte MoBo never used EasyTune.

The key is to find the point were the chip need voltage,

i normally start at @4.6 and then undervolt it to the point it be unstable.

then 4.7 , 4,8 , 4.9 , 5.0 , 5.1 , the IB have a point close to 4.8 were you most

feed mutch more for 0.1ghz increase.

 

Then you have the ram , i run the cpu @4.5 when testing mem controller and rams,

Find out the fastest speed with lowest timings , you have the VTT,IMC and PLL to ply with.

Test with Aida64 to get the lovest latens with same cpu speed.

 

Its useless to run a IB with rams slower than 2400 optimal 2666-2800 cl 10-11.

I have a good pair of 2133 that do 2350 at cl9 and thats to slow for IB.

 

If you compare to SB the diff is 0.35-0.40ghz if you have 2666 cl 10 on IB and 2133 cl 9 on SB.

with 2133 on IB and SB the diff is 0.2ghz to match a SB @5.2 you ned @5.0 for the IB to have the

same performance!!!

 

I put in the IB 2700K @5.15 24/7 with HT enabled to get that performance with my 3770k ram 2350 and need to push it to @4.95 no ht and have less performance the diff was 1fps in FSMark11.

 

A shall run Nvida surround with 3 monitors, if a not pleased with the perf a shall build me a

SS phase cooler for the 3770 to push it to @5.5-5.7 24/7.

 

on the fs9 days i run a AMD 3200+ on a prometia ss cooler 24/7 to get decent fps.

 

Hasse

Finally able to run FSXMark 11 again with my GPU and CPU OC'd together, unlike before which was CPU only.

 

 

Frames Time (ms) Min Max Avg

16176 300000 32 73.67 53.31

 

Here are .CSV files, including the first run logged in frame render times rather than FPS:

 

 

fsx 2012-05-22 17-58-48-04 frametimes.csv - 236.8 KB

fsx 2012-05-22 18-28-24-93 minmaxavg.csv - 71 bytes

fsx 2012-05-22 18-36-03-51 minmaxavg.csv - 71 bytes

fsx 2012-05-22 18-44-20-03 minmaxavg.csv - 71 bytes

 

I obviously haven't followed this thread close enough. I only saw the csv files today. Been bussy with my own testing so I must have missed it and since been away from home working.

 

I've been able to pilot the stutters for the first run that we exclude for the official FSmark result. Do you still have the frame time csvs for the other 3 runs as well and the FPS csvs for all 4 runs?

 

Would you be able to do a test with the exact same configuration apart from changing to x8 PCIe 3.0 and upload the frame time and FPS csvs so I can compare the difference?

 

Thanks for your testing Max

I've reloaded the system and wiped everything out since performing those tests, I'd have to test all over again. I'm still in the process of getting the system to a completely stable base, including FSX, then I'll image and I can run some tests again. Don't know how long it will take this time, probably a couple weeks.