GridinSoft Threat Intelligence

OpenCL32.dll file report

Clean record File reputation report
MD5 8bdb447b46fb96ec17062833383e64a1
Latest seen 2021-01-09 22:40:01 (5 years ago)
First seen 2017-05-22 09:06:25 (9 years ago)
Size 65 KB
Publisher Khronos Group
Signed by NVIDIA Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-22 09:06:25 (9 years ago); latest analysis 2021-01-09 22:40:01 (5 years ago).

Publisher context

Company metadata: Khronos Group. Product metadata: Khronos OpenCL ICD.

Digital signature

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

OpenCL32.dll is a Windows file recorded in the ThreatInfo database. It is associated with Khronos OpenCL ICD. The reported company name is Khronos Group. The current detection status is Clean, based on the latest analysis from 2021-01-09 22:40:01 (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: Khronos OpenCL ICD
Company Name: Khronos Group
MD5: 8bdb447b46fb96ec17062833383e64a1
Size: 65 KB
First Published: 2017-05-22 09:06:25 (9 years ago)
Latest Published: 2021-01-09 22:40:01 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-09 22:40:01 (5 years ago)
Signed By: NVIDIA Corporation
Status: Valid

The signature on OpenCL32.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\tmp\display\pci_ven_10de@amp;dev_0a75@amp;subsys_c06a144d
%localappdata%\slimware utilities inc\slimdrivers\backups\20200309t215000647104\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20191022t110208690982\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20191017t121155279469\pci
%localappdata%\innovative solutions\drivermax\agent\uploads\x6gjwf5u3759p2afcq28f455n3bh315ar5p434453261ttjfel\display
%localappdata%\innovative solutions\drivermax\agent\uploads\5xw718n3co4h0er1vaeo4uj2j6xs1qkecl2ntp1dg76f1hf457\display
%localappdata%\innovative solutions\drivermax\agent\restore\4h22fdu3e8l0022j6n931gin6836vfrqmc4c97gf4n20h75daf\display
%localappdata%\slimware utilities inc\slimdrivers\backups\20190909t185637300008\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20190909t192657628288\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20181024t150454895719\pci

ThreatInfo has observed OpenCL32.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 7 75.0%
Windows 10 16.7%
Windows Vista 8.3%

The most common operating system signal for OpenCL32.dll is Windows 7 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.

OpenCL32.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x00003313
Image base 0x10000000

PE Sections:

Sections 5
Raw data 51712

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

.text 33792 bytes · 65.3% of section data
MD5 cf836617b7967b2f0ed8815d940dc843
.rdata 11776 bytes · 22.8% of section data
MD5 ee540429c40ba7b6dec9ac999e78d561
.data 3072 bytes · 5.9% of section data
MD5 7067b5b3ec35708d0af61454204a5635
.rsrc 1024 bytes · 2.0% of section data
MD5 1bc40cc61b901055213d977aefca79ea
.reloc 2048 bytes · 4.0% of section data
MD5 a218d4390e1fa3e78991b988c9a96c11

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 8bdb447b46fb96ec17062833383e64a1.
  • 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.