Files signed by Advanced Micro Devices

Advanced Micro Devices

Advanced Micro Devices is a digital signature publisher name observed in ThreatInfo records. This page groups 16 signed files and shows whether those files are currently classified as clean, undefined, or detected.

A digital signature can help identify a publisher, but it does not always prove that a file is safe. Certificates may be abused, stolen, expired, or attached to modified installers, so the file hash and detection status should be checked together.

Detection signal

Detected files use this signature name

At least one file signed as Advanced Micro Devices is detected by GridinSoft. Review the hashes below and scan the device if one of these files is present.

Download GridinSoft scanner
amd-software-adrenalin-edition 11ff1fc9a757196f165239e3b8aa5f6c Suspicious Object
cncmd.exe 8bc3b67af90e8a4125a67807e27229e2 Possible Threat
RSServCmd.exe c99e120bde6a6be2a12ee3a46b34128c Possible Threat
InstallManagerApp.exe c611d00e3a43a7ab97dd865f83af770c Possible Threat
AUEPMaster.exe 162d2742496a409b527cd0e587f3931b Possible Threat
cncmd.exe b678433f74a2e3bc6cd7267bd780e798 Possible Threat
InstallManagerApp.exe 470720620bc92c7f39674de56ef95612 Possible Threat
RSServCmd.exe 8d62e1f1bfbc3bb8d7328aea4952df50 Possible Threat
cpumetricsserver.exe acb7bee085ebf3b6996919bcf811ab2e Possible Threat
AMDBugReportForm.exe 827f8766f549e5f577f102d765b0b328 AIDetect.de042df
hiprtc0601.dll 35b5c9f2deabfb1d2ffcf8fe3699707c Adware.DNSKeep (Heuristic)
amd_comgr0601.dll e226559d8f1989ffaf0cfe0d519a1eb4 Adware.DNSKeep (Heuristic)
hiprtc-builtins0601.dll 3245e41759f1ac50fb04e50b9e39ace3 Adware.DNSKeep (Heuristic)
AMDBugReportForm.exe ec5811d055eda9440f4d69afe6ca7d59 Trojan.Heur!
amd-software-adrenalin-edition 67f6c08dd7f4e3c7052b721ecb169f20 Suspicious Object
AMDBugReportForm.exe 5cf873ae8098e983707067ec4178f3a0 Trojan.Heur!

Certificate review summary

Do not trust this signature name by itself

ThreatInfo found detected files associated with Advanced Micro Devices. A matching signature name should be checked together with the file hash, detection verdict, and source path.

Recommended checks

  • Open any matching file report and compare the MD5 hash.
  • Confirm the file path and download source before trusting the binary.
  • Run a GridinSoft scan if a detected file from this list is present.