Can't get ENB's to work at all.

[jhx96]

So I followed the Viva New Vegas guide (https://vivanewvegas.github.io/index.html), minus a few hardcore survival things and added some other mods not listed in the guide, but avoided most said mods to avoid in the guide. The exception being ENBs, cuz simply put, I want a better looking new vegas. I've also tried NVReloaded + the viva new vegas NVGE preset for it in addition. But for some reason now, MO2 just immediately crashes to desktop upon launching New Vegas with the d3d9.dll file installed, even without NV Reloaded installed. And I've tried using the injector version, the game launches but the enb never applies. I've searched high and low for a solution, but nothing seems to work.

 

Weird part is I was able to run enbs on this computer back in February.

Also as a side note, using NVR 3.2.0 for some reason causes a weird glowing blue texture on the ground. However switching to 1.3.0 seems to have resolved that issue.

Here's my load order:

 

# This file was automatically generated by Mod Organizer.
FalloutNV.esm
DeadMoney.esm
HonestHearts.esm
OldWorldBlues.esm
LonesomeRoad.esm
GunRunnersArsenal.esm
ClassicPack.esm
MercenaryPack.esm
TribalPack.esm
CaravanPack.esm
Navmesh Fixes and Improvements.esm
YUP - Base Game + All DLC.esm
TheHUDEditor.esm
Landscape_Seam_Fix.esm
Character Expansions Revised.esm
Functional Post Game Ending.esm
TLD_Travelers.esm
Lightweight Strip Overhaul.esm
Th3OverseerCore.esm
3DNPC_BlueNote.esm
Ragdolls.esm
Afterschool Special.esm
YUP - NPC Fixes (Base Game + All DLC).esp
WMIMNV.esp
WMIM Addendum.esp
Unofficial Patch NVSE.esp
FIXforLegionArmors.esp
The Mod Configuration Menu.esp
JIP Improved Recipe Menu.esp
Simple DLC Delay.esp
Vanilla UI Plus.esp
CPI Icons.esp
Enslave Gannon fix.esp
Melee Reach Revised.esp
Psycho and Slasher Bonus Damage Fix.esp
NoTrapsPopup.esp
FOVSlider.esp
Vurt's WFO.esp
EnhancedGrass_NoVL.esp
NVxAnimatedMicrofilMachine.esp
STDG.esp
Book of Steel.esp
Weapon Retexture Project.esp
YUP - WRP Patch.esp
Character Expansions Revised - YUP.esp
dD - Enhanced Blood Main NV.esp
B42Inertia.esp
B42 Weapon Inertia - Config INI.esp
Little More Lamplight.esp
Burning Campfire.esp
BC2.esp
Bathroom Doors Fix.esp
Strip Wall Billboards.esp
CIB Bighorners.esp
CIB Bighorners - HH.esp
Alsatian NCR Guard Dogs.esp
NVAnimatedTerninalScreenSaver.esp
OWB-Path Lights.esp
brayduck_classic.esp
IMPACT.esp
SimpleGlowingRangerVisors(NeckCover).esp
Windows of the Mojave v1.2.1.esp
JSawyer Ultimate.esp
JSUE Addendum.esp
Economy Overhaul.esp
Mojave Arsenal.esp
Mojave Wildlife (Vanilla-Style + No Chanced).esp
Mojave Raiders.esp
Mojave Raiders Addendum.esp
Character Expansions Revised - MR.esp
JSawyer Ultimate - Mojave Raiders Patch.esp
JSawyer Ultimate - Mojave Arsenal Patch.esp
Follower Tweaks.esp
Changed Vendor Flags.esp
Real Recoil.esp
Yukichigai Gameplay Tweaks.esp
JIP Companions Command & Control.esp
VNV Follower Tweaks.esp
Qolore Gameplay Tweaks.esp
GRA Scavenger Hunt Unbalanced.esp
BetterNCRSupplyCache.esp
Honest Hearts Workbench Crate Luck.esp
Toxic Cloud Fix.esp
VWBarterRepairCosts.esp
VWPerceptionRangedAccuracy.esp
Stat Choices.esp
NPC Use Aid.esp
Enhanced Vision.esp
FO3WeaponsRestoration.esp
OldWorldBlues - Light Stealth Suit MKII.esp
OldWorldBlues - Keep Big MT Active No Announcements.esp
LessWhiteLegWeaponry.esp
HHrespawn.esp
MigCompanionTweaks.esp
MigKao.esp
Rex Brains.esp
MigGaussFix.esp
MigMeltdown.esp
MigTeslaChain.esp
FO4PowerArmor.esp
FO4PowerArmor-JSU.esp
MigFortune.esp
migWellRested.esp
CIB Supermutants - Overlords.esp
Gameplay - Conflict Resolution AIO (Core + Visuals + Gameplay).esp
Gameplay - JSUE - WRP Patch.esp
NorthRoad.esp
Uncut Wasteland.esp
Uncut Extra Collection.esp
Character Expansions Revised - UW.esp
TMCOTT - Restored.esp
Functional Post Game Ending - Uncut Extra Collection Patch.esp
Functional Post Game Ending - Uncut Wasteland Patch.esp
Functional Post Game Ending - YUP Patch.esp
Mojave Raiders - TLD Patch.esp
Lightweight Strip Overhaul - Uncut Wasteland Patch.esp
Lucky38Overhaul.esp
Vanilla Intro Plus.esp
NorthRoadLegionFactionFix.esp
NorthRoadRemasteredToddPerkFix.esp
TheREPCONNBlues.esp
The REPCONN Blues Tweaks.esp
Afterschool Special Tweaks.esp
AutumnLeaves.esp
YUP - AutumnLeaves Patch.esp
Delay Autumn Leaves.esp
Lore Friendly Weapons Pack.esp
Lore Friendly Armor Pack.esp
FNVOppositeTraits.esp
All Weapon Sounds Overhaul .esp
Explosive Sounds Overhaul.esp
Combat Music.esp
MojaveExtended100.esp
Cut Sewers Restored.esp
Beyond The Beef Tweaks.esp
The Law Won.esp
SecuritronsOnAlert.esp
CloudGrenades.esp
Toasterizer.esp
Burden to Bear Armor.esp
ImmersivePickupSoundsFNV.esp
Content - Character Expansions Revised - FPGE Patch.esp
Content - Character Expansions Revised - TLD Patch.esp
Content - Character Expansions Revised - Uncut Wasteland Patch.esp
Content - JSUE - FPGE Patch.esp
Content - JSUE - Lore Friendly Armor Pack Patch.esp
Content - JSUE - Lore Friendly Weapons Pack Patch.esp
Content - JSUE - Opposite Traits Patch.esp
Content - JSUE - Uncut Wasteland Patch.esp
Content - Mojave Raiders - Lore Friendly Weapon Pack Patch.esp
Content - Mojave Raiders - Uncut Wasteland Patch.esp
Content - WFO - TLD Patch.esp
Content - YUP - TMCOTT Restored Patch.esp
FNVLODGen.esp
tmzLODadditions.esp
JustAssortedMods.esp
Logic and Consistency Fixes.esp
NevadaSkies.esp
NS - Remember Weather.esp

 

 

Specs:

CPU - AMD Ryzen 7 3700X 8-Core Processor

GPU - NVIDIA GeForce RTX 2080 Ti

RAM - 16.0 GB

OS - Windows 10

[M48A5]

What do you have installed that does not appear in the load order?

[jhx96]

I have nvse_loader.exe, the 4gb patcher, Improved Lighting Shaders, JIP LN NVSE Plugin, JohnnyGuitar NVSE Plugin, New Vegas Anti-Crash, New Vegas Tick Fix, New Vegas Heap Replacer, and Mod Limit Fix.

[dubiousintent]

I get the impression you are trying to use both ENB and NVGE at the same time. Last time I looked into it, those two were incompatible as they are two different approaches attempting to do the same graphics "thing". Try removing one or the other. If you did so and are still having problems, recheck your various "shaders" for compatibility with your primary graphics enhancement solution.

 

-Dubious-

[jhx96]

Uninstalled both NVGE and Improved Lighting Shaders, still immediately ctd's.

[dubiousintent]

Back to "basics" then.

 

You should always start troubleshooting from any error messages you can see. (They are your best "clue"; and why they exist at all.) Reporting such messages accurately is an essential first step.

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

Logs generated by the game itself (not Windows) are found in the game folder, where the "FalloutNV.EXE" file is located. They generally have the ".log" file extension, or a filename with "_log" in the name and a ".txt" extension.

A "CTD" is a "fatal" error, meaning the program/game did not know how to handle the error, nor how to proceed from that point; and shutdown to let the Windows Operating System (OS) take over again from the "desktop". The only thing worse is the so-called "Blue Screen of Death (BSoD)", which means the OS itself encountered a similar fatal error and entire computer has to be "rebooted" ("reset" switch or "power off-for-10-seconds-and-on-again") to return to function. DO NOT attempt to resume the game again from the point of a CTD, as your system memory is in an unpredictable state and make cause "save game" corruption even if it does get past the point where it crashed before. Reboot first.

"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, and records which do NOT begin with "00" (which are in the vanilla game files and not typically going to be fixable by yourself). 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 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.
---
"Windows Exception code: 0xc0000005". The "Faulting Application" is often the victim of another program rather than the actual culprit, making it virtually impossible for the user to trace the source. In at least one instance it appears to be caused by VWD/LOD files that had not been regenerated (when caught by NVAC as "DISABLED _LOD_ERR"). Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running. Run AV from multiple sources when checking for infections. There are a number of free online scanners on the internet (though they are all going to try to sell you their services after the first time).

You may need to exclude FNV from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)" (or Microsoft's "Enhanced Mitigation Experience Toolkit (EMET)" for Win7). Please see "Issue - NVSE - fails to load after update KB4058043 to Win10 FCU v1709" under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode once you have scanned since the last connection), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering. There are also tools (often called "Game Boosters") to help you determine "unnecessary when offline" Windows services you can temporarily shut down.

It is also possible that any recent change to your mods (such as updates) or your existing "load order" (such as additions or removals) has caused a corruption of the current save game file. Try going back to a save game from before the problem started. Often starting a "new game" with a vanilla test character can help confirm if the problem lies in the current load order.

-Dubious-

[jhx96]

There's no windows system error that pops up. I go to launch FalloutNV.exe from MO2 executables dropdown menu, it loads up a black screen with a tiny window also featuring a black screen in the top left corner, then after a few seconds it closes back to desktop with MO2 unlocked. The only overlay I have on is the steam overlay, but whether it's on or off doesn't really seem to make a difference.

 

And I'm not seeing any errors in any of the .log files. Unless I'm blind/stupid which is likely, but here's my nvac.log:

 

01011905 _ NewVegasAntiCrash FalloutNV.exe
01011905 _ 10FC0000 07050000 nvac.dll
01011905 _ 16800000 05010060 nvse_1_4.dll
01011905 _ 76E60000 0A004A61 ntdll.dll
01011913 e 00E8C00D C0000005 FalloutNV.exe
01011913 r 00E768DA 00E8C00D FalloutNV.exe
01011913 h 00E79102 89068B43 FalloutNV.exe
01011913 h 00E79107 8946048B FalloutNV.exe
01011913 h 00E7910D 89460803 FalloutNV.exe
01011913 h 00E79102 89068B43 FalloutNV.exe
01011913 h 00E79107 8946048B FalloutNV.exe
01011913 h 00E7910D 89460803 FalloutNV~
TRUNCATE _
01011914 n 00000000 00B98FE3
01011914 r 00B98FE3 00000000 FalloutNV.exe
01011914 h 00B99079 8B168B92 FalloutNV.exe
01011914 h 00B9907B 8B928800 FalloutNV.exe
01011914 n 00000000 00B99087
01011914 r 00B99087 00000000 FalloutNV.exe
01011914 h 00B9908B 8B068B50 FalloutNV.exe
01011914 h 00B9908D 8B506C57 FalloutNV.exe
01011914 n 00000000 00B99099
01011914 r 00B99099 00000000 FalloutNV.exe
01011914 h 00B9909D 8B038B90 FalloutNV.exe
01011914 h 00B9909F 8B90E000 FalloutNV.exe
01011914 n 00000000 00B990AA
01011914 r 00B990AA 00000000 FalloutNV.exe
01011914 h 00B990AA 8B068B90 FalloutNV.exe
01011914 h 00B990AC 8B908C00 FalloutNV.exe
01011914 n 00000000 00B990B7
01011914 r 00B990B7 00000000 FalloutNV.exe
01011914 n 00000000 4488045F
01011914 r 00B995F5 00000009 FalloutNV.exe
01011914 h 00B99514 8B81C000 FalloutNV.exe
01011914 h 00E72C26 8B87B800 FalloutNV.exe
01011914 h 00E72C2C 83783400 FalloutNV.exe
01011914 h 00E72C3B 8B87BC00 FalloutNV.exe
01011914 h 00B995A1 8B118B42 FalloutNV.exe
01011914 h 00B995A3 8B4230FF FalloutNV.exe
01011914 n 00000000 00B995A8
01011914 r 00B995A8 00000000 FalloutNV.exe
01011914 h 00B995C0 8B018B50 FalloutNV.exe
01011914 h 00B995C2 8B5034FF FalloutNV.exe
01011914 n 00000000 00B995C7
01011914 r 00B995C7 00000000 FalloutNV.exe
01011914 h 00B98E8F 8BABB800 FalloutNV.exe
01011914 h 00B98E96 8BB3C000 FalloutNV.exe
01011914 h 00E88E1C 83783400 FalloutNV.exe
01011914 h 00E9493F 837E3400 FalloutNV.exe
01011914 h 00E94966 8B168B42 FalloutNV.exe
01011914 h 00E94968 8B42088B FalloutNV.exe
01011914 n 00000000 00E9496F
01011914 r 00E9496F 00000000 FalloutNV.exe
01011914 h 00E9499E 896E3483 FalloutNV.exe
01011914 h 00E949A1 837E2800 FalloutNV.exe
01011914 h 00E949A9 837E2400 FalloutNV.exe
01011914 h 00E949C9 0FB7460C FalloutNV.exe
01011914 h 00B98ED5 8B55348B FalloutNV.exe
01011914 h 00B98FCF 8B168B42 FalloutNV.exe
01011914 h 00B98FD1 8B427857 FalloutNV.exe
01011914 n 00000000 00B98FD9
01011914 r 00B98FD9 00000000 FalloutNV.exe
01011914 h 00B98FD9 8B168B42 FalloutNV.exe
01011914 h 00B98FDB 8B427C57 FalloutNV.exe
01011914 n 00000000 00B98FE3
01011914 r 00B98FE3 00000000 FalloutNV.exe
01011914 h 00B99079 8B168B92 FalloutNV.exe
01011914 h 00B9907B 8B928800 FalloutNV.exe
01011914 n 00000000 00B99087
01011914 r 00B99087 00000000 FalloutNV.exe
01011914 h 00B9908B 8B068B50 FalloutNV.exe
01011914 h 00B9908D 8B506C57 FalloutNV.exe
01011914 n 00000000 00B99099
01011914 r 00B99099 00000000 FalloutNV.exe
01011914 h 00B9909D 8B038B90 FalloutNV.exe
01011914 h 00B9909F 8B90E000 FalloutNV.exe
01011914 n 00000000 00B990AA
01011914 r 00B990AA 00000000 FalloutNV.exe
01011914 h 00B990AA 8B068B90 FalloutNV.exe
01011914 h 00B990AC 8B908C00 FalloutNV.exe
01011914 n 00000000 00B990B7
01011914 r 00B990B7 00000000 FalloutNV.exe
01011914 n 00000000 0000009C
01011914 r 00B995F5 00000009 FalloutNV.exe
01011914 e 00E8C00D C0000005 FalloutNV.exe
01011914 r 00E768DA 00E8C00D FalloutNV.exe
01011914 h 00E79102 89068B43 FalloutNV.exe
01011914 h 00E79107 8946048B FalloutNV.exe
01011914 h 00E7910D 89460803 FalloutNV.exe
01011914 h 00E79102 89068B43 FalloutNV.exe
01011914 h 00E79107 8946048B FalloutNV.exe
01011914 h 00E7910D 89460803 FalloutNV.exe
01011914 h 00E79102 89068B43 FalloutNV.exe
01011914 h 00E79107 8946048B FalloutNV.exe
01011914 h 00E7910D 89460803 FalloutNV.exe
01011914 h 00E79102 89068B43 FalloutNV.exe
01011914 h 00E79107 8946048B FalloutNV.exe
01011914 h 00E7910D 89460803 FalloutNV.exe
01011915 h 00E790C2 89068B43 FalloutNV.exe
01011915 h 00E790C7 8946048B FalloutNV.exe
01011915 h 00E790CD 8946088B FalloutNV.exe
01011915 h 00E790D3 89460C03 FalloutNV.exe
01011915 h 00E790C2 89068B43 FalloutNV.exe
01011915 h 00E790C7 8946048B FalloutNV.exe
01011915 h 00E790CD 8946088B FalloutNV.exe
01011915 h 00E790D3 89460C03 FalloutNV.exe
01011915 h 00E790C2 89068B43 FalloutNV.exe
01011915 h 00E790C7 8946048B FalloutNV.exe
01011915 h 00E790CD 8946088B FalloutNV.exe
01011915 h 00E790D3 89460C03 FalloutNV.exe
01011915 h 00E790C2 89068B43 FalloutNV.exe
01011915 h 00E790C7 8946048B FalloutNV.exe
01011915 h 00E790CD 8946088B FalloutNV.exe
01011915 h 00E790D3 89460C03 FalloutNV.exe
01011915 h 00E79136 89068B43 FalloutNV.exe
01011915 h 00E7913B 89460403 FalloutNV.exe
01011915 h 00E79136 89068B43 FalloutNV.exe
01011915 h 00E7913B 89460403 FalloutNV.exe
01011915 h 00E79136 89068B43 FalloutNV.exe
01011915 h 00E7913B 89460403 FalloutNV.exe
01011915 h 00E79136 89068B43 FalloutNV.exe
01011915 h 00E7913B 89460403 FalloutNV.exe
01011915 h 00E8C0FD 8B088B51 FalloutNV.exe
01011915 h 00E8C0FF 8B513050 FalloutNV.exe
01011915 n 00000000 00E8C105
01011915 r 00E8C105 00000000 FalloutNV.exe
01011915 m 19016490 00000000
01011915 r 00AA22E2 0000000D FalloutNV.exe
01011915 ñ 1D011C80 00000020
01011915 r 00E722C6 00000001 FalloutNV.exe
01011915 m 19019D00 6459590A
01011915 r 6459590A 00000000 d3d9.dll (1005590A)
01011915 ^ 00E74431 00000003 FalloutNV.exe
01011915 h 6459590A 39463474 d3d9.dll (1005590A)
01011915 ^ 00E74431 00000002 FalloutNV.exe
01011915 h 645958F5 8B868400 d3d9.dll (100558F5)
01011915 ^ 00E74431 00000002 FalloutNV.exe
01011915 m 00000001 2904F300
01011915 r 00E74C12 0000000D FalloutNV.exe
01011915 M 8BB74100 C000001D
01011915 r 00E74F5C 00000000 FalloutNV.exe
01011915 h 00E8B566 395F1874 FalloutNV.exe
01011915 h 00E8B5E3 8B572489 FalloutNV.exe
01011915 h 00E8B5E6 8957285F FalloutNV.exe
01011915 h 00E74F6D 8B088B91 FalloutNV.exe
01011915 h 00E74F6F 8B91A400 FalloutNV.exe
01011915 n 00000000 00E74F78
01011915 r 00E74F78 00000000 FalloutNV.exe

 

 

does a capital "M" letter code mean anything?

[dubiousintent]

The "black screen with a tiny window also featuring a black screen in the top left corner," is a "command prompt" window, indicating that a "command line program" has been launched. A "command line program" is technically different from a "windows" program and the OS automatically detects that and launches them differently. Which indicates to me that you have something other than a normal game configuration. That is likely something to do with how you are telling MO2 to run FalloutNV.exe, but that would best be addressed by that support team. Most likely it is something as simple as a "syntax" error or a "typo" in the command.

 

You can try posting an image of how you have configured FNV in the "MO2 executables dropdown menu" and I will see if I can spot anything, but I caution you that I do not use MO/MO2 and can only deal with something obvious. Which is why I recommend you bring the problem to that support team.

 

As for the NVAC log, I don't know any more about it's codes than are listed on the description page. But given the "command line prompt" window, I assume your problem occurs before the game actually launches, so worry about NVAC errors later on.

 

Finally, Windows "system errors" don't always "pop-up" messages. Most are logged to the system "EventLog" without other notification, so you have to manually search them out and compare the date-time stamps to known events (like a game CTD). Please accept that a CTD will always create an eventlog entry. It is considered a "serious" event.

 

-Dubious-

[jhx96]

Ok well, this is what it's giving me in the Event Viewer and my executable tab:

[dubiousintent]

I would put both the "Binary" and the "Start In" field paths in double quotes, i.e. 'Binary: "D:\SteamLibrary\steampapps\common\Fallout New Vegas\FalloutNV.exe" ' because of the folder named "Fallout New Vegas". If MO2 assumes quotes, then it will tell you. But assumptions are a dangerous practice and I doubt it.

 

"Windows Exception code: 0xc0000005". The "Faulting Application" is often the victim of another program rather than the actual culprit, making it virtually impossible for the user to trace the source. In at least one instance it appears to be caused by VWD/LOD files that had not been regenerated (when caught by NVAC as "DISABLED _LOD_ERR"). Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running. Run AV from multiple sources when checking for infections. There are a number of free online scanners on the internet (though they are all going to try to sell you their services after the first time).

You may need to exclude FNV from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)" (or Microsoft's "Enhanced Mitigation Experience Toolkit (EMET)" for Win7). Please see "Issue - NVSE - fails to load after update KB4058043 to Win10 FCU v1709" under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode once you have scanned since the last connection), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering. There are also tools (often called "Game Boosters") to help you determine "unnecessary when offline" Windows services you can temporarily shut down.

It is also possible that any recent change to your mods (such as updates) or your existing "load order" (such as additions or removals) has caused a corruption of the current save game file. Try going back to a save game from before the problem started. Often starting a "new game" with a vanilla test character can help confirm if the problem lies in the current load order.

But it might be as simple as needing the double quotes as pointed out above, so try that first.

 

-Dubious-

Edited December 2, 2020 by dubiousintent