Odd, I installed the catalyst 7.12 when it came out and nothing seemed to change.
Printable View
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
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 :confused:
EDIT: Figured it out - CRC has to match for a sucsessful flash. (not the case on my late 975 board.)
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...
@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. :D
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.
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
Thanks Truckchase.
Been bussy this evening - *wife agitated* :D
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.
Thanks ZenEffect.
(Can't belive I missed that one:slapass:)
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 :D
And ur bios is rdy to use with atiwinflash :P
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....
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
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? ;)
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):shrug:
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
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. :D
im attempting 8.1 with the 8.1 hotfix to see if the hotfix resolves this issue.
http://support.ati.com/ics/support/d...estionID=31625
8.1 hotfix, 8.1 alone does not work.. let you know in 5 min :-)
hotfix drivers DID NOT resolve this issue
Are the hotfix drivers newer than the official 8.1? I have seen people saying that they are actually older. Can anybody verify this by checking the version numbers in CCC?
do the clocks of the card revert to 2d speed with catalyst 7.12 and up with the modded bioses even if the checksum is matched on the modded bios
This seems to have everything to do with the "new" overdrive stuff introduced in 7.12. I've noticed that when the card isn't going to correctly go into 3d mode, the ATI CCC reports that "overdrive has not been initialized properly".
Still no solution. I'm thinking of trying to call ATI and see if this is on purpose on their part. I want to know if they're actively trying to discourage people from modifying BIOSes or if this is just a side effect...
im going to try different bios versions tonight.
thanks truckchase , yes only works a ok with 7.11 driver nothing higher with modded bios , shame that also tried 8.1 and same
I FIGURED IT OUT!!!!!!!
THE TRICK IS TO COMPARE 7.11 DRIVER INF FILE WITH THE NEW 8.1 AND GET RID OF SOME STUFF. HERE IS MY INF THAT I MADE. I HAVE NOT TRIED IT WITH 8.1 CCC BUT THE OLD 7.11 CCC WORKS JUST FINE *MODDED BIOS = NO NEED FOR CCC OVERDRIVE*
C:\ATI\SUPPORT\8-1_xp32_dd_ccc_wdm_enu_57717\Driver\Driver\XP_INF
THIS IS WHERE I FOUND THE FILE
I UPLOADED THE INF AS A ZIP, JUST PLACE IT WHERE I FOUND IT *SHOULD BE SAME PLACE AS I LET IT RUN ON AUTO*
extract, replace and enjoy :-)
im sure i could have chopped up this file a little less but this is my first attempt so im not sure exactly what was the culpurate but i think it might be amdpcom32.dll :up:
hiya zeneffect what you saying start the 8.1 driver only cancel once the files have been extracted leave the existing catalyst control center 7.11 and replace the file with the one you have kindly uploaded and then install 8.1 driver will run the modded bios at the modded clocks
thanks
download the modded inf file i made and replace it with the one from the directory i said before. then go to this directory : C:\ATI\SUPPORT\8-1_xp32_dd_ccc_wdm_enu_57717\Driver\Driver
and run the setup from there
btw this is from the 8.1 hotfix driver but probably works on regular 8.1 though the filename will have to be changed to the approprate one.
so in short yes.
how do i figure these things out? SMOKE WEED FOO!
interestingly enough, i lost about 400 pts on 3dmark06 :down:
back to the drawing board
http://i48.photobucket.com/albums/f2...976/foundu.jpg
this is what i narrowed it down to for driver non working thingy issue. on left is the original inf file, on right is the one i modified just now to figure out exactly what is the cause.
just add the string
HKR,, PP_ForceReportOverdrive4, %REG_DWORD%, 1
to the inf and viola!
now i gotta get rid of ccc and just use ati tray tools.
so it seems that the problem stems from the ati overdrive software. the string forces it into od4, i tried changing the 4 to a 5 and got the previous results of no 3dmode switching. so here u guys go. just add the string to the inf file and you can install THE WHOLE CATALYST SUITE. verified and tested just now :-)
Uhhhhhh why go through the trouble of all this INF modding? Just leave overdrive OFF and overclock with ATiTool it's been working great for me, 3D modes always switches
We just have our 3d speeds set in the BIOS, no manual overdrive intervention needed. It's the "new" overdrive crap in 7.12 and up that messes with modded BIOSes.
ATI Tool is flaky. I'm glad it works for you, but I don't have the same experience. Besides, being as anal as I am about performance, the fewer apps the better. :scope:
i would be happy if i could just get beta drivers, plus they probably drug test.
well done anyway i have 3 2900xts in mine so when or if ever the tri crossfire is enabled i'll be able to use the modded bios with them, atm with 8.1 no increase with having 3 cards instead of 2
i think its about time to put the gfx cards on liquid. i want a 890 core too! :p: mabye i will hit 21k in 3dmark06 afterwards :up:
you've done some good work truckchase and zeneffect on here , so thanks for sharing your insights, i think the quickest drivers in 3dmarks anyway were the 7.11 hotfix crysis driver but the 8.1's are pretty close, heres my aquamark score on an e6850 at 4.11 ghz 2 sapphire 2900xts at 893 core 980 mem with 8.1 driver and ccc with modded bios using quantum editor, so zeneffects fix definitely works, weird how 1 line of text in driver makes it work or not work
http://gbwatches.com/pics/aq237.jpg
thanks dude . i'll test it
Zen, here are those numbers I promised:
http://www.xtremesystems.org/forums/...1&postcount=18
I have read every page in this thread and still cant get my modded bios's to work with 8.1...I have 2900pro 1gb/2900xt 512mb in xfire. I have tried ever flash there is with 7.11 (pro to xt custom bioses on both and it works great) When I went to 7.12 or 8.1 I get problems mentioned before...So I try the inf. fix, but that line was already in my 8.1inf... I try that zip file you put on here, didnt work...Ive installed/uninstalled drivers, still works with 7.11, but just cant get it to work with 8.1...Would be really nice to get these working, Im still trying some things myself but any further thoughts on this issue would be awsome
(using quantum force editor, still learning this with the hex editor)
http://service.futuremark.com/orb/mu...1&c=-298598096
3dmark06 runs from last night :up:
It appears that my card is now stuck at 800/1000 1.25v after flashing using the following command:
atiflash -p 0 -newbios xxxx.bin -f
Even though GPU-Z shows a different clock if i flash a new bios, it still loads as 797/1000 1.25v when loading up 3DMark06.
Btw, this is with 8.1 drivers on Vista 32-bit.
After that, I tried the command:
atiflash -f -p 0 xxxx.bin
to no avail.
Edit: This is what I mean.
http://img352.imageshack.us/img352/870/captureze2.jpg
i would try 1 of 2 things... 1st i would try a different manufacture bios such as the asus bios or ati or vice versa. going from a ati bios to asus bios makes the system re-detect the entire card.
2nd i would try a different version of atiflash or atiwinflash
hope it helps
I know why you guys are having probs with the new drivers. You have to change the voltages for the other voltage Powerstates too, not just "3D". There are 2 additional power states for UVD decoding mode, and crucially "overdrive" mode.
Before 7.12, enabling overdrive in CCC activated 3D mode only, but afterwards they fixed it to use the overdrive setting (which might have been set higher than 3D on some factory OC'd cards)
yes zeneffects inf fix worked for me i used it on 8.1 drivers in xp with 8.1 ccc and it worked just fine
i think im on track with a new bios mod. searching techpowerup i found a msi bios that is 843c/828m 1.25volts that works with the new ccc no inf mod.
link is here
http://www.techpowerup.com/vgabios/3...512.070416.bin
im modding it for 990 mem to see if it will still work. then if it does, im going to mod the volts to 1.2 with quantum force editor and see what changes it made. after that im going to compare the msi 743c/828m to the 843c/828m to see what the differences in their bios' look like in the powerplay table. from that i should be able to crack this sucka once and for all. my feeling is HKPolice has the right idea but i gotta find out for myself if the data is there. :up:
it is now confirmed.
THE DRIVERS NEED TO BE HACKED TO ALLOW ATI OVERDRIVE TO SET MEMORY ABOVE 900
you can use any bios you want so long as the memory is below *blows* 900
voltage has nothing to do with it.. its all in the memory speed and the way ati overdrive detects it. something for sure to do with drivers or reg... imma look into that now.
so so far the inf fix is the only thing going if you want 900+ memory. ati really trying to push their new hardware it seems :mad:
thats not the case at all man. its has something to do with the drivers blocking default memory clock above 900. im trying to figure out a way to extend the slider bar so memory clocks can reach beyond 900 as in with the 3850 *3850 in girlfriend's computer.. she built it herself and it screams! :up: *
for those of you that have experienced this problem you know if you dont get the overdrive screen, your 3d does not work. this pic not only shows that i got it to work, but is functional as well
http://i48.photobucket.com/albums/f2...ttingthere.jpg
default inf file, just a standard 1.2v modded bios *im on factory cooler and thats about all it will handle and keep things at a max of 75 with my fan profile in ati tool (i like things COOL)* 833 core 880 *sigh* memory default. the only trick is to crack this mo-fo to enable the slider to go above 900 and i will be happy. im SOOOO close too....
#1.) There is NO ADDITIONAL SPECIAL BIOS HACK OTHER THAN THE USUAL STUFF, JUST THAT THE MEMORY WAS SET BELOW 900
#2.) These were the 3870x2 drivers i used to test this, but every other version above 7.11 works
#3.) I DID NOT MODIFY THE INF FILE AS I HAD FIGURED OUT PREVIOUSLY, THIS WAS JUST THE STANDARD INSTALL
so yeah... drivers blocking memclocks above 900, but if i can trick the drivers into putting the same slider settings as the 2900xt's offspring then we are in business :)
my guess is the answer either lies in my registry or the inf file
too bad ati isnt letting me beta test anything *I KNOW YOU GUYS READ THIS* even though ive submitted like 1000000000000x applications...
http://i48.photobucket.com/albums/f2...976/hahaaa.jpg
getting there :up:
forcing 3850 or 3870 doesnt work :down:
nice going again zeneffect so as long as the modded bios has a memory clock below 900 , the overdrive panel will work on 8.1 driver without having to mod the inf file as before
if its there zen you'll find it , can you overclock the 2 cards in crossfire on the overdrive with the later ccc
so if I use 7.11 drivers i can use a bios with higher than 900 memory and everything will work? or of I use the INF in 8.1 it will work?
I have tried flashing so many different bios versions and tried omega and 8.1 driver and rivatuner and atitool. the only time I can do anything stable is when i just use display driver and rivatuner and i am good for 850/1000...
Only other thing I can do is max out 8.1 overdrive at 858/900 and thats fine also. The minute I try and go over 900 with any means It eventually screws up somehow. This $170 512bit card is more trouble than its worth lol.
I guess I will try 7.11 and rivatuner and see if that works.
i'm on the 8.2 drivers. i made sure all old stuff was deleted and i just noticed that the 8.2 drivers have the "HKR,, PP_ForceReportOverdrive4" line in there already. i checked it against the link you put up for the 8.1 for vista and in that, they are the same...i noticed that the line isn't in the same place as in xp (after all the fleshtone stuff). so i'm guessing with 8.2 the inf is already fixed?
Take a look under what section the "HKR,, PP_ForceReportOverdrive4" is noted. You'll notice it isn't in the right section to work properly and it doens't include the full string.
Just add the full string (HKR,, PP_ForceReportOverdrive4, %REG_DWORD%, 1) between:
HKR, "UMD", AAF_Mapping_SET, %REG_SZ%, "0(Box:2,Narrow-tent:4,Wide-tent:6) 2(Box:2,Narrow-tent:4,Wide-tent:6) 4(Box:4,Narrow-tent:6,Wide-tent:8,Edge-detect:12) 8(Box:8,Narrow-tent:12,Wide-tent:16,Edge-detect:24)"
and
HKR,, DALNonStandardModesBCD1, %REG_BINARY%,07,20,04,80,00,00,00,60,07,20,04,80,0 0,00,00,75,07,20,04,80,00,00,00,85,08,48,04,80,00, 00,00,60,08,48,04,80,00,00,00,75,08,48,04,80,00,00 ,00,85,12,80,07,20,00,00,00,60,12,80,07,20,00,00,0 0,75
I don't know if it matters if its placed somewhere else, aslong as its added in the section:
[ati2mtag_R600_SoftwareDeviceSettings]
When you now set the memory clock above 900 in e.g. RivaTuner, CCC overdrive will report the setting you applied in RivaTuner.
Don't know if it works with XP :shrug: , It works fine here with Vista X64 ;)
I have a wierd problem when installing those 8.2 drivers.. my 3d clockspeed switches to 2mhz.. but my ram wil run on 1100mhz :S..
Wil this extra line in the inf file help me get rid of that problem? So that my clock speed wil be back to 900 like in the catalyst 7.12 release?
And is there any fix yet for the hd2900xt to get 3d speeds in windowed games?
Little cryptic but I tried it, and guess what its working now :D thQ m8
here a pic of what my ccc now looke like.. damn shame I cant change my 3d clocks but then again ccc only goes to 858mhz something so its all good :P
And the windowed mode problem still isnt fixed by ati.. And im not fund of setting 3d speeds in 2dmode all the freaking time.. But from what ive heard new version of Rabit is nearly completion 80%.. still no beta but its getting there
http://www.acidcool.nl/catalyst82works.jpg
http://www.people.freenet.de/BAGZZlash/RBE.exe
try this one bios editor. it even corrects the checksum :p:
nice find again zeneffect i wonder if this lets you set a higher voltage than 1.35 on gpu core, does winflash work with these cards i have always used atiflash through a floppy on dos
p.s i see you've upped the clocks to over 900 on your pros now ,nice going, i can run my xts at 900 core on 3dmarks except 06 which i have to turn down to 874, thats with 1.35 volt on h20
I haven't had these problems; I guess you have bad luck or something. Anyway, you seem very driven by something, and I hope you can get this all worked out, and I hope to see more of this kind of work. I must admit, this is entertaining :) :up:
@ glenboy
the bios editor was posted in the 2900 PRO owners thread by road-runner
i suggest you guys check that thread out if you have not already since the xt and pro are the same card.
also
it seems bios does not support above 1.35 *ive set it to 1.4 bios but rivatuner always reads it back as 1.35*
and ive been using winflash primarily because i dont have to make a disk, reboot with a boot cd and all that other garbage
@ superdank
thanks! the need for more 3dmarks is what is driving me to push my cards further and further. i do not experience the 900+ memory bug with the new drivers as im using a 6 pin and 6 pin instead of a 8 and 6 like i used to. im assuming you are using the same thing having not experienced any of the problems we have been running into here... anyways, see what you started? thanks for all your work to kick this all off!
btw i will have to run the 2900's on a isolated loop it seems as my idle temps went from 33 to 38... after playing cod4 for a few hours idle goes to 48 but cools down to 38-39 after 10 min or so... not something i am comfortable with.
my plan is
thermochill 240mm rad for cpu *dont know exact model off hand, will have to research*
use existing 240mm bix for gpu's
use 120mm bix for my girlfriend's computer *to upgrade a nautilus 500 external*
let you all know in 2 weeks when i can afford the parts!
Anyone try'd the 8.3 drivers yet?..
Im too scared to install :shocked:
yes with zeneffects inf fix work ok no performance improvement i've noticed
im actually considering dropping the water cooling portion to my cpu and having it exclusively for the gpu's. phase change seems to be what i want on cpu :p: :cool:
http://rapidshare.com/files/99718706/old.bin.html
Can somebody mod my bios for 1.3v and 850/950 and repair checksum,thanks...
yes the bios editor works ok and i used ati winflash (for first time i usually flash from a floppy) and all ok