Hello to all the forum members,

Error message: Fallout:NV has stopped working

I have started a new thread for this error message as per a request from a member

My system spec's:

CPU: Intel I5-750 2.66 (not overclocked at the moment)
Mobo: Asus Maximus III extreme
Psu: Corsair 850
Corsair H50
GPU Asus EAH5870 matrix platinum 2 gig
Sound card: Xonar DX2
Ram: Corsair dominatror DDR3 - 2000 (8 gig)
O/S: Windows 7 ultimate edition
Monitor Dell U2311H Ultrasharp
Keyboard Logitech G19
Mouse Logitech G9
SSD drive 120 gig
Hard drives: 2 * 1T Caviar black, 2 * 640 gig caviar black

All drivers are up to date as this is a new build.



Yesterday evening I loaded the game purchased at a retail store.

I installed the gane, followed the instructions, waited while it updated to the latest version off the Steam website.

The game indicated it recognized my video card and set ultra high video settings (or something close to that)


All good so far!

I watched the intro - no problem


Got to the play, load, settings screen

Started new gane, answered yes to message about lossing data of previous games.


Once I hit play and start the game I get this game screen , various messages at the top (never the same) with some sort of progress indicator in lower center and about 3 seconds later, the system crashes and returns me to Windows.

A pop up window appears with the following message "Fallout:NV has stopped working" and Windows will look for a solution. No solution and that's the end of the road.

This is as far as I can get.


Following verious posts on this forum:

1) I have reloaded the game 3 times,
2) I have cleared the cache, - under the settings menu
3) I have run file integrity, - over and over and always get the message about a bad file and that it will reacquire the file
4) I have gone to the exe files and changed compatibility to Windows XP service pack 3 (All suggestions from this forum).

Regardless of the above I have had no further success in this endeavour.

Still having the same exact problem.

" Fallout:NV has stopped working" crash.


I have loaded other games such as Civilisation 5, Civilisation 4, Battlefield: Bad company 2, Supreme Commander 2 and they all run flawlessly.

Hopefully the above long winded description helps in finding a possible solution to the "Fallout: New Vegas has stopped working" issue.

I wish to thank you in advance for any help the forum members could provide to try and get this game working or by pointing me in the direction where I may inquire further.

Again many thanks

When it crashes, does it give any other info about the crash such as the module or .dll file that crashed or an error number?

Hello cancausecancer,

No I am sorry I do not get any other details, just a pop up windows with the error message, plus windows checking for a solution and then poof nothing.

Logical_mr

Update

I re installed all the drivers for the Asus 5870 matrix platinum card.

I re installed the game

I modified one by one the settings for windows xp service pack 3

I did the validity check, defrag and anything else that was listed as possible solutions....

No positive results so far.


Logical_mr

Next time it happens, if there is a "View problem details" arrow at the bottom of the dialog box, click it and paste some of the info from there. Also how much hdd space is left on each of your disks? Do you have ffdshow or a codec pack installed? Do you have environmental 3d enabled in the .ini or GX mode enabled in your xonar panel?

Alternatively you can check the Event Viewer's Application log to see what it has in there.

Hi Cancausecancer,

Ok, when I get the pop up dialogue window I do not have a details tab.

I did go to the event log window but as I do not know what to search for it was of no use.

Update - I tried the "perform a clean startup" and still had the same exact problem.

Disk space is not a concern:

SSD: 72 gig free
disk 1: 545 gig free
disk 2: 596 gig free
disk 3: 780 gig free
disk 4: 898 gig free


Do you have environmental 3d enabled in the .ini or GX mode enabled in your xonar panel? - Nope

Still trying to get it working....
Thank you all for the help

Logical_mr

Windows may have created an error report with a list of modules and some other info when the crash happened, if it didn't then the thorough way to get info on the crash is to use DebugDiag.

Windows Error Report method

See if Windows created an error reports for the crash by going to Start, Run, and pasting in this folder path and clicking Ok:

%LOCALAPPDATA%\Microsoft\Windows\WER\ReportArchive

Look for folders named AppCrash_FalloutNV_(mixed characters) and upload the Report.wer from the most recent one using http://www.quickfilepost.com/, then paste the quick file post url here.

That file may have something useful in it to point us in the right direction.

Debug Diagnostic Tool method

This is the other method, this is what you do when you can't find the source of the crash using conventional methods. Install Microsoft DebugDiag v1.2 (its a bitter harder to find than v1.1 but it's better), and then set it up to debug the crashes and then upload the crash logs. I'll give some steps to setting it up to debug the crashes:

• Launch FalloutNV and once it's running, ALT+TAB back to Windows
  
• Open DebugDiag
  
• Click Add Rule in DebugDiag
  
  • Select the Crash rule type and click next
    
  • Select a specific process for the process type and click next
    
  • Select FalloutNV.exe from the list (don't check the This process instance only) and click next
    
  • On the Advanced Configuration window
    
    • For the Unconfigured First Chance Exceptions, select Full Userdump for the Action type
      
    • For the Unconfigured First Chance Exceptions, type 10 for the Action limit
      
    • Set the Maximum Userdump Limit to 20
      
      (You can set it higher but if the game crashes a lot and each full userdump is 1.2gb then you want to limit it or you'll have to manually remove old log files)
    
    
  • Click the Exceptions button
    
    • Click Add Exception
      
    • Click on C0000005 Access Violation in the list
      
    • For Action Type select Full Userdump
      
    • For Action Limit type 15 or something less than the max userdump limit you set to ensure there is room for unconfigured exceptions to be logged.
      
    • click OK then Save & Close
    
    
  • On the Advanced Configuration window click Next
    
  • On the Select Dump Location And Rule Name window click Next (change the location if you want the logs to be somewhere easier to find)
    
  • On the Rule Completed window select Active the rule now and click Finished
  
  
• Now to enable Hang anolyzing, this can help pin point exactly what causes a crash.
  
  • Open this folder:

    %ProgramFiles%\DebugDiag\Scripts\inc

    and edit the Globals.asp file with a text editor like notepad or something
    
    Chances are you won't have permission to save this file unless your text editor is launched with Admin permissions so you may have to change the modify/write Permissions on this file
    
  • Search the file for g_DoCombinedanolysis, it should be on line 8
    
  • Change it from
    

    Const g_DoCombinedanolysis = False

    to
    

    Const g_DoCombinedanolysis = True

    
    
  • Save the file and close the text editor
  
  
  
• Now go back to FalloutNV and do whatever you do to make it crash.
  
  When it crashes, the crash will be logged, it can take a minute to write the crash dump(s).
  
  
• Once the crash has happened, you should be able to see that it was logged by Looking at the rule in DebugDiag, It should have a non 0 number under the Userdump Count column.
  If you see that it has logged the crash then:
  
  
  • Click on the Advanced anolysis tab
    
  • Click on Crash/Hang anolyzers from the list of Available anolysis Scripts
    
  • Click the Add Data Files button and navigate to the folder where the logs were saved (maybe "%ProgramFiles%\DebugDiag\Logs\Crash rule for all instances of FalloutNV.exe\")
    
  • Select the most recent crash file(s) by Date modified and not by the date time in the file name, and click Open
    
  • Click the Start anolysis button
    
    It will anolyze the dumps and generate a report as an mhtml file which can be opened with internet explorer. By default it should auto open after it's generated. If not, the reports are stored in DebugDiag's reports folder.
    
    The report may point at a specific module (like a .dll or a .ax file) which caused the crash.
  
  
• upload the report file and paste the link to it in here, the file will look something like: CrashHang_Report__Date_10_02_2011__Time_01_02_03AM__123

Another way may be to set the steam app id for the game in an environment variable so you can launch it without calling steam and then using WinDbg to watch it load and see what modules are loading when it crashes.

I am having the same issue. Here is what i was able to get out of the error report.

Problem signature
Problem Event Name: APPCRASH
Application Name: FalloutNV.exe
Application Version: 1.2.0.314
Application Timestamp: 4cfdf842
Fault Module Name: FalloutNV.exe
Fault Module Version: 1.2.0.314
Fault Module Timestamp: 4cfdf842
Exception Code: c0000005
Exception Offset: 001dfa5c
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

That's a general crash so it's not so easy to know what is causing it. What is your FalloutNV's history? Did it work before? How far do you get before the crash happens? Does the crash always happen at the same time or after the same event? Do you have mods installed or any custom .ini tweaks? Are you using a steam copy or a stolen copy? What hardware do you have and what running processes/modules are loaded?

There seems to be a fair amount of causes for FalloutNV crashes and the most common method to fixing it is trial and error using other people's suggested solutions. You can search these forums or in google to find suggested fixes. Search for appcrash falloutnv.exe and try other keywords like solved, resolved or fixed.

Well, it is just an HP elite from Best Buy, nothing special, Phenomx4, 4g ram, 750gb hard drive, I have a ATI Radeon 5700HD in there now. Pretty sure that should be able to handle that.

And the history.. well I had a similar problem with fallout 3 way back when, but it was no where near as bad as NV is for me right now. It has been bad from the start pretty much, it used to stutter a lot, and i fixed that for the most part.

The situation that prompted my posting... I port somewhere, and I am running to my objective and at about the same spot every time, it crashes, although MOST of the time it seems random.

It is a steam copy, so I check the integrity and it says its missing a file and will be put in automatically... but that never happens.

The only thing i can think of is the DX tweak or whatever it was that someone made, but I read that the patch should have fixed it.. so I am kind of stuck

Every once in a while my FO3/NV starts crashing on it's own. The causes have been different at different times. Here are the causes I can remember:

• GPU overheating during a hot summer
  To fix this I just turned air conditioning on
  
  
• Game being unable to access more ram
  This is probably due to HD textures (http://www.newvegasnexus.com/downloads/file.php?id=35645) + a lot of .ini tweaks for quality. The Large Address Aware fix remedied this.
  
  If you're using XP, Robynah posted http://www.gamesas.com/index.php?act=findpost&pid=17149432 that his/her crashes were due to the /3GB switch in his boot.ini
  
  
• Codecs probs
  Uninstalling my codec pack (k-lite) fixed it one time. Manually unregistering ffdshow fixed it another time. I had to hunt for ffdshow one time because it didn't show it was installed anywhere but it was being loaded when the game ran.
  
  One time I used madfilter to fix a radio bug and later the madfilter was responsible for crashes, but not very frequent crashes so I left it in.
  
  
• Low disk space.
  I have 6 internal hdds and if any one of them is low on space (even only 6GB free) then I get repeated crashes. At least 15GB free on each fixes it for me.