GridinSoft Threat Intelligence

ocl_cpu_cpu_device64.dll file report

Clean record File reputation report
MD5 d7bb1e24b9ebe1aab8bbe86985125823
Latest seen 2023-12-11 23:24:50 (2 years ago)
First seen 2017-05-22 09:04:45 (8 years ago)
Size 653 KB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-22 09:04:45 (8 years ago); latest analysis 2023-12-11 23:24:50 (2 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) OpenCL(TM) SDK.

Digital signature

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

ocl_cpu_cpu_device64.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) OpenCL(TM) SDK. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2023-12-11 23:24:50 (2 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) OpenCL(TM) SDK
Company Name: Intel Corporation
MD5: d7bb1e24b9ebe1aab8bbe86985125823
Size: 653 KB
First Published: 2017-05-22 09:04:45 (8 years ago)
Latest Published: 2023-12-11 23:24:50 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-12-11 23:24:50 (2 years ago)

The signature on ocl_cpu_cpu_device64.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%\innovative solutions\drivermax\agent\uploads\55qm5eg6mj3jhs8t9878e2a485a00lbffog7w6ybk1yv266x31\display\pci_ven_8086@amp;dev_0416
%localappdata%\innovative solutions\drivermax\agent\uploads\3g8928js2t22o4o26mw3283l0wqb0f5x19de6304t0vvxn0k8a\display
%localappdata%\innovative solutions\drivermax\agent\uploads\bbcur974lee8586295185ctc6ep64xl0wu53riscob127mi1tb\display
%localappdata%\innovative solutions\drivermax\agent\uploads\227n90436fqy3b9wo9k78xvbg4b0yw4ou8w5c6w31334lt9608\display

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

ocl_cpu_cpu_device64.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x0004daec
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 650752

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

.text 436736 bytes · 67.1% of section data
MD5 fa5512ef9594788f601b83aea3a34f16
.rdata 154624 bytes · 23.8% of section data
MD5 28ea1dc842f2282a93977ebe5b94b166
.data 26112 bytes · 4.0% of section data
MD5 9ce455fb11bcc1a3b57a34283d8d168c
.pdata 22016 bytes · 3.4% of section data
MD5 668fdca9ed4df78b8d1e19b8bdcd24d3
.tls 512 bytes · 0.1% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1536 bytes · 0.2% of section data
MD5 a0c143f734afc664ef384fb0ee25748b
.reloc 9216 bytes · 1.4% of section data
MD5 1528243b78be977399e3314d373cae05

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.

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 d7bb1e24b9ebe1aab8bbe86985125823.
  • 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.