The 400th "constant crashing" Thread

[Farlo]

I've tried just about every remedy that Google can throw at me, so this is one of my last shots. Like a lot of other people, I get the constant crashes to desktop and "Fallout New Vegas has encountered an error" messages, always within 5-15 minutes of starting the game. My current load order is as follows:

 

 

[X] FalloutNV.esm

[X] MercenaryPack.esm

[X] TribalPack.esm

[X] CaravanPack.esm

[X] ClassicPack.esm

[X] DeadMoney.esm

[X] HonestHearts.esm

[X] OldWorldBlues.esm

[X] LonesomeRoad.esm

[X] Community Bugfix Compilation Patch.esm

[X] CBC Dead Money Patch.esm

[X] FOOK - New Vegas.esm

[X] FOOK - New Vegas DLCs.esm

[X] Continue After End.esp

[X] NewVegasBounties.esp

[X] NewVegasBountiesII.esp

[X] FOOK - New Vegas.esp

[X] FOOK - New Vegas DLCs.esp

[X] EVE FNV.esp

[X] DYNAVISION 2 - Dynamic Lens Effect.esp

[X] ShilohDS-Color Maps and Icons.esp

+ NMC Texture Pack

+ NVSE latest version

 

My Specs:

Intel i5 2500k @ 3.6 GHz

8 GB DDR3 @ 1333 MHz

AMD Radeon HD 6870 DirectCU

Windows 7 x64 Home Premium

Plenty of freshly defragmented HDD space

 

With everything updated as it should be and anti-virus off, along with the majority of my other applications, it still crashes constantly. It's weird how it crashes, it'll start stuttering after a few minutes, then spike really hard about 5 seconds before the actual crash. Even without any of the mods and a brand new save, it's still the same, although I can usually make it outside into Goodsprings, so interiors seem safe enough. The one thing I haven't tried is disabling NVSE which I saw some people saying has caused crashing. Other than that, I have no idea what else might do it; 3 month old computer, properly kept up, etc.

 

Thanks in advanced for any help you guys can provide!

[Farlo]

Alrighty, after some more testing, I found out that disabling NVSE helped A TON! But now the main issue is that I'm CtDing after just about any change from exterior to interior. I don't think it's happened from interior to exterior or from interior to interior, but I'm not sure.

[Cornflower]

Don't you need some compatibility patches for FOOK/EVE?

[GrindedStone]

[X] MercenaryPack.esm

[X] TribalPack.esm

[X] CaravanPack.esm

[X] ClassicPack.esm

 

 

These inject into the main .esm While they used to cause major issues after launch, it's been patched out. Still injecting into the main .esm though which in the past caused issues in Fallout 3. It's also a good indication that you steal games, otherwise how would you get them so there's that. There's folks around here that have said using all 4 causes issues by itself. So at any rate it's a good place to start. Don't feel bad. I bought the pre-order an I don't use mine either, it's all really sucky bonus content. We are also really strict about EULA around here fyi. Which is a really good thing. shame shame... LOL :D

 

Also I can't impart the importance of this next bit enough, so I'm going to try wasting an entire sentence to reinforce it. <------ Did it work yet? You have FalloutNV.esm then all the offical DLC.esm right? Right. Okay so let's just say there is a quality control issue between how we make .esm an .esp an how a Developer makes em. There's also no communication from them to us on why things are the way they are. They just are that way an we have to accept them. Me, I tend to lean toward whatever it is the main.esm an DLC.esm are doing is the correct way, because I know the Developer at least knows what quality control is. That an I've seen inside thousands of player made mods. So to speak it is advantageous to start Fallout with the main .esm and the DLC .esm and in the order they came out in. Start a new game, create a character, and then play the game for a week or a month 8 hours a day to test it to see how well it works before you blindly dump in 3rd party content created by people that don't exactly know what the words quality control mean. HA who are we kidding, most of us don't even know the word compatibility or easy to use means.

 

You should also contact Steam Support, Obsidian Support, or Bethesda Support and in that order, because Win7 is still kind of a mystery along with symtoms for XP pro having these issues, to which the official tech support would be your only guide thru a endless amount of useless rumor an pointless experimentation.

 

*images removed*

Edited September 26, 2011 by GrindedStone

[Farlo]

Haha, thanks for the advice! I've always wanted to try Gears of War, but always hated Xbox, so that might be an idea. Also, I did in fact buy New Vegas and all the DLCs, I just downloaded the Packs because I hate all that special pre-order/buy from Gamestop bullcrap and I wanted the items :P. I always buy the games I really love and support the companies that make awesome stuff.

 

Anyways, yeah, I assumed mods might do bad things, so I installed the game to another location that had the main .esm, the packs, and then the DLC alone and in order, and it still happened. Then I remembered I could use Comparability Mode, so I set it for WinXP SP3 and everything works fine now! I did the same for the install that had my mods and stuff, along with using the 4GB Patch, and everything plays flawlessly now, so I'm all good, I might even install other mods since there were a few I wanted to try but thought it might break the game more. Anyways, thanks for the advice and I'll check out Gears. Take care!

[Cornflower]

You need the proper compatibility patches.

Another good idea is to make a merged patch with FNVEdit, that usually solves about 90% of crashes (if you have the proper load order as well, if you don't, you're farged...).

[GrindedStone]

A GLEAM OF LIGHT IS SHEAD UPON THE ALL KNOWING ALL POWERFUL win7 woo hoo! lulz

I need to use what you said, you worded it well. I guy I know did the same thing for Fallout 3 on win7.

I kinda got a feeling it doesn't always work, sometimes they never find a fix for it, an it drags on for weeks.

Gears of War on PC is crazy, put it on medium diffculty is called hardcore lol an you have to learn how to reload.

 

Compatibility patches are when two mods directly conflict, this is usually two huge mods or two really popular mods. FIOP- Fallout Inner Operability patches is how it started, as a single source, though it's moved to being spread around now, I think.

 

Merge Patch/Bashed Patch are the same thing, but different flavors. If you have a bunch of mods (like 40-80-120) you know a lot. They override each other an break the lists that places content into the world. Think of it like 3 mods that add 3 weapons, only the mod loading last will have that weapon in the game on that list. Like a spawn list, loot list, NPC list, race list, containers, ect, these merge those lists into one list.

 

There isn't anything that conflicts with FOOK enough to need a merge patch/bashd patch or compatibility patch yet.

If the mods that loaded after FOOK changed the same list type data, race, loot, NPC inventory, ect

then you would need a merge patch, an if the mod was large enough also a compatibility patch.

Don't get the wrong idea though, you are using FOOK in the ideal way because there isn't a high chance of ever having problems.

You need to dump a whole lot of mods in an see how it breaks the game, to learn the lesson.

 

FOOK is set up in a .esm master .esp slave format, which is kind of dirty, but it allows you to move the slave around.

For example if you really like FOOK, load it last, all the other mods in front of it, so now FOOK overrides those.

Rather than overide FOOK with all those other mods. FOOK is an Overhawl, there are a few, an those are about the size of 200 little mods.

Some mods have to be loaded last though because of the way they are designed.

 

http://i895.photobucket.com/albums/ac156/grindedstone/Techsupport/bro.jpg