GridinSoft Threat Intelligence

nvhda64v.sys file report

Clean record File reputation report
MD5 e366a5681c50785d4ed04fcfd65c3415
Latest seen 2022-11-18 23:45:20 (3 years ago)
First seen 2017-07-30 14:05:22 (8 years ago)
Size 192 KB
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 2017-07-30 14:05:22 (8 years ago); latest analysis 2022-11-18 23:45:20 (3 years ago).

Publisher context

Company metadata: NVIDIA Corporation. Product metadata: NVIDIA HDMI Audio Driver.

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.

nvhda64v.sys is a Windows file recorded in the ThreatInfo database. It is associated with NVIDIA HDMI Audio Driver. The reported company name is NVIDIA Corporation. The current detection status is Clean, based on the latest analysis from 2022-11-18 23:45:20 (3 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 HDMI Audio Driver
Company Name: NVIDIA Corporation
MD5: e366a5681c50785d4ed04fcfd65c3415
Size: 192 KB
First Published: 2017-07-30 14:05:22 (8 years ago)
Latest Published: 2022-11-18 23:45:20 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-11-18 23:45:20 (3 years ago)
Signed By: NVIDIA Corporation
Status: Valid

The signature on nvhda64v.sys 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.

%commonappdata%\winzip\winzip driver updater\downloads\27\9bcce3df-6331-429e-a9a2-1bc32324347c
%appdata%\uniblue\driverscanner\drivers\-20716458
%programfiles%\drivertoolkit\download\44a77a1a1da12507a8e4af3362a3a48e
%commonappdata%\log\intel\nvidia\displaydriver\340.52\win8_winvista_win7_64\english
%programfiles%\drivertoolkit\download\4fb5d8ea204b018bbeabd46ded32e69b
%programfiles%\drivertoolkit\download\f9c22d7f71b2642f446dcaf4dd930896
%localappdata%\slimware utilities inc\slimdrivers\backups\20181105t115940621069\hdaudio
%localappdata%\slimware utilities inc\slimdrivers\backups\20181105t120935968618\hdaudio
%localappdata%\slimware utilities inc\slimdrivers\backups\20140915t134545072157\hdaudio
%localappdata%\slimware utilities inc\slimdrivers\backups\20170419t204216954944\hdaudio

ThreatInfo has observed nvhda64v.sys 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 80.6%
Windows 10 16.1%
Windows Vista 3.2%

The most common operating system signal for nvhda64v.sys is Windows 7 with 80.6% 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.

nvhda64v.sys is identified as pe for 64-bit systems. The subsystem is Native. 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 Native
Entry point 0x0003043c
Image base 0x0000000000010000

PE Sections:

Sections 9
Raw data 187392

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

.text 32256 bytes · 17.2% of section data
MD5 451be2c18cf74a1a1226e686e2788264
CODE 25600 bytes · 13.7% of section data
MD5 9f83574994cc30470c611fa2cc004df6
.rdata 17408 bytes · 9.3% of section data
MD5 5164bdc5f44d3ffa15e219de0fa8ed50
.data 4096 bytes · 2.2% of section data
MD5 df2140dcb089861232b0f1290125402d
.pdata 5632 bytes · 3.0% of section data
MD5 cda67fedc9b2f35dae51e2120df79a81
PAGE 97280 bytes · 51.9% of section data
Uncommon name
MD5 9da1df9b8a5d6856c79286a5bcd68b3d
INIT 2048 bytes · 1.1% of section data
Uncommon name
MD5 2461215f50d9e7205478fa17f799638b
.rsrc 1024 bytes · 0.5% of section data
MD5 a072045ab22c9a815f8f9bb942816c60
.reloc 2048 bytes · 1.1% of section data
MD5 4d0e62bc50d9936ad8aa587a33179f48

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