• Fallout: New Vegas CTD After 15-20 Minutes
    23 replies, posted
Greetings Facepunch. I wish we could meet under better circumstances, but the situation here is grave. I will be brief: After fixing problem after problem after goddamned problem, I have run into one, final, seemingly unconquerable obstacle. Regardless of the oh-so-many fixes I have tried, New Vegas gives me a cruel pimp-slap-crash back to the desktop after about 15-20 minutes, 25 at the VERY most. Speccy: [url]http://speccy.piriform.com/results/2tUIxv0k7a0icxaLtHoG03s[/url] As much as I'm sure many laughs will be had from my i3 processor and my HD Graphics 3000, I am fairly certain the problem doesn't lie in my specs because I have played through the game fine(even with an acceptable 30 fps average) on a different install without any problems aside for the expectable glitch here and there. If I had to make a guess, I would say the problem has something to do with the fact that crashes in general started when I got Old World Blues and pretty much all of the weapon packs. However, after deletion of these, the crashes remain. I don't have any addons whatsoever installed. Drivers are up to date. FFDSHOW is deleted, bUseThreadedAI and iNumHWThreads added. Numerous wild goose chases on google followed. Any help would be appreciated, etc. etc. Thanks guys!
Try turning off the autosave feature, it fixed so many problems for me.
Will try right now and report back. If it doesn't work, when I try it i'm going to set a stopwatch on my phone for the exact playtime, starting at save load. [editline]25th July 2012[/editline] Argh, no such luck. about 22:20 minutes in, but the time generally varies by a few minutes.
No, but I should note that I've been having problems with old leftover texture files for mods like Nevada Skies, where the sky at night looked like that rainbow screen you see on TV sometimes. Load order is literally just FalloutNV.esm
Reluctant to try but I guess it's last resort stuff. This does mean that I have to go and fix every bug I spent time fixing though :/ Obsidian is lucky they have such a good game or people wouldn't even bother with this crap. [editline]27th July 2012[/editline] Thanks to everyone who helped, by the way. [editline]27th July 2012[/editline] Went to uninstall, then checked what was left afterwards. 877 MBs of stuff. IIIIINTERESTING. Hopefully this fixes some problems.
Please excuse me while I go kill a variety of small, helpless animals in my consuming rage for this fine product. 21 minutes, fresh install, my docs files and steamapps files completely deleted and reinstalled. I didn't have this problem before! What is it that suddenly it's happening? I thank you guys for helping again and if you have anything else to suggest I'll tell you if it's been tried.
Have you tried starting a completely new save? Then you can atleast somewhat narrow down if the problem lays there.
Completely new save was what I started on when I tried the above, IE completely fresh install.
I really wish I also had this problem so I could troubleshoot the shit out of it and come up with a solution. My friend has a similar issue but with Skyrim. The more I try and look into it the more I think it's hardware related but he just doesn't seem interested anymore. At this point all I can really suggest is that you check your drivers out and see if there's any outstanding updates (I know you said they were updated, but literally just check everything anyway because it could be related to any number of them) or corruption since it doesn't seem to be related with any of the core files in the game itself.
I'm to the point where it's like, "Fuck it, I'll do it if you have an idea but I don't feel like raging over it anymore." Checking for driver updates......up to date. Nuegheugheughgergheurhg.
Settings are ALWAYS at low, for good reason if you look at the speccy diag.
As a very last resort if there's absolutely no solution here or elsewhere online start switching out hardware. It may seem drastic and could in no way be related but it really is a last resort option.
Open up the fallout.ini file in: My Documents\My Games\FalloutNV Find the line: bUseThreadedAI=0 change it to: bUseThreadedAI=1 Add another line after it and insert: iNumHWThreads=2 try this and see what happens
[QUOTE=LtZKilla;36919390] Drivers are up to date. FFDSHOW is deleted, bUseThreadedAI and iNumHWThreads added.[/QUOTE]
wishing I could rate myself dumb right now. Sorry
I need all the main DLCs and all I have is OWB. [editline]30th July 2012[/editline] [QUOTE=Pridit;36997523]As a very last resort if there's absolutely no solution here or elsewhere online start switching out hardware. It may seem drastic and could in no way be related but it really is a last resort option.[/QUOTE] It's a laptop. I could probably switch out the HDD and if I really wanted to work on it, I could get an ACTUAL GFX CARD instead of the built in 3000 but at that point, yeah, i'm not paying more money than the game actually cost when I bought it to fix it.
[QUOTE=LtZKilla;37002950]It's a laptop. I could probably switch out the HDD and if I really wanted to work on it, I could get an ACTUAL GFX CARD instead of the built in 3000 but at that point, yeah, i'm not paying more money than the game actually cost when I bought it to fix it.[/QUOTE] I'm still convinced it's related to hardware one way or another, if it's not the core game files or drivers there's not much else it can be.
[QUOTE=Pridit;37003240]I'm still convinced it's related to hardware one way or another, if it's not the core game files or drivers there's not much else it can be.[/QUOTE] You're probably right and there's probably a point in the driver updates that from there backwards the game would have worked but it still annoys me that this problem just popped up.
Sorry, you need to Log In to post a reply to this thread.