GridinSoft Threat Intelligence
qd162x64.sys file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-08-14 14:09:30 (8 years ago); latest analysis 2021-01-12 03:47:21 (5 years ago).
Company metadata: Intel Corporation. Product metadata: Intel(R) 5000 Series Chipsets Integrated Device - 1A38.
Signed by Intel Corporation. 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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
qd162x64.sys is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) 5000 Series Chipsets Integrated Device - 1A38. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-12 03:47:21 (5 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Intel(R) 5000 Series Chipsets Integrated Device - 1A38 |
| Company Name: | Intel Corporation |
| MD5: | e45575812630b049ce0f679d87561a4d |
| Size: | 39 KB |
| First Published: | 2017-08-14 14:09:30 (8 years ago) |
| Latest Published: | 2021-01-12 03:47:21 (5 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-01-12 03:47:21 (5 years ago) |
Overview
| Signed By: | Intel Corporation |
| Status: | Valid |
The signature on qd162x64.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:
| %programfiles%\drivertoolkit\download\c5c2e9d7c5c9d0c9e3e1fb218cd181ae\platform\ioatdma\winx64\ndis62 |
| %programfiles%\drivergenius\temp\18_3_cd\platform\ioatdma\winx64\ndis62 |
| %programfiles%\drivertoolkit\download\c5c2e9d7c5c9d0c9e3e1fb218cd181ae\platform\ioatdma\winx64 |
| %appdata%\easeware\drivernavigator\drivers\5jm5oayw.a2d\19_5_cd\platform\ioatdma\winx64 |
ThreatInfo has observed qd162x64.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 qd162x64.sys across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Hong Kong with 75.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 qd162x64.sys is Windows 10 with 75.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
qd162x64.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.
ef4403a9222f1b79aed9a5be335d93c1
6b89829ca2a1bb5d805364d88566089e
043c46095689123e1f5be96c109c2f46
e29f1935ebe055f1bd5b023ba8169975
42b53c927e1a7dadb8723f366a00eafc
cc52770ff04a48bd6845206c80e4b219
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 hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.