GridinSoft Threat Intelligence
nvlddmkm.sys file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-05-22 09:06:25 (9 years ago); latest analysis 2021-01-09 22:46:53 (5 years ago).
Company metadata: NVIDIA Corporation. Product metadata: NVIDIA Windows Kernel Mode Driver, Version 342.01 .
Signed by NVIDIA Corporation. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
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.
File Details
| 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) |
Overview
| 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.
Common Places:
| %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.
Geographic signal
Observed country distribution
ThreatInfo has seen nvlddmkm.sys across 24 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Russian Federation with 13.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
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.
Analysis
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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
f226bb846c4c635bbe12dc52619ce349
173c8d4c127f68fdac7504803d580397
0607a3d70ebaa1deb59a144ec4b89a31
c66bca0e3a9e12c339daec36e64e673d
33de1da00b2137a72b88fc1fe715feb7
abe814dda43d3c02ac5ee2ca8c7a0cb7
58b6b9771ab4bf4af2a63a3cb106d8b5
1c5ce75169931a2b164b4317048504b9
7c91e9bf16a66fc2801543a68310a633
7c91e9bf16a66fc2801543a68310a633
ba302a05b59384f844ee8ca075411a73
bf20e32c7a58f4db0fe3f9701198b42b
c4fa682471bdd6bf7f23610db8044c72
a2f0a2346cdb0de91adb98181d657c5a
bb68bd4bdbe2276ecac78e57b7c13fd4
81f50846028bd0dfb4d8e044a32527ea
13cfc6ccb647ccc290726be0b75a4400
e23d57e127f4cb6deb35409f65180a51
bf619eac0cdf3f68d496ea9344137e8b
bf619eac0cdf3f68d496ea9344137e8b
bf619eac0cdf3f68d496ea9344137e8b
3eddfe1ae238286fe5aa3288984aa4dd
c2416cc9f932be8eceda951d9cf62707
d6c7d0546f1deb0d1e27eb06294d23b5
75c9f3b73b6320f633a83185f1af35e7
359a2c19e77e96c3d9bc04aea6eef483
d299682970084b7d16767c6000a34085
74799aad4d5ceefbc32882d27775bfc1
03a5873c7193fd4e0030afe2cf56affc
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.