Nvidia Drivers crash after I close the Game

[crpz41]

after 3-5 min I close the game, the drivers stop working and I have to force the pc shutdown through the power button.
Often some game commands stop being reactive and I have to terminate the process, and as before, the nvidia drivers will crash in 3 to 5 minutes.
I've already checked the installation through steam's interface, I haven't deleted and re-installed the game because 180GB are too much to re-download for a simple experiment. on top of that microsoft's servers are painfully slow, it would take forever.

current specs: RTX4090 + i9-12900ks + 32GB RAM. this happens with the latest nvidia driver (565.90), but also with some older I had from 3 months ago. None of these drivers gave me problems with any game, except Msfs 2020.

[jbonesmd]

How do you know it's the Nvidia drivers crashing the game and not something else being the cause? There are many reasons that MSFS can crash including conflicting, corrupted or out of date mods. Some users have reported issues running DX12 with it also, which in some cases would cause a graphics card related error to appear just before freezing and crashing.

Your profile is private so I can't see your specs. I did see your specs listed in a post in the 'Shadow of the Tomb Raider' forums where you were having problems playing that a while back. Don't know if those specs are current or not. What turned out to be the cause there?

I would try rolling the driver back to the last one that didn't give you any issues if that is what you think is causing the issue but I have my doubts about that being the problem. If your running the RTX 3080, that's a pretty solid card. Roll back to a known good driver and recheck. If it still crashes then it's probably something else going on.

[Narf]

Have you been using DDU to make sure you really have a clean reinstall of the drivers?

[d[-_-]b]

This is a real pitfa issue that can appear with a number of games.
I've had it happen with Starfield, ACC, MSFS, and EA WRC.
Same issue, a few minutes after closing a game (where you could have played for hours with no issues) your PC will suddenly freeze. Only option is to hard reset.

It's a very tricky issue to resolve, as on the surface it appears to be GPU driver issue, maybe TDR failure or something similar.

It's not related to the GPU driver version, or how you install/uninstall them.
It's also not related to your game install, at least nothing a verify files can't fix (the msfs issue with this is long fixed, it doesn't reinstall the whole game anymore. I did it very recently when MSFS would CTD on load and it found a couple of files and fixed them just fine).

Here's a few things you can check that are the potential causes or triggers.

1. Check windows event system log for Service Control Manager errors related to a duplicate old version of the gameinput service .
"The GameInput Service service terminated with the following error:
The compound file GameInput Service was produced with a newer version of storage."
Solution:
https://www.reddit.com/r/WindowsHelp/comments/18bb6e0/comment/kcw2mem/

2. If you're using Discord , turn off Debug Logging in User settings/Voice and Video scroll to bottom.

3. If you're using Razer Cortex. turn off Auto Boost. Better yet, do that, and uninstall it.

4. Also in the Windows System even log, if you see lots of "nvlddmkm Error 14" errors try this: https://www.reddit.com/r/nvidia/comments/12l01wf/comment/jg4ygjh/

5. Turn OFF GPU acceleration in any browsers you use. Ditto for Slack, Discord and any others.

Good luck.

[crpz41]

Originally posted by jbonesmd:

How do you know it's the Nvidia drivers crashing the game and not something else being the cause? There are many reasons that MSFS can crash including conflicting, corrupted or out of date mods. Some users have reported issues running DX12 with it also, which in some cases would cause a graphics card related error to appear just before freezing and crashing.

Your profile is private so I can't see your specs. I did see your specs listed in a post in the 'Shadow of the Tomb Raider' forums where you were having problems playing that a while back. Don't know if those specs are current or not. What turned out to be the cause there?

I would try rolling the driver back to the last one that didn't give you any issues if that is what you think is causing the issue but I have my doubts about that being the problem. If your running the RTX 3080, that's a pretty solid card. Roll back to a known good driver and recheck. If it still crashes then it's probably something else going on.

ok here the updated specs:
RTX4090 + i9-12900KS + 32GB RAM

the crash happened before I updated to the newest driver so it doesn't make sense to roll back.

Originally posted by d-_-b:

This is a real pitfa issue that can appear with a number of games.
I've had it happen with Starfield, ACC, MSFS, and EA WRC.
Same issue, a few minutes after closing a game (where you could have played for hours with no issues) your PC will suddenly freeze. Only option is to hard reset.

It's a very tricky issue to resolve, as on the surface it appears to be GPU driver issue, maybe TDR failure or something similar.

It's not related to the GPU driver version, or how you install/uninstall them.
It's also not related to your game install, at least nothing a verify files can't fix (the msfs issue with this is long fixed, it doesn't reinstall the whole game anymore. I did it very recently when MSFS would CTD on load and it found a couple of files and fixed them just fine).

Here's a few things you can check that are the potential causes or triggers.

1. Check windows event system log for Service Control Manager errors related to a duplicate old version of the gameinput service .
"The GameInput Service service terminated with the following error:
The compound file GameInput Service was produced with a newer version of storage."
Solution:
https://www.reddit.com/r/WindowsHelp/comments/18bb6e0/comment/kcw2mem/

2. If you're using Discord , turn off Debug Logging in User settings/Voice and Video scroll to bottom.

3. If you're using Razer Cortex. turn off Auto Boost. Better yet, do that, and uninstall it.

4. Also in the Windows System even log, if you see lots of "nvlddmkm Error 14" errors try this: https://www.reddit.com/r/nvidia/comments/12l01wf/comment/jg4ygjh/

5. Turn OFF GPU acceleration in any browsers you use. Ditto for Slack, Discord and any others.

Good luck.

1. I haven't found trace of that on the Service Control Manager
2. I don't use discord
3. I don't use Razer cortex
4. I found a match for the error nvlddmkm but it dates to 3 months ago, so it can't be useful to us right now.
5. I use firefox, and gpu acceleration is off, I checked it by looking in about:config under layers.acceleration.force-enabled, and layers.acceleration. on the system I also have brave and there it was ON. though I never opened it while playing or after playing. I use firefox 95% of the time

thank you to everyone ! I guess we have to look for something else.
on sunday I updated 2 game packages from inside the game, I think that update is the cause. it's the only thing that ever changed on the system apart from me DDU the system and updating the drivers in an attempt to fix the issue.

[Simracer]

Originally posted by Narf:

Have you been using DDU to make sure you really have a clean reinstall of the drivers?

Nvdia also offers a clean install if you chose the custom download option. I have never had any problems with installs.

[d[-_-]b]

There's a few more things you can try.

. In NVidia Control panel, use "Let the 3D application decide" instead of "Use the advanced 3D image settings", if you have gone the custom NV CP route.
. Make sure you're using the right Windows Power Plan.

Windows updates also have an impact on this. (24H2 is incoming, and still has issues around PC stability for gaming and regular use).

PC's seem to have become much more twitchier and unreliable the last few years.
Windows updates, bios/chipset updates, GPU updates all combine to make it a non-linear PC stability crapshoot. KISS.

[dclonghorns]

Well, if it was a 13th generation I would suspect that it was a problem with the CPU:
https://www.tomshardware.com/pc-components/intel-raptor-lake-instability-troubles-everything-you-need-to-know

[d[-_-]b]

No, this isn't a new issue so it's not related to the latest Intel CPU problems.
If you're unlucky enough to experience this "game freezes after closing game" pitfa issues you'll find it's more common than you think.

It appears to be a Windows/GPU power state that's triggered by a few different conditions. Even browsers using GPU acceleration can cause BSOD's or instant restarts nowday's, but that's a separate issue. It's also not a hardware issue per se, it's software glitching, but the end result is a hardware lockup.

So many non-linear glitches, they've gotten too complex.
GPU models and manufacturer variants are a big part of the non-linearity, not to mention the rest of the PC parts equation. NVidia/AMD release one driver update, but it's certainly not equal on all machines.

If you have a stable PC enjoy it while you can, and try not to frak with it too much.

https://pureinfotech.com/should-install-windows-11-24h2/
https://www.pcworld.com/article/2460159/september-windows-11-update-riddled-with-issues-heres-what-you-can-do.html

BIOS also needs to keep up with these as well, and then that forces a chipset driver update. Any of these can impact the fiddlesticks game of per game settings, along with playing new GPU driver problem bingo.

[crpz41]

Originally posted by d-_-b:

No, this isn't a new issue so it's not related to the latest Intel CPU problems.
If you're unlucky enough to experience this "game freezes after closing game" pitfa issues you'll find it's more common than you think.

It appears to be a Windows/GPU power state that's triggered by a few different conditions. Even browsers using GPU acceleration can cause BSOD's or instant restarts nowday's, but that's a separate issue. It's also not a hardware issue per se, it's software glitching, but the end result is a hardware lockup.

So many non-linear glitches, they've gotten too complex.
GPU models and manufacturer variants are a big part of the non-linearity, not to mention the rest of the PC parts equation. NVidia/AMD release one driver update, but it's certainly not equal on all machines.

If you have a stable PC enjoy it while you can, and try not to frak with it too much.

https://pureinfotech.com/should-install-windows-11-24h2/
https://www.pcworld.com/article/2460159/september-windows-11-update-riddled-with-issues-heres-what-you-can-do.html

BIOS also needs to keep up with these as well, and then that forces a chipset driver update. Any of these can impact the fiddlesticks game of per game settings, along with playing new GPU driver problem bingo.

I've been able to play a few more hours for testing and this is what I concluded: there is glitch inside the game when you use autopilot on this airplane: https://flight.fandom.com/wiki/SOCATA_TBM

it happened at least 5 times in the last week, I was cruising, I wanted to change the route with the keyboard (the HDG you see on the compass), instead of stopping turining at the selected value it continues to rotate like a clock needle, so the airplane starts flying in a circle and I can't stop it. all commands stop working so the only solution is to terminate the game from task manager. it turns out the driver crash occours ONLY 3-5 minutes after this event, when the game is not running anymore.

[d[-_-]b]

That's correlation, not causation. The cause is you terminating it via task manager somehow putting it into the state that triggers this issue, not the glitch causing you to terminate it. You can google this issue, it's not uncommon, it's not recent, and it's not game dependant. Or GPU model for that matter. Generally this issue occurs just closing [insert game here] via normal shutdown, and then your system freezes 1 to 5 minutes later.

Does it ever happen if you close MSFS normally?
If it doesn't, and it only does when you TM kill it, then don't do that and solve the TBM AP issue. Problem solved, Beats worrying about an issue that doesn't show up otherwise.

If it does happen when you close the game normally, then terminating via TM is just doing the same thing so you're back to working through the various options to try.
It is a real pitfa to resolve.
Mine finally seems resolved, but I probably just jinxed myself too. 🤷
That said, I now have a good understanding (more or less) of what game/windows settings are triggering PC freezes/BSOD's on my system (at least until the next windows/nvidia/bios update) so avoid using any of them.

There's been some issues with the TBM AP in the past but not aware of any current ones. Could be an add-on conflict maybe. Have you checked the forums?

[ZombieHunter]

Originally posted by crpz41:

Originally posted by d-_-b:

No, this isn't a new issue so it's not related to the latest Intel CPU problems.
If you're unlucky enough to experience this "game freezes after closing game" pitfa issues you'll find it's more common than you think.

It appears to be a Windows/GPU power state that's triggered by a few different conditions. Even browsers using GPU acceleration can cause BSOD's or instant restarts nowday's, but that's a separate issue. It's also not a hardware issue per se, it's software glitching, but the end result is a hardware lockup.

So many non-linear glitches, they've gotten too complex.
GPU models and manufacturer variants are a big part of the non-linearity, not to mention the rest of the PC parts equation. NVidia/AMD release one driver update, but it's certainly not equal on all machines.

If you have a stable PC enjoy it while you can, and try not to frak with it too much.

https://pureinfotech.com/should-install-windows-11-24h2/
https://www.pcworld.com/article/2460159/september-windows-11-update-riddled-with-issues-heres-what-you-can-do.html

BIOS also needs to keep up with these as well, and then that forces a chipset driver update. Any of these can impact the fiddlesticks game of per game settings, along with playing new GPU driver problem bingo.

I've been able to play a few more hours for testing and this is what I concluded: there is glitch inside the game when you use autopilot on this airplane: https://flight.fandom.com/wiki/SOCATA_TBM

it happened at least 5 times in the last week, I was cruising, I wanted to change the route with the keyboard (the HDG you see on the compass), instead of stopping turining at the selected value it continues to rotate like a clock needle, so the airplane starts flying in a circle and I can't stop it. all commands stop working so the only solution is to terminate the game from task manager. it turns out the driver crash occours ONLY 3-5 minutes after this event, when the game is not running anymore.

This would not cause your issue. As has been said correlation is not causation. If this were the issue, others would be experiencing this and we would see more than one post about it here or on the official forums. It is possible that some of your files in packages are corrupted. Unfortunately due to the way FS 2020 downloads files from Asobo servers there is no way to verify the packages are good. You could delete some folders and then restart the game and hope you found the corrupted ones, but that is shooting in the dark. FS 2020 knows what packages you should have, but it cannot verify that what you do have is correct. The only way to fix this is to re-download all of the packages. This takes forever, but it might fix your issue.

[crpz41]

Originally posted by ZombieHunter:

Originally posted by crpz41:

I've been able to play a few more hours for testing and this is what I concluded: there is glitch inside the game when you use autopilot on this airplane: https://flight.fandom.com/wiki/SOCATA_TBM

it happened at least 5 times in the last week, I was cruising, I wanted to change the route with the keyboard (the HDG you see on the compass), instead of stopping turining at the selected value it continues to rotate like a clock needle, so the airplane starts flying in a circle and I can't stop it. all commands stop working so the only solution is to terminate the game from task manager. it turns out the driver crash occours ONLY 3-5 minutes after this event, when the game is not running anymore.

This would not cause your issue. As has been said correlation is not causation. If this were the issue, others would be experiencing this and we would see more than one post about it here or on the official forums. It is possible that some of your files in packages are corrupted. Unfortunately due to the way FS 2020 downloads files from Asobo servers there is no way to verify the packages are good. You could delete some folders and then restart the game and hope you found the corrupted ones, but that is shooting in the dark. FS 2020 knows what packages you should have, but it cannot verify that what you do have is correct. The only way to fix this is to re-download all of the packages. This takes forever, but it might fix your issue.

I can confirm the issue is not caused by msfs, this strange crash happened after I played another game.
if you have any useful idea to fix this windows issue it would be amazing! thank you guys!
now I went back to driver 556.12 (June 2024)