GridinSoft Threat Intelligence

ocl_cpu_cpu_device32.dll file report

Clean record File reputation report
MD5 21ecf156d50f17ba7864ecc6edc34da2
Latest seen 2021-08-26 20:37:29 (4 years ago)
First seen 2018-04-22 17:08:46 (8 years ago)
Size 551 KB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-04-22 17:08:46 (8 years ago); latest analysis 2021-08-26 20:37:29 (4 years ago).

Publisher context

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

Digital signature

Signed by Microsoft Windows Hardware Compatibility Publisher. ThreatInfo marks this publisher as trusted for this record.

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_device32.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 2021-08-26 20:37:29 (4 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: 21ecf156d50f17ba7864ecc6edc34da2
Size: 551 KB
First Published: 2018-04-22 17:08:46 (8 years ago)
Latest Published: 2021-08-26 20:37:29 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-08-26 20:37:29 (4 years ago)
Signed By: Microsoft Windows Hardware Compatibility Publisher
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%appdata%\uniblue\driverscanner\drivers\154853\gfx_win10_64_15.65.4.4944
%localappdata%\innovative solutions\drivermax\agent\restore\9r3tj8eaft28q0f18x01gik3l5kng349ka29l5on1524583im3\display

ThreatInfo has observed ocl_cpu_cpu_device32.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_device32.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_device32.dll is identified as pe for 32-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 32-bit
Subsystem Windows CUI
Entry point 0x0003d690
Image base 0x10000000

PE Sections:

Sections 7
Raw data 546816

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

.text 395264 bytes · 72.3% of section data
MD5 5ddf45eba471d54a3145eb3e5cae3368
.rdata 107008 bytes · 19.6% of section data
MD5 b3baec5165867380c03dfb90942f547c
.data 16384 bytes · 3.0% of section data
MD5 0833429c1892465d2f0946ec0a1d9812
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 be3ed56b01183ce8bb6ae88dce08ebca
.tls 512 bytes · 0.1% of section data
MD5 0a36dfcc93086c110a87ea944c25868a
.rsrc 1536 bytes · 0.3% of section data
MD5 bb41a2a525c123f2140dab41df1146b6
.reloc 25600 bytes · 4.7% of section data
MD5 1127b3984284a0a046ea86a2a92fa799

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 21ecf156d50f17ba7864ecc6edc34da2.
  • 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.