Jump to content
HWBOT Community Forums

Blaylock

Members
  • Posts

    8
  • Joined

  • Last visited

Converted

  • Location
    United States

Blaylock's Achievements

Newbie

Newbie (1/14)

10

Reputation

  1. Update. I updated the SystemInfo to 4.23 but still recieved the same error. It was suggested to reduce my Ram speed to 1333 from stock (1600) on another forum. That resulted in a valid result. Sounds crazy but there you have it. Now to find out if I can RMA my RAM. Thanks for the help everyone.
  2. I'm using Window 7 Home Premium 64 bit with SP1. Yes a system update was recomended on another forum also. Going to try that tonight and Report back. Thanks
  3. Thanks for the reply Chispy. All my hardware is listed in my sig. With the exception of the storage. I'm running a seperate HDD for Benching. It's an older Hitachi Sata1 drive. I don't have the numbers on it right now but will edit this post after work. I over clock the CPU with the Bios and the GPU with TriXX. I've tried running 3dMark05 Overclocked and stock, with and without TriXX in the background. I've even run the benchmark on to different installs of W7. I have ACHI HPET Enabled in the Bios, as I've read this can cause the error also. I will verify the time on my computer tonight but that seems unlikely. In fact I think I'll try running this BM on my second rig just to see if I can get a clean run. All help and advice is appreciated.
  4. Ticket ID: 1855 Priority: Medium While running 3dMark05 I received this error. \"Time measurement data not available\". After Googling and checking HWBot help It seems to be related to the system clock. How can I find out the cause and of course fix the issue. The only programs running in the background were HWMonitor and TriXX. Could TriXX be causing this issue? Iv\'e tried running the bench mark at stock speeds also with the same results.
  5. While running 3dMark05 I received this error. "Time measurement data not available". After Googling and checking HWBot help It seems to be related to the system clock. How can I find out the cause and of course fix the issue. The only programs running in the background were HWMonitor and TriXX. Could TriXX be causing this issue? Iv'e tried running the bench mark at stock speeds also with the same results.
×
×
  • Create New...