Basically, both Catalyst and GPU-Z are saying my core clock is 500 MHz. I have tried upping it to 750 in Catalyst 8.7 Overdrive, and it passes the test, but when I click accept, the clock goes to 750 for one second, then back to 500. What is going on?
This is on a brand new clean install of Vista Ultimate 64-bit. I did at one point try out the ASUS Smart Doctor program, and it said that my Voltage wasn't in the safe zone and that it wasn't getting reliable 12V. or something. Given that most of the ASUS utilities that came with my hardware are crap, I don't know how accurate that is, but it could be.
Any suggestions? I have:
CORSAIR CMPSU-650TX 650W ATX12V Power Supply
http://www.newegg.com/Product/Product.aspx?Item=N82E16817139005
ASUS Maximus II Formula Motherboard
http://www.newegg.com/Product/Product.aspx?Item=N82E16813131319
ASUS EAH4870
http://www.newegg.com/Product/Product.aspx?Item=N82E16814121258&Tpk=asus%2b4870
Not much else connected, just Lite-On DVD Burner, Q6600 @ stock with Thermalright 120-Ultra heatsink and fan, 500GB 7,200rpm Seagate HD, 4gb RAM 800hz, 2 120mm case fans.
BTW, memory clock is fine I think. Core clock is the issue.
This is on a brand new clean install of Vista Ultimate 64-bit. I did at one point try out the ASUS Smart Doctor program, and it said that my Voltage wasn't in the safe zone and that it wasn't getting reliable 12V. or something. Given that most of the ASUS utilities that came with my hardware are crap, I don't know how accurate that is, but it could be.
Any suggestions? I have:
CORSAIR CMPSU-650TX 650W ATX12V Power Supply
http://www.newegg.com/Product/Product.aspx?Item=N82E16817139005
ASUS Maximus II Formula Motherboard
http://www.newegg.com/Product/Product.aspx?Item=N82E16813131319
ASUS EAH4870
http://www.newegg.com/Product/Product.aspx?Item=N82E16814121258&Tpk=asus%2b4870
Not much else connected, just Lite-On DVD Burner, Q6600 @ stock with Thermalright 120-Ultra heatsink and fan, 500GB 7,200rpm Seagate HD, 4gb RAM 800hz, 2 120mm case fans.
BTW, memory clock is fine I think. Core clock is the issue.