Jump to content

Who vegas


fearomega117

Recommended Posts

You should always start troubleshooting from any error messages you can see. (They are your best "clue"; and why they exist at all.) Reporting such messages accurately is an essential first step.

 

Anytime the game "Crashes To the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog because the game engine was not able to predictably handle the error. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article.

Logs generated by the game itself (not Windows) are found in the game folder, where the "FalloutNV.EXE" file is located. They generally have the ".log" file extension, or a filename with "_log" in the name and a ".txt" extension.

 

A "CTD" is a "fatal" error, meaning the program/game did not know how to handle the error, nor how to proceed from that point and shutdown to let the Windows Operating System (OS) take over again from the "desktop". The only thing worse is the so-called "Blue Screen of Death (BSoD)", which means the OS itself encountered a similar fatal error and entire computer has to be "rebooted" so it can function again. DO NOT attempt to resume the game again from the point of a CTD, as your system memory is in an unpredictable state and make cause "save game" corruption even if it does get past the point where it crashed before. Reboot first.

* Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so.

Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as the version of Windows, if you are using a "Steam" or "GOG" and/or "regional language version" of the game (even if you are playing it in English); using the FNV4GB Patch, NVSE and it's related plugins; replacements for textures (specifically their larger image sizes: 1024x1024, etc.), animations, or "bodies", etc.; and "post-processors" like ENB or SweetFX. It saves us playing "20 questions" and gets you a more specific answer more quickly. (The usual turn-around on post and reply in an older game forum is 24 hours.) Screenshots of the "load order" don't usually work so well because they tend to cut off or fail to display needed information and are hard to "piece together" into a complete and coherent picture.

* See "How to markup images (etc) in forum posts and comments" article for how to use "Spoiler tags". "LOOT" already includes those tags in the "load order" it copies to your clipboard, so you can just paste it's list into your post.

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

Troubleshooting takes time. I gave you a number of possible, generalized things to try because you only gave us a very generalized problem statement. After you work your way through those suggestions, if you are still having problems just ask again with more details (especially any error message details).

 

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

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