Quote Originally Posted by nfm View Post
I cannot run Ch Clock Crossing Setting: More Aggressive anymore on the LT, I had no problem on older UT version, also the memory delays greatly differ from those using same settings, maybe do to the different revision?
I see a similar thing with BIOS 0521, I can hold PL6 on the 266 strap well over 1200mhz with earlier BIOS's but with 0521 I have to use PL7 & pull in all the phases.

Quote Originally Posted by mb. View Post
hello, since i have added an hd4870x2 to my system i am experiencing weird problems from which i dont know whats causing them. first off, i get that annyoing "the display driver has stopped working but was recovered..." in vista, but only with aero turned on. the bigger issue though is that i cant do 3d at all, either i get a bsod or the pc just reboots itself with a black screen. this only happens in vista home premium 64 sp1 though, in xp i didnt have a crash or whatsoever yet.
in vista i have tried four different driver sets for the x2 already and also tried with and without overclocked cpu. no success. now i am not sure what could be the reason. could it be the mainboard? i doubt that though since the user "C-N" stated that his x2 "works like a champ" on this board. but it seems he doesnt have a 64 bit os judging from his signature.
i was thinking maybe its the combination of p35 + vista64 + x2 (maybe + q6600)... but as i said i dont know thats why i am asking here.
ive already considered buying a new p45 mobo in hope that it will solve my problems but theres no guarentee and id rather not replace this board.
do you have any idea? thanks in advance...

my system:

q6600
dfi lp ut p35 (biso 521)
4 x 1gb teamgroup xtreem ddr2 800
gainward hd4870x2
corsair hx1000w
xfi xtreme music
My 4870X2 runs great on my DFI P35 but like you say I have only ever run XP SP2 or Vista 32Bit so it is possible you are seeing a 64 bit issue

I am using the BETA 8.9 drivers but retail 8.8 was fine.

The only way I can get my driver to stop responding if I run an unstable setup, overclock the card to far, overheat the card, or push the PCI-E frequency up too high.

CN