GridinSoft Threat Intelligence

nvwgf2um.dll file report

Clean record File reputation report
MD5 565b498d8d30ca689cd1c6db93c7d37a
Latest seen 2021-01-09 23:04:22 (5 years ago)
First seen 2017-05-22 09:06:28 (9 years ago)
Size 15 MB
Publisher NVIDIA Corporation
Product NVIDIA D3D10 drivers
Signed by NVIDIA Corporation PE Sign v2016

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

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

Publisher context

Company metadata: NVIDIA Corporation. Product metadata: NVIDIA D3D10 drivers.

Digital signature

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

File context

nvwgf2um.dll is a Windows file recorded in the ThreatInfo database. It is associated with NVIDIA D3D10 drivers. The reported company name is NVIDIA Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-09 23:04:22 (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.

File Details

Product Name: NVIDIA D3D10 drivers
Company Name: NVIDIA Corporation
MD5: 565b498d8d30ca689cd1c6db93c7d37a
Size: 15 MB
First Published: 2017-05-22 09:06:28 (9 years ago)
Latest Published: 2021-01-09 23:04:22 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-09 23:04:22 (5 years ago)

Overview

Signed By: NVIDIA Corporation PE Sign v2016
Status: Valid

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

Common Places:

%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 nvwgf2um.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 nvwgf2um.dll across 6 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Turkey
Share 41.7%
Low High activity

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

OS Version:

Windows 7 75.0%
Windows 10 16.7%
Windows Vista 8.3%

The most common operating system signal for nvwgf2um.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.

Analysis

nvwgf2um.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 0x00009480
Image base 0x10000000

PE Sections:

Sections 9
Raw data 16027648

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

.text 9642496 bytes · 60.2% of section data
Large raw data
MD5 2cb652073f9af54bc63cc209cf7afe46
PAGE 20992 bytes · 0.1% of section data
Uncommon name
MD5 322a6a3b7565bacd24c992fde08653ea
.rdata 1027584 bytes · 6.4% of section data
MD5 8b87e3facc7d37434048b84c91fb2456
.data 4978688 bytes · 31.1% of section data
MD5 84365ee50a5b565c7af9ece542b8702f
PAGECONS 28672 bytes · 0.2% of section data
Uncommon name
MD5 c5053d36014ca12c879705a733093282
PAGEDATA 9216 bytes · 0.1% of section data
Uncommon name
MD5 5ad3e12e533247a39805df7c08406e63
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1024 bytes · 0.0% of section data
MD5 1c50110923f123cfa339e3c47387f149
.reloc 318464 bytes · 2.0% of section data
MD5 e9a50ae6cbe12c9a0e7a63527f321d57

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 565b498d8d30ca689cd1c6db93c7d37a.
  • 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.