nvidia game driver update BSOD horror

[keithhazel13]

i "upgraded" from geforce experience to nvidia app and then clicked on update game driver, i did the full new install and not the install over new one, played game for 15 minutes all was well and shut down for night, opened this morning to dreaded bluescreen with constant loop of "your device ran into a problem and needs restarting" with info at the bottom saying its CRITICAL PROCESS DIED, no matter which recovery option and several given which iv'e tried all it says ran into error, safe mode will not happen after f8 press upon start.. i have read that older gpu's can have this problem and mine is 5 years old an i7 i once before had a problem with a driver uddate but i was able to do a system restore but won't let me do that either, with hindsight the game driver never mentioned ets2 but i just assumed one driver update works for all... any ideas what to do ? thanks

[r.linder]

https://www.wagnardsoft.com/display-driver-uninstaller-ddu-

Run DDU while Windows is in safe mode, wipe the GPU drivers from the system and reboot back into the normal Windows environment, then reinstall the latest drivers.

https://www.wikihow.com/Start-Windows-in-Safe-Mode

[Phénomènes Mystiques]

And people make fun of me for not updating the Aug driver for this 1080Ti.

How about, WinRE < Startup Repair? Can you even get into WinRE?

The best thing to do is not panic and perhaps, Google this specific issue on this specific board, most likely it's happened to others on this exact series board.

I cannot really suggest anything concrete as this issue has never happened to me with the new Nvidia App nor do I even have that thing installed so I am out-of-ideas.

[Trout]

keithhazel13님이 먼저 게시:

safe mode will not happen after f8 press upon start..

you can't get into recovery mode at all? even if you try twice to constantly power off/fhard reboot while windows is booting to force automatic repair?

r.linder님이 먼저 게시:

Run DDU while Windows is in safe mode

this will be good advice once he can actually boot into safe mode in the first place

[Bad 💀 Motha]

Just STOP "updating" drivers.
Clean install them each and every time. Very simple, easy and less headache.

[keithhazel13]

I did not update drivers i did a "clean install" , i have had a failed driver install error once before using gforce app and was lucky i was able to do a system restore and got rid of new driver update as well as gforce app, this time however it would NOT allow ANY recovery method, no safe mode or any of the other half dozen options the recovery section lets you pick, it was just an ongoing loop straight back to bluescreen....luckily my brother knows about computers and he did a total wipe of windows and re-installed it, drastic but no other option...unsure what to do now as do i re-install geforce experience which i like although i hear that's going to be took off and replaced with gforce app ,if i don't have driver updates after missing a few will the game work anymore...i think it was set to automatically download new drivers so not sure why i had the option to download one which did this, it was the one showing indiana jones, i did read about it and it never said it covered ets2 so i should have kept away..or should I ? I am living proof that "a little bit of knowledge can be a dangerous thing"

[Bad 💀 Motha]

Why a system restore could just use safe mode and wipe all of that put very easily

[GOD RAYS ON ULTRA™]

https://nvidia.custhelp.com/app/answers/detail/a_id/5554/~/pc-may-bugcheck-when-installing-nvidia-graphics-driver-version-555.85-through

[GOD RAYS ON ULTRA™]

keithhazel13님이 먼저 게시:

i "upgraded" from geforce experience to nvidia app and then clicked on update game driver, i did the full new install and not the install over new one, played game for 15 minutes all was well and shut down for night, opened this morning to dreaded bluescreen with constant loop of "your device ran into a problem and needs restarting" with info at the bottom saying its CRITICAL PROCESS DIED, no matter which recovery option and several given which iv'e tried all it says ran into error, safe mode will not happen after f8 press upon start.. i have read that older gpu's can have this problem and mine is 5 years old an i7 i once before had a problem with a driver uddate but i was able to do a system restore but won't let me do that either, with hindsight the game driver never mentioned ets2 but i just assumed one driver update works for all... any ideas what to do ? thanks

That link explains nvidia now requires sse 4.2 instruction set to install drivers. If your i7 is too old then this could be why.

[↑↑↓↓←→←→BASelect]

Here use this as a very easy way to get into safe mode. Copy this into notepad even include the Windows Registry Editor Version 5.00 part. Rename it to Add safe mode to desktop right click context menu.reg when you save it make sure it says .reg and not .txt. When you click on it will ask you to add it to the registry click yes. Then right click an empty space on your desktop find the safe mode item and choose one.

Windows Registry Editor Version 5.00



[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode]
"icon"="bootux.dll,-1032"
"MUIVerb"="Safe Mode"
"Position"=-
"SubCommands"=""


[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode\shell\001-NormalMode]
@="Restart in Normal Mode"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode\shell\001-NormalMode\command]
@="powershell -windowstyle hidden -command \"Start-Process cmd -ArgumentList '/s,/c,bcdedit /deletevalue {current} safeboot & bcdedit /deletevalue {current} safebootalternateshell & shutdown -r -t 00 -f' -Verb runAs\""


[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode\shell\002-SafeMode]
@="Restart in Safe Mode"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode\shell\002-SafeMode\command]
@="powershell -windowstyle hidden -command \"Start-Process cmd -ArgumentList '/s,/c,bcdedit /set {current} safeboot minimal & bcdedit /deletevalue {current} safebootalternateshell & shutdown -r -t 00 -f' -Verb runAs\""


[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode\shell\003-SafeModeNetworking]
@="Restart in Safe Mode with Networking"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode\shell\003-SafeModeNetworking\command]
@="powershell -windowstyle hidden -command \"Start-Process cmd -ArgumentList '/s,/c,bcdedit /set {current} safeboot network & bcdedit /deletevalue {current} safebootalternateshell & shutdown -r -t 00 -f' -Verb runAs\""


[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode\shell\004-SafeModeCommandPrompt]
@="Restart in Safe Mode with Command Prompt"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SafeMode\shell\004-SafeModeCommandPrompt\command]
@="powershell -windowstyle hidden -command \"Start-Process cmd -ArgumentList '/s,/c,bcdedit /set {current} safeboot minimal & bcdedit /set {current} safebootalternateshell yes & shutdown -r -t 00 -f' -Verb runAs\""

Here is a pic of what it looks like.

https://steamcommunity.com/sharedfiles/filedetails/?id=3400091143

[Bad 💀 Motha]

It's very simple to get into safe mode, its very straight-forward and you can do it a # of ways.

DDU is also a way to do it, as it has a Safe Mode + Restart option.

You can use the F8 boot menu key for WinOS if you disable Fast Boot in your BIOS.

[Neo]

That new nvidia app is terrible. Tried it once and half of my games couldn't be found in the app. Keep hearing bad things about it.

[Phénomènes Mystiques]

Neo님이 먼저 게시:

That new nvidia app is terrible. Tried it once and half of my games couldn't be found in the app. Keep hearing bad things about it.

I told everyone in June to stay far away from that thing, but no one listens.

I knew about the impending doom from a new feature/app but meh, I'm happy that I didn't make the jump over.

[Illusion of Progress]

GOD RAYS ON ULTRA™님이 먼저 게시:

That link explains nvidia now requires sse 4.2 instruction set to install drivers. If your i7 is too old then this could be why.

Anything in the Core i series has SSE 4.2 and the capability to do the POPCNT instruction. You'd have to go way back to CPUs from around two decades ago, not merely five years ago, to the Core 2 or Athlon 64 to be talking about anything that doesn't have it.

That link also explains that it's only for drivers within that version window, not all drivers since then, and it also explains why; the drivers were compiled with those instruction flags set even though the drivers don't use (or at least need) them.

So either way, that's not relevant and the thread starter's "CRITICAL PROCESS DIED" BSODs are being caused by something else.

I'd start by undoing any RAM profiles (XMP) if they are active and set it to stock RAM speeds, and testing RAM using something like MemTest86. This will rule out RAM instability or faulty RAM.

It might also be worth verifying the storage drive and Windows installation isn't corrupt to rule out a faulty SSD or software corruption.

You could also roll back to whatever video drivers you were using previously and hope for the best, but correlation isn't always causation so the new drivers might not be what's causing it.

If those don't resolve it (suggesting storage, RAM, and Windows installation is probably good), then the cause would likely be some other software conflict or other hardware issue.

[AmaiAmai]

You need to list the OS you are using and the hardware.

Remember only Windows 10/11/12 are officially supported.

[Phénomènes Mystiques]

AmaiAmai님이 먼저 게시:

You need to list the OS you are using and the hardware.

Remember only Windows 10/11/12 are officially supported.

Oic we are putting Win12 in the variable mix now.