Memory Timings for Gf6800

Phill-7 · **Memory Timings for Gf6800 -** 04-07-2005, 13:51 | posts: 44 | User is Offline

I have Albatron Gf6800, and I cannot overclock the memory... It's stuck on 780.

Does anybody know how to relax the timings using NiBitor 2.0?

jimmor · *Last edited by jimmor; 04-07-2005 at 16:12.*

Quote:

Originally posted by Phill-7
I have Albatron Gf6800, and I cannot overclock the memory... It's stuck on 780. Does anybody know how to relax the timings using NiBitor 2.0?

Using NiBiTor v2a, and assuming the timings of your 6800nu to be,

Timing0 = 10110A05
Timing1 = 07040105
Timing2 = 05032400

then you should set them to,

Timing0 = 0A150A06
Timing1 = 06030105
Timing2 = 06032400

And depending on the memory chips fitted to your card, you may be able to overclock memory to 900+, especially if yours happen to be 2.2ns types like on my 6800LE. Obviously therefore don't expect as high an overclock if your card just happens to have 2.8ns memory chips.

Also, the new timings should give an overall performance improvement !

Give them a try, and let us know what your card achieves ?

However, because of the incorrect way that NiBiTor v2 currently displays Timings for a 6800LE/NU, it will be necessary to use the HEX EDITOR function to change the binary values. And you will find the correct timing strings for your card immediately before the ones displayed in the NiBiTor timings tab. So if you know how to use NiBiTor and its hex editor, the changes are extremely easy.

Phill-7 · 04-08-2005, 03:38 | posts: 44 | User is Offline

Thanx, jimmor . But actually my original timings are -
T0 - 060F1B15,
T1 - 09010509,
T2 - 20250407.
That's what Nibitor shows on "Timings" page.
Would you be so kind as to tell me how can I find the heeded values in hex editor and how exactly can I edit it. Please. I've never used it before...

P.S. Generally, it would be nice to create a thread with a little collection of moded bioses for 6800NU, like you did once with 5900XT (it was my favorite thread)

jimmor · *Last edited by jimmor; 04-09-2005 at 11:14.*

Quote:

Originally posted by Phill-7
Thanx, jimmor . But actually my original timings are -
T0 - 060F1B15,
T1 - 09010509,
T2 - 20250407.
That's what Nibitor shows on "Timings" page.
Would you be so kind as to tell me how can I find the heeded values in hex editor and how exactly can I edit it. Please. I've never used it before...

P.S. Generally, it would be nice to create a thread with a little collection of moded bioses for 6800NU, like you did once with 5900XT (it was my favorite thread)

Then you obviously didn't read my above posting, since I said that NiBiTor v2a does not display correct timings for a 6800LE or NU card/bios !

NiBiTor for whatever reason just locks itself onto the last timing string in a list of many timing strings.

The strings you need to change, using a suitable HEX Editor, are those stored in the bios immediately before the ones that NiBiTor shows.

So what you need to do is open your bios with NiBiTor, then at the "Tools" tab select NiBiTor's "HexView" option. After which a popup Hex Editor will appear.

Now select NiBiTor's "Timings" tab and firstly put cursor on the "Timing0" string. When you do this, you will see a binary string in the Hex Edtior being highlighted in green. The green string should have exactly same value as shown a Timing0 option on Timings tab. However it will look different, but only because it is stored in the bios, as the reverse of what NiBiTor actually displays.

Now all you have to do is look in the hex editor at the 8 bit binary string stored immediately before the green string, and you will see it is same as the value I posted above for 6800nu cards. Now just change this 8 bit string to what I posted above.

Do same procedure for "Timing1" and "Timing2", then save and flash the modded bios.

EDIT:

Glad you made good use of moded 5900 bioses thread. However if you look closely at that thread you will see that although I probably supplied most of the bioses, I didn't actually host them. That function was down to the help and good graces of Dr.Infern0.

So for a 6800 moded bioses thread to work, a suitable host is also be required; along with the good graces of Guru3D forum management, of course ?

Alexstarfire · 04-08-2005, 08:39 | posts: 7,859 | Location: Georgia | User is Offline

Think you can provide me with some tighter timings for a PNY 6800 GT card?
In case you don't already know the timings for a 6800 GT mine are:

T0 - 060F1B15
T1 - 09010509
T2 - 20250407

As shown in NiBiTor, but are:

T0 - 060D1513
T1 - 06010407
T2 - 00240406

The way you show how to find it for the 6800 NU/LE cards. I wasn't sure which was corret so I posted both. I assume that NiBiTor is showing them correctly since you said it reports the 6800 NU/LE one incorrectly.

I appreciate any help that you give me. Thanks in advance.

jimmor · *Last edited by jimmor; 04-09-2005 at 11:49.*

Quote:

Originally posted by Alexstarfire
Think you can provide me with some tighter timings for a PNY 6800 GT card?
In case you don't already know the timings for a 6800 GT mine are:

T0 - 060F1B15
T1 - 09010509
T2 - 20250407

As shown in NiBiTor, but are:

T0 - 060D1513
T1 - 06010407
T2 - 00240406

The way you show how to find it for the 6800 NU/LE cards. I wasn't sure which was corret so I posted both. I assume that NiBiTor is showing them correctly since you said it reports the 6800 NU/LE one incorrectly.

I appreciate any help that you give me. Thanks in advance.

NiBiTor v2a usually shows the last timing string in a row of timing strings. So as I said before, the correct string for a 6800LE/NU card, is the 8 bit string stored immediately before the one shown by NiBiTor.

Your card/bios uses different values, but same rule for finding it is probably also same as indicated for LE/NU cards.

However best method for identifying which timing strings your card currently uses, is to look in Rivatuner's Diagnostic report for following,

$0200100220 NV_PFB_TIMING0 : 060F1B15
$0200100224 NV_PFB_TIMING1 : 09010509
$0200100228 NV_PFB_TIMING2 : 20250407

Where I have shown GT timings only as an example.

So you just look in bios for the strings identified by Rivatuner, and change them to whatever you want.

Also, the timings set for a GT card are generally very good for performance. However, you can set them same as for a Ultra bios and probably get some more memory speed.

The timings I supplied for 6800nu were looser in some areas to allow slightly higher overclock, but tighter in others to give better performance at chosen speed. These timing should only be used with LE and NU cards, and will work best for cards that have 2.2ns memory chips. If a card has 2.8ns chips for example, then even tighter timings could be used because of the likelyhood of only being able to overclock at levels lower than 900..

There is no one answer for all cards/bioses, so a bit of trial and error is usually required for those that want best from any particular setup.

Phill-7 · 04-08-2005, 14:20 | posts: 44 | User is Offline

Yesssss! I've got it working on 900MHz!

3DMarks run smoothly and so HL2 and FarCry.
jimmor - THANKS!

If there would be some more relaxed timings, don't hesitate - post'em!

Alexstarfire · 04-08-2005, 15:33 | posts: 7,859 | Location: Georgia | User is Offline

Note to self: Don't touch timings

Man, I'm lucky to have my card still working after trying that out. I changed the timings and flashed. It all looked good until I restarted, then BAM. There was so much corruption that about the only thing I could notice was when stuff changed colors.

I'm not sure if it's directly because of the change in timings as when I originally flashed back to the unmodified BIOS it didn't work. Then when I went back and used WFFlash instead of NVFlash. After I used ole trusty WFFLash it came back to this. Now I can go flash to the ocrrect BIOS and change it back to where it was.

Gotta go put all my modified crap back on. Thought I was gonna have to RMA it so I put all the stock crap back on. Once I couldn't flash the original BIOS back on with NVFlash I got scared.

I'll leave modifying stuff like that up to you pros, Jimmor.

desdick · 04-08-2005, 20:23 | posts: 994 | Location: Singapore | User is Offline

How do you fing the type of memory you are using?

desdick · 04-08-2005, 20:44 | posts: 994 | Location: Singapore | User is Offline

Is artifacts in games due to memory timings?

sharpturn · 04-09-2005, 10:34 | posts: 60 | Location: Cleveland, OH | User is Offline

Jimmor,

Many thanks for the info. I just applied those timings you listed to my eVGA 6800 NU. My memory is now stable at 900 Mhz and I noticed an improvement in Far Cry.

Now all I need to figure out is why my GPU can only reach 370 Mhz on my new A64 system and I will be a happy camper. I used to be at 414 Mhz on my Athlon XP system.

jimmor · 04-09-2005, 11:19 | posts: 4,528 | Location: Scotland | User is Offline

Quote:

Originally posted by Alexstarfire
Note to self: Don't touch timings

Man, I'm lucky to have my card still working after trying that out. I changed the timings and flashed. It all looked good until I restarted, then BAM. There was so much corruption that about the only thing I could notice was when stuff changed colors.

I'm not sure if it's directly because of the change in timings as when I originally flashed back to the unmodified BIOS it didn't work. Then when I went back and used WFFlash instead of NVFlash. After I used ole trusty WFFLash it came back to this. Now I can go flash to the ocrrect BIOS and change it back to where it was.

Gotta go put all my modified crap back on. Thought I was gonna have to RMA it so I put all the stock crap back on. Once I couldn't flash the original BIOS back on with NVFlash I got scared.

I'll leave modifying stuff like that up to you pros, Jimmor.

What new timings did you try ?

Hope it wasn't the ones I posted for Phill-7, because those can only be used with 6800LE and NU cards !

jimmor · 04-09-2005, 11:23 | posts: 4,528 | Location: Scotland | User is Offline

Quote:

Originally posted by desdick
Is artifacts in games due to memory timings?

Most of the time, artifacts when stressed is either, memory being overclocked too high, or, the cards temps are rising too high for the volts and speeds it is set at ?

So are you overclocking ?

And what are cards temps at, especially ambient temp ?

jimmor · *Last edited by jimmor; 04-09-2005 at 11:57.*

Quote:

Originally posted by sharpturn
Jimmor,

Many thanks for the info. I just applied those timings you listed to my eVGA 6800 NU. My memory is now stable at 900 Mhz and I noticed an improvement in Far Cry.

Now all I need to figure out is why my GPU can only reach 370 Mhz on my new A64 system and I will be a happy camper. I used to be at 414 Mhz on my Athlon XP system.

No prob's, glad to help !

And if GPU speed is limited to 370, then maybe GPU volts is too low ?

For example, my 6800LE can only overclock stable at 400 when set at 1.3v. And its current 425, with GPU volts of 1.4v.

I see your spec's show as 1.4v, but is this still true ?

EDIT:

Also, sometimes overclocking becomes reduced because of PSU supply limitations. Which can even happen when you share the cards mollex 12v supply with other active devices ?

Phill-7 · 04-09-2005, 13:24 | posts: 44 | User is Offline

Maybe I was in a hurry with my conclusions about 900MHz... It's good for 3Dmarks but not for games. Now I got it stable only on 870. But it's still good result for me...

jimmor · 04-09-2005, 13:55 | posts: 4,528 | Location: Scotland | User is Offline

Quote:

Originally posted by Phill-7
Maybe I was in a hurry with my conclusions about 900MHz... It's good for 3Dmarks but not for games. Now I got it stable only on 870. But it's still good result for me...

Considering you started hitting a wall at 780, you are still getting a good overclock with 870 ?

What you achieve depends a lot on the quality and rating of memory chips !

And remember you can always change timings further, for example you could try,

Timing1 at 06030106 or even 07030106

As I have said before, there is no single best solution for every card. So generally a little trial and error is necessary.

Phill-7 · 04-10-2005, 01:31 | posts: 44 | User is Offline

Quote:

Originally posted by jimmor
And remember you can always change timings further, for example you could try,

Timing1 at 06030106 or even 07030106

Ok, I'll try'em.

Could you please post some more examples of T0,T1 and T2?.. I would experiment... (sorry for my English)

thewiseyoda · 04-10-2005, 02:44 | posts: 309 | User is Offline

how do u know which timings are relaxed or which ones are tighter?

jimmor · *Last edited by jimmor; 04-10-2005 at 03:58.*

Quote:

Originally posted by thewiseyoda
how do u know which timings are relaxed or which ones are tighter?

With these bioses, relaxing the timing requires higher values. And conversely, tighter timings require smaller values. And sometimes the values are increased or decreased depending if you want better overclocks or just better performance at the lower stock, or a specific, clocked speed.

But since best values for all cards are likely to be different, I have no intention of turning this general discussion thread into a Fine Tuning thread for everybody's bios/card.

People interested in better performance should therefore start tweaking either, from the original bios values, or, from the slightly adjusted values I have already provided !

Phill-7 · 04-10-2005, 03:29 | posts: 44 | User is Offline

I've changed the T1 to 07030106. Now my 6800nu is stable on 900.

So far so good...

Phill-7 · 04-11-2005, 02:23 | posts: 44 | User is Offline

jimmor
I noticed that you talk about GPU voltage... So, I have one more question. I heard that NiBitor does not apply correctly the voltage values for GPU... Since mu GPU doesn't want to OC over 360MHz, I'd like to change the value to 1.4v. How can I do this using NiBitor v2a? I mean, what value I have to choose to have real 1.4V?

desdick · 04-11-2005, 06:05 | posts: 994 | Location: Singapore | User is Offline

Does this timings work on a nv41, or should I say, a geforce 6800 PCI-E?

jimmor · *Last edited by jimmor; 04-11-2005 at 09:56.*

Quote:

Originally posted by Phill-7
jimmor
I noticed that you talk about GPU voltage... So, I have one more question. I heard that NiBitor does not apply correctly the voltage values for GPU... Since mu GPU doesn't want to OC over 360MHz, I'd like to change the value to 1.4v. How can I do this using NiBitor v2a? I mean, what value I have to choose to have real 1.4V?

The basic problem with a 6800LE or NU BIOS, is that the GPU Volts Lookup Table is programmed as if for GT or U types of cards ?

Which for my 6800LE, meant that the 1.4v table option was unfortunately setting GPU at only 1.2v !

The GPU volts lookup table structure of vanilla 6800's is supposed to be same as for FX59xxx cards. For some reason only known to nvidia or their partners, the table spec for the higher 6800GT and U cards was made different ?

As an example; in order to set 1.4v with a 6800LE or NU card, it is necessary to use NiBiTor's Hex editor to change the GPU volts lookup table "8C01" (if thats what is currently stored) option to "8C03". The bottom line being that 1.4v option of LE/NU needs to be "8C03". Now when you select 1.4v with NiBiTor, you will actually get 1.4.

But as I said before; if you only want to overclock at 400, then this should be possible with the 1.3v setting.

jimmor · 04-11-2005, 06:58 | posts: 4,528 | Location: Scotland | User is Offline

Quote:

Originally posted by desdick
Does this timings work on a nv41, or should I say, a geforce 6800 PCI-E?

The rules governing timing settings will work regardless of a card having a AGP or PCI-E interface.

So as said before, check current bios timings with NiBiTor, and if same as I show for a 6800NU, then no reason why you can't try new settings !

Phill-7 · 04-11-2005, 08:34 | posts: 44 | User is Offline

Quote:

Originally posted by jimmor

...In order to set 1.4v with a 6800LE or NU card, it is therefore necessary to use NiBiTor's Hex editor to change the GPU volts lookup table "8C01" option to "8C03". Now when you select 1.4v with NiBiTor, you will actually get 1.4....

I'm confused a little... NiBiTor's Hex editor shows "8C68"...