Jump to content

Featured Replies

  • Crew

i also had that problem mit those "n/a" stuff at gpu and cpu.

for me it turned out to be the OS, i was using. (win xp sp1). now with win xp sp2 i have no problems. ;)

 

hth

Seems like anything over a 300 mhz overclock using Nvidia system tools caused a bug with Aquamark3 GPU/CPU score.

 

Jumping too far with software in Windows does this, been happening since the beginning with Clockgen, SetFSB ect. :)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...