GridinSoft Threat Intelligence

nvcuvid32.dll file report

Clean record File reputation report
MD5 ed64c503e431d04121c4271d47595d97
Latest seen 2023-06-09 23:55:00 (2 years ago)
First seen 2023-06-09 23:55:00 (2 years ago)
Size 2 MB
Publisher NVIDIA Corporation
Signed by NVIDIA Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-06-09 23:55:00 (2 years ago); latest analysis 2023-06-09 23:55:00 (2 years ago).

Publisher context

Company metadata: NVIDIA Corporation. Product metadata: NVIDIA CUDA Video Decode API.

Digital signature

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

nvcuvid32.dll is a Windows file recorded in the ThreatInfo database. It is associated with NVIDIA CUDA Video Decode API. The reported company name is NVIDIA Corporation. The current detection status is Clean, based on the latest analysis from 2023-06-09 23:55:00 (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: NVIDIA CUDA Video Decode API
Company Name: NVIDIA Corporation
MD5: ed64c503e431d04121c4271d47595d97
Size: 2 MB
First Published: 2023-06-09 23:55:00 (2 years ago)
Latest Published: 2023-06-09 23:55:00 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-06-09 23:55:00 (2 years ago)
Signed By: NVIDIA Corporation
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.

%programfiles%\drivertoolkit\backup

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

nvcuvid32.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 0x000e27a3
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2930176

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

.text 992256 bytes · 33.9% of section data
MD5 6355ab8992e6a92549eb10f8e7142ec9
.rdata 480256 bytes · 16.4% of section data
MD5 c673584f25394e5213e312e0af0d927c
.data 1378304 bytes · 47.0% of section data
MD5 0bc0e87067382c3466ca3781baf733a2
.rsrc 1536 bytes · 0.1% of section data
MD5 a76c5266fc55c608c9ddd2488b12ee9f
.reloc 77824 bytes · 2.7% of section data
MD5 53ffb44ecb4c54780e359071dfcc3ae8

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