Jump to content

omega

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by omega

  1. I've just been trying out various memory speeds etc... and discovered that AIDAs "GPU memory clock" isn't related to the memory clock at all.

    If you alter the core speed, then the "GPU memory clock" value changes. This leads me to think the sensor you're reading is probably shader related.

    Here are a few readings I got,

    Actual Core clock --- value that AIDA reports as "GPU memory clock"

    1125 --- 2850

    1100 --- 2725

    1050 --- 2450

    1000 --- 2175

    975 --- 2050

    925 --- 1775

    850 --- 1375

    There doesn't appear to be a linear sequence here, but it does match the readings you got, as I guess you're running at stock core speed - i.e 925Mhz, which correlates to 1775.

  2. Just so it's reported, the memory clock is 1/4 of it's true value in 2D clocks, and 1/2 it's true value at 3D clocks.

    (Memory is double data rate, so the actual rate is twice that shown in CCC / Afterburner etc)

    If we're talking about those rates, then at 2D clocks, AIDA is reporting half it's value, and 3D clocks AIDA is reporting 2x actual value.

    (I re-read this and it's confusing, but I can't explain it any better :D)

    Also, any plans to implement the VRAM usage, if it is indeed possible?

  3. Hi, Installed the beta, the GPU temps seem to be functioning fine, as do the fan speeds.

    However when running Furmark benchmark, the Core clock seems to jump around erratically (random numbers between 600 - 1300) and the memory clock jumps between 75 & 1600. (Actual values are 1100/1375)

    Also, the GPU utilisation doesn't work. It will occasionally change to 100%, but 99% of the time it is displaying 0%.

    Scratch that! Bit of an update, just fired up Crysis and Crysis 2, Core clock AND utilisation are being reported correctly :)

×
×
  • Create New...