amdgpio2.sys file report

MD5 dc96dca2a7d1010195905597616946e8
Latest seen 2023-03-03 23:38:31 (3 years ago)
First seen 2020-08-25 20:43:21 (5 years ago)
Size 42 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-08-25 20:43:21 (5 years ago); latest analysis 2023-03-03 23:38:31 (3 years ago).

Publisher context

Company metadata: Advanced Micro Devices, Inc. Product metadata: AMD GPIO Controller Driver.

Digital signature

Signed by 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.

amdgpio2.sys is a Windows file recorded in the ThreatInfo database. It is associated with AMD GPIO Controller Driver. The reported company name is Advanced Micro Devices, Inc. The current detection status is Undefined, based on the latest analysis from 2023-03-03 23:38:31 (3 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.

Product Name: AMD GPIO Controller Driver
Company Name: Advanced Micro Devices, Inc
MD5: dc96dca2a7d1010195905597616946e8
Size: 42 KB
First Published: 2020-08-25 20:43:21 (5 years ago)
Latest Published: 2023-03-03 23:38:31 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-03-03 23:38:31 (3 years ago)

The signature on amdgpio2.sys 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\20200823t015409873\acpi
%localappdata%\slimware utilities inc\slimdrivers\backups\20200823t014710364\acpi
%localappdata%\slimware utilities inc\slimdrivers\backups\20180122t201154419030\acpi
%localappdata%\slimware utilities inc\slimdrivers\backups\20190418t181303658435\acpi

ThreatInfo has observed amdgpio2.sys 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.

50.0%
50.0%

The strongest geographic signal for this file is Bosnia and Herzegovina with 50.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for amdgpio2.sys 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.

amdgpio2.sys is identified as pe for 64 systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x00002b20

PE Sections:

Name Size of data MD5
.text 10240 ecff73e48d98d41243983aa385982856
.rdata 2048 04ab63ffb9cbe91a534f885ce7dc9b5e
.data 512 0374cdb7cc3303e0fafa2f46b5e8b3b3
.pdata 512 b52a157e4a6f2a279b67d12a34840555
.gfids 512 ad2b84f3b448a758243c6d6e89099751
PAGE 512 64b051c547c9d8edcaaca40547c0017e
INIT 1024 e78faad4f4994a4a0a3b79d180cf86e6
.rsrc 1536 d6dd5ce376022312107f4e14b06b23a1
.reloc 512 47ab22cfc01b362c7a2dc583f2ed6f0d

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.

More information: