8800gts 640mb Overclock?

[ShiningHolden]

My OC's were achieved with ATI tool with settings to halt the OC when any errors were detected.

What setting would that be? My ATITool settings look like this:

Here is a picture of me overclocking my 8800GTS to 690/1040 with ATITool, testing it's stability.

 

[MassiveOverkill]

What setting would that be? My ATITool settings look like this:

I am going to post a picture of me overclocking my 8800GTS to 690/1040 with ATITool in 10 minutes.

Actually it's the slider at the bottom set to the far left, that's what I meant, sorry for the confusion.

I manually scan as well and if any errors are detected, I scale it back.

 

[ShiningHolden]

Actually it's the slider at the bottom set to the far left, that's what I meant, sorry for the confusion.

I manually scan as well and if any errors are detected, I scale it back.

Oh? You mean, you bring the scale higher, for a higher overclock, and then you bring it back if you see any errors?

Do you have AIM/MSN?

 

[MassiveOverkill]

I leave the scale at the far left, but as far as artifiact scanning, my final overclock, I did what you did for like 5 mnutes, but just to show that I'm not BSing, how's 30 minutes sound? BTW, I started Orthos about 20 minutes into the GPU test..........I didn't see the relevance of my CPU stability to my GPU stability but figured I'd throw it in there.

PM me and I'll send ya my IM.......got Yahoo, AIM, MSN.

 

[TheRapture]

As far as using ATITool to overclock...some cards are REPORTING an overclock but not actually overclocking the card. 690 is a bit abnormal overclock for a GTS, I would be highly suspect that you are actually overclocking the core that high. 690 without a volt mod is pretty much a non occurence.

You should verify that overclock (or lack of) with Rivatuner's graphing function....

 

[pagkalis]

As far as using ATITool to overclock...some cards are REPORTING an overclock but not actually overclocking the card. 690 is a bit abnormal overclock for a GTS, I would be highly suspect that you are actually overclocking the core that high. 690 without a volt mod is pretty much a non occurence.

You should verify that overclock (or lack of) with Rivatuner's graphing function....

I would have to concur with TheRapture.
Please use the RivaTuner 2.01 hardware monitor and tell us what it reports.


I must say, congrats to PCduster for posting that superb link (this link)
It explains all the inconsistencies in overclocking 8800 cards. Please read it before bothering posting any overclocking results.


My eVGA 8800GTS 640MB SC, reached: 648-1566-1053
(completely artefact free)

But the settings in ATItool 0.26 read: core = 657, memory = 1049.



Read the article and you'll see how this makes sense.

 

[ShiningHolden]

As far as using ATITool to overclock...some cards are REPORTING an overclock but not actually overclocking the card. 690 is a bit abnormal overclock for a GTS, I would be highly suspect that you are actually overclocking the core that high. 690 without a volt mod is pretty much a non occurence.

You should verify that overclock (or lack of) with Rivatuner's graphing function....

You could very well be right. Let me run RivaTuner right now and see what it says.

EDIT:
Quite odd. One part of RivaTuner says 690, the other says 684. I want to try to push it all the way to 690 in RivaTuner. Anyone got any tips?

EDIT:
I tried to set the clocks in RivaTuner, and 690 still decreases to 684.

EDIT:
I said what the heck, and I increased it to 695, and it jumped to 702.

 

[pagkalis]

That is a superb overclock already! Is that on stock-cooling?

Ok so you've got core = 695 when it is in fact core = 702.


Firstly, at core = 690, could you lower by 1 MHz at a time you core, so that we can see when it makes the jump below to core = 675 (missing from the article).
Secondly, from core = 695, could you lower by 1 MHz at a time you core, so that we can see when it makes the jump from 675 to 702 (missing from the article)?

Also, running your memoey at 1040 is useless. It is still 1044. Try 1048 (which will make it 1053).
If that works, try 1067 (which will make it 1080).


P.S. Can anyone tell what software I need to use to measure a graphic card's memory bandwidth?
How does the manufacturer know that the 8800gts has a memory bandwidth of 64GB/s ?

 

[ShiningHolden]

That is a superb overclock already! Is that on stock-cooling?

Now, the article states that a shader of 1620 is achieved once you hit core = 681
Could you lower by 1 MHz at a time you core, so that we can see when it makes the jump to beyond core = 675 (missing from the article).

Once you know that exact number, add 23 to it and check with RivaTuner hardawre monitor what the actual speed is.

If core > 684, then lower 1 MHz at a time you core, so that we can see when exactly it made the jump upwards.
If core < 684, then increase by 1 MHz at a time until Riva hardware monitor reports a jump upwards.
That way you can help everyone here achieve safe and high overclocks.


P.S. Can anyone tell what software I need to use to measure a graphic card's memory bandwidth?
How does the manufacturer know that the 8800gts has a memory bandwidth of 64GB/s ?

This is water-cooled. In the morning's, my graphic's card load temperature is 38c. I say in the morning because my room itself gets VERY hot in the summer.

On stock-air, I was able to reach 650/1000.

I am almost positive that the shader clock speed is linked to the core or memory clock speed.

What core speed do you want me to go to?
And you want me to decrease/increase how much until what speed?

I am more than willing to do anything.

 

[SuperKeijo]

P.S. Can anyone tell what software I need to use to measure a graphic card's memory bandwidth?
How does the manufacturer know that the 8800gts has a memory bandwidth of 64GB/s ?

Memory controller: 320 bit on gts, 384bit on gtx (5x64 bit on gts, 6x64 bit on gtx)
Memory speed: 800/900MHz (Effective speed 1600/1800, data is send on the rise and fall cycle on ddr memory)

Memory bandwidth (example with the gts): 5x64 (=320bit, which means that 320 bits of data is sent with every clock pulse) x 1 600 000 000 1/s (hz) (1,6 billion clock pulses every second) = 512 000 000 000 bits/s. And since 1 byte is 8 bits, 512Gb is 64 GB.

 

[TheRapture]

ShiningHolden, very impressive, it appears Rivatuner is reporting you as having a massive overclock! Water cooled, yes, I think 690 would kill a stock cooled card with heat under hard loads.


The reason you get varying speeds and not the EXACT speed you set, is because the frequency generator runs at an odd setting, not an even number, so when you set a speed x the multiplier, you may be "in between" what you set and what it can physically do. Hence why setting to say 680 may report 686 or 675.....normal for the card to vary a bit from what you set.

 

[pagkalis]

aaaah, that oh so inviting eagerness....
(I wish my girlfriend was so eager to please me , oh well...)

Set it at core = 690, then lower by 1 MHz at a time, be checking each time with Riva and report when is it that it makes the jump to core = 675 (missing from the article).

After that, start from core = 695, then lower by 1 MHz at a time, be checking each time with Riva and report when is it that it makes the jump to core = 684 (missing from the article).


Also, running your memoey at 1040 is useless. It is still 1044. Try 1048 (which will make it 1053).
If that works, try 1067 (which will make it 1080).
But do all that separately from the core testing. we don't want any confusions.

 

[pagkalis]

Memory controller: 320 bit on gts, 384bit on gtx (5x64 bit on gts, 6x64 bit on gtx)
Memory speed: 800/900MHz (Effective speed 1600/1800, data is send on the rise and fall cycle on ddr memory)

Memory bandwidth (example with the gts): 5x64 (=320bit, which means that 320 bits of data is sent with every clock pulse) x 1 600 000 000 1/s (hz) (1,6 billion clock pulses every second) = 512 000 000 000 bits/s. And since 1 byte is 8 bits, 512Gb is 64 GB.

Thanks man, I'll get to it.

EDIT: So if my calculations are correct: 320bit bus * 2106MHZ (effective) = 320 * 2 106 000 000 = 673920000000 / 8 = 84240000000

In other words, my card's memory bandwidth is 84.24GB/s
Nice!!! That matches the GTX right?

Anyone knows a piece of software that might do all that automatically?

 

[MassiveOverkill]

I read that EVGA and others may have BIOS' where the clocks are set differently than your vanilla 8800. I'm too lazy to look it up, but here's my screenie..........I used the latest RivaTuner to set my OC's and set my fan speed to 100% when my card hits 62C

 

[SuperKeijo]

Thanks man, I'll get to it.

Anyone knows a piece of software that might do all that automatically?

If you want to know the bandwidth of your overclocked memory, just divide the new frequency with the stock one and then multiply it with the stock memory bandwidth. Example, memory overclocked at 1950MHz:

1950/1600 (or 975/800) x 64 = 78GB/s

 

[MrSneis]

I run 640/2000 with 90% fan

Breaking over 11000 in 3dm06 is awesome.

 

[pagkalis]

I read that EVGA and others may have BIOS' where the clocks are set differently than your vanilla 8800. I'm too lazy to look it up, but here's my screenie..........I used the latest RivaTuner to set my OC's and set my fan speed to 100% when my card hits 62C

I don't have a vanilla 8800. I have an eVGA Superclocked

Am I reading this correctly? It is at core = 700 that the actual core jumps to 705 ?

 

[pagkalis]

If you want to know the bandwidth of your overclocked memory, just divide the new frequency with the stock one and then multiply it with the stock memory bandwidth. Example, memory overclocked at 1950MHz:

1950/1600 (or 975/800) x 64 = 78GB/s

Brilliant! That is so much easier.

Thanks SuperKeijo

2 hours of googling and I couldn't come up with this simple bit of information.
However, this second formula applies only to this card right?
For all other cards, apply the first?

 

[ShiningHolden]

I run 640/2000 with 90% fan

Breaking over 11000 in 3dm06 is awesome.

I thought under 12,000 was bad!
I get 11,800 with my CPU, RAM, and GPU overclocked.

I am going to do all of the core and memory jumps. Stay tuned.

Core Clock Jumps:
712 jumps to 720.
693 jumps to 702.
692 to 680 stays at 684.
679 jumps to 675.
661 jumps from 675 to 648.

496 - 508 = 504
509 - 526 = 513
527 - 553 = 540
554 - 571 = 567
572 - 584 = 576
585 - 603 = 594
604 - 616 = 612
617 - 634 = 621
635 - 661 = 648
662 - 679 = 675
680 - 692 = 684
693 - 711 = 702

This is with memory at STOCK. (792)

I will do memory later.

Anyone knows a piece of software that might do all that automatically?

I could program one in C++ easily, if you would like.

Am I reading this correctly? It is at core = 700 that the actual core jumps to 705 ?

At 693 the core jumps to 702.

 

[pagkalis]

496 - 508 = 504
509 - 526 = 513
527 - 553 = 540
554 - 571 = 567
572 - 584 = 576
585 - 603 = 594
604 - 616 = 612
617 - 634 = 621
635 - 661 = 648
662 - 679 = 675
680 - 692 = 684
693 - 711 = 702

This is with memory at STOCK. (792)

I will do memory later.

That's the stuff!
Good man.
I will contact the author of the guide and give him your data. He should credit you.

I could program one in C++ easily, if you would like.

Oh, yes pretty please!
(For calculating the bandwidth of any card, right?)

 

[SuperKeijo]

However, this second formula applies only to this card right?
For all other cards, apply the first?

It applies to all memory in general, system RAM also if you like. DDR400 has a bandwidth of 3,2GB/s. DDR2 667 has a memory frequency of 667MHz. 667/400 x 3,2 = 5,3GB/s.

You just need to know the stock MHz, stock bandwidth and overclocked MHz and you can calculate the overclocked bandwidth.

 

[ShiningHolden]

Oh, yes pretty please!
(For calculating the bandwidth of any card, right?)

I am doing it right now.
Yes. You input your effective memory speed, and it outputs your bandwith.

It applies to all memory in general, system RAM also if you like. DDR400 has a bandwidth of 3,2GB/s. DDR2 667 has a memory frequency of 667MHz. 667/400 x 3,2 = 5,3GB/s.

You just need to know the stock MHz, stock bandwidth and overclocked MHz and you can calculate the overclocked bandwidth.

Right now, I am using this formula to figure out the stock:
((StockGTXMemorySpeed * 2) * (GTXMemoryBusWidth/8)/1000)
That returns 86.4 GB/s.

If I want to do overclocked, it is
((OverclockedGTXMemorySpeed/StockGTXMemorySpeed) * 86.4)) ?

 

[pagkalis]

It applies to all memory in general, system RAM also if you like. DDR400 has a bandwidth of 3,2GB/s. DDR2 667 has a memory frequency of 667MHz. 667/400 x 3,2 = 5,3GB/s.

You just need to know the stock MHz, stock bandwidth and overclocked MHz and you can calculate the overclocked bandwidth.

That's what I thought.
But that won't always be the case.
It's best to have a generic equation that can produce the result with fewer input data.

 

[reswob]

Is this right? evga superclocked and regular 640mb GTS is the same price?

http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DEPA=0&Description=evga+8800gts+640&x=0&y=0

 

[pagkalis]

Is this right? evga superclocked and regular 640mb GTS is the same price?

http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&DEPA=0&Description=evga+8800gts+640&x=0&y=0

Get it now before they realise their mistake!

There is a 99% chance it too will be able to do 648-1566-2106

 

[ShiningHolden]

Get it now before they realise their mistake!

There is a 99% chance it too will be able to do 648-1566-2106

648 is easy stuff man! I did 650 on stock air.
2106? You sure on that? That seems good!

Here is the program I promised:

EDIT: I have the program, but, how can I attach it here? I will post anti-virus results in case anyone is wondering.
Until then, here it is:
http://universal-chess.com/muffinfl...mory Bandwith Calculator by ShiningHolden.exe

File: nVIDIA_8800GTS_and_8800GTX_Memory_Bandwith_Calculator_by_ShiningHolden.exe
Status:
OK
MD5 cd318910a9e9d7c6c7a109a9572e49f1
Packers detected:
-

Scan taken on 19 May 2007 19:55:38 (GMT)
A-Squared
Found nothing
AntiVir
Found nothing
ArcaVir
Found nothing
Avast
Found nothing
AVG Antivirus
Found nothing
BitDefender
Found nothing
ClamAV
Found nothing
Dr.Web
Found nothing
F-Prot Antivirus
Found nothing
F-Secure Anti-Virus
Found nothing
Fortinet
Found nothing
Kaspersky Anti-Virus
Found nothing
NOD32
Found nothing
Norman Virus Control
Found nothing
Panda Antivirus
Found nothing
Rising Antivirus
Found nothing
VirusBuster
Found nothing

 

[PCduster]

I had posted a link earlier in the thread, but I came across a gem that I really want to share!

link


It pretty much answers any questions you may have when it comes to OC'ing these cards..

BTW, nice clocks!

 

[pagkalis]

648 is easy stuff man! I did 650 on stock air.
2106? You sure on that? That seems good!

Here is the program I promised:

EDIT: I have the program, but, how can I attach it here? I will post anti-virus results in case anyone is wondering.

You're not paying attention to your own work!

650 = 648, in fact 657 = 648

Anyway, upload the file to sendspace and post the link here.

 

[pagkalis]

I had posted a link earlier in the thread, but I came across a gem that I really want to share!

link


It pretty much answers any questions you may have when it comes to OC'ing these cards..

BTW, nice clocks!

Another superb link!

Madshripms is one of my daily visits, I probably missed that because I didn't own a 8800gts at the time

Hmmm, they don't even push the core to 648.
Apparently I should be able to push the shader clock to 1620. I will try it now and post in a while.

 

[ShiningHolden]

You're not paying attention to your own work!

650 = 648, in fact 657 = 648

Anyway, upload the file to sendspace and post the link here.

I just retested that, and, my data is right?

Anything between 635 and 661 will be 648.

I think I am going to take this project to another level, and have the program read your card type, and your memory speed, and tell you your bandwith.

 

[pagkalis]

I just retested that, and, my data is right?

Anything between 635 and 661 will be 648.

Yes, that's right.

I think I am going to take this project to another level, and have the program read your card type, and your memory speed, and tell you your bandwith.

Ooooooohhh, nice!

But I have another request of you.

I think raising the Shader clock is going to be easy for me. Did you get another reading higher than 1620?
I have already achieved that and it seems rock solid, so I want to try higher.

 

[ShiningHolden]

Yes, that's right.
Ooooooohhh, nice!

But I have another request of you.

I think raising the Shader clock is going to be easy for me. Did you get another reading higher than 1620?
I have already achieved that and it seems rock solid, so I want to try higher.

The shader clock is tied to the core clock speed.
If your core clock goes above 702, which is what is still 1620 (I will do the same thing I did fo core clock for shader and memory in a few.) then it will rise.


Are you saying you manually raised the shader speed, and not the core nor memory?
If so, how did you do that?

 

[pagkalis]

The shader clock is tied to the core clock speed.
If your core clock goes above 702, which is what is still 1620 (I will do the same thing I did fo core clock for shader and memory in a few.) then it will rise.


Are you saying you manually raised the shader speed, and not the core nor memory?
If so, how did you do that?

I copied the BIOS with Nibitor3.4a, changed that value alone, flashed the card with it and voila!

Total time < 3 mins

Here is a pic confirming everything:



And here is NiBiTor 3.4a in action:




A piece of warning!

With the shader at 1620 the card will get warmer. After about half an hour of scanning for artefacts with ATItool mine topped at 81 C (no case PC)
(but the scan process is very intense, normal gaming is not that hard on the card, you should get lower temps than that)

 

[Odin75]

After getting motivated to overclock my card as soon as I get it. Will I lose my warranty. I've read a few times that EVGA will still warrant your card if you overclock it, but I'm not completely sure. Because I mean, you don't want to spend $400 on a card, and not having the security that it'll work the next day.

 

[pagkalis]

UPDATE 1
If you raise the Shader clock before overclocking, it won't work.

Overclocking core and/or memory after that will raise the shader even further than you already have.

The shader needs to be overclocked last, after you have discovered your max core + max memory, and all 3 settings together through a modification of the card's BIOS.


UPDATE 2
Raising the Shader to 1620 (648-1620-1053 instead of 648-1566-1053) has given me another 29 points in 3DMark06 1.10
(although to be fair, I think my CPU is holding me back: 9*275=2475 AMD X2 3800+)

I have raised fan to 74% and I am retesting now.


UPDATE 3
I've been playing STALKER for almost an hour at 648-1620-1053 with fan at 74%, absolutely no problems.


UPDATE 4
Again, playing STALKER for more than half an hour at 648-1620-1053 with fan at stock 60%, absolutely no problems. Temps did not go above 75 C.


UPDATE 5
Increased the Shader to 1674 and gained exactly another 29 points in 3DMark06 1.10, just like with the jump from 1512 to 1620.
I played Stalker for a no more than half and hour and noticed nothing weird. ATItool reports artefacts immediately but I can't see any in-game.

 

[ShiningHolden]

I am testing the highest clock and memory speed I can get.
After that, I will then test overnight to see if it is COMPLETELY stable.

Then, I will save it into the BIOs. I am highly against BIOs flashing for some reason.

Then, I will see if I can beat your 1620 shader clock speed.

I will only temper with my shader clock speed, after I know I have a ROCK SOLID core/memory overclock.

 

[pagkalis]

The thing is that the shader clock is much more flexible than the core clock.
EDIT: I got the info from the Madshrimps article (once again, superb link PCduster )
At core = 702, shader = 1674

I just saw the link to the program. You should make a new post if you are not the latest one.
I had to spent an entire night away from it. Still, you made it 8800 specific. Weren't you able to implement the original equation supplied by SuperKeijo?

Memory controller: 320 bit on gts, 384bit on gtx (5x64 bit on gts, 6x64 bit on gtx)
Memory speed: 800gts, 900gtx (Effective speed 1600gts, 1800gtx, data is send on the rise and fall cycle on ddr memory
Memory bandwidth (example with the gts): 5x64 (=320bit, which means that 320 bits of data is sent with every clock pulse) x 1 600 000 000 1/s (hz) (1,6 billion clock pulses every second) = 512 000 000 000 bits/s. And since 1 byte is 8 bits, 512Gb/8 = 64 GB.

So instead of making it GTS/GTX specific, make it 256 / 320 / 384 / 512 bus width specific.

P.S. I like the icon. How do you get one there?

 

[dot_Zen]

Thx for the links PCDuster, good reads!

[Snip..] Tony @ TheTechRegistry for 8800 Overclocking

[Snip..]
MadShrimps 8800 Series Overclocking Guide


It pretty much answers any questions you may have when it comes to OC'ing these cards..

BTW, nice clocks!

After reading through these, I decided to head back to the "lab". (we need more smiley's! Evil scientist woulda been perfect here)

My results? 657 (648 effective) Core clock, 1512 (My shader clock seems to be stuck!), and 1066mhz (1053mhz effective) memory; all scanned for artifacts for 1 hr. via ATI Tool. I'll check some benchmarks later to confirm stability, so far so good.

Not too shabby, still thoroughly impressed by this card!

 

[pagkalis]

Are those you max figures for core + mem?

If so, once you have them, you can set the Shader higher through a BIOS flash.

 

[dot_Zen]

I think so, wasn't acting too friendly any higher. But I didn't test the core and mem separately to find out which was causing artifacts. @ 658 I'd artifact around the 14 min. mark.

But, I'm curious--I thought, from reading those links, the shader scales with the core? I'm not completely opposed to flashing the BIOS, but I'd like to know why I have to force the shader clock to budge.