Jump to content

Splash Screen Crash (Desperation ;~:)


maximizers

Recommended Posts

Hey there! I don't normally make all that many threads but I'm a little desperate, I've been grappling with this problem of mine for a couple of weeks now and it's got me worried that I won't get it sorted before the Frontier's release. >_<

I'll jump straight into the problem and what I've tried doing in the hopes of fixing it.
Right, my problem is with the initial startup of Fallout New Vegas (Ultimate Edition), during the introductory splash screens I'll get as far as the Obsidian Entertainment logo... (Sometimes I might reach the Bethesda one if I've restarted the computer and it's my first try at running it.) and then I crash back to my desktop with that familiar 'Fallout: New Vegas has stopped working...' message.

- I've tried the .ini 'fix' that requires adding ThreadedAI and iNumHWThreads to both FALLOUT.ini and Fallout_default.ini. (Didn't expect this to do much.)
- I've tried running the game completely vanilla. (With and without DLCs.)
- Disabling my Sound Card.
- Running in Compatibility mode.
- Running as an Administrator.
- Running in Windowed Mode.
- Running with and without Vsync.
- Sooooo many settings tweaks, far too many to list. =p
- Reinstalling the game through steam. (Three times and counting now.)
- Verifying my game cache. (1 file always remains outstanding, but I've heard that's normal.)
- I've tried running the game through NVSE as well as the FNV4GB Launcher.
- Disabling the Steam Overlay as well as Raptr. (Don't have Overwolf.)
- Probably something else I'm forgetting...

And yep, that's the list as far as I can remember it for now.
But here's the kicker... And it's got me downright confused...
I've been playing Fallout: New Vegas for quite a while now on
the very same machine, without fault. And then suddenly it's
started going on with this issue. o_o

I'm hoping someone here in the community has dealt with this bugger of a bug before and can lend me hand, or some 'Ouch that sucks' sympathy at the very least. <=D

EDIT: Nearly forgot my specs!

AMD Athlon II X2 255 Processor (3.10 GHz )
12.0 GB of Corsair gaming RAM.
AMD Radeon R9280X Graphics Card.
- Probably forgetting something here too... >_> -
Link to comment
Share on other sites

Been there: tried so many things you lose track of what has been tried and what hasn't. Can't see the forest for all the trees situation.

 

First of all, it sounds like you are possibly suffering from an update of some driver or to your OS. See the "Solutions to Starting the game problems" section of the "Fallout NV Mod Conflict Troubleshooting" guide. You didn't mention which version of Windows you are running, but there were some earlier Win10 updates that caused similar issues to previously fully working games. The Nov 2016 Win10 updates and later video driver updates resolved those, so that may be all you need. The other issues in that section are the most common other problems.

 

If none of that resolves it, work your way through the "Checklist" portion of that article, which will help you see if you overlooked something or spark an idea. Usually if you get a "stopped working" message, there will be something in the Windows Event Viewer as well because that is a "controlled crash" instead of a CTD; meaning it was anticipated enough to cause a message to be displayed even if pretty vague.

 

If you still need help, please provide a list of your "load order" so we can see if there is something obvious. (Though if you had been running fine without adding any new mods, I wouldn't expect much from that. But every bit of info helps.)

 

-Dubious-

Link to comment
Share on other sites

Well, I feel like a lump now. =p

NVAC went right ahead and solved the problem, don't know why it'd escaped me for so long.

Plum forgot about it. At any rate, thanks for the answers @jim_uk and @dubiousintent!

Link to comment
Share on other sites

  • Recently Browsing   0 members

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