How to Modify Your HD2900 BIOS Clock Frequencies by Hex File

[TouGe]

Touge have you been able to perceive any improvements in benches. Like in 3dmark or crysis??

I say so, cause in my case overclocking does not yield ANY improvement in benches or fps.

There must be something bottlenecking you then. If not hardware, then software related.

I would agree. Even bumping to 800/900 on the stock coolers gained several hundred points in 3dmark06 for me, and that was on my E6600. My 3dmark06 score is now over 20K.

Yeah, there definitely is a good bump in 3DMark05/06 w/ higher core clocks. If you are not seeing improvements in benchs then you've got something holding you back, what hardware are you using?

[Guz]

Yeah, there definitely is a good bump in 3DMark05/06 w/ higher core clocks. If you are not seeing improvements in benchs then you've got something holding you back, what hardware are you using?

intel e6600 at 3.2ghz, intel badaxe 2, 2xhd2900 in crossfire, 4gb of ram. I always get 14,000 3dmarks with any bios be it at default speeds or overclocked.

[super dank]

intel e6600 at 3.2ghz, intel badaxe 2, 2xhd2900 in crossfire, 4gb of ram. I always get 14,000 3dmarks with any bios be it at default speeds or overclocked.

Your cpu clock speed is bottlenecking you, plain and simple. Another 500-600mhz would resolve it, and get you closer to 18,000.

[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!

[Truckchase!]

finally, no more guesswork!

Thanks for the breakdown!

[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

[Guz]

Your cpu clock speed is bottlenecking you, plain and simple. Another 500-600mhz would resolve it, and get you closer to 18,000.

If that were true then why crysis benchmark at 1920 does not bench any higher? Crysis is totally gpu bound.