Why does the copy of MGSV: TPP on PC crash during loading sequences

metal-gear-solid-5-the-phantom-painpctechnical-issues

While playing Metal Gear Solid V: The Phantom Pain, the game seems to crash my nVidia drivers during loading sequences (spinning gray circle in upper right).

It is very frustrating, especially when it happens during the mission complete statistics screen and I lose all of my progress on that mission.

How can I solve this issue?

Note: The symptoms of an nVidia driver crash include:

  • Your display stops responding (showing a still image of the last thing that was happening)
  • Your display goes black
  • A combination of the two.

Sometimes, the driver will recover and Windows will inform you that the driver did just recover from a crash with a message in the system tray.

Best Answer

Make sure of these things:

  1. You are running the latest, MGSV:TPP and Mad Max game-ready nVidia driver, version 355.82.
  2. Run the game in full-screen mode, not borderless or windowed. nVidia's driver recommends this setting. It is also easier for the game's software to take full control of your display device hardware to render the game, as opposed to having to render it in a window on top of your desktop, which borderless does. Effectively, it prevents your computer from having to render your desktop and the game at the same time.
  3. Set all of your graphics settings to low, either manually in-game or set the performance-quality slider all the way to the "performance" side in Geforce Experience and apply your optimizations. You can experiment with increasing your graphics settings one-by-one until you find the offending setting, and leave it off.

Background

I had this issue, and it was game-breaking. Every time I completed mission 16, my nVidia driver would crash on the statistics screen and I would lose my progress, starting at the last checkpoint in the mission when I restarted the game client. However, the game would also crash randomly every time I would experience the loading sequence, additionally to the consistent mission 16 crash. At the time, I already had driver version 355.82 running. I made changes #2 and #3 simultaneously, so I am not sure which is the exact solution. Considering how frustrating and potentially game-breaking this issue is, I decided to post it for others' benefit before I had a completely definite answer, but it is forthcoming -- I am experimenting with my graphics settings to find the culprit.

Related Topic