• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

How to install nvidia driver for rtx3080 on windows 1709?

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
24,444 (3.64/day)
Processor Core i7-8700K
Memory 32 GB
Video Card(s) RTX 3080
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 10 64-bit
Google around how to generate a self-signed certificate, make sure you put it into Start -> Manage user certificates ->Trusted Root Certification Authorities -> Certificates

If you've been using NVCleanstall you'll see its certificates in that same location. For security, NVCleanstall throws away the private key once it's signed the CAT file during installation, so bad people can't use it to sign stuff that's valid on the current machine.
 

leightonbmw

New Member
Joined
Jul 20, 2022
Messages
2 (0.03/day)
Can anyone please do it for me on teamviewers ive been stuck for 2hours
My discord is: LL#0101
someone please help me please.

Remove the version check in INF of the NVIDIA driver:

Code:
[Manufacturer]
%NVIDIA_A% = NVIDIA_Devices,NTamd64.10.0...14393,NTamd64.10.0...17098

[NVIDIA_Devices.NTamd64.10.0...14393]

[NVIDIA_Devices.NTamd64.10.0...17098]

Then in NVCleanstall select any expert tweak to trigger rebuilding signature.

Bear in mind that DirectX12 Ultimate is not available in old Windows 10 versions.
can u please help me on teamviewer I have been stuck for hours man :(
my discord is: LL#0101
 
Joined
Jun 8, 2021
Messages
44 (0.09/day)
If you intend to game with that modified driver, self-signing methods without an EV certificate are not viable.
You should find everything else in here but I can recall the essential steps briefly:
1. Pick the driver in Nvcleanstall, proceed to the Optional tweaks section and keep it open
2. Go into the Nvcleanstall temp folder/display driver and delete all INFs except for nv_dispi and the other 2 essential ones
3. Remove the Windows version number from the nv_dispi file
4. Unpack the nvlddmkm.sy_ and modify the .sys in HxD or IDA or WinDbg by finding the hex value of your winver and replacing it (for Ampere on 1709 it's 00 7C 3F 00 replaced with 00 0F 3A 00 and 00 AD 42 00 with 00 AB 3F 00 (among other options))
5. Rename the file to nvlddmkm.sy_ (keeping it as .sys could work, too)
6. In Nvcleanstall tick the "second" Disable Telemetry to trigger resigning (should pop up ticked then) and build the package (Note that this does not resign the .sy_)
7. Run testsigning mode on and or DSE off or somehow sign the .sy_ if you want to game

____

@W1zzard I noticed that sometimes Nvcleanstall downloads are incredibly slow, stall or don't proceed at all.
I also sometimes have to activate the KeyIso service to resign or an error message pops up (which then quits Nvcleanstall and doesn't clear the temp folder).
 

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
24,444 (3.64/day)
Processor Core i7-8700K
Memory 32 GB
Video Card(s) RTX 3080
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 10 64-bit
Just tested to sign the .sys with NVCleanstall's signing certificate (which gets put intro Trusted Root). Not enough, it still won't load the driver.

There will be a warning in next version that will alert you if KeyIso isn't running + "Retry", "Cancel" buttons
 
Joined
Jun 8, 2021
Messages
44 (0.09/day)
Just tested to sign the .sys with NVCleanstall's signing certificate (which gets put intro Trusted Root). Not enough, it still won't load the driver.

If you make it work somehow (or can circumvent the OS restriction without losing the signature in a different way), I'd be eternally grateful :D
 

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
24,444 (3.64/day)
Processor Core i7-8700K
Memory 32 GB
Video Card(s) RTX 3080
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 10 64-bit
If you make it work somehow (or can circumvent the OS restriction without losing the signature in a different way), I'd be eternally grateful :D
Can't even think of a way how to approach this
 
Joined
Jul 7, 2022
Messages
18 (0.23/day)
Just update your damn OS, why are you even on 1709 anymore

People who neglect updates are the anti-vaxxers of the IT world
 
Joined
Jun 8, 2021
Messages
44 (0.09/day)
I have nothing against newer Windows versions, I multiboot 2009 and 21H1 and whatever. But I have my reasons to partly maintain 1709. Question is why you would bother.
 

qubit

Overclocked quantum bit
Joined
Dec 6, 2007
Messages
17,482 (3.23/day)
Location
Quantum Well UK
System Name Quantumville™
Processor Intel Core i7-2700K @ 4GHz
Motherboard Asus P8Z68-V PRO/GEN3
Cooling Noctua NH-D14
Memory 16GB (2 x 8GB Corsair Vengeance Black DDR3 PC3-12800 C9 1600MHz)
Video Card(s) MSI RTX 2080 SUPER Gaming X Trio
Storage Samsung 850 Pro 256GB | WD Black 4TB | WD Blue 6TB
Display(s) BenQ XL2720Z (144Hz, 3D Vision 2, 1080p) | Asus MG28UQ (4K, 60Hz, FreeSync compatible)
Case Cooler Master HAF 922
Audio Device(s) Creative Sound Blaster X-Fi Fatal1ty PCIe
Power Supply Corsair AX1600i
Mouse Microsoft Intellimouse Pro - Black Shadow
Keyboard Yes
Software Windows 10 Pro 64-bit
Why don't you just upgrade to 21H2? I can't see any benefit to staying with an old, unsupported version of Windows. Look at the trouble you're having just installing a simple driver.
 
Joined
Jun 8, 2021
Messages
44 (0.09/day)
Why don't you just upgrade to 21H2? I can't see any benefit to staying with an old, unsupported version of Windows. Look at the trouble you're having just installing a simple driver.

The only reason I comment on useless contributions like this again is to hopefully make you see how useless they are.
This is about signing a modified kernel driver (1 hex string) to make it work on an outdated Windows version that I have to maintain - and not about my personal preference of Windows versions.
Again, I multiboot many Windows versions for different purposes and have no issue with the recent versions.
The driver works, the limitations is unnecessary and there are more scenarios where solving this is useful.
 

qubit

Overclocked quantum bit
Joined
Dec 6, 2007
Messages
17,482 (3.23/day)
Location
Quantum Well UK
System Name Quantumville™
Processor Intel Core i7-2700K @ 4GHz
Motherboard Asus P8Z68-V PRO/GEN3
Cooling Noctua NH-D14
Memory 16GB (2 x 8GB Corsair Vengeance Black DDR3 PC3-12800 C9 1600MHz)
Video Card(s) MSI RTX 2080 SUPER Gaming X Trio
Storage Samsung 850 Pro 256GB | WD Black 4TB | WD Blue 6TB
Display(s) BenQ XL2720Z (144Hz, 3D Vision 2, 1080p) | Asus MG28UQ (4K, 60Hz, FreeSync compatible)
Case Cooler Master HAF 922
Audio Device(s) Creative Sound Blaster X-Fi Fatal1ty PCIe
Power Supply Corsair AX1600i
Mouse Microsoft Intellimouse Pro - Black Shadow
Keyboard Yes
Software Windows 10 Pro 64-bit
The only reason I comment on useless contributions like this again is to hopefully make you see how useless they are.
This is about signing a modified kernel driver (1 hex string) to make it work on an outdated Windows version that I have to maintain - and not about my personal preference of Windows versions.
Again, I multiboot many Windows versions for different purposes and have no issue with the recent versions.
The driver works, the limitations is unnecessary and there are more scenarios where solving this is useful.
Apologies, my comment was intentended for the OP @Wasaki (I would still like to know :) ) but thanks for the clarification. I can see the confusion coming right after yours, which I hadn't seen. I should have perhaps tagged the OP.

I know what you mean about maintaining outdated systems - what a pita.
 

leightonbmw

New Member
Joined
Jul 20, 2022
Messages
2 (0.03/day)
The only reason I comment on useless contributions like this again is to hopefully make you see how useless they are.
This is about signing a modified kernel driver (1 hex string) to make it work on an outdated Windows version that I have to maintain - and not about my personal preference of Windows versions.
Again, I multiboot many Windows versions for different purposes and have no issue with the recent versions.
The driver works, the limitations is unnecessary and there are more scenarios where solving this is useful.
same..

The only reason I comment on useless contributions like this again is to hopefully make you see how useless they are.
This is about signing a modified kernel driver (1 hex string) to make it work on an outdated Windows version that I have to maintain - and not about my personal preference of Windows versions.
Again, I multiboot many Windows versions for different purposes and have no issue with the recent versions.
The driver works, the limitations is unnecessary and there are more scenarios where solving this is useful.
I am still stuck can u please add me on discord.
LL#0101
I need help via teamviewer please.
 
Top