GridinSoft Threat Intelligence

nvvad64v.sys file report

Clean record File reputation report
MD5 e502016a185b5bb9dc341873f82cd49c
Latest seen 2022-04-30 23:08:49 (4 years ago)
First seen 2020-08-22 04:46:36 (5 years ago)
Size 49 KB
Publisher NVIDIA Corporation
Product NVIDIA Virtual Audio Driver
Signed by NVIDIA Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-08-22 04:46:36 (5 years ago); latest analysis 2022-04-30 23:08:49 (4 years ago).

Publisher context

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

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.

File context

nvvad64v.sys is a Windows file recorded in the ThreatInfo database. It is associated with NVIDIA Virtual Audio Driver. The reported company name is NVIDIA Corporation. The current detection status is Clean, based on the latest analysis from 2022-04-30 23:08:49 (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: NVIDIA Virtual Audio Driver
Company Name: NVIDIA Corporation
MD5: e502016a185b5bb9dc341873f82cd49c
Size: 49 KB
First Published: 2020-08-22 04:46:36 (5 years ago)
Latest Published: 2022-04-30 23:08:49 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-04-30 23:08:49 (4 years ago)

Overview

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.

Common Places:

%localappdata%\slimware utilities inc\slimdrivers\backups\20180117t020633240692\usb
%localappdata%\slimware utilities inc\slimdrivers\backups\20180117t015921439151\usb
%localappdata%\slimware utilities inc\slimdrivers\backups\20180117t020317360348\usb
%localappdata%\slimware utilities inc\slimdrivers\backups\20180117t020833440501\usb
%localappdata%\slimware utilities inc\slimdrivers\backups\20180122t201154419030\usb

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

Geographic signal

Observed country distribution

ThreatInfo has seen nvvad64v.sys across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Ecuador
Share 80.0%
Low High activity

The strongest geographic signal for this file is Ecuador with 80.0% 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 nvvad64v.sys 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

nvvad64v.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 0x0000b0a0
Image base 0x0000000000010000

PE Sections:

Sections 9
Raw data 34816

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

.text 6656 bytes · 19.1% of section data
MD5 d1f87d5df4a87109700da1dac72e2c2d
CODE 512 bytes · 1.5% of section data
MD5 0d254fc1674a24095bfe355b7f24eb8d
.rdata 3584 bytes · 10.3% of section data
MD5 b1a7bf2268cee72cbe9ce8fadcb68dc5
.data 2560 bytes · 7.4% of section data
MD5 f17818ef628c42c65dfd01d684dcd9a2
.pdata 1024 bytes · 2.9% of section data
MD5 08c8a43c26c92dbfb2128ea6190de023
PAGE 15360 bytes · 44.1% of section data
Uncommon name
MD5 3e16ee642b423722b7620356b698fae6
INIT 2048 bytes · 5.9% of section data
Uncommon name
MD5 8b29edfd8898e0928f25801504961ca9
.rsrc 2048 bytes · 5.9% of section data
MD5 1c1abe76d51ba4d9f73c1918d031f87d
.reloc 1024 bytes · 2.9% of section data
MD5 a9dc8fc8f1f8e984fff88ab4824110e9

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