qd162x64.sys file report

MD5 e45575812630b049ce0f679d87561a4d
Latest seen 2021-01-12 03:47:21 (5 years ago)
First seen 2017-08-14 14:09:30 (8 years ago)
Size 39 KB
Publisher Intel Corporation
Signed by Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-08-14 14:09:30 (8 years ago); latest analysis 2021-01-12 03:47:21 (5 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) 5000 Series Chipsets Integrated Device - 1A38.

Digital signature

Signed by Intel Corporation. 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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

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.

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)
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.

%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.

75.0%
12.5%
12.5%

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.

Windows 10 75.0%
Windows XP 12.5%
Windows 7 12.5%

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.

qd162x64.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: 0x0000000000010000
Entry Address: 0x0000a064

PE Sections:

Name Size of data MD5
.text 22016 ef4403a9222f1b79aed9a5be335d93c1
.rdata 1536 6b89829ca2a1bb5d805364d88566089e
.data 512 043c46095689123e1f5be96c109c2f46
.pdata 1024 e29f1935ebe055f1bd5b023ba8169975
INIT 2560 42b53c927e1a7dadb8723f366a00eafc
.rsrc 4608 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.

More information: