Check out this screenie off my computer...

[IMG][/IMG]

Crazy no?

Dani AI

Generated

A few practical notes that build on the thread: when a GPU-monitoring utility reports wildly implausible clock numbers only while the system is under a heavy test run, the likeliest causes are telemetry/driver/tool reporting issues rather than immediate hardware failure. later pointed out the anomaly occurred under a stress run, and the troubleshooting suggestion from and to check running processes is a good starting point.

Possible technical causes (briefly): monitoring tools read values through the GPU driver/API and can sample mid-update, return transient or partial values, or misinterpret raw register fields (units or overflow). Overlays and hooks from other utilities can interfere. Older drivers or outdated monitoring software increase the chance of misreports.

Practical checklist to follow when this shows up:

  • Check background processes (Task Manager or Process Explorer) as and suggested to rule out system-wide resource contention.
  • Cross-check with a second monitoring tool (for example GPU-Z or HWMonitor) to see if two independent tools show the same numbers.
  • Update GPU drivers and the monitoring utility (use the vendor clean-install option if available).
  • Disable overlays/hooks (Steam, Afterburner OSD, FRAPS, etc.) and retry.
  • Monitor GPU temperatures/fan speeds to confirm the card is not thermally throttling or unstable.
  • If the issue is reproducible after those steps, record exact steps, driver version, OS, and screenshots and report it to the GPU vendor with the logs.

If temperatures and system stability are normal and only the numbers look wrong, treat it as a reporting glitch until multiple tools/drivers reproduce it.

Recommended Answers

All 4 Replies

Can you see what the top 5 processes are that use the most CPU?

Chances are you've got some spyware or other nasty happily sucking up your CPU cycles. It would definitely be a good idea to post the top processes. Especially if your computer is just idling.

Hope this helps

Lol. Guys, this is a joke screenshot, not to say it isn't legit, but that I did it under certain cirumstances, I was running 3DMark06 at 1280x1024 4xaa. The thing I found funny was the speed ratings Nvidia monitor threw off, I get a normal reading of 3000 MHz any other time. 3DMark eats up so much resources that NVIDIA's clock view on my system threw off some phoney numbers is all. No spyware or nothin', I'm sure of that much. I know the regular processes that are routine in procmanager, and I have a few extra xp plugins that I use myself, just saying, this is a bug, not a 3rd party problem.

:)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.