Jump to content

Game Chrashing more often then it should


Recommended Posts

I have good news and bad news

Good news I resolved the error

bad news we got another error

 

Faulting application name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed
Faulting module name: FalloutNV.exe, version: 1.4.0.525, time stamp: 0x4e0d50ed
Exception code: 0xc0000417
Fault offset: 0x00ac7c62
Faulting process id: 0x20c0
Faulting application start time: 0x01d321af0509314b
Faulting application path: E:\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
Faulting module path: E:\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe
Report Id: bdb544f9-8ba4-4438-9e69-2cd70e423ec0
Faulting package full name:
Faulting package-relative application ID:

Link to comment
Share on other sites

  • Replies 73
  • Created
  • Last Reply

Top Posters In This Topic

The "0xc0000417" error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer. It may also be caused by third-party software. That error code can be produced by any application. It basically means "unexpectedly terminated by the program".

 

First, try a reboot. Otherwise, the usual instructions call for rolling back to a previous "system restore checkpoint". HOWEVER, I have recently (the last two days) started to encounter a number of different reports from people who have had to verify files or otherwise reinstall their game (various Steam games, not just FNV) and encountered problems trying to get it to simply launch after a Steam Client update. I have a suspicion that Steam broke something on their end. You might want to check with Steam Support before assuming your system is at fault.

 

-Dubious-

Link to comment
Share on other sites

Scroll down that page to "Steam Client". Click on the "rightward pointing triangle" on the right edge to expand the context menu. Review the listed FAQs. If not covered, report the Windows error in post #51 to the "Contact Steam Support" link. If you can, review your Windows Eventlog for any previous instances of that error and when they occurred. (That's more to eliminate that you were encountering them prior to the Steam Client update/reinstall.) If they are having a number of related problems, this may help them pin down the cause.

 

Whether they will admit the issue or not, is another question. If not, then you will have to "rollback" to a previous restore checkpoint anyway.

 

Edit: One of the other cases just reported that their problem seemed to be Steam related. They suspect a server-side problem, which has now been fixed. Anyway, their latest re-install attempt was successful in launching the game.

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

Is it "hanging" at the same location/state in each instance or is it in random circumstances? No Windows Eventlog or NVSElog errors? As we have ruled out "overheating", the most likely cause is "memory exhaustion", likely from not adjusting the "heap size".

 

We have covered just about every possible cause and solution in this thread, so you need to consider if you rolled back to a previous "system restore checkpoint" at some point, you may have lost/reverted a "fix" previously implemented. Review what has been tried from the beginning of the thread. As before, we need more than just a symptom to make any progress.

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

The only thing I remember NOT trying is the commit limit 'cause I didn't understand what to do

I checked the event viewer for errors when it froze and there was nothing but sometimes i get a 000x0005 (or something like that) but i have already mentioned that

And I never used a system rollback

That's all I know

Link to comment
Share on other sites

If you can't figure out the "commit limit", either let Win10 manage your swap/page file size, or set it to twice the size of your system RAM (rule of thumb).

 

See post #47 regarding the "0xc0000005" error. That article has more than one solution to try.

 

-Dubious-

Link to comment
Share on other sites

Actual, "yay!" is appropriate. That is fairly solid evidence that your crash is due to memory exhaustion. Most likely it is due to a memory leak from some program that is not releasing memory when done with it. Until something gives you a clue as to the culprit, about all you can do is shutdown any unessential programs and services while playing (as in run in "offline mode" and disable your anti-virus, printer monitor programs, etc.). I would reboot my system before starting a game session just to flush out everything from RAM, and then use something like "Razor Cortex" to manage the background apps. Also, be sure you exit the game to the desktop whenever you have to reload from a save file during a session. If the game CTDs, reboot as well to flush the RAM again.

 

-Dubious

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...