GridinSoft Threat Intelligence

amdhdl64.dll file report

Under review File reputation report
MD5 6fb07839de79e7c402c6be234547ab75
Latest seen 2021-01-12 16:19:14 (5 years ago)
First seen 2021-01-12 16:19:14 (5 years ago)
Size 425 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-12 16:19:14 (5 years ago); latest analysis 2021-01-12 16:19:14 (5 years ago).

Digital signature

Signed by AMD PMP-PE CB Code Signer v20190327;Advanced Micro Devices INC.;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

amdhdl64.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-01-12 16:19:14 (5 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

MD5: 6fb07839de79e7c402c6be234547ab75
Size: 425 KB
First Published: 2021-01-12 16:19:14 (5 years ago)
Latest Published: 2021-01-12 16:19:14 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-12 16:19:14 (5 years ago)

The signature on amdhdl64.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%localappdata%\slimware utilities inc\slimdrivers\backups\20200430t181054726041\pci

ThreatInfo has observed amdhdl64.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 10 100.0%

The most common operating system signal for amdhdl64.dll is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

amdhdl64.dll is identified as pe for 64-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x00001d38
Image base 0x0000000180000000

PE Sections:

Sections 5
Raw data 403968

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 312320 bytes · 77.3% of section data
MD5 6113f01e2d91b9f75de5108308f154ca
.rdata 68096 bytes · 16.9% of section data
MD5 c6f718e3168b22bc0503243ab7c7dd6f
.data 3584 bytes · 0.9% of section data
MD5 bce4c5676204cbe2d5a4ff1a6a18e2a3
.pdata 17920 bytes · 4.4% of section data
MD5 fde64cfffbf4e1c7bea4eead168a856d
.reloc 2048 bytes · 0.5% of section data
MD5 f92d1627109457578c63b3da12d2c9cf

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 6fb07839de79e7c402c6be234547ab75.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.