Jump to content

Photo

Starting any modded quest causes game to crash


  • Please log in to reply
14 replies to this topic

#1
EldritchBloke

EldritchBloke

    Journeyman

  • Members
  • Pip
  • 28 posts

As the title suggests, whenever I attempt to start a modded questline, a get an instant CTD. I first learned of this when I tried to pick up the note in the Prospectors Saloon which would have begun NV Bounties I, my game immediately froze. I thought it was just a minor issue so I ingored it and moved on. Yet when I tried to start another modded quest, The New Bison Steve Hotel, I got the same result. Que some testing with other unrelated but modded quests and its a game-wide issue. Vanilla quests work perfectly. The only thing I can think to have caused something this game breaking is a mod I downloaded which raised the plugin limit from 135 to 200+. I've only got 160 active ones, but I'm afraid I might have pushed it too far and now I've broke my game. Could someone please help?



#2
M48A5

M48A5

    Resident poster

  • Members
  • PipPipPipPipPip
  • 8,530 posts

Please see the article "How to ask for help" and provide all the information noted there.  Providing that information is the only way anyone can provide any help. 



#3
EldritchBloke

EldritchBloke

    Journeyman

  • Members
  • Pip
  • 28 posts

Please see the article "How to ask for help" and provide all the information noted there.  Providing that information is the only way anyone can provide any help. 

 

Ok. My PC Specs are:

Intel i5 - 2500 CPU @ 3.3ghz

16GB Ram

GTX 1050Ti - 4GB VRAM

 

My load order is : (using LOOT)

  

GameMode=FalloutNV
FalloutNV.esm=1
DeadMoney.esm=1
HonestHearts.esm=1
OldWorldBlues.esm=1
LonesomeRoad.esm=1
GunRunnersArsenal.esm=1
ClassicPack.esm=1
MercenaryPack.esm=1
TribalPack.esm=1
CaravanPack.esm=1
YUP - Base Game + All DLC.esm=1
oHUD.esm=1
Interior Lighting Overhaul - Core.esm=1
Run the Lucky 38.esm=0
ELECTRO-CITY - CompletedWorkorders.esm=1
FCOMaster.esm=1
AWorldOfPain(Preview).esm=1
TLD_Travelers.esm=1
NevadaSkies.esm=1
NPC Project.esm=1
More Traits.esm=1
Project Nevada - Core.esm=1
Project Nevada - Equipment.esm=1
Project Nevada - Rebalance.esp=1
ELECTRO-CITY - Highways and Byways.esm=1
The New Bison Steve Hotel.esm=1
Project Nevada - Cyberware.esp=1
Interior Lighting Overhaul - L38PS.esm=1
More Perks.esm=1
SomeguySeries.esm=1
Tammer's NIF-Bashed Weapons Mega-Pack.esm=1
Weapons.of.the.New.Millenia.esm=1
SCAV.esm=1
YUP - NPC Fixes (Base Game + All DLC).esp=1
The Mod Configuration Menu.esp=1
ILO - Nevada Skies Patch.esp=1
Project Nevada - Honest Hearts.esp=1
NPC Project - Freeside.esp=1
Wasteland Warrior.esp=1
Legion Quests Expanded.esp=1
FCO - NPC Changes.esp=1
The Lucky 38 Empire.esp=0
More Perks Update.esp=1
WMIMNV.esp=1
The True Revival of Luxury - An Ultra-Luxe Overhaul.esp=1
EVE FNV - ALL DLC.esp=1
Project Nevada - Gun Runners' Arsenal.esp=1
WeaponModsExpanded.esp=1
WMX-DLCMerged.esp=1
WMX-FOOKNV-DLCMerged CP.esp=0
Lucky38Reloadedv5.esp=1
CNR_Beta.esp=1
WMX-FOOKNV CP.esp=0
WMX-FOOKNV-DLCs CP.esp=0
WMX-EVE-AllDLCMerged.esp=1
WMX-Arwen_NV_Realism.esp=0
GoodspringsFarmhouse_v1.2.esp=1
Blackrow.esp=1
YUP - WMX PN.esp=1
Project Nevada - Dead Money.esp=1
Project Nevada - Lonesome Road.esp=1
Project Nevada - Old World Blues.esp=1
AWOP-WMX.esp=1
Project Nevada - WMX.esp=1
FNV Realistic Wasteland Lighting - All DLC.esp=1
MTB.esp=1
NevadaSkies - Darker Nights.esp=1
MuchNeededLOD.esp=0
Zan_AutoPurge_SmartAgro_NV.esp=1
DYNAVISION 3.esp=1
CCO - Ulysses Companion.esp=1
NewVegasBounties.esp=1
TheInheritance.esp=1
1nivVSLArmors.esp=1
populatedcasino-light.esp=1
Russell.esp=1
Badmothafucka.esp=1
More Traits Update.esp=1
FCO + YUP.esp=0
TrooperOverhaul-Dragbody.esp=1
FCO - Race Addon.esp=1
FCO - Russell.esp=0
FCO + CNR.esp=1
FCO + LQE.esp=1
FCO + TOD.esp=1
FCO - OHSB NPC Edits.esp=1
LightUpAndSmokeThoseCigarettes_edisleado.esp=1
DarNifiedUINV.esp=1
FCO - PathFixing Vanilla.esp=1
Surgical Scar.esp=0
Unarmed And Melee Revolution.esp=1
ILO - PipBoy Light.esp=1
pipboy2500_edisleado.esp=1
LFox Bottle That Water.esp=1
Bottle That Water-PN.esp=1
JIP Companions Command & Control.esp=1
SuperSledgebyWJS_Replacer.esp=0
ExtendedNVRadio.esp=1
YUP-FCO3-LQE.esp=1
YUP-CNR.esp=1
Weapon Retexture Project.esp=1
WMX-ArenovalisTextures.esp=1
Weapons.of.the.New.Millenia.Leveled.Lists.esp=1
Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp=1
ArmedToTheTeeth-NewVegas.esp=1
The Town of Vice - A Gomorrah Overhaul.esp=1
Lucky38Overhaul.esp=1
Project Nevada - EVE All DLC.esp=1
YUP - Base Game + All DLC-EVE FNV - ALL DLC.esp=1
dD - Enhanced Blood Main NV.esp=1
WMX-EnergyWeaponsNoTrueIronSightsFix.esp=0
WMX-ShotgunCommando.esp=0
Merged Suits.esp=1
Delay DLC - DM + HH + OWB + LR + GRA.esp=1
Weapons.esp=1
NCRTrooperOverhaul.esp=1
Sharecropper Ranch.esp=1
FCO - PathFixing BugFixes.esp=1
YUP-AWOP.esp=1
OldWorldRadio.esp=1
YUP-NCRO.esp=1
Brotherhood and House Alliance.esp=1
FNV Vlad's Weapon Emporium.esp=1
Suit_Up.esp=1
Custom Suit.esp=0
CasinoHeistPack.esp=0
CasinoBankMoney.esp=0
Cowboy Outfit Pack.esp=1
Cowboy Weapons Holster.esp=1
Convenient Accessories.esp=1
AQS_SackfulOfHats.esp=1
w44Satchels - Lite.esp=1
w44Satchels - Full.esp=1
Weapons.of.the.New.Millenia.Store.LITE.esp=1
WesternRifles.esp=1
SuperSledgebyWJS_Collection.esp=1
PortableCampsite.esp=1
BuzzAxe.esp=1
chainsaw.esp=1
Tailor Maid - NV.esp=1
NewVegasBounties - ImmersiveStart.esp=1
LQE-AWOP.esp=1
bzArmour.esp=1
XChainsaw.esp=1
Radio Free Wasteland.esp=1
Conelrad 640-1240.esp=1
Shabby Suits.esp=0
Outfits.esp=0
ilbuonorevolver.esp=1
TheFinalWord.esp=1
MoraelinsProfessionalsSuitMod.esp=0
manwithnoname.esp=1
clintsfistfulrevolver.esp=1
Cowboy Starter Crate.esp=1
I Got Spurs.esp=1
HuntingRevolver&Sequoia.esp=1
JL121_Sheriffs_Star_Armor_Piece.esp=1
Colt1847Walker.esp=1
HIIheadgearpack.esp=1
ColtDragoonV2.esp=1
Interior Lighting Overhaul - Ultimate Edition.esp=1
ILO - A World of Pain.esp=1
ILO - New Vegas Bounties.esp=1
ILO - New Vegas Bounties II.esp=0
FNVLODGen.esp=0
NevadaSkies - TTW Edition.esp=0
NevadaSkies - Ultimate DLC Edition.esp=1
NevadaSkies - Basic Edition.esp=0

 

in regards to the other requested information, it used to work, but since adding a some other mods (weapons and armour mostly) after increasing the plugin limit, it's stopped working. I'm beginning to thinl that this is a memory related issue, as I've been getting 'Out of Memory' messages. Not all the time, but sometimes when it craps out on me. I've some memory fixes, but to no avail (already had 4gb patcher before this negun happening). Could a memory issue be causing the CTD when gaining quests? Even hovering over them on my pipboy causes it to crash. Or does this behaviour point towards something else entirely? Thank you for your time anyway. 

 

EDIT: Just to clarify, Im not getting 'Out of Memory' crash alerts when I'm trying to start a new quest. I'm just wondering whether this is inadvertently contributing to the problem. 


Edited by EldritchBloke, 01 August 2020 - 10:25 PM.


#4
M48A5

M48A5

    Resident poster

  • Members
  • PipPipPipPipPip
  • 8,530 posts

The first thing you need to do is to clean-up your load order.  Get rid of all those inactive files.  The are clogging the memory.  Just because the file is inactive doesn't mean it isn't loaded into memory.  It is.

 

I did notice that there are two WW4Schatels.  I don't think you need both of them.

 

What else do you have installed that doesn't show in the load order.  ENB? NVSE? NV Tic Fix?  ENBoost?  NVAC?

 

So you added some mods and you started crashing.  Did you remove the mods?



#5
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 7,980 posts

Please see the 'Common Game Problems' section of the wiki "FNV General Mod Use Advice" article.  

If the problem persists, then see either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

I recommend anyone read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to play a modded FNV or it's been more than a year since you last did so.  It is designed for someone who has never played a modded PC game before, so it tries to avoid making any assumptions, is kept "up-to-date", and covers years of "lessons learned".  It is NOT a list of various mods to install that happen to work on the author's machine.  It addresses fundamentals underlying how to get the basic game and mods to work together.

* Are you using the FNV 4GB Patcher (even with the GOG version)?  For FNV Steam users (and now for GOG users as well with v1.4 or later) the tool easily solves the problem of the 2GB memory limit and loading NVSE for both the game and '''GECK'''.  (Older versions of the tool are deprecated.  The latest version (v1.4+) now supports the GOG version for auto loading NVSE, and the "NVSE_CONFIG.INI" file does not work for the GOG version without RoyBatty's patch.  Revert to the backup copy created if you did run an older version.)  Run the patcher once (as "Local Administrator" if necessary) and thereafter just use the default game FalloutNV.EXE or FalloutNVLauncher.EXE as a normal user.  The patched game automatically detects and launches NVSE.

How can you tell if the 4GB Patch is working?
: Look for the "Data\NVSE\NVSE_CONFIG.INI" file which for GOG users will otherwise will not get created without the "nvse_steam_loader".  Check the "nvse_steam_loader.log" file (in the game root folder with the FalloutNV.EXE file) for errors.
: The [http://www.nexusmods...egas/mods/58277 JIP LN NVSE Plugin] has a function which can be run from the console: "GetIsLAA" (not case sensitive).
: Possible return codes:
:* 0=patch is not applied
:* 1=patch was applied to the executable, but extra memory is not being allocated
:* 2=successfully allocated extra memory from the patch and is fully working.
: If "GetIsLAA" is returning code "1", try running the game from a "Local Administrator" account.  If that is succesfull, you need to move the game install location out of the "C:\Program Files" folder tree, or correct the "permissions" on it's folder if you have moved it, as you are going to have other problems down the road.  Please see the wiki "Installing Games on Windows Vista+" article for details.
: Alternatively: if the Windows "Task Manager" indicates the "FalloutNV.exe" program has more than 2GB (2,000,000KB) of "Memory (Private Working Set)", then the 4GB Patcher is in effect.  However, to the contrary: less does not mean it is not working.  The game simply hasn't needed that much memory as yet.

Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog.  Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article.

"NVAC - New Vegas AntiCrash" error log entries are described on the "Description" page.  This an important log for "in-game" errors.  Some are intended to assist mod authors; while others are there to help "you, the player" trying to resolve a problem.  You are interested in the entries which are NOT automatically handled successfully by NVAC.  Key entries to look for are the following "letter codes":
* "e" entries are Exceptions handled specifically by NVAC's targeted code changes
* "h" entries are exceptions identified Heuristically by NVAC's "global" exception handler, sometimes handled unsuccessfully.
* "m" entries are "Middle of nowhere" exceptions, sometimes handled unsuccessfully.
* "ñ" entries are Null instruction exceptions, sometimes handled unsuccessfully.
* "n" entries are Null pointer call exceptions, sometimes handled unsuccessfully.
* "o" entries are stack Overflow exceptions, usually handled unsuccessfully.
* "q" entries are program self-termination information; these are effectively crashes.
* "u" entries are Unhandled exceptions reported from the Unhandled Exception Filter; these are crashes (and the NVAC author wants to hear about them).
* "v" entries are unhandled exceptions reported by NVAC's "global" exception handler; these are crashes.
* "w" entries are informative, relaying exception information as it passes through New Vegas's final exception handler.
* "x" entries are critical errors in Windows exception data; these entries should never occur.
* ":" entries are output from OutputDebugString calls.
* ";" entries are output from the game's own error checking.
Other codes may be of interest, but are not things the player is likely to be able to resolve,  They are useful for informing the author of the mod to aid them in fixing their plugin.  In particular, pass along the
* "_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs
* "!" entries are informative, relaying human-readable text for the user
entries.
Any error codes found in the log but not listed on the mod "Description" page should be reported to the NVAC comments page.

'Expression Error: SYNTAX' is not uncommon, even in vanilla without any mods loaded.  These are basically "typos".  Such errors are reported by NVAC but ignored. Those lines of script code do not get executed, but also (when caught by NVAC) are not "fatal" to the game.  They are the sort of thing mods like "Yukichigai Unofficial Patch - YUP", "JIP LN NVSE", "JohnnyGuitar NVSE", "lStewieAl's Tweaks" etc. are designed to fix or supplement if possible.

-Dubious-



#6
EldritchBloke

EldritchBloke

    Journeyman

  • Members
  • Pip
  • 28 posts

The first thing you need to do is to clean-up your load order.  Get rid of all those inactive files.  The are clogging the memory.  Just because the file is inactive doesn't mean it isn't loaded into memory.  It is.

 

I did notice that there are two WW4Schatels.  I don't think you need both of them.

 

What else do you have installed that doesn't show in the load order.  ENB? NVSE? NV Tic Fix?  ENBoost?  NVAC?

 

So you added some mods and you started crashing.  Did you remove the mods?

 

I am using NVSE and I think that might be the source of my problems. When I go into the nvse_config.ini file, its become completely blank. I.e. when I load into a game it generates in this way. I think that adding the NVSE plugin to allow more mods than the standard limit may have caused it to stop working properly. Ergo, whenever I try to begin a quest that has scripting outside the vanilla parameters, it crashes. At least that's what I'm thinking. I had a similar problem with my fallout.ini file generating completely blank about a year ago, which meant the game didn't work at all. It was caused by a permission issue which I solved, but 'im not sure that will solve the error I'm having this time. Any thoughts? 



#7
M48A5

M48A5

    Resident poster

  • Members
  • PipPipPipPipPip
  • 8,530 posts

I think you are off the mark about NVSE and the mod limit fix.  With over eighteen thousand unique downloads, if there was a problem, it would have been reported and corrected by now.

 

It could be a permissions problem, particularly if you are using Windows 10 and have the game installed in "Program Files".

 

Did you clean-up your load order?



#8
EldritchBloke

EldritchBloke

    Journeyman

  • Members
  • Pip
  • 28 posts

I think you are off the mark about NVSE and the mod limit fix.  With over eighteen thousand unique downloads, if there was a problem, it would have been reported and corrected by now.

 

It could be a permissions problem, particularly if you are using Windows 10 and have the game installed in "Program Files".

 

Did you clean-up your load order?

 

I cleaned my load order, and while clearing a lot of space for memory, doesn't have seemed to rectified the issue im having with quests. I moved my installation of Fallout out of program files after I had the permission issue last year. I'm not sure if its to do with windows as its been fine up to now. Are you sure the nvse_config.ini is supposed to be empty? Would reinstalling nvse rectify this issue perhaps?

 

EDIT: Still getting 'Out of Memory Issues'. So maybe even with the plugin limit raised I'm still managing to use up 3.5GB with all of my mods. (as I've read that not matter what memory extending methods you use, if you reach that number the game cannot simply handle it and crashes). I've also thought it might be a memory leak, and I've tried a few fixes for that with no avail. Could the memory being exceeded cause the scripting of quests to fail? I'm not very well versed in the inner working of the engine. I've also enabled error lgging with NVSE, and I'm getting a lot of ''Unable to find function definition for command 21048 in script''. I could post the whole thing if it would help, but I doubt anyone would want to scour thorugh the whole thing. Thoughts?


Edited by EldritchBloke, 02 August 2020 - 09:06 PM.


#9
dubiousintent

dubiousintent

    Resident poster

  • Premium Member
  • 7,980 posts

* If you are suddenly having a "slowdown" or lag; or a lack of sound; or problems getting NVSE to load, or really anything new unexpectedly, please see the 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.  This may be due to an on-going series of Windows Updates for the "Meltdown and Spectre Vulnerabilities".

Re: NVSE config file.  Please see the 'Checklist Item #4' entry of the "Checklist" section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.  At the very least apply the "Sheson" patch and enable logging until this problem is resolved.

-Dubious-
 



#10
EldritchBloke

EldritchBloke

    Journeyman

  • Members
  • Pip
  • 28 posts

 

I think you are off the mark about NVSE and the mod limit fix.  With over eighteen thousand unique downloads, if there was a problem, it would have been reported and corrected by now.

 

It could be a permissions problem, particularly if you are using Windows 10 and have the game installed in "Program Files".

 

Did you clean-up your load order?

 

I cleaned my load order, and while clearing a lot of space for memory, doesn't have seemed to rectified the issue im having with quests. I moved my installation of Fallout out of program files after I had the permission issue last year. I'm not sure if its to do with windows as its been fine up to now. Are you sure the nvse_config.ini is supposed to be empty? Would reinstalling nvse rectify this issue perhaps?

 

EDIT: Still getting 'Out of Memory Issues'. So maybe even with the plugin limit raised I'm still managing to use up 3.5GB with all of my mods. (as I've read that not matter what memory extending methods you use, if you reach that number the game cannot simply handle it and crashes). I've also thought it might be a memory leak, and I've tried a few fixes for that with no avail. Could the memory being exceeded cause the scripting of quests to fail? I'm not very well versed in the inner working of the engine. I've also enabled error lgging with NVSE, and I'm getting a lot of ''Unable to find function definition for command 21048 in script''. I could post the whole thing if it would help, but I doubt anyone would want to scour thorugh the whole thing. Thoughts?

 

 

I've added both FalloutNV.exe and nvse_loader to the Windows security exceptions but that doesn't seem to have done anything. In regards to the config file, I've enabled the Sheson patch but that doenst seem to have done anything either. All the checks I perform in the console imply that NVSE, and it's various plugins, are working, but how could that be the case if I'm unable to start modded quests? Would it help if I posted the whole error log? I'm really not sure what to do anymore. Do you think it could be a memory issue? It wouldn't surprise me if I was using up all of it, even with the patchers. 






Page loaded in: 1.143 seconds