looks like 3706 might be on the horizon too yippee
Printable View
looks like 3706 might be on the horizon too yippee
Found another not fixed bug on M4A89GTD PRO/USB3: with bios 1703, as with all other, Primary Video Controller option doesn't work at all, videocard in lower pci-e slot is always Primary...
Was having the upper slot as the primary ever a design choice for this board? I thought the bottom slot was always supposed to be the primary...
I can confirm though that the mixed board arrangement (ATI & Nvidia) does not work with ATI in the primary and Nvidia in the secondary. The board ignores the Nvidia card as before.
Has anyone tried upping cpu-vdda to compensate for the vcore increase that you'de need to go from 100% llc to 50% llc?
The idea, increase vdda so you don't have to increase vcore.
Then you can use 50% llc and prevent spikes (less fluctuation overall).
I just noticed that decreasing vdda to 2.2v, I failed prime and had some issues in opera that I attribute to a low vcore, even though it's the same level that just pased 14hrs of it.
So I increases to 2.3v, and all seems well.
I'm thinking, instead of running another 12hrs run at vdda 2.3v, I should be focusing on decreasing the vcore back to it's min (which isn't to far...) and increasing the vdda to compensate for the loss of 100% llc.
Gaining back my lower vcore advantage that I had with 100% llc.
Sound feasible?
I'm gonna try in 10mins...
Edit:
Tried, I'll mess with it more later, maybe with more vdda I can go down a step or 2 in vcore but it needs more testing.
So far notta, only diff is the cpu is slightly faster (after 2.675v the speed diff dropped).
Same goes for the nb 1.8v voltage, so far increasing it a notch hasn't allowed me to lower the nb voltage or keep the pcie bus stable (which upping the nb voltage one step is doing so far).
I know this probably isn't the right thread to ask but, what's the vddr voltage setting that's around 1.2v stock?
Where does it go to?
And am I right to "assume" :\ that the chipset nb 1.8v setting is a pll voltage setting thing ?, just like vdda is to the vcore...
Forgive me but I don't wanna take out my board and use a resistance meter with a 2nd pc running to map out stuff...
did any1 test 1102 for the m4a89td pro, any chance that it fixes the ram clocking with micron kits
what did chew say, i run 1.8-1.9 but my kit dose nit like volts as much as the gtr as i have gts. i just knew that they did not clock well and i want to make sure i run a board that will clock them properly before i try and rma as i currently cannot go over about 1530mhz and be stable but back on 775 i could get over 2ghz with cas7 and i think it was also with pl7 or 8 (im not sure it was a few years ago now)
anyways is the bios stable.
My sticks are GTS, I've also got a kit with a bad stick from chew that doesn't like to go over 1.8 or it errors in memtest (subsequently BSOD's). ...so I've got 4 GTS sticks here and that's why I offered to help. We run similar boards, and I'm running a bios dated from December.
GTS take 1.8-2.3 fine imo, GTR likes 2.0-2.4 to get results.
chew said Thuban IMC gets screwy close to 1.8 I believe, he didnt want to run sticks above 1.7. I'd be happy to throw in the 965 or 565 with the good set and attempt to overclock them, I know I had 1M at 7-6-6 the first day I played with DDR3 when him, simon, and chispy donated me some things.
thats some rather good clocks compaired to what i can pull. and the td pro and td pro usb3 are the same boards the usb3 just has the extra chip plugged in, they also had the same bios checksums in the past and numbers so i assumed the same bios.
i updated and still get no clocks and crashes/no boot if i try so time to rma the ram (and not feel bad about it since i did not over volt it, and it was alot of money)
with the new bios i can clock them in single channel (and surprisingly not raising the timings but uping the clocks from 1:3 to 1:4 gave the same aida results even though i changed to single channel mode.)
so right now im doing 1644 with 1.825V on the ram and 7-7-7-18-30 1T (what they are rated for +44mhz)
1 ?
The cpu-nb llc, are there any oddities with using a 100% value for that?
Obviously there are issues with 100% on the cpu, but I'm wondering if it has a negative effect on the cpu-nb as well.
So far I haven't need any extra voltage on my cpu-nb at all going from 100% to 50%.
But I still haven't went back and checked to see if I can lower the voltage.
I'm curious to know if using a 100% llc setting for cpu-nb will help anything or just make things worse.
I should probably stick with 50% anyways since I don't seem to need the 100%.
I guess it depends on if it lowers the req's for the voltage a shiz load like the cpu llc setting does.
Rather not mess with it if it's gonna cause probs like the 100% llc on the cpu.
I have half a mind to think that the 100% llc cpu setting was killing my stability...
That and the bad ram didn't help either that's for sure.
It's nice to have a system that seems reliable :).
Perhaps asus can add a 35% and 75% setting...
Something a bit better that still doesn't have the wider fluctuations/spikes.
double post, sorry...
I was priming the other day for a 24/7 safe config.
I got above 44hrs of prime, not exactly sure how close to 48hrs, I just know I was passed 44hrs.
The pc just hard locked out of the blue.
I have a suspicion that I got a cpu-nb voltage spike and I was wondering if anyone has noticed any voltage fluctuation/spiking issues on the cpu-nb.
The same hardlock happens if I go past 1.4v on the cpu-nb, noticed this when testing for 3250mhz.
I am able to get 3.1ghz stable on the cpu-nb but I can't get the mem to clock much past 2040mhz so it's pointless.
When I was testing the cpu-nb limits I was getting the exact same hardlocks.
I have this fealing that if I goto use my system as is from now on, non stop, that once every 2-3 days it'll hardlock out of the blue for no reason.
I suppose all the BIOS's will need updating now for the Phenom 975BE.
Any recent M498TD EVO BIOS love? I sure would like to see some further adjustability to compensate for vdroop.
So no EFI bios for CHIV ?
The Sound Blaster X-Fi Utility needs updating too , since it contains bugs . (last update 5/11/2009)
Why do you think that we won't see any major and / or minor BIOS updates for our Crosshair IV Formula in future?
That pessimistic point of view (not only on CIVF) came from simple conclusions: two month after SB release we don't see any updates, this and next one or two month will be spend on upcoming Bulldozer mobos, and june/july/august is Ivy Bridge time. And very sarcastic pessimist also remembers about Llano in Q2...
Sad but true ...