Driver problems are real, but many “driver issues” turn out to be display path problems, unstable memory, old chipset firmware, or settings that survived from earlier installs. Use this checklist before posting.

Include these facts up front

• Exact GPU model and board partner.
• Driver branch and full version number.
• Windows build or Linux distribution, kernel, and desktop stack if relevant.
• Whether you are using Game Ready, Studio, open kernel modules, proprietary Linux packages, or containerized workloads.
• Whether the system is new, recently updated, or long-stable before the issue started.

Describe the symptom precisely

• Installer fails.
• Driver installs but games crash.
• Display wakes incorrectly.
• Video playback fails.
• CUDA or NVENC disappears.
• HDR, VRR, DSC, or multi-monitor behavior breaks.

Minimum tests before posting

• Cold reboot after the problem appears.
• Test one display at stock refresh and color format.
• Disable overlays, third-party tuning tools, and unstable OC/UV profiles.
• Note whether the issue persists across at least one older or newer driver version when that comparison is safe.

For Linux threads, also include

• Kernel version.
• X.Org or Wayland session.
• Package source or installer method.
• Secure Boot status if relevant.
• Any taint, module, or DKMS errors.

For creator or compute threads, also include

• CUDA version.
• Framework version.
• Container base image if used.
• Whether graphics output, encode, and compute are all affected or only one path.

Do not say “latest is broken” without the version, repro conditions, and a clear previous-known-good reference point.