Jump to content

Error 52 on GT 1030 Driver on Windows 8.1


legacyfan

Recommended Posts

does anyone know how to fix this? ive been having this problem for the past 2 days and can't figure out what causes it ive even tried updating the root certificates and that did nothing to fix the problem if anyone know how to fix this it would be much appreciated

Link to comment
Share on other sites


Error Code 52 is a blatant driver digital signature issue with your Graphics Driver in the combination with the operating system. 8.1 has very strict demands towards WHQL. Clean manual installation of WHQL graphics drivers resolve the issue.

Link to comment
Share on other sites

14 hours ago, bruno16757 said:

have to turn on test signing

This is needed only if he somehow managed to mod the drivers, which I very much doubt, knowing legacyfan.

Also, he would get a watermark then. 

Link to comment
Share on other sites

9 hours ago, bruno16757 said:

Changes to the display driver installation process under Microsoft Windows 7 | NVIDIA (custhelp.com)

 

https://nvidia.custhelp.com/app/answers/detail/a_id/5445/~/changes-to-the-display-driver-installation-process-under-microsoft-windows-7

 

it applys to windows 8.1 as well

The article you gave is for Microsoft Windows 7, the original question was about Windows 8.1.

Also, I'm pretty sure this is not relevant, not only because of the wrong OS, but also due to the 

fact his card is 6 years old, and the last driver for it was from 2021, 2 years old, and they claim 

in the article - they made these changes only starting from the January of 2023. (!)

"Starting January 16th 2023 ..."

Try this driver 471 (the R470 branch from 2021 is the last for Windows 8.1):

I myself tried and it worked with my spare (guinea pig) GT1030 EVGA SC.

https://www.evga.com/products/specs/gpu.aspx?pn=c22d5809-ca26-4974-901f-07065acf1bf1

https://www.nvidia.com/download/driverResults.aspx/176519/en-uk/

My remark : This is insane, actually. MS and Nvidia can't get their crap together, lol.

End users shouldn't burden themselves with such inconveniences .

Edited by D.Draker
a typo in the date (month)
Link to comment
Share on other sites

22 hours ago, bruno16757 said:

i said you have to turn on testsigning on for windows 8.1 as well to to use the latest driver.  

GeForce Security Update Driver | 474.30 | Windows 7 64-bit, Windows 8.1 64-bit, Windows 8 64-bit | NVIDIA

 

thats the latest driver for windows 8.1   https://www.nvidia.com/Download/driverResults.aspx/203218/en-us/

He wouldn't need to do anything if he hadn't touched that "Security Update Driver", because it's 

what creates the issue in the first place. According to Nvidia themselves "Security Update Drivers"

don't bring anything new to the table in terms of gaming, in fact they do reduce FPS, it's been known for decades.

So it's the same old 471 driver (branch R470) from 2 years ago, in the flesh.

But whaddaiknow from only 23 years of using Nvidia.

Looks like the OP lost the diesire to talk and went dark, so we'll never know the happy end (not).

Link to comment
Share on other sites

I did get it working I just used the latest WHQL driver from nvidia official site (from November 2022) and that driver installed without issues 

Edited by legacyfan
Link to comment
Share on other sites

4 hours ago, legacyfan said:

I did get it working I just used the latest WHQL driver from nvidia official site (from November 2022) and that driver installed without issues 

Yes, that's right, just like I suggested, before they made the stupid changes in 2023.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...