Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: BaldEagl on March 17, 2012, 01:45:37 AM
-
I DL'd Nvidia precision today and OC'd my video card. It's hard to believe my old 8800 GTS 512 was running the game tonight with self shadows, smooth shadows, building shadows and ground clutter at 1024 res at a smooth 55-60 fps in nearly all situations, none of which I could run before. The only thing that seems to hurt my FPS is bump mapping buildings but I don't actually like the difference anyway. I've also left off shadows on others, bump map my vehicle and bump map other poeples vehicles. Other than that everything is on and all sliders are maxed.
Stock card speeds: 670 core clock, 1674 shaders, 972 memory
Speed I hit but unstable: 800 core clock, 1998 shaders, 1160 memory
Settings I'm running: 750 core clock, 1873 shaders, 1088 memory
I origionally had the fan set to auto and ran up into the 80's C but the fan never exceeded 35%. I manually set the fan to 80% and temps remained at or under 60C for hours online.
I set up two profiles; one with stock settings and one with the OC settings. Stock settings launch on start-up and when I'm ready to play I just right click Nvidia precision in my task bar to change profiles.
Again, I really can't believe the difference this relatively mild OC made but am maybe even more astounded that a 5 year old video card is handling the game like it is. Someday I'll have to buy a new one to see what they can do. In the meantime I'm a happy camper now.
BTW, for those who don't know this is mated to an Intel E6750 OC'd to 3.2 Ghz with 4 Gb Kingston Hyper-X (4-4-4-12) on an Nvidia 780i running Win XP Pro, pushing an LG 22" widescreen LCD and powered by an 850W Corsair PSU.
Forgot to mention other relevant data: Running 8x AA, 4X anistopic filtering, 3 frame pre-render with most other card settings maxed and overriding game settings.
-
I DL'd Nvidia precision today and OC'd my video card. It's hard to believe my old 8800 GTS 512 was running the game tonight with self shadows, smooth shadows, building shadows and ground clutter at 1024 res at a smooth 55-60 fps in nearly all situations, none of which I could run before. The only thing that seems to hurt my FPS is bump mapping buildings but I don't actually like the difference anyway. I've also left off shadows on others, bump map my vehicle and bump map other poeples vehicles. Other than that everything is on and all sliders are maxed.
Stock card speeds: 670 core clock, 1674 shaders, 972 memory
Speed I hit but unstable: 800 core clock, 1998 shaders, 1160 memory
Settings I'm running: 750 core clock, 1873 shaders, 1088 memory
I origionally had the fan set to auto and ran up into the 80's C but the fan never exceeded 35%. I manually set the fan to 80% and temps remained at or under 60C for hours online.
I set up two profiles; one with stock settings and one with the OC settings. Stock settings launch on start-up and when I'm ready to play I just right click Nvidia precision in my task bar to change profiles.
Again, I really can't believe the difference this relatively mild OC made but am maybe even more astounded that a 5 year old video card is handling the game like it is. Someday I'll have to buy a new one to see what they can do. In the meantime I'm a happy camper now.
BTW, for those who don't know this is mated to an Intel E6750 OC'd to 3.2 Ghz with 4 Gb Kingston Hyper-X (4-4-4-12) on an Nvidia 780i running Win XP Pro, pushing an LG 22" widescreen LCD and powered by an 850W Corsair PSU.
Forgot to mention other relevant data: Running 8x AA, 4X anistopic filtering, 3 frame pre-render with most other card settings maxed and overriding game settings.
take note every one overclocking video cards has its upsides! not burning down your house and being called stupid.
And for you BaldEgal im happy your overclocks work well. just make sure you wacth those temps close.
-
<insert random facepalm picture here>
:bhead
-
<insert random facepalm picture here>
:bhead
why? is he doing somthing you cant becuase you dont know how to do?
-
take note every one overclocking video cards has its upsides! not burning down your house and being called stupid.
Ive investigated thousands of house fires, never saw one caused by a vid card.
Congrats Bald.... :aok
-
why? is he doing somthing you cant becuase you dont know how to do?
exactly what im talking about.
my phenomIIx2 can reach a steady 4.0 GHz with 4 cores (3.2 GHz by factory default), L3 cache at 2600MHz against the original 2GHz, DDR3-1600 memory at 1700MHz, also my HD 5830 can run steady at 883MHz (vs the 800MHz stock core speed). I dont need it, so its set back to factory clocks, but its not inportant. Im not jelous to BE or anything.
My point is, you know nothing yet you act like youre the god of wisdom. please...
:bhead
-
And for you BaldEgal im happy your overclocks work well. just make sure you wacth those temps close.
Olds, I know my OC's will work well. It's because I do them the way they should be done; in small incremental steps adjusting only one timing at a time and testing for heat and stability between each step then backing down and doing extended testing for heat and stability over the long haul. I don't just crank the dials up and throw it on a test bed to see what happens.
Each of my OC's are backed down significantly from where they could be. I've had my CPU up to 3.6 Ghz but I don't need to push the limits for daily driving and I'm not much into doing it simply for bragging rights. I want a good, stable, cool OC that improves performance but that I can set and forget without worrying what bad things might happen. My CPU's been running with it's OC for almost five years now and I expect if I still have this PC five years from now both the CPU and GPU will still be running at these settings.
-
take note every one overclocking video cards has its upsides! not burning down your house and being called stupid.
And for you BaldEgal im happy your overclocks work well. just make sure you wacth those temps close.
There is no need to go into everyone's thread and complain.
Bald knows what he is doing, you didn't. Move on.
-
There is no need to go into everyone's thread and complain.
Bald knows what he is doing, you didn't. Move on.
This
-
exactly what I'm talking about.
my phenomIIx2 can reach a steady 4.0 GHz with 4 cores (3.2 GHz by factory default), L3 cache at 2600MHz against the original 2GHz, DDR3-1600 memory at 1700MHz, also my HD 5830 can run steady at 883MHz (vs the 800MHz stock core speed). I dont need it, so its set back to factory clocks, but its not inportant. Im not jelous to BE or anything.
My point is, you know nothing yet you act like youre the god of wisdom. please...
:bhead
hmm know nothing how do you know this? you think because I'm a kid i don't know anything. well lets get this straight.
i know what I'm doing, am i a IT Tech guy? no of course not but i do know some. i read articles on line on how to overclock. and yes it was via BIOS not some software program. if you really want to know how i overclocked my CPU it went like this.
1: raised the FSB (front side bus) by 5MHz. (why didnt i just raise the ratio? well because the ATHLON x4 630 has a locked ratio at 14)
2: stability test. ran AMD's stability test putting each core at 100% one at a time for a hour then all the cores at once for 4hours
3: did math calculations of what FSB number would give me 2.9ghz that being 210 giving me 2940MHz or 2.9ghz going 500MHz at a time from here
4: then i got to 3.0ghz and hit a wall. the computer would not boot and give me a start up error so i looked around online. then i found out the higher the FSB the higher everything got. so i lowered the ram multiplier from 6.66x to 5.56x lowering the ram MHz (i had to do this because my ram don't go higher than 1333MHz)
5: i also hit a wall at 2.3ghz and the NB and hyperlink from 9x to 8x, it booted this time but was unstable so i lowered RAM and it was fine all the way up to 3.4ghz any thing higher than that i would need to get better cooling and at 3.4ghz i didn't need anymore power.
you see i do know how to overclock. I'm a "beazt omgz 1337 mode" at it no. but i would love you guys to stop treating me as a dumbarse
-
There is no need to go into everyone's thread and complain.
Bald knows what he is doing, you didn't. Move on.
how did i complain to bald? i said good for him and i hope it goes well.
-
hmm know nothing how do you know this? you think because I'm a kid i don't know anything. well lets get this straight.
i know what I'm doing, am i a IT Tech guy? no of course not but i do know some. i read articles on line on how to overclock. and yes it was via BIOS not some software program. if you really want to know how i overclocked my CPU it went like this.
1: raised the FSB (front side bus) by 5MHz. (why didnt i just raise the ratio? well because the ATHLON x4 630 has a locked ratio at 14)
2: stability test. ran AMD's stability test putting each core at 100% one at a time for a hour then all the cores at once for 4hours
3: did math calculations of what FSB number would give me 2.9ghz that being 210 giving me 2940MHz or 2.9ghz going 500MHz at a time from here
4: then i got to 3.0ghz and hit a wall. the computer would not boot and give me a start up error so i looked around online. then i found out the higher the FSB the higher everything got. so i lowered the ram multiplier from 6.66x to 5.56x lowering the ram MHz (i had to do this because my ram don't go higher than 1333MHz)
5: i also hit a wall at 2.3ghz and the NB and hyperlink from 9x to 8x, it booted this time but was unstable so i lowered RAM and it was fine all the way up to 3.4ghz any thing higher than that i would need to get better cooling and at 3.4ghz i didn't need anymore power.
you see i do know how to overclock. I'm a "beazt omgz 1337 mode" at it no. but i would love you guys to stop treating me as a dumbarse
then stop bringing up the fact that you were called a dumbarse or keep going and be a dumbarse, your choice not ours.
semp
-
then stop bringing up the fact that you were called a dumbarse or keep going and be a dumbarse, your choice not ours.
semp
sorry but ever thread i post i get called it.
-
hmm know nothing how do you know this? you think because I'm a kid i don't know anything. well lets get this straight.
i know what I'm doing, am i a IT Tech guy? no of course not but i do know some. i read articles on line on how to overclock. and yes it was via BIOS not some software program. if you really want to know how i overclocked my CPU it went like this.
1: raised the FSB (front side bus) by 5MHz. (why didnt i just raise the ratio? well because the ATHLON x4 630 has a locked ratio at 14)
2: stability test. ran AMD's stability test putting each core at 100% one at a time for a hour then all the cores at once for 4hours
3: did math calculations of what FSB number would give me 2.9ghz that being 210 giving me 2940MHz or 2.9ghz going 500MHz at a time from here
4: then i got to 3.0ghz and hit a wall. the computer would not boot and give me a start up error so i looked around online. then i found out the higher the FSB the higher everything got. so i lowered the ram multiplier from 6.66x to 5.56x lowering the ram MHz (i had to do this because my ram don't go higher than 1333MHz)
5: i also hit a wall at 2.3ghz and the NB and hyperlink from 9x to 8x, it booted this time but was unstable so i lowered RAM and it was fine all the way up to 3.4ghz any thing higher than that i would need to get better cooling and at 3.4ghz i didn't need anymore power.
you see i do know how to overclock. I'm a "beazt omgz 1337 mode" at it no. but i would love you guys to stop treating me as a dumbarse
:confused: I'm surprised your compter actually runs based on that description. I've never heard of an OCing proceedure like that.
If I were you I'd do some more studying, reset your BIOS to default settings and try again armed with better knowledge.
-
sorry but ever thread i post i get called it.
you brought it up in the last two threads. forget about it, let it go. if you are happy you got your answer then that's it, no need to be bitter because somebody else didnt get the same responses you did.
semp
-
:confused: I'm surprised your compter actually runs based on that description. I've never heard of an OCing proceedure like that.
If I were you I'd do some more studying, reset your BIOS to default settings and try again armed with better knowledge.
The BIOS procedure?
-
The BIOS procedure?
No. You always OC through the BIOS. On reading this a second time he must have had his RAM linked. There's no reason to link it unless your going to link and sync but even then you'd do it after getting the CPU stable. He'd have been better off to leave it unlinked to begin with, get the CPU up to speed then bring the RAM into sync if possible then link it. The way he did it he had two points of potential failure and there's no knowing which it was. Then he introduced yet another point of potential failure by jacking with the NB. You don't even have a stable OC on the CPU yet and your messing with the RAM and the NB at the same time?
Although I'm afraid to suggest it, nowhere in his proceedure did I see him raise CPU voltage, most likely because the RAM stressed before he got that far .
As to the RAM itself, If you're going to overclock it you have to loosen timings but if your going to underclock it you might be able to tighten them up and get back some lost performance. So he stumbled into slowing down the RAM while loosening the timings or slightly bumping voltage might have done the trick. Either of those can be tricky so what he did was probably for the best given his inexperience.
I was also curious about the initial 5 Mhz raise in the FSB with a bunch of testing then later just jacking it up then jumping 500 Mhz per step? Where did he learn that?
Hey, I get it, he's a kid and he wants it done now but if he wats it done right then some more reading and research and trying it again with better information would probably do a world of good for his PC. As it is who knows what he's got.
-
hmm know nothing how do you know this? you think because I'm a kid i don't know anything. well lets get this straight.
i know what I'm doing, am i a IT Tech guy? no of course not but i do know some. i read articles on line on how to overclock. and yes it was via BIOS not some software program. if you really want to know how i overclocked my CPU it went like this.
1: raised the FSB (front side bus) by 5MHz. (why didnt i just raise the ratio? well because the ATHLON x4 630 has a locked ratio at 14)
2: stability test. ran AMD's stability test putting each core at 100% one at a time for a hour then all the cores at once for 4hours
3: did math calculations of what FSB number would give me 2.9ghz that being 210 giving me 2940MHz or 2.9ghz going 500MHz at a time from here
4: then i got to 3.0ghz and hit a wall. the computer would not boot and give me a start up error so i looked around online. then i found out the higher the FSB the higher everything got. so i lowered the ram multiplier from 6.66x to 5.56x lowering the ram MHz (i had to do this because my ram don't go higher than 1333MHz)
5: i also hit a wall at 2.3ghz and the NB and hyperlink from 9x to 8x, it booted this time but was unstable so i lowered RAM and it was fine all the way up to 3.4ghz any thing higher than that i would need to get better cooling and at 3.4ghz i didn't need anymore power.
you see i do know how to overclock. I'm a "beazt omgz 1337 mode" at it no. but i would love you guys to stop treating me as a dumbarse
exactly what im talking about.
My point is, you know nothing yet you act like youre the god of wisdom. please...
Dude, you started with a rant how awesome OC-ing is. Wasnt it you just burned your card, huh? Yet you present another "dumbarse" procedure how to torture your CPU for a 15% advantage, while about only 3% is going to appear on the in-game performaces due to your cheap video card?
Building and OCing a computer is about finding the bottlenecks, and NOT about pushing every part by "500mhz steps", until it burns.
It was you calling me jelous to BE "couse i cant do what he can". Wondering youre being handled as a dumbarse?
Check the mirror, dude, before you give advice to ones who got much more knowledge than you. Please...
-
how did i complain to bald? i said good for him and i hope it goes well.
You didn't complain to BE. You are bringing something up over and over that shouldn't brought up anymore.
-
No. You always OC through the BIOS. On reading this a second time he must have had his RAM linked. There's no reason to link it unless your going to link and sync but even then you'd do it after getting the CPU stable. He'd have been better off to leave it unlinked to begin with, get the CPU up to speed then bring the RAM into sync if possible then link it. The way he did it he had two points of potential failure and there's no knowing which it was. Then he introduced yet another point of potential failure by jacking with the NB. You don't even have a stable OC on the CPU yet and your messing with the RAM and the NB at the same time?
Although I'm afraid to suggest it, nowhere in his proceedure did I see him raise CPU voltage, most likely because the RAM stressed before he got that far .
As to the RAM itself, If you're going to overclock it you have to loosen timings but if your going to underclock it you might be able to tighten them up and get back some lost performance. So he stumbled into slowing down the RAM while loosening the timings or slightly bumping voltage might have done the trick. Either of those can be tricky so what he did was probably for the best given his inexperience.
I was also curious about the initial 5 Mhz raise in the FSB with a bunch of testing then later just jacking it up then jumping 500 Mhz per step? Where did he learn that?
Hey, I get it, he's a kid and he wants it done now but if he wats it done right then some more reading and research and trying it again with better information would probably do a world of good for his PC. As it is who knows what he's got.
Ahh. As I had originally said, I've never tried it on my CPU out of inability on part, and lack of need. after reading this though I realize I do need to do a lot more research.
-
All of this is written in English but reads like Greek. I sense by downloading something your video performance improved. I have an Nvidia card. In laymans terms, what did you do and what were the results?
Thanks in advance!
Boo
-
All of this is written in English but reads like Greek. I sense by downloading something your video performance improved. I have an Nvidia card. In laymans terms, what did you do and what were the results?
Thanks in advance!
Boo
he Downloaded a software called nVidia Precision. it is an overlocking tool. When he increseaed the values of numbers in 3 or 4 fields overall his card was working harder and he gained a substantial gain in video card performance/ability
-
No. You always OC through the BIOS. On reading this a second time he must have had his RAM linked. There's no reason to link it unless your going to link and sync but even then you'd do it after getting the CPU stable. He'd have been better off to leave it unlinked to begin with, get the CPU up to speed then bring the RAM into sync if possible then link it. The way he did it he had two points of potential failure and there's no knowing which it was. Then he introduced yet another point of potential failure by jacking with the NB. You don't even have a stable OC on the CPU yet and your messing with the RAM and the NB at the same time?
Although I'm afraid to suggest it, nowhere in his proceedure did I see him raise CPU voltage, most likely because the RAM stressed before he got that far .
As to the RAM itself, If you're going to overclock it you have to loosen timings but if your going to underclock it you might be able to tighten them up and get back some lost performance. So he stumbled into slowing down the RAM while loosening the timings or slightly bumping voltage might have done the trick. Either of those can be tricky so what he did was probably for the best given his inexperience.
I was also curious about the initial 5 Mhz raise in the FSB with a bunch of testing then later just jacking it up then jumping 500 Mhz per step? Where did he learn that?
Hey, I get it, he's a kid and he wants it done now but if he wats it done right then some more reading and research and trying it again with better information would probably do a world of good for his PC. As it is who knows what he's got.
I ment 50MHZ at a time not 500mhz and you dont really know what your talking about do you? the higher the FSB the higher EVERYTHING goes higher you have a FSB the higher the ram so when im at 230 FSB times 6.66 and the max is 1333mhz due to the motherboard not allowing for more and the ram defaulted at 1333mhz what do you think will happen? changing the times wont do anything for a motherboard that cant handle more than 1333mhz. how ever underclocking the ram to 1275mhz works just fine. yet i guess that's stupid as well?
the 5mhz raise i got at first was just to test if the CPU was overclockable.(and i did this because i got the original computer custom made).
and 50mhz is not a HUGE JUMP for CPU overclocking. because the easier way of overclock by raising the ratio (and im sure most do this way insted of raising the FSB because its way easier) you can raise the ratio by 0.5 at a time. meaning you guys are going 0.1 GHZ at a time or 100mhz. with the FSB way (that was the only way i could due to a locked ratio) 50mhz at a time is like raising the ratio by 0.25mhz at a time. and that is imposable on any BIOS i know of. \
and im going to bold this I MENT 50MHZ NOT 500MHZ
Dude, you started with a rant how awesome OC-ing is. Wasn't it you just burned your card, huh?to your cheap video card?
find this "OMG IM BEAST RANT" for me i dint remember posting it. my video card is fine ive said this a million times now that the drivers where bad because i rolled back the drivers and now furmark is FINE ON THE SAME CARD.
-
I ment 50MHZ at a time not 500mhz and you dont really know what your talking about do you? the higher the FSB the higher EVERYTHING goes higher you have a FSB the higher the ram so when im at 230 FSB times 6.66 and the max is 1333mhz due to the motherboard not allowing for more and the ram defaulted at 1333mhz what do you think will happen? changing the times wont do anything for a motherboard that cant handle more than 1333mhz. how ever underclocking the ram to 1275mhz works just fine. yet i guess that's stupid as well?
the 5mhz raise i got at first was just to test if the CPU was overclockable.(and i did this because i got the original computer custom made).
and 50mhz is not a HUGE JUMP for CPU overclocking. because the easier way of overclock by raising the ratio (and im sure most do this way insted of raising the FSB because its way easier) you can raise the ratio by 0.5 at a time. meaning you guys are going 0.1 GHZ at a time or 100mhz. with the FSB way (that was the only way i could due to a locked ratio) 50mhz at a time is like raising the ratio by 0.25mhz at a time. and that is imposable on any BIOS i know of. \
and im going to bold this I MENT 50MHZ NOT 500MHZ
find this "OMG IM BEAST RANT" for me i dint remember posting it. my video card is fine ive said this a million times now that the drivers where bad because i rolled back the drivers and now furmark is FINE ON THE SAME CARD.
The only way your RAM speeds up when you raise the FSB is because you have the CPU and RAM clocks locked. Had you unlocked them before you started the RAM would have remained at it's original settings.
-
All of this is written in English but reads like Greek. I sense by downloading something your video performance improved. I have an Nvidia card. In laymans terms, what did you do and what were the results?
Thanks in advance!
Boo
I DL'd a program called NVidia Precision. It allows you to raise or lower the GPU core clock, shader clock and RAM clock settings and manually set fan speeds. You can either leave the GPU processor and shader clocks locked together or set them independantly (I left mine locked).
Start by raising the core/shader clocks slightly. There's a short test built into the program to make sure you're within the drivers allowed range. You can run until it fails the test then back it down. Then move on to the RAM clock. Do the same thing. Then go jump into a game. The program will monitor temps while in the game. Jump in and out watching temps. You may have to raise the fan speed if the temps rise too far or lower the clock settings if you see video artifacts.
If you're really ambitioos and want the most you can get from your card you can set the core and shader clocks independently and, as long as temps remain low enough you could overvolt slightly although video cards can't be overvolted by much so tread lightly.
You could also do this with RivaTuner but Precision is much easier to use.
-
I DL'd a program called NVidia Precision. It allows you to raise or lower the GPU core clock, shader clock and RAM clock settings and manually set fan speeds. You can either leave the GPU processor and shader clocks locked together or set them independantly (I left mine locked).
Start by raising the core/shader clocks slightly. There's a short test built into the program to make sure you're within the drivers allowed range. You can run until it fails the test then back it down. Then move on to the RAM clock. Do the same thing. Then go jump into a game. The program will monitor temps while in the game. Jump in and out watching temps. You may have to raise the fan speed if the temps rise too far or lower the clock settings if you see video artifacts.
If you're really ambitioos and want the most you can get from your card you can set the core and shader clocks independently and, as long as temps remain low enough you could overvolt slightly although video cards can't be overvolted by much so tread lightly.
You could also do this with RivaTuner but Precision is much easier to use.
I use Precision solely for monitoring (my rig is still good to go at stock speeds on everything, including the E8400). It was designed by EVGA with RivaTuner. It's a good program IMO.
-
This software seemed to conflict with the drivers I am using and caused me to lose my whole desktop including start menu.
Not sure why, just thought I would mention this to maybe save someone hours of trying to get their desktop back. :headscratch:
Perhaps you need to update your drivers before using this program.
-
This software seemed to conflict with the drivers I am using and caused me to lose my whole desktop including start menu.
Not sure why, just thought I would mention this to maybe save someone hours of trying to get their desktop back. :headscratch:
Perhaps you need to update your drivers before using this program.
when was the last time yo updated your drivers? which vc do you have? never heard of anybody losing their desktop. you sure you d/l the program from evga? as I believe it's only meant to be for evga video cards.
semp
-
when was the last time yo updated your drivers? which vc do you have? never heard of anybody losing their desktop. you sure you d/l the program from evga? as I believe it's only meant to be for evga video cards.
semp
LOL, I've never updated my drivers. I have an evga 8800gt.
In any case, it wasn't meant to be an indictment of the program, which I'm sure is very good, just some info for others if they experience the same problems I encountered.
I know for certain that is was the program that caused a conflict of some sort because when I shut down one of the processes it was running, my desktop came back.