How to Modify Your HD2900 BIOS Clock Frequencies by Hex File

[super dank]

7.12 drivers dont work with my modded bios' and ati overdrive only lets me clock mem to 900

7.11 modded bios blew away my 7.12 stock bios with overdrive by like 1000 pts

Odd, I installed the catalyst 7.12 when it came out and nothing seemed to change.

[ZenEffect]

Odd, I installed the catalyst 7.12 when it came out and nothing seemed to change.

cat 7.12 does not work with my bios and thus the difference.

[Manicdan]

ok, after playing with flash attempts i get the 0FL01 error. i belive my msi board needs the checksum to be identical as flashing a downloaded bios worked fine.

this is my bios
http://www.techpowerup.com/vgabios/8...12.070426.html

if someone could/has increased just the voltage from stock to 1.3 and correct the checksum that would be great, i figure its not that hard to do. but im not having much fun with hex editors

[akabane]

It works, confirmed as well.
Upped the voltage on Powerstate 2 & 3 to 1.300 V.

Think I also found the place for Vram and Vddq in the bios - but I dont see any application for this yet.

I might be interested in knowing where vram and vddq are located because my GDDR3 dont go higher than 837 Mhz at stock voltage.

Let me experiment your findings

[roger_h99.nor]

Guys, need some help on this one, my 2900 pro/xt is temporary out of action. Did a bios edit (as many times before) and tried to edit the 2D voltage from 1.00 to 0.850. (Yes, I did it the right way)
Got an error (which I don't remember). After reboot it was silence and darkness.
Well, no problem, I'll just do a blindflash. Well, this did not work - cause there is no sign of pc booting (no beeps, no nothing).Any ideas, before I get myself a cheap PCI card? Thanks.

Card revived with help from a PCI card. What bothers me is that it seems impossible to flash with a modded bios anymore. Flashed my card many times with my old mobo (P5WDH), problems started with new mobo - P5K Premium.

Don't get it
EDIT: Figured it out - CRC has to match for a sucsessful flash. (not the case on my late 975 board.)

[roger_h99.nor]

I might be interested in knowing where vram and vddq are located because my GDDR3 dont go higher than 837 Mhz at stock voltage.

Let me experiment your findings

Suggest using Atitool to adjust vmem and vddq - they stick - not like vcore.

[Truckchase!]

Odd, I installed the catalyst 7.12 when it came out and nothing seemed to change.

Which bios mod method are you using?

- "Quantum force bios" ?
- Modding standard vCore using the "Quantum Force" method? (i.e. raising voltages across all pre-defined settings)
- Modding standard vCore using direct edits? (i.e. "hard coding" the vCore values for each power profile)

I'm using the third method, and I suspect that might be what is causing the problem with the 7.12 drivers. I haven't had time to experiment yet tho...

[roger_h99.nor]

@Truckchase!
Do you have to correct the checksum before you flash the modded bios?
Do you have to use the '-f' switch?

Thx.

[Truckchase!]

@Truckchase!
Do you have to correct the checksum before you flash the modded bios?
Do you have to use the '-f' switch?

Thx.

Good point; no, I did NOT correct the checksum. I did have to use -f. We'll call that point #4.

Hopefully I'll have a chance to mess around with it tonight. I've been having so much fun playing Stalker that I can't bring myself to flash the bios back and forth lately.

[Manicdan]

i was able to make a bios with just the 3D volts up to 1.35 and still pass the checksum error. after a quick OC session i got my old high of 850core to a new high of 941. im not sure what my old one really was cause i found out theres only a change every 14, and 955 would artifact.

thanks for all the help guys, im not pushing about 100 more Mhz thanks to your work

[roger_h99.nor]

Thanks Truckchase.

Been bussy this evening - *wife agitated*

Well, after approx 20 flashes with and without correct checksum -
Not one sucsessful flash with incorrect checksum on this mobo. Leads me to belive that the chipset is a player in this game as well.
(I have a PCI card, luckily..)

Fair enough - only that correcting the crc is a real pain in the ass - is the any other way than just guessing the HEX?
---
One a sidenote: 1.35V dos not give me higher temps than +50 (C). Would very much have the opportunity to give this chip a little more juice. If interested - have a look at the 3870-thread; ppl there feeding the chip +1.50V.

[ZenEffect]

Which bios mod method are you using?

- "Quantum force bios" ?
- Modding standard vCore using the "Quantum Force" method? (i.e. raising voltages across all pre-defined settings)
- Modding standard vCore using direct edits? (i.e. "hard coding" the vCore values for each power profile)

I'm using the third method, and I suspect that might be what is causing the problem with the 7.12 drivers. I haven't had time to experiment yet tho...

im using the 1st method as i am LAZY, but i correct the crc... still takes a big dump in 7.12... guess im just gonna wait for 7.13 or whatever they are going to call it

[ZenEffect]

about us abit users and our checksum fixing.

ive figured out the math behind it, its rather simple actually.

#1 there are numbers and letters in order from least to greatest is 0-9 then A-F (representing 10, 11, 12, 13, 14, 15) then it loops back to 0

#2 when this numbering system is taken into account you can compare the checksums to see what the difference (#) between a modified and unmodified bios checkums... i.e. (just did this 1 in 1 try) unmodified bios is 0xD200 and the modified bios is 0xD1D1.. thus the checksum numbers are ordered as follows... 0xD200 > 0xD1D1.

so to find the difference between them (an actual numerical value) you can count/calculate it. for example the difference between 0xD1D1 and 0xD1D2 = +1, 0xD1D3= +2... 0xD1DF= +14... 0xD1E0= +15... 0xD200 = 47.

so the numerical difference between 0xD1D1 and 0xD200 is 47

47 converted to hex is 2F

so what do we do? we insert the calculated checksum difference in hex (2F) in 2 00's in the no power cord message to get matching checksums.

finally, no more guesswork!

im quoting myself to answer the guy above me

[ZenEffect]

about us abit users and our checksum fixing.

ive figured out the math behind it, its rather simple actually.

#1 there are numbers and letters in order from least to greatest is 0-9 then A-F (representing 10, 11, 12, 13, 14, 15) then it loops back to 0

#2 when this numbering system is taken into account you can compare the checksums to see what the difference (#) between a modified and unmodified bios checkums... i.e. (just did this 1 in 1 try) unmodified bios is 0xD200 and the modified bios is 0xD1D1.. thus the checksum numbers are ordered as follows... 0xD200 > 0xD1D1.

so to find the difference between them (an actual numerical value) you can count/calculate it. for example the difference between 0xD1D1 and 0xD1D2 = +1, 0xD1D3= +2... 0xD1DF= +14... 0xD1E0= +15... 0xD200 = 47.

so the numerical difference between 0xD1D1 and 0xD200 is 47

47 converted to hex is 2F

so what do we do? we insert the calculated checksum difference in hex (2F) in 2 00's in the no power cord message to get matching checksums.

finally, no more guesswork!

Thanks Truckchase.

Been bussy this evening - *wife agitated*

Well, after approx 20 flashes with and without correct checksum -
Not one sucsessful flash with incorrect checksum on this mobo. Leads me to belive that the chipset is a player in this game as well.
(I have a PCI card, luckily..)

Fair enough - only that correcting the crc is a real pain in the ass - is the any other way than just guessing the HEX?

page 6

[roger_h99.nor]

Thanks ZenEffect.
(Can't belive I missed that one)

[ZeRo4u]

page 6

Well its all nice and stuff but this is my method:

My original crc was 0xDA00

Moddedbios crc was 0xD97C

now use windows calculator goto view and set it to scientific/hex then calculate this:

DA00 - D97C = 84

Enter 84 in a line of text where some "00" are and done
And ur bios is rdy to use with atiwinflash :P

[binormalkilla]

So do you guys find that OCing the memory helps with gaming FPS at all? I have mine running at 945 MHz with 1.35V and the memory at stock 1075....I'm testing 1153 to see though. I wonder if the timings are affected if I flash the BIOS instead of OCing with software....

[Compiller]

For correcting the CRC there is automatic utility one from Ray Adams X-BIOS Utility, other from One Russian coder. All two in this archive.
Syntax for first
crcbios oldfile newfile
second show the CRC and say if it is right.
The Rabit can recalculate CRC also.

http://rapidshare.com/files/58378722/CRC_BIOS.ZIP

[Circaflex]

anyone willing to cook up a HIS 512MB XT Bios with a voltage bump on the 3d clocks for me with a fixed checksum for abit boards? Pretty please?

[ZenEffect]

anyone willing to cook up a HIS 512MB XT Bios with a voltage bump on the 3d clocks for me with a fixed checksum for abit boards? Pretty please?

dont be so lazy... read the 5 posts before yours and dowit yourself!!

[ZenEffect]

Very good I would say

About 300pts short of my '06

an interesting thought... your gpu clock is way higher than mine, though my mem clocks are faster. when i ran 3dmark06 with the q6600 at 3.8, i got the extra 300 pts. is it possible (as was said before on this forum) that oc'ing the gpu's is not having the effect it should? (i know the math tells us otherwise, but 3dmark is saying a different story)

[ZenEffect]

catalyst 8.1 is having same problems switching to 3d mode just like 7.12. mabye the modded bios is having something to do with this? FOR THOSE OF YOU WHO GOT THESE TO WORK, WHAT BIOS DID YOU USE TO MOD AND HOW EXACTLY DID YOU MOD IT (direct hex edit or the quantumforce bios editor)????

this is really frustrating being stuck on 7.11

[Truckchase!]

catalyst 8.1 is having same problems switching to 3d mode just like 7.12. mabye the modded bios is having something to do with this? FOR THOSE OF YOU WHO GOT THESE TO WORK, WHAT BIOS DID YOU USE TO MOD AND HOW EXACTLY DID YOU MOD IT (direct hex edit or the quantumforce bios editor)????

this is really frustrating being stuck on 7.11

Confirmed here. I'm working on a fix, but I don't have any leads thusfar so...

[Truckchase!]

No love yet. Here's things that don't have any effect:

- Setting all powerplay settings save #2 to the 3d speed
- Making sure the crc checksum matches the original bios

The best I've been able to do is get the 3d mode all the time by setting #2 to my 3d settings as well. I'm giving up for tonight, time for chores.

[ZenEffect]

No love yet. Here's things that don't have any effect:

- Setting all powerplay settings save #2 to the 3d speed
- Making sure the crc checksum matches the original bios

The best I've been able to do is get the 3d mode all the time by setting #2 to my 3d settings as well. I'm giving up for tonight, time for chores.

what are you using to edit the bios? im using quantum force bios editor to no avail.