CTD on Loading New Cells and FNV4GB question

[aresx130]

So, I have a small problem. My game crashes almost every time I load a new cell both indoors and outdoors. My system is more than capable of running it as I have an i7-3610 , 8GB RAM and GTX660M. I run the following mods in this load order as well as WRP and NMC's texture pack and I used FNVedit to create a merged patch.

 

 

 

FalloutNV.esm

DeadMoney.esm

HonestHearts.esm

OldWorldBlues.esm

LonesomeRoad.esm

GunRunnersArsenal.esm

ClassicPack.esm

MercenaryPack.esm

TribalPack.esm

CaravanPack.esm

Ambient Temperature.esm

Advanced Recon Tech.esm

CFWNV.esm

Inventory Access.esm

Project Nevada - Core.esm

Project Nevada - Equipment.esm

Selective Fire.esm

ELECTRO-CITY - CompletedWorkorders.esm

ELECTRO-CITY - Highways and Byways.esm

oHUD.esm

MikotoBeauty.esm

Project Nevada - Rebalance.esp

Project Nevada - Cyberware.esp

Mission Mojave - Ultimate Edition.esp

MMUE-CP-Electrocity.esp

DarNifiedUINV.esp

The Mod Configuration Menu.esp

Armor Replacer Child NPC Fix.esp

GoodspringsPlayerHome.esp

UWHNV-Addon-DLC.esp

UWHNV-Addon-GRA.esp

UWHNV-Addon-FollowerHome.esp

Project Nevada - Dead Money.esp

Project Nevada - Honest Hearts.esp

Project Nevada - Old World Blues.esp

Project Nevada - Lonesome Road.esp

Project Nevada - Gun Runners' Arsenal.esp

Selective Fire - Project Nevada.esp

Advanced Recon Gear.esp

Advanced Recon Tech.esp

christinecos.esp

Shotgun Commando.esp

Advanced Recon Gear - Project Nevada.esp

FlashlightNVSE.esp

Powered Power Armor.esp

Ambient Temperature - PPA.esp

MMUE-CP-PNCore.esp

MMUE-CP-PNRebalance.esp

MMUE-CP-PNEquipment.esp

MMUE-CP-PNOWB.esp

NVWillow.esp

Jump Fall Fixer.esp

WeaponModsExpanded.esp

Project Nevada - WMX.esp

WMX-ModernWeapons.esp

WMX-DeadMoney.esp

WMX-HonestHearts.esp

WMX-OldWorldBlues.esp

WMX-LonesomeRoad.esp

WMX-GunRunnersArsenal.esp

WMX-ArenovalisTextures.esp

WMX-PreOrderPackClassic.esp

WMX-PreOrderPackCaravan.esp

WMX-PreOrderPackMercenary.esp

WMX-PreOrderPackTribal.esp

MMUE-CP-WMX.esp

Vurt's WFO.esp

UWHNV-Core.esm

MMUE POP.esp

UWHNV-Addon-NoCompanionsRoom.esp

WMX-MW-GRA.esp

CFW-DLC.esp

CFW-PN.esp

CFW-PN-DLC.esp

mergedpr.esp

 

 

 

I have been looking around at various threads for the past few days and I have tried the multithread fix, I replaced Nevada Skies with Project Reality, I have reinstalled the game and it still has these CTDs. Granted I am still in Goodsprings, and I have read that sometimes this area is corrupted. I run with NVSE beta 3 and I have attempted to use FNV4GB( the NVSE version) in the hopes that this was a memory error. My question is this, are these crashes caused because of a mod interaction? Second question, is there a particular reason why I can launch New Vegas with NVSE_Loader yet I am unable to do so with the FNV4gb NVSE loader?

Edited October 27, 2012 by aresx130

[SpartanVOO1]

Mission Mojave should be just after DLCs. Always read the description of the mods you install

[aresx130]

Mission Mojave should be just after DLCs. Always read the description of the mods you install

 

I had it that way originally in my own load order and then ran BOSS and that's where it stuck Mission Mojave. Unfortunately neither of them fixed the crashing issue. In addition that is as far up as I can move it on the load order using NMM.

Edited October 27, 2012 by aresx130

[SpartanVOO1]

And

Vurt's WFO.esp

UWHNV-Core.esm - place it to another .esms

MMUE POP.esp

It is the source of your problems

You have esm mixed in your esps

[aresx130]

Fixed, however still crashes, I am also seeing some strange bugs including textures not loading as well. If I restart the client, the textures reload. Is it possible that I could have a corrupted FNV download from steam? This would not be the first time that I have a corrupt FNV download.

[aresx130]

I completely uninstalled all mods and the game as well, and the issue appears to be with the game itself as it crashes as soon as I walk into the saloon in goodsprings.

[aresx130]

Issue is fixed, I had not lowered the thread limiting low enough. It required setting the thread limiter to 1 instead of two. Thanks for your help Spartan.