Jump to content

Game causes PC to self restart

wolf6541

By wolf6541
in Mod Troubleshooting

 Share

Recommended Posts

wolf6541 Rookie

wolf6541

Posted
Posted (edited)

I've been having game crashes that restart the PC unavoidably. They are random and don't seem to depend on any particular aspect of the game. I would play for a while, usually a few hours, then the game along with the audio would freeze for 5 seconds, then the PC would restart. I can't go to the desktop or call the task manager, the whole system becomes unresponsive during those seconds.

I'm inclined to believe that it is not a thermal or hardware issue, because I've put the machine through memtest, prime95, and 3dMark without being able to reproduce the crash. It also only crashes in FalloutNV.

 

Any ideas would be appreciated.

 

Specs

GA AB350

Ryzen 7 1700

GeForce GTX 1060 6GB

 

Plugin load order

 

  Reveal hidden contents

 

 

Mod list /reversed/

 

  Reveal hidden contents

 

Edited by wolf6541
Link to comment
Share on other sites
dubiousintent Grand Master

dubiousintent

Posted
Posted

Anytime the game "Crashes to the Desktop" (CTD) or forces a reboot it's typically going to generate an error message in the Windows Eventlog. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article.

"NVAC - New Vegas AntiCrash" error log entries are described on the "Description" page. This an important log for "in-game" errors. Some are intended to assist mod authors; while others are there to help "you, the player" trying to resolve a problem. You are interested in the entries which are NOT automatically handled successfully by NVAC. Key entries to look for are the following "letter codes":
* "e" entries are Exceptions handled specifically by NVAC's targeted code changes
* "h" entries are exceptions identified Heuristically by NVAC's "global" exception handler, sometimes handled unsuccessfully.
* "m" entries are "Middle of nowhere" exceptions, sometimes handled unsuccessfully.
* "ñ" entries are Null instruction exceptions, sometimes handled unsuccessfully.
* "n" entries are Null pointer call exceptions, sometimes handled unsuccessfully.
* "o" entries are stack Overflow exceptions, usually handled unsuccessfully.
* "q" entries are program self-termination information; these are effectively crashes.
* "u" entries are Unhandled exceptions reported from the Unhandled Exception Filter; these are crashes (and the NVAC author wants to hear about them).
* "v" entries are unhandled exceptions reported by NVAC's "global" exception handler; these are crashes.
* "w" entries are informative, relaying exception information as it passes through New Vegas's final exception handler.
* "x" entries are critical errors in Windows exception data; these entries should never occur.
* ":" entries are output from OutputDebugString calls.
* ";" entries are output from the game's own error checking.
Other codes may be of interest, but are not things the player is likely to be able to resolve, They are useful for informing the author of the mod to aid them in fixing their plugin. In particular, pass along the
* "_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs
* "!" entries are informative, relaying human-readable text for the user
entries.
Any error codes found in the log but not listed on the mod "Description" page should be reported to the NVAC comments page.

Do you have "New Vegas Stutter Remover" (NVSR) installed? If so, please see the 'Issue: CTD after 10-20 minutes of play (post-Win10 2017 FCU)' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* Related to the NVSR problem, for problems AFTER a save game is loaded see also 'Issue: Incomplete save game load' in the "Troubleshooting" guide.

* The game has "memory leaks", primarily linked to the audio system due to the version of the Ogg Vorbis Libraries used by Bethesda. Getting 2-3 hours before a CTD is pretty good. The audio problem is fixed by using the updated [http://www.nexusmods.com/newvegas/mods/61265 Ogg Vorbis Libraries] posted by Kane Wright. You might also want to try using the tool "CleanMem", which periodically (you can set the interval; default is every 15 minutes) tells the OS to perform it's built-in "clean up" of memory. It has a "mini-monitor" that displays memory usage. Doesn't seem to hurt and might help.

* If you are using the full 4GB of memory, most likely your CTD problem (now or in the future) is the default "heap size" is too small. It's so common you might as well deal with it now. Please see the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu') entry in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* You can also get "out of memory" errors from the graphics system (which is separate from exhausting system memory), even with the game 4GB enabled. The video pipeline is known to have "memory leaks", and these occur faster with "beautification mods". Here the cause is a combination of larger image sizes ("higher resolutions", aka "hi-rez"), hi-rez texture packs for skin, hair, clothes, weapons, and landscape; along with mods that increase the number of NPCS in a given cell. (All those hi-rez texture "personal accessories" get multiplied by the number of Actors.) Please see the wiki "Display resolution versus Image Size" article. While "ENBoost" can help, you may need to switch to lower resolution/ smaller sized images or even lower quality in your game graphics configuration.

Please see the 'Common Game Problems' section of the wiki "FNV General Mod Use Advice" article.

If the problem persists, then see either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

I recommend anyone read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to play a modded FNV or it's been more than a year since you last did so. It is designed for someone who has never played a modded PC game before, so it tries to avoid making any assumptions.

-Dubious-

Link to comment
Share on other sites
wolf6541 Rookie

wolf6541

Posted
  • Author
Posted (edited)

Thank you for the quick reply.
I have checked the event log. The crashes are logged under the System section as "critical" events, but the reports themselves contain no useful information other than "the system has rebooted without cleanly shutting down first." There are no events associated with the game under the Application section in the same time stamps of the crashes.

I have only recently installed NVSR, but I'm using the following config file - https://www.nexusmods.com/newvegas/mods/66063
The crashes were still persistent when I wasn't running NVSR.

I'm already running Sheson's patch.

I'll try the updated libraries as well as the suggestions on memory, and the system override options, and I'll post again.

Also, I'm not sure if this can be a video memory issue. On my old system, which was pretty weak compared to this one /i3, 550ti/, I've ran the same mods with the same ENB, and the same high res textures - I have never experienced system critical crashes on it.

Edited by wolf6541
Link to comment
Share on other sites
wolf6541 Rookie

wolf6541

Posted
  • Author
Posted (edited)

All right, I've put the updated libraries and did the system override recommendations from the wiki. I haven't had critical system crashes yet, but the game CTDed once right after a fast travel. The error window was titled as "Microsoft Visual C++ runtime library" saying "This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."

Fallout error log prior to the crash

 

  Reveal hidden contents

 

 

Nvac log

 

  Reveal hidden contents

 

Edited by wolf6541
Link to comment
Share on other sites
dubiousintent Grand Master

dubiousintent

Posted
Posted

The "Fallout Error Log" is showing primarily "audio" problems. I can't tell precisely what is causing the problem, but my guess would be a mod has an issue with the sound in an animation. The last referenced animation was for:

AI: Could not initialize FootIK system for Giant Mantis.
ANIMATION: (SpecialIdle) End frame is less than or equal to Start frame in "Meshes\Creatures\Dog\IdleAnims\MTSpecialIdle_LookLeft.kf".

so I would start by trying to identify a mod adding or replacing the "Dog\IdleAnims\MTSpecialIdle_LookLeft.kf" file and disable that mod to see what happens.

The NVAC log didn't tell me anything, though someone else might glean something from it.

-Dubious-

Link to comment
Share on other sites
 Share
Go to topic listing

  • Recently Browsing   0 members

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