#PNY RTX 5070 driver issues out of nowhere

1 messages · Page 1 of 1 (latest)

lament socket
#

I have tried everything. I asked AI first before coming to seek help here.

What occured?
I tried installing nvidia home app and it failed through the app so I tried installing manually and it too failed 0x80070002.
THEN I tried installing the game ready graphics driver STANDALONE no extra checks in the installer. It will show the install bar and stop at a very specific point (shown all in pictures) and then it will fail the installaton.

What have I done?
Delete NVIDIA apps from apps section in settings, deleted hkey/regedit keys, deleted program data and program files (and 86x), Ive gone to bios changed auto to gen 4 for the speed thing (forgot what its called), Ive taken out my GPU physically and refit it and plugged it in and the hdmi to the graphics card. I booted into safe mode and tried DDU (Display Driver Uninstaller) Ive DONE EVERYTHING so Im lost please help

#

Win 11 23H2 (OS Build 22631.6199)

i7-13700KF
48 Gig RAM
RTX 5070
2 TB storage

#

I DO have a 3080ti on the side I can try if you suggest I should

#

let me know

#

I was kinda hoping not having to

#

the AI was suggesting driver store errors or something and said I might have to reset to 0 nuke everything on my PC like its MW2 2009. If this is the case I am switching to linux.

lament socket
#

nvm dont answer the 3080 ti question

#

I am on it rn and just tried installing standalone drivers

#

the same way I did with the 5070 installed

#

SAME ISSUE

lament socket
#

Ping me whenever any updates/questions/tips please

quaint lintel
paper axleBOT
#

Some Intel 13th/14th gen desktop CPUs (unlocked CPUs, as well as locked i7/i9), may have stability issues due to excessive voltages, on out of date BIOS/microcode. This may show up as errors, crashes, and BSODs. In some occasions, this error may blame a different part (e.g. out of video memory) despite it being caused by a defective CPU.

Common things that may fail with a defective CPU include the following, and more:

  • Crashes during shader compilation
  • Crashes during decompression (game loading)
  • Crashes during driver installation/updates

Please go to these Intel Community threads for further information: https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633446#M40
https://community.intel.com/t5/Processors/Intel-Core-13th-and-14th-Gen-Vmin-Shift-Instabilty-Update-New/m-p/1686948

To prevent damage to your CPU and possibly restore stability, please perform a BIOS/firmware update for your motherboard (or system, if this is a name-brand pre-build system).

  • At a minimum, to a version containing the 0x12B microcode or newer.
  • Ideally, and if offered, have the supplementary 0x12F microcode or newer.

You can check the support pages for your motherboard/system model for any BIOS updates you may need. Below are a few common motherboard manufacturers:
ASRock
Asus
Gigabyte
MSI

If your CPU is currently exhibiting instability even after performing BIOS/firmware and microcode updates, please contact Intel or your system builder for a warranty exchange (RMA), as your CPU may be permanently damaged.

quaint lintel
#

Start planning to send your CPU for warranty/RMA

lament socket
#

Wait wait

#

Is it possible it isnt cooked yet

#

And all i gotta do is update bios

pulsar ivy
#

Right as you get a 13th or 14th gen you have to update your bios to prevent it

#

If you do not and the damage is done or early symptoms start then most of the time is too late

#

sorry

pulsar ivy
#

your best option currently

lament socket
#

I updated the bios

#

and it stills fails to update

#

or install

#

any graphics drivers or nvidia home app

#

im not crashing

#

so thats why I dont think I have this issue

#

this wouldve popped up a long time ago if it was a CPU issue

#

its been like 3 years

quaint lintel
#

Please RMA your CPU

lament socket
#

well im looking at the logs and that doesnt seem to be the issue at all

#

it says its a driver store issue

#

likely so

#

0x00000002 errors when installing the infs from the extracted contents of the display driver game ready exe

#

even AI says otherwise on this one

#

and im giving it the logs

lament socket
#

other then installing a graphics driver

#

because I dont thjink this is the case

quaint lintel
#

the game will crash at shader compilation or comes out with out of VRAM errors

#

It's unlikely that two of your GPUs are broken tbh

lament socket
#

I think I know one game of mine to test

#

dead island 2 has a shader comp everytime at launch

#

let me try that rq

quaint lintel
#

The first descendants, ark, the finals and Fortnite are literally free

lament socket
#

oh oh ohh

#

ill try the finals

#

I gotta reinstall it htough

#

😭

lament socket
#

btw heres what github copilot had to say after seeing part of my logs from a few things

Short answer: No — this isn’t a CPU issue.

Why:

The failure happens at driver registration with 0x80070002 (“File not found”) when creating the package object in the DRIVERS registry hive. That’s an OS/DriverStore/registry plumbing problem, not compute instability.
Both GPUs fail identically. Hardware faults (CPU/GPU) wouldn’t consistently produce “missing registry key” errors at the same stage.
DISM/SFC completed cleanly, and manually loading HKLM\DRIVERS immediately changed behavior — again pointing to registry/hive state, not CPU.

If you still want to sanity‑check CPU:

Look in Event Viewer for WHEA-Logger errors (System log, Event ID 18 or 19).
Run a 10–15 minute stress test (e.g., OCCT or Prime95 small FFTs) and watch for errors or throttling.
Check for random BSODs, app crashes, or compile/test failures — those are typical CPU instability signs.

Best path forward remains:

Persist the DRIVERS hive mapping: reg add "HKLM\SYSTEM\CurrentControlSet\Control\hivelist" /v "\REGISTRY\MACHINE\DRIVERS" /t REG_SZ /d \Device\HarddiskVolume3\Windows\System32\Config\DRIVERS /f
Then install with: pnputil /add-driver "C:\NVIDIA\DisplayDriver" /subdirs /install
If it fails, grab the last 200 lines of C:\Windows\inf\setupapi.dev.log right after the attempt and share them. That will pinpoint any remaining file/path issue.
#

I would share logs here but I dont have nitro and dont got money for nitro and discord limits my uploads

quaint lintel
lament socket
#

YES

#

I did

#

talon debloater

#

A LONGGGG

#

TIME AGO

#

when I first setup windows

quaint lintel
lament socket
#

I dont think it has anything to do with that

#

because I update graphics drivers often and it never had issues like this

#

and it wasnt now it was before I even installed the graphics drivers that I ran talon debloater

#

so it isnt that either

quaint lintel
#

not a joke, Debloaters actually break your PC since it removes the files that are needed by the system especially after a version update (like from 23H2 to 24H2 and 25H2)

#

sure it doesn't break, until a windows update arrives with feature updates

#

cause the debloater "assumes" that the file isn't used

#

But the file itself will be used/activated with a package enabler in a future windows update

lament socket
#

hmmm

#

ill get back to you on this one

quaint lintel
#

Please do a full Windows reinstall

paper axleBOT
#

If you are intending to reinstall Windows or reset your PC, do not use the “Reset This PC” option. Instead, please use the Media Creation Tool for Windows 10 or 11 to create a USB install to wipe the disk and reinstall Windows. Alternatively, you can use the recovery drive/factory image to restore your PC to the original manufacturer state if you are using a prebuild PC.

If Windows is not working properly especially after a Windows update or a Windows feature upgrade (such as from 23H2 to 24H2), you can do the following:

  • Use the “Fix Problems using Windows Update”. Open the settings app > System > Recovery > Fix Problems using Windows Update
  • Use the Media Creation Tool for Windows 10 or 11 and perform an in-place upgrade. Boot up the Windows Installation on your USB and press “Upgrade:Install Windows and keep files, settings and applications.”
  • Roll back to a previous Windows upgrade: Open the settings app > System > Recovery > Previous Version of Windows.
  • Uninstall problematic Windows Update: Open the settings app > System > Windows Update > Update History (Take note of the recent update installed) > Uninstall Updates
quaint lintel
lament socket
#

if I have to reset I might as well switch to linux so im not spywared on my OS at least

quaint lintel
lament socket
#

Ive done it before

#

its supported

quaint lintel
#

you're getting a 30% performance loss

lament socket
#

not at all LOL

#

that is not the case

#

at least when I tried it with the real drivers but on my linux back then it worked fine

quaint lintel
# lament socket that is not the case

Nvidia GPUs on Linux often suffer from 18-30% lower performance compared to Windows, particularly in DirectX 12 titles, with issues worsening to ~50% in ray-tracing scenarios. Recent regressions (drivers 570-580+) have caused significant drops, often linked to VRAM mismanagement, stuttering, and poor Wayland support.

lament socket
#

it just sucked cause I couldnt play all my games

quaint lintel
#

The 50 series is performing worse than the 40 series

#

Also good luck trying to turn on DLSS overrides on Linux

lament socket
#

WAITWAITYWAIT

#

SteamOS

#

I WINNNNNN

#

thats my best card to pull on this one

#

benchmarks say its onyl 5-10%

#

ok so im gonna keep trying with githubcopilot but if nothing avails I will ultimately reset my PC probably switch to linux and use steamOS for gaming but if I survive this im probably STILL going to use SteamOS for gaming maybe

quaint lintel
#

Also, you still have performance loss of up to 15%, or as slow as a 5060 in some games even in Bazzite

#

Good luck with the 1% lows

lament socket
#

🥀

#

iim going to continue my fixing tomorrow or after

#

my bday is tomorrow