x1950 PRO PCI-E catalyst driver issue...

[jtelep]

I am sure this has come up in the past but I am going to ask again for my own sanity's sake simply becaukkkkkkkkkkkkkkkkse I am not sure where to find it. I recently upgraded and installed a new GeCube 1950PO 256MB PCI-E loaded up the Catalyst driivers, bounced the system and now as soon as I attempt to login to XP the system starts bouncing and I can only successully get to the login screen. Please tell me somebody has heard of this before has a fix.

Thanks,

 

[herbiehancock]

Yeah....roll back your driver, not the CCC, to the 6 series. I've noticed some very odd behavior in the Catalyst drivers after AMD became involved in ATI.....don't know the connection, or if there is one at all, but every since driver 7.1 came out, I've been unable to overclock my 1950 Pro through the CCC. Keeping the current CCC and using driver 6.11, I can overclock the gpu to 621 and the memory to 780. With driver 7.1 or 7.2, the moment I increase either the gpu speed or memory speed 1MHz over stock, it immediately begins to artifact.

Go figure.

Anyway, I run the latest CCC, 7.2, with older drivers, 6.11.

I'd honestly go in on safe mode, delete the current driver, not the CCC, and then install an older driver set.

 

[jtelep]

OK, no problem but one other question as I began thinking about this this morning and had forgotten about it last night. Please bear with me as I am a "noob" when it comes to PCI-e. I'm running this card on an Asus K9N Platinum and noticed that in addition to the 6-pin power connector on the card there is also a 4-pin molex power connector on the system board as well and according to the manual it is also for the PCI-e card(s) (as this is a CrossFire-ready board). Not wanting to do anything stupid I did not plug the power for the PCI-e on the board in but instead just the card. Could that have anything to do with it? I checked both the system board and graphics card manuals and could not find anything specific for this question but I didn't want to plug both in if perhaps only one was ever intended.

Let me know your thoughts on that and I will go ahead and roll back that driver.

Thanks.