Simviation Forums

Hello Everyone,

Just picked up this puppy:

http://www.newegg.com/product/product.a ... 6835999001

Not top of the line stuff here but I needed something before my eVGA 7600gt burned up. Installed it and was doing some intense flying. When I checked the temp I was sitting at 49 deg C after about 45 min of flight. Is this a good result? So far my sim seems to be running better after longer jaunts.

In addition I wanted to overclock the mem a bit so I picked up these:

http://www.tigerdirect.com/applications ... u=ULT30100

And this:

http://www.tigerdirect.com/applications ... u=C13-8020

My system temps are stable at 27 deg C and with a copper coolermaster heatsink on the cpu running about 37 deg c, this is all topped off with 3 case fans.

Should I attempt to overclock this system?

Well you just spent a bunch of money on a bunch of worthless cooling. Memsinks barely do anything for your RAM, and that VGA cooler isn't worth the aluminum and powder coat.

But the good news is that your systems temps are in the range that if your power supply can handle it you could probably get a 20% clock out of it.

Cheers
Cameron

Was that an intentional contradiction?  

Hello Everyone,

Just picked up this puppy:

http://www.newegg.com/product/product.a ... 6835999001

Not top of the line stuff here but I needed something before my eVGA 7600gt burned up. Installed it and was doing some intense flying. When I checked the temp I was sitting at 49 deg C after about 45 min of flight. Is this a good result? So far my sim seems to be running better after longer jaunts.

In addition I wanted to overclock the mem a bit so I picked up these:

http://www.tigerdirect.com/applications ... u=ULT30100

And this:

http://www.tigerdirect.com/applications ... u=C13-8020

My system temps are stable at 27 deg C and with a copper coolermaster heatsink on the cpu running about 37 deg c, this is all topped off with 3 case fans.

Should I attempt to overclock this system?

Did you check that 49c 'In Flight"? In other words, you have a monitor running a time base graph and dropped to the desktop from the program to see where the card was running for the 5-10 minute period it recored the temp.

If not, as soon as you closed MSFS, the core dropped just about instantly so the 49c was not valid.

If that is a full load in flight temp, you have room to work on an overclock. try and keep it under or around 75c. Spikes a but higher are OK but dont run it flat out at 80c

Thanks nick, yeah she is running at 54 with the sim running still not too shabby I guess.  For some reason the bios for my MB doesnt allow me to change the multiplier for the cpu. Im running a 533 p4 2.93 cpu and my multiplier is set to 133 X 22.0 in addition there are no jumpers on the MB for this.

A while back I flashed the bios a while back and the frequency voltage control disappeared in the bios? Im debating on flashing it again with another update and hopefully that F&V comes back or is there something Im missing?

I also have proper cooling on the memory right now and want to kick that up a bit. Nothing crazy overall just a bit of a kick to the system for better performance.

Do you think an investment in a 3.2 prescott would help with overall performance TD had one for 69.00?

I understand that overclocking is a lone project but any advice would be helpful and if I cause damage to my system I will not care too much.

[quote]Thanks nick, yeah she is running at 54 with the sim running still not too shabby I guess.

Im doing some research right now but I think I might need to revert back to that older BIOS. This current bios really doesnt have much for over clocking. The biggest performance boost so far was a manual change to the AGP Driving control from EA to maxed out at FF. I also dropped my CAS Latency from 2.5 to 2. Both of these settings were unstable before cooling was applied.

By the way thanks Nick!

Im doing some research right now but I think I might need to revert back to that older BIOS. This current bios really doesnt have much for over clocking. The biggest performance boost so far was a manual change to the AGP Driving control from EA to maxed out at FF. I also dropped my CAS Latency from 2.5 to 2. Both of these settings were unstable before cooling was applied.

By the way thanks Nick!

So you are dealing with an older rig. I have not seen AGP drive control in many years. I think the last time was around 2003.

Older system interface terms such a AGP Drive Control with their hex values instead of reading the video card BIOS and tuning that by the video card manufacture setup. That AGP/DC setting is available in your BIOS for that reason. Later motherboards and BIOS designs were collaborated on between the manufactures so the user did not have to deal with that. Enabling things such as FAST WRITES or AGP 3.0 Calibration automatically made those changes.

Sometimes the latest BIOS is not the best. And, there are people out there who write and edit hacked BIOSes for motherboards. Another handy tool was WPCREDIT/WPCRSET which allowed direct Windows editing of the chipset registers and would also allow being set at boot. The old AMD systems were tweaked that way. Promise RAID efficiency and speed could be dramatically increased using that interface along with setting CPU and AGP values not available in the BIOS.

As I said, the FSB/memory speed is the key to a clock. GHz is important but the trick is to get the memory talking to the CPU at the speed the CPU wants it. Older systems are very restricted in that area. To get the memory discussing FS9 at the speed the CPU wants to talk about it, means your memory wants to be chatting at about 533Mhz, at least. Older memory and motherboards wont do that soothe goal is to get the memory and FSB up as high as you can, and with that the GHz as high as they will go at the same time with the focus being on the FSB/memory.

The memory timing and sub-timings are also very important, but, the difference between CAS2 and CAS 2.5 when CAS2.5 will allow the memory be run at a much higher speed makes the decision about where that is set. If you were able to run the memory 200MHz higher because you raise CAS to 3, then that would be better than running CAS2 @ default.

It

clarification:

I just read that again and I dont want to confuse anyone... the COMMAND RATE and the CAS TIMING are 2 different numbers

The COMMAND RATE which is not always available in a BIOS tells the system how to deal with the latency on the entire stick. 1T being the fastest and 2T being the most stable.

CAS is different.

Right now I have one system running CAS-6 7-6-15 CMD-1T @ 720MHz (DDR3 1440) and another running CAS-8 7-7-8 22 1T @ 1000MHz (DDR3 2000)

being I am not playing around at 200-300MHz true memory speeds and well over the 533MHz barrier, I run much higher CAS and sub timing to maintain stability but ALWAYS make sure the CMD RATE is 1T when tweaking it out.


Although, with the processor I am running it really wants to discuss things @ 1066MHz which means I am still a bit shy of chatting with it on its own terms

not for long though  

I just need the next installment of DDR3 memory and I should be good to go.