irkfineIn my system with EVGA Titan X (Maxwell) the last working NVIDIA driver is 385.69, all later drivers either fail to install or "install" but show error 43, this also including the last EVGA driver. I do not know if and to what extent hardware configuration may be impacting this though the system is not very typical. There are two Titan X in SLI configuration and GTX 970 assembled in workstation with Xeon processor, 128GB RAM and Windows 10 64-bit. Advice I get is to test with with one Titan X but this is not so simple since the GPUs are watercooled in a single loop and dismantling would be cumbersome. The hardware does not seem to me be big part of the problem since up to the driver 385.69 the system works absolutely prefect including overclocking and stressing. I tried whatever possible with the installation of drivers and any other tricks I could find but nothing helps. What could be the problem here? I find amazing that the driver 385.69 works perfectly and the next in line 388.00 and all after it totally fail. There had to be some change in the driver software but what it could be?
SajinYou running a modded vbios on your cards? If yes, that is the issue.
veganfanaticI suggest installing Windows 10 v 20H2 so that all patches are current
irkfineveganfanaticI suggest installing Windows 10 v 20H2 so that all patches are currentOh yes, but this version does not install, when I try it runs installation but when it restarts goes into undoing changes. That of course is likely caused by graphics drivers not installing properly which in turn could be because the GPU BIOS is not signed properly.
irkfineSajinYou running a modded vbios on your cards? If yes, that is the issue.How do I check this? in GPU-Z there is BIOS version 84.001F.00.90 version but is this modded? Another question is why modded does not work after the driver 385.86, has Nvidia changed drivers to eliminate modding?
irkfineNow perhaps somebody could explain if there is modded BIOS for Titan X which is compatible with current Nvidia drivers?
irkfineIndeed the problem was modded BIOS of Titan X. After reflashing original BIOS with NVFlash Nvidia drivers install with no problems. That was also the issue with Windows 10 update 20H2. Thank you guys for your help, I appreciate this. Now perhaps somebody could explain if there is modded BIOS for Titan X which is compatible with current Nvidia drivers?
irkfineThank you for the explanation.Indeed starting from Pascal signatures are required and from Ampere BIOS is encrypted. Another potential way is Maxwell BIOS Tweaker but again the question will such tweaked VBIOS work with recent NVidia drivers? Some kind of tweaking is done even with the RTX30* cards, just replacing BIOS with BIOS form another card which has higher settings:
HeavyHemiNo that is not another potential way. Modifying the BIOS invalidates the signature. Valid signature is required by the driver. You'd end up where you are now. It's not like folks have not been trying this for literally years.
bob16314If you haven't yet, I would try Disable Driver Signature Enforcement in Windows and see if the driver installs with a modded VBIOS..Otherwise, I suppose you'd need to flash a valid/approved VBIOS when you wanna update/change/reinstall the driver, then flash it back to your modded VBIOS after that.
bob16314If you haven't yet, I would try in Windows and see if the driver installs with a modded VBIOS..Otherwise, I suppose you'd need to flash a valid/approved VBIOS when you wanna update/change/reinstall the driver, then flash it back to your modded VBIOS after that.
irkfinebob16314If you haven't yet, I would try in Windows and see if the driver installs with a modded VBIOS..Otherwise, I suppose you'd need to flash a valid/approved VBIOS when you wanna update/change/reinstall the driver, then flash it back to your modded VBIOS after that.Disabling Driver Signature does not help, I checked this. This indicates that Nvidia goes farther than standard driver signature and during installation the driver software checks some kind of internal signature of VBIOS. As described above there is at present no way to mod the VBIOS and make it running with recent Nvidia drivers. It is possible to flash VBIOS between same type cards of different manufacturers which to me looks that there is only single Nvidia key for signing it. However manufacturers must have access to the signature producing software for setting VBIOS parameters. It is kind of amazing that nobody was able to crack this when people are able to do seemingly much more crazy things like emulation of the Nintendo Switch console.
safan80I don't see any mention of using the DDU driver install method.
ty_ger07safan80I don't see any mention of using the DDU driver install method.Irrelevant.He was using a modified BIOS which will not work with modern drivers, no matter the driver install method.
safan80ty_ger07safan80I don't see any mention of using the DDU driver install method.Irrelevant.He was using a modified BIOS which will not work with modern drivers, no matter the driver install method.It would work with the last working driver that the modded bios was running on.
ty_ger07safan80ty_ger07safan80I don't see any mention of using the DDU driver install method.Irrelevant.He was using a modified BIOS which will not work with modern drivers, no matter the driver install method.It would work with the last working driver that the modded bios was running on.Yes, but it was/is. DDU is irrelevant to that. He has no problem installing and using the last working driver. The problem is that he wants to use a newer driver. The last working driver is probably missing features he is interested in using, and is not compatible with newer Windows updates.
HeavyHemiWhen you modify the BIOS you change the checksum. It really isn't that complicated which is why it is still effective. Your other question is of course you can use MSI Afterburner to set whatever overclock on the core or memory or fan profile you'd like, to be applied at Windows boot. I ran SLI for a long time so I am quite familiar with it.
ty_ger07Yes, but it was/is. DDU is irrelevant to that. He has no problem installing and using the last working driver. The problem is that he wants to use a newer driver. The last working driver is probably missing features he is interested in using, and is not compatible with newer Windows updates.
irkfineI am now looking into the use of Afterburner but does it include a way of applying modified parameters to the card at boot without starting the whole application with its user interface etc?
irkfineHeavyHemiWhen you modify the BIOS you change the checksum. It really isn't that complicated which is why it is still effective. Your other question is of course you can use MSI Afterburner to set whatever overclock on the core or memory or fan profile you'd like, to be applied at Windows boot. I ran SLI for a long time so I am quite familiar with it.I believe Nvidia signature is more than checksum checking, it is kind of signing of the driver. Most recent Ampere cards have VBIOS encrypted. All this is understandable since drivers sit in the OS kernel and that cuts one backdoor whcih could be used for bad purpose. I am now looking into the use of Afterburner but does it include a way of applying modified parameters to the card at boot without starting the whole application with its user interface etc?