GridinSoft Threat Intelligence

ocl_cpu_cpu_device64.dll file report

Clean record File reputation report
MD5 85fb61748c753bbef715e0b75db3d2c3
Latest seen 2021-08-26 20:44:04 (4 years ago)
First seen 2018-04-22 17:08:45 (8 years ago)
Size 733 KB
Publisher Intel Corporation
Product Intel(R) OpenCL(TM) SDK
Signed by Microsoft Windows Hardware Compatibility Publisher

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-04-22 17:08:45 (8 years ago); latest analysis 2021-08-26 20:44:04 (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.

File context

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 2021-08-26 20:44:04 (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.

File Details

Product Name: Intel(R) OpenCL(TM) SDK
Company Name: Intel Corporation
MD5: 85fb61748c753bbef715e0b75db3d2c3
Size: 733 KB
First Published: 2018-04-22 17:08:45 (8 years ago)
Latest Published: 2021-08-26 20:44:04 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-08-26 20:44:04 (4 years ago)

Overview

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.

Common Places:

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

Geographic signal

Observed country distribution

ThreatInfo has seen ocl_cpu_cpu_device64.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Canada
Share 33.3%
Low High activity

The strongest geographic signal for this file is Canada with 33.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

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.

Analysis

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 0x00051d50
Image base 0x0000000180000000

PE Sections:

Sections 8
Raw data 732672

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

.text 492032 bytes · 67.2% of section data
MD5 cb2e776f075fc00d4d4cc72658f8c441
.rdata 180224 bytes · 24.6% of section data
MD5 4c20be7e0ec0bf8b86406a30a823e68f
.data 22016 bytes · 3.0% of section data
MD5 1c660aec1eea1a743dfd6bea74ee5002
.pdata 28160 bytes · 3.8% of section data
MD5 058557f7b9ba64134270f74068466bf3
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 183dcc32688d4f4e47c2dabbf4d52a58
.tls 512 bytes · 0.1% of section data
MD5 d978138e240b70d742967d1716b4c33d
.rsrc 1536 bytes · 0.2% of section data
MD5 2698b4201dcb6309fdda56f88cddab1f
.reloc 7680 bytes · 1.0% of section data
MD5 93ec53af3a35ffdbc49f2bcd518d900b

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 85fb61748c753bbef715e0b75db3d2c3.
  • 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.