I need a little help with my load order

[ShaderMarc]

i'm just need a little help to organize my mods, it is crashing my game sometimes, here's my load order:

[X] FalloutNV.esm

[X] DeadMoney.esm

[X] HonestHearts.esm

[X] OldWorldBlues.esm

[X] LonesomeRoad.esm

[X] GunRunnersArsenal.esm

[X] ClassicPack.esm

[X] MercenaryPack.esm

[X] TribalPack.esm

[X] CaravanPack.esm

[X] FCOMaster.esm

[X] oHUD.esm

[X] Interior Lighting Overhaul - Core.esm

[X] ELECTRO-CITY - CompletedWorkorders.esm

[X] ELECTRO-CITY - Highways and Byways.esm

[X] Interior Lighting Overhaul - L38PS.esm

[X] Weapons.of.the.New.Millenia.esm

[X] The Mod Configuration Menu.esp

[X] DarNifiedUINV.esp

[X] ILO - PipBoy Light.esp

[X] Roberts_NewVegas.esp

[X] FCO - Roberts Patch.esp

[X] Better Game Performance.esp

[X] FCO - NPC Changes.esp

[X] WeaponModsExpanded.esp

[X] WMX-DLCMerged.esp

[X] WMX-POPMerged.esp

[X] WMX-ArenovalisTextures.esp

[X] 1nivVSLArmors.esp

[X] RWD-NV v1.4 [standard Version].esp

[X] PerkEveryLevel.esp

[X] FNV Realistic Wasteland Lighting - All DLC.esp

[X] Weapons.of.the.New.Millenia.Store.LITE.esp

[X] UrgeWasterScarf.esp

[X] Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp

[X] Weapons.of.the.New.Millenia.Leveled.Lists.esp

[X] RSO - Realistic Stealth Overhaul - NV.esp

[X] Interior Lighting Overhaul - Ultimate Edition.esp

[M48A5]

Try this https://loot.github.io/ It will organize your load order for you. Does not work for Fallout 3.

[ShaderMarc]

Try this https://loot.github.io/ It will organize your load order for you. Does not work for Fallout 3.

i tried, still crashing

[dubiousintent]

Not all CTDs are due to "load order" issues. Depends upon a number of things, which is why we ask people to provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as NVSE and it's related plugins, texture replacements (specifically their larger image sizes: 1024x1024, etc.), and "post-processors" like ENB or SweetFX.

 

All of the following may not apply to your specific situation, but are worth repeating anyway.

* Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so.

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

* Are you running Win10? Did you get the "Fall Creator's Update" of 2017 (FCU aka "RedStone 3")? Do you have "New Vegas Stutter Remover" (NVSR) installed? If all three are "true", then please see the 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (and other "heap size") entries in the 'Solutions to Performance problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

These "Creator's Updates" are Microsoft's replacement to the old "new release" and "service pack" improvement and bug-fix mechanism. They are scheduled to occur every six months, so they will be in the "Spring" and "Fall" of each year.

The FCU 2017 update was released in mid-November 2017, so a "brand new" system probably did not come with it installed. However, the default configuration is usually to have OS updates automatically installed. (Those usually start being distributed on the second Tuesday of each month, but may take a week or more to get to everyone.) See the MS "Get the Windows 10 Fall Creators Update" article for how to check your version release and manually pull down the update if necessary. It is important to keep your OS always "up to date" to prevent malware infections.

* 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 a Windows Update for the "Meltdown and Spectre Vulnerabilities".

* Are you using the 4GB Patcher? If not, please see the 'Maximizing use of memory' section of the wiki "FNV General Mod Use Advice" article.

* The game has "memory leaks". Getting 2-3 hours before a CTD is pretty good. You might want to try using the tool "Memclean", which periodically (you can set the interval; default is every 15 minutes) tells the OS to perform it's built-in "clean up" of memory. It has a "mini-monitor" that displays memory usage. Doesn't seem to hurt and might help.

* If you are using the full 4GB of memory, most likely your CTD problem (now or in the future) is the default "heap size" is too small. It's so common you might as well deal with it now. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

* Move any "inactive" plugins out of the game "Data" folder. They count against the "plugin cap" because they get loaded by the game engine if found, and can cause "Missing Master" problems. Please see the wiki "Missing Masters" article if you get that error message.

* Don't install every optional file for a mod. Read the install instructions carefully. Optional files need to be selected on a "case by case" basis. For example: with any mod you usually only need one ESP (and possibly one ESM) "base" file depending upon whether you have all the DLCs active or not. Only if you don't have them all active do you need to install any specific DLC versions if there is an "Ultimate Edition/All/Merged DLC" version.

* "Compatibility patches" to make one mod work with another need to be placed after (as in "physically lower, higher numbered") in the "load order" than all of the plugins they are designed to make compatible. ESMs should always be placed at the top (lowest numbered) positions in the "load order", followed by the related ESPs though they can be separated from their ESMs by other plugins. "LOOT" does a good job of determining those basic orders. Getting the "load order" incorrect will cause "Missing Master" errors as well.

FYI: The "pre-order packs" (Caravan, Classic, Mercenary, and Tribal; available now in the "Courier's Stash" addon), are not considered "DLCs" by most mods and "compatibility patches". So their absence should not deter you from using "All DLC Merged" plugins. When in doubt, follow the process in the wiki "Missing Masters" article to confirm they are not "master files" for that plugin.

* Don't install compatibility patches for mods you do not have installed/active (e.g. get rid of any "TTW" patches if you aren't running TTW).

* Do not use an "Auto-purge" mod for game play. (That was old advice from before we knew better.) They are designed for debugging by mod creator's only, according to the author of the JIP extensions to NVSE. See the 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu', "Cause-2", "Solution-3" entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for the game settings that do the same job.

* Please see the paragraph about "auto-saves" under the 'Essentials for Getting Started' section of the wiki "FNV General Mod Use Advice" article. If you have been using the built-in "auto-save" feature and you get the endless "roulette wheel" when loading a save game, then your current save game file is corrupted and you will have to either go back to a save before the corruption occurred (hard to tell) or start over.

* If you have more than one mod that makes any change to the same record or set of records in the vanilla game, then you really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.

-Dubious-

[ShaderMarc]

i did everythin really everything, my game crashes aftes 10-20 minutes in every single location, loading screen, or anything, i don't know what to do anymore

[dubiousintent]

Usually it's either the NVSR/"Win10 FCU" conflict in the third bullet point above, or you need the "heap size fix" in the 6th, that are behind CTDs after a period of time. Otherwise work through the list of issues under the 'Solutions to "Crash To Desktop" (CTD) problems' and 'Solutions to Performance problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

If none of that resolves it, you need to provide some more detail to help us pin down just when and where they occur. Vague responses of "I did everything" and "in every single location, loading screen, or anything" doesn't give us anything to work with that isn't covered by the solutions previously provided. Please provide ALL the "updated" information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as NVSE and it's related plugins, texture replacements (specifically their larger image sizes: 1024x1024, etc.), and "post-processors" like ENB or SweetFX.

-Dubious-