GridinSoft Threat Intelligence
AMDPCIDev.sys file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2022-04-30 23:04:57 (4 years ago); latest analysis 2022-04-30 23:06:38 (4 years ago).
Company metadata: Advanced Micro Devices. Product metadata: AMD PCI Device driver.
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.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
AMDPCIDev.sys is a Windows file recorded in the ThreatInfo database. It is associated with AMD PCI Device driver. The reported company name is Advanced Micro Devices. The current detection status is Undefined, based on the latest analysis from 2022-04-30 23:06:38 (4 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.
File Details
| Product Name: | AMD PCI Device driver |
| Company Name: | Advanced Micro Devices |
| MD5: | 1a44848081c332c661079babe3858f3e |
| Size: | 30 KB |
| First Published: | 2022-04-30 23:04:57 (4 years ago) |
| Latest Published: | 2022-04-30 23:06:38 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2022-04-30 23:06:38 (4 years ago) |
Overview
| Signed By: | Advanced Micro Devices Inc.;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on AMDPCIDev.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.
Common Places:
| %localappdata%\slimware utilities inc\slimdrivers\backups\20180122t201154419030\pci |
ThreatInfo has observed AMDPCIDev.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.
Geographic signal
Observed country distribution
ThreatInfo has seen AMDPCIDev.sys across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Austria with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for AMDPCIDev.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.
Analysis
AMDPCIDev.sys is identified as pe for 64-bit 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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
b2f767d97e40558b6a30a3b2437d1ba4
c5d14454587cac3617fb253c66d34e06
76f2fb85c5a3f9d260f33834a8becce4
01210186abb43cf1cfec862cd841a599
64d1f04ee674327483852f238bb2c4a5
80ea71715a024784a63b4dcb1553fb5a
b2203662c0195f537ccb6c12263d48fc
afb9352f43eb622558957a530a98ca28
a087335228392c187dbbf2cbfde8bd7e
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.