GridinSoft Threat Intelligence

nvlddmkm.sys file report

Clean record File reputation report
MD5 f83abf2df6d4bc8ba11f463e2353d2e1
Latest seen 2021-01-09 22:46:53 (5 years ago)
First seen 2017-05-22 09:06:25 (9 years ago)
Size 10 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 2017-05-22 09:06:25 (9 years ago); latest analysis 2021-01-09 22:46:53 (5 years ago).

Publisher context

Company metadata: NVIDIA Corporation. Product metadata: NVIDIA Windows Kernel Mode Driver, Version 342.01 .

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.

nvlddmkm.sys is a Windows file recorded in the ThreatInfo database. It is associated with NVIDIA Windows Kernel Mode Driver, Version 342.01 . The reported company name is NVIDIA Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-09 22:46:53 (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: NVIDIA Windows Kernel Mode Driver, Version 342.01
Company Name: NVIDIA Corporation
MD5: f83abf2df6d4bc8ba11f463e2353d2e1
Size: 10 MB
First Published: 2017-05-22 09:06:25 (9 years ago)
Latest Published: 2021-01-09 22:46:53 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-09 22:46:53 (5 years ago)
Signed By: NVIDIA Corporation
Status: Valid

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

%localappdata%\innovative solutions\drivermax\agent\tmp\display\pci_ven_10de@amp;dev_0a75@amp;subsys_c06a144d
%system%
%sysdrive%\$windows.~q\data\windows\system32\driverstore\filerepository
%system%\driverstore\filerepository
%sysdrive%\برامج\2019\nvidia\forced\ntx86
%localappdata%\slimware utilities inc\slimdrivers\backups\20200309t215000647104\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20191017t121155279469\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20191022t110208690982\pci
%localappdata%\innovative solutions\drivermax\agent\uploads\5xw718n3co4h0er1vaeo4uj2j6xs1qkecl2ntp1dg76f1hf457\display
%localappdata%\innovative solutions\drivermax\agent\restore\4h22fdu3e8l0022j6n931gin6836vfrqmc4c97gf4n20h75daf\display

ThreatInfo has observed nvlddmkm.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 72.5%
Windows 10 17.5%
Windows 8.1 7.5%
Windows Vista 1.3%
Windows 8 1.3%

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

nvlddmkm.sys is identified as pe for 32-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 32-bit
Subsystem Native
Entry point 0x00a2d000
Image base 0x00010000

PE Sections:

Sections 30
Raw data 10694656

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

.text 4638208 bytes · 43.4% of section data
MD5 f226bb846c4c635bbe12dc52619ce349
_OSSVC 1024 bytes · 0.0% of section data
Uncommon name
MD5 173c8d4c127f68fdac7504803d580397
.rdata 1022464 bytes · 9.6% of section data
MD5 0607a3d70ebaa1deb59a144ec4b89a31
.data 1947648 bytes · 18.2% of section data
MD5 c66bca0e3a9e12c339daec36e64e673d
.text 512 bytes · 0.0% of section data
MD5 33de1da00b2137a72b88fc1fe715feb7
PAGE 749056 bytes · 7.0% of section data
Uncommon name
MD5 abe814dda43d3c02ac5ee2ca8c7a0cb7
PAGE_WSV 512 bytes · 0.0% of section data
Uncommon name
MD5 58b6b9771ab4bf4af2a63a3cb106d8b5
PAGE_MCM 12288 bytes · 0.1% of section data
Uncommon name
MD5 1c5ce75169931a2b164b4317048504b9
PAGECNLG 512 bytes · 0.0% of section data
Uncommon name
MD5 7c91e9bf16a66fc2801543a68310a633
PAGECTES 512 bytes · 0.0% of section data
Uncommon name
MD5 7c91e9bf16a66fc2801543a68310a633
PAGECFER 5120 bytes · 0.0% of section data
Uncommon name
MD5 ba302a05b59384f844ee8ca075411a73
PAGEcTSL 666112 bytes · 6.2% of section data
Uncommon name
MD5 bf20e32c7a58f4db0fe3f9701198b42b
PAGEcKPL 50176 bytes · 0.5% of section data
Uncommon name
MD5 c4fa682471bdd6bf7f23610db8044c72
PAGEcMXL 50688 bytes · 0.5% of section data
Uncommon name
MD5 a2f0a2346cdb0de91adb98181d657c5a
PAGEcFRM 108032 bytes · 1.0% of section data
Uncommon name
MD5 bb68bd4bdbe2276ecac78e57b7c13fd4
.edata 512 bytes · 0.0% of section data
MD5 81f50846028bd0dfb4d8e044a32527ea
PAGECONS 49152 bytes · 0.5% of section data
Uncommon name
MD5 13cfc6ccb647ccc290726be0b75a4400
PAGEDATA 198656 bytes · 1.9% of section data
Uncommon name
MD5 e23d57e127f4cb6deb35409f65180a51
PAGEDNLG 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
PAGEDTES 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
PAGEDFER 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
PAGEcRMA 9728 bytes · 0.1% of section data
Uncommon name
MD5 3eddfe1ae238286fe5aa3288984aa4dd
PAGEcRM 199168 bytes · 1.9% of section data
Uncommon name
MD5 c2416cc9f932be8eceda951d9cf62707
PAGEdMXL 122368 bytes · 1.1% of section data
Uncommon name
MD5 d6c7d0546f1deb0d1e27eb06294d23b5
PAGEdKPL 223232 bytes · 2.1% of section data
Uncommon name
MD5 75c9f3b73b6320f633a83185f1af35e7
PAGEdFRM 270336 bytes · 2.5% of section data
Uncommon name
MD5 359a2c19e77e96c3d9bc04aea6eef483
PAGEdTSL 51200 bytes · 0.5% of section data
Uncommon name
MD5 d299682970084b7d16767c6000a34085
INIT 21504 bytes · 0.2% of section data
Uncommon name
MD5 74799aad4d5ceefbc32882d27775bfc1
.rsrc 18944 bytes · 0.2% of section data
MD5 03a5873c7193fd4e0030afe2cf56affc
.reloc 275456 bytes · 2.6% of section data
MD5 1fbc10970d32e3ab9726d778f3591a14

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