A useful repair starts by locating the boundary of the failure, not by reinstalling every component. In AMD Software, the specific symptom is this: GPU usage and clock values remain at zero even while a graphics workload runs. The practical objective is to restore the affected feature, determine the actual failing layer, and confirm the result without sacrificing data or account protection.
Recognize the pattern
GPU usage and clock values remain at zero even while a graphics workload runs. The key distinction is whether the failure happens before the service, game, application or device becomes available, or only when the user performs the specific action. Compare Adrenalin readings with Windows Task Manager GPU engine data during the same short workload.
- Exact observation: GPU usage and clock values remain at zero even while a graphics workload runs.
- First useful comparison: Compare Adrenalin readings with Windows Task Manager GPU engine data during the same short workload.
- Expected healthy state: Metrics increase during a repeatable load while the game’s performance stays unchanged.
Keep a short timeline: when did the behavior start, what software or network condition changed immediately beforehand, and is the failure consistent on every attempt? A successful unrelated feature should not be treated as proof that the affected layer is healthy.
How to distinguish the causes
The metrics provider or overlay can fail independently of the GPU driver and the game. This is a hypothesis that should be confirmed through the comparison above. A black monitor is not proof of a defective GPU; a bad display link can look identical. Likewise, an overlay or sensor fault does not automatically establish rendering instability.
Compare the original workload at the same refresh rate and GPU power state. If a driver rollback makes the issue disappear, record the exact versions rather than assuming the newest installer is inherently defective If the test result contradicts the suspected cause, do not push forward with a broad reset. Return to the recorded baseline and investigate the next boundary instead.
Safe starting point
Keep a known-working graphics driver installer, capture display topology and record the current GPU device ID before making changes. If this is a laptop, the OEM graphics switch and integrated GPU may be part of the display path.
- Compare Adrenalin readings with Windows Task Manager GPU engine data during the same short workload.
- Compare per-engine activity and record sensor availability through GPU-Z or the OEM tool to determine whether monitoring rather than rendering is affected.
- Note the original settings and capture any relevant error identifier without copying passwords or session tokens.
Do not begin with formatting a disk, deleting a player profile, disabling secure boot, bypassing TLS checks or running registry cleaners. The controlled tests below are designed to find the narrow failure before considering any operation that could affect unrelated data.
Step-by-Step Troubleshooting
Choose Beginner for reversible checks or Advanced for focused diagnostics.
Capture the exact failure in AMD Software
GPU usage and clock values remain at zero even while a graphics workload runs. Record the product model, application build and time of failure. Compare Adrenalin readings with Windows Task Manager GPU engine data during the same short workload. Use a screenshot or a non-sensitive log excerpt as the baseline; do not attempt three repairs at once.
Run the lowest-risk comparison
Compare Adrenalin readings with Windows Task Manager GPU engine data during the same short workload. Compare the outcome with a known-working account, device, cable or network only where it is permitted and relevant. A black monitor is not proof of a defective GPU; a bad display link can look identical. Likewise, an overlay or sensor fault does not automatically establish rendering instability Keep the original settings written down so each test is reversible.
Apply a supported, targeted correction
Toggle metrics overlay off and on, update the supported Adrenalin version and reset overlay preferences before reinstalling anything. Confirm that the changed component actually belongs to AMD Software and is supported by the installed OS and hardware. Restart only the necessary app or device, and leave unrelated security settings intact.
Check the original workflow again
Metrics increase during a repeatable load while the game's performance stays unchanged. Repeat the exact action that failed originally, not a different synthetic test. Record whether the problem is resolved completely, only on one connection, or only after a restart; that distinction determines the next action.
Identify the responsible subsystem
The metrics provider or overlay can fail independently of the GPU driver and the game. Compare per-engine activity and record sensor availability through GPU-Z or the OEM tool to determine whether monitoring rather than rendering is affected. Use the resulting difference to decide whether this is a client, runtime, transport, account or hardware problem rather than assuming all of them are defective.
Collect narrow technical evidence
Compare per-engine activity and record sensor availability through GPU-Z or the OEM tool to determine whether monitoring rather than rendering is affected. Retain only timestamps, error identifiers, compatible versions and the relevant event sequence. When investigating a driver, distinguish the hardware enumerated by the operating system from the features exposed to a specific application. Do not force-install incompatible drivers or modify firmware based on an unverified forum workaround Mask identifiers, tokens and personal data before handing logs to anyone.
Isolate the change with rollback
Toggle metrics overlay off and on, update the supported Adrenalin version and reset overlay preferences before reinstalling anything. Test a second known-good configuration where available. Note the original setting and apply only one approved change; if the expected signal does not improve, restore the baseline before trying another hypothesis.
Confirm stability and document the limit
Metrics increase during a repeatable load while the game's performance stays unchanged. Run a second test after a normal restart or reconnect if the original symptom involved state transitions. Retain a rollback path for graphics profiles and test at the same resolution, power profile and workload. A short repeatable benchmark is more useful than comparing two unrelated games If evidence points to unsupported hardware or organization policy, escalate rather than inventing a bypass.
Diagnostic decision table
Use the following evidence map after completing the Beginner checks. Each row provides an interpretation, not an instruction to apply every possible fix.
| Layer | Evidence to compare | Next decision |
|---|---|---|
| Driver and operating-system discovery | Compare Adrenalin readings with Windows Task Manager GPU engine data during the same short workload. | Investigate the local setup or initial prerequisite. |
| Rendering, link or sensor path | The metrics provider or overlay can fail independently of the GPU driver and the game. | Compare the failing component with a known working control. |
| Power, temperature or display negotiation | Compare per-engine activity and record sensor availability through GPU-Z or the OEM tool to determine whether monitoring rather than rendering is affected. | Keep only observations supported by a log or repeatable test. |
Compare per-engine activity and record sensor availability through GPU-Z or the OEM tool to determine whether monitoring rather than rendering is affected. If the evidence points away from this layer, return to the previous row. The process is intentionally sequential: a configuration change only has diagnostic value when the prior state is recorded.
Do not do these things
- Avoid changing unrelated layers. When investigating a driver, distinguish the hardware enumerated by the operating system from the features exposed to a specific application. Do not force-install incompatible drivers or modify firmware based on an unverified forum workaround
- Do not confuse a temporary workaround with a fix. The metrics provider or overlay can fail independently of the GPU driver and the game.
- Do not erase the evidence. Keep the original settings and note whether gPU usage and clock values remain at zero even while a graphics workload runs.
Decision rule: If the proposed change does not produce the expected result in a repeatable test, restore the previous configuration. A problem that remains identical needs better evidence, not a larger reset.
Verify in practice
Metrics increase during a repeatable load while the game’s performance stays unchanged. Use the same device, title, workload or service path on which the failure was observed. Compare the outcome directly with the original screenshot or error log, and repeat the test twice if the failure was intermittent.
Retain a rollback path for graphics profiles and test at the same resolution, power profile and workload. A short repeatable benchmark is more useful than comparing two unrelated games If one test passes but the underlying account, certificate, performance metric or data synchronization is still wrong, mark the result as partial and continue with the Advanced checks rather than claiming a complete repair.
Solution Checklist
What to do next
Compare per-engine activity and record sensor availability through GPU-Z or the OEM tool to determine whether monitoring rather than rendering is affected. If AMD Software still fails the original operation, revert temporary test settings that did not help and capture the precise evidence for the vendor or administrator. Include what worked, what failed and whether the comparison was conducted on the same build and connection.
Do not keep repeating account resets, firmware flashes or driver removals when there is no measurable improvement. For unsupported hardware, managed work devices or possible physical failure, ask the relevant vendor or qualified technician to confirm the supported route forward.
Reduce repeat failures
Toggle metrics overlay off and on, update the supported Adrenalin version and reset overlay preferences before reinstalling anything. Keep the exact working driver, firmware version, app build or policy setting documented. Future changes should be tested against the same baseline, especially after operating-system, network or application updates.