LOL-Linpack/OCCT stable system can't run 3DMark Vantage!

Dadofamunky

Platinum Member
Jan 4, 2005
2,184
0
0
Man, I'm scared to upgrade my ATI drivers. I've had major problems with both Cat8.9 and Cat8.10 (video and audio jitter) and had to refresh completely back to the older Cat8.8. Now, with my system (in my sig) able to run 100 passes of IntelBurn Test, and pass several hours of OCCT, I can't run the trial version of 3DMark Vantage 1.1 to completion!

OC settings are:

FSB 410
DDR2-984 6:5
Clock Over-Charging Mode auto
CPU voltage 1.35
CPU Voltage Reference 0.63
CPU Voltage Damper Disabled
PLL Voltage 1.5V
NB Voltage 1.37
NB Voltage Reference 0.67

4850 is OCd to 699/1051. Do I need to throttle the video card back a bit?

3DMark06 fails too.

I usually get this behavior when I have bad CPU OC settings. But this is unheard of. Seems like a driver issue.

Anyone got any thoughts?
 

manimal

Lifer
Mar 30, 2007
13,559
8
0
Try it with the graphics card at stock to try to isolate your issue...Run your driver cleaner of choice and update to the newest ati drivers since they helped alot of people with stability. Also crank up the fan on the graphics card as well-ati tray tools is awesome if you havent used it before.

When trying to find gremlins isolate, rinse repeat...
 

SSChevy2001

Senior member
Jul 9, 2008
774
0
0
manimal is right. Increase your GPU fan speed and overclock with a third party app. ATI Tray Tools. Even if you don't OC, you should still use ATI Tray Tools to lock your clock speeds to avoid powerplay problems.
 

Dadofamunky

Platinum Member
Jan 4, 2005
2,184
0
0
I'm actuallly running RivaTuner 2.11 in the system trey, with OCing disabled and only to manage the fan speed, which it does effectively.

ATI Tools does not work under Vista 64. Just made an attempt. Ick. Plus a Google shows tons of links discussing that issue.

ohhh... I note Catalyst 8.11 WHQL is out...
 

Dadofamunky

Platinum Member
Jan 4, 2005
2,184
0
0
Heyyy! Catalyst 8.11 worked. Serious eye candy there in Vantage. Too bad it's purely a synthetic benchmark, hence not terribly useful in the real world.

My score was P6774 3DMarks, whatever that means.

Obviously my original post was due to a driver issue.