SaikoEspada Posted January 29, 2018 Share Posted January 29, 2018 Game keep crashing and I don't know why. Can someone look at my load order and tell me if something is wrong with it? 0 0 FalloutNV.esm 1 1 DeadMoney.esm 2 2 HonestHearts.esm 3 3 OldWorldBlues.esm 4 4 LonesomeRoad.esm 5 5 GunRunnersArsenal.esm 6 6 ClassicPack.esm 7 7 MercenaryPack.esm 8 8 TribalPack.esm 9 9 CaravanPack.esm 10 a YUP - Base Game + All DLC.esm 11 b ELECTRO-CITY - CompletedWorkorders.esm 12 c FCOMaster.esm 13 d SomeguySeries.esm 14 e More Perks.esm 15 f More Perks for Dead Money.esm 16 10 Project Nevada - Core.esm 17 11 Project Nevada - Equipment.esm 18 12 ELECTRO-CITY - Highways and Byways.esm 19 13 NVWillow.esp 20 14 Weapons.of.the.New.Millenia.esm 21 15 Project Nevada - Rebalance.esp 22 16 oHUD.esm 23 17 SolidProject.esm 24 18 Advanced Recon Tech.esm 25 19 Project Nevada - Cyberware.esp 26 1a Project Nevada - Extra Options.esm 27 1b NevadaSkies.esm 28 1c More Perks for Honest Hearts.esm 29 1d More Traits.esm 30 1e Military NV Backpacks.esm 31 1f More Perks for Old World Blues.esm 32 20 More Perks for Companions.esm 33 21 YUP - NPC Fixes (Base Game + All DLC).esp 34 22 FCO - NPC Changes.esp 35 23 DarNifiedUINV.esp 36 24 FPSWeaponWheel.esp 37 25 JIP Companions Command & Control.esp 38 26 JIP Improved Recipe Menu.esp 39 27 Project Nevada - Rebalance Complete.esp 40 28 Project Nevada - All DLC.esp 41 29 Project Nevada - Cyberware Additions.esp 42 2a The Mod Configuration Menu.esp 43 2b The Weapon Mod Menu.esp 44 2c FlashlightNVSE.esp 45 2d DYNAVISION 3.esp 46 2e EVE FNV - ALL DLC.esp 47 2f More Perks Update.esp 48 30 delilah.esp 49 31 WeaponModsExpanded.esp 50 32 WMX-ArenovalisTextures.esp 51 33 WMX-DLCMerged.esp 52 34 Project Nevada - WMX.esp 53 35 Project Nevada - EVE All DLC.esp 54 36 WMX-EVE-AllDLCMerged.esp 55 37 WMX-POPMerged.esp 56 38 B42Inertia.esp 57 39 Reload Sounds.esp 58 3a Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp 59 3b Weapons.of.the.New.Millenia.Leveled.Lists.esp 60 3c NVWillow - Project Nevada Rebalance.esp 61 3d FCO - Delilah.esp 62 3e FCO - Willow.esp 63 3f Military NV Backpacks - BumBagUseSlot1.esp 64 40 Military NV Backpacks - No Straps.esp 65 41 Military NV Backpacks - Vendor Script Replenish.esp 66 42 FNV Realistic Wasteland Lighting - All DLC.esp 67 43 T60.esp 68 44 ADAM Complete.esp 69 45 ADAM - MERGE.esp 70 46 ADAM - Nemesis Armor Pack.esp 71 47 NewVegasBounties.esp 72 48 NewVegasBountiesII.esp 73 49 KerberosPanzer.esp 74 4a ADAM - MAIN.esp 75 4b ADAM - NCR Patrol Armor.esp 76 4c ADAM - Rangers on Patrol.esp 77 4d ADAM - Outcast Ranger Armor.esp 78 4e Weapons.of.the.New.Millenia.Cheat.Cabinet.esp 79 4f Holster Gear.esp 80 50 ADAM - Trooper Gloves.esp 81 51 LootMenu.esp 82 52 Advanced Recon Armor.esp 83 53 Advanced Recon Armor-Stealth With Drawn Weapon.esp 84 54 Advanced Recon Gear.esp 85 55 Advanced Recon Tech.esp 86 56 More Perks for Companions Update.esp 87 57 More Perks for Dead Money Update.esp 88 58 More Perks for Old World Blues Update.esp 89 59 More Traits Update.esp 90 5a More Perks for Honest Hearts Update.esp 91 5b pipboy2500_edisleado.esp 92 5c dD - Enhanced Blood Main NV.esp 93 5d NevadaSkies - Ultimate DLC Edition.esp Link to comment Share on other sites More sharing options...
dubiousintent Posted January 29, 2018 Share Posted January 29, 2018 There is nothing obviously wrong with your "load order". A lot depends upon what you are doing when the game crashes. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. All of the following may not apply to your specific situation, but are worth repeating anyway.* Are you running Win10? Did you get the "Fall Creator's Update" (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.The FCU 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.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, where it talks about configuring for an application in the "Windows Defender Exploit Guard (WDEG)".* 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 using the 4GB Patcher? If not, please see the 'Maximizing use of memory' section of the wiki "FNV General Mod Use Advice" article.* 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. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.* 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.* Please see the paragraph about "auto-saves" under the 'Essentials for Getting Started' section of the wiki "FNV General Mod Use Advice" article. -Dubious- Link to comment Share on other sites More sharing options...
SaikoEspada Posted January 30, 2018 Author Share Posted January 30, 2018 There is nothing obviously wrong with your "load order". A lot depends upon what you are doing when the game crashes. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. All of the following may not apply to your specific situation, but are worth repeating anyway. * Are you running Win10? Did you get the "Fall Creator's Update" (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. The FCU 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. 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, where it talks about configuring for an application in the "Windows Defender Exploit Guard (WDEG)". * 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 using the 4GB Patcher? If not, please see the 'Maximizing use of memory' section of the wiki "FNV General Mod Use Advice" article. * 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. Please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. * 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. * Please see the paragraph about "auto-saves" under the 'Essentials for Getting Started' section of the wiki "FNV General Mod Use Advice" article. -Dubious-I do have all the things you have listed. So I'm guessing it has something to do with the auto saves because that is usually when the game crashes. When the game crashes it usually just stays there frozen replaying the last second of sound over and over. I'm going to remove the auto save and see if it keeps happening. Thank you very much. Link to comment Share on other sites More sharing options...
Deleted1205226User Posted January 30, 2018 Share Posted January 30, 2018 I see many esp mixed with esm. I always been told that esm should go first and esp after. Esm with multiple esp dependencies should be ordered like DLC. Link to comment Share on other sites More sharing options...
dubiousintent Posted January 30, 2018 Share Posted January 30, 2018 (edited) That is a good general rule, but there is an exception. Some ESP files have the internal file header ESM flag enabled. (These are always from mods in my experience.) This causes them to be sorted and treated as an ESM by LOOT, regardless of the file extension. There are pros and cons to the technique, but that is something the mod author found necessary. xEdit sorts them differently than LOOT; by extension only and completely ignoring the internal flag. This can trip up the player if they are not aware of it. Please see the 'Issue: What are these Red "!" kite icons in the game?' entry "Solution-2b" "Green note" under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. I've always found LOOT to be the correct positioning for game play in such cases. (xEdit is an "editor". LOOT is a "plugin sorter". Different tools for different purposes.) If you have a firm reason to disagree with LOOT, you can change it's "metadata" for that plugin to cause it to load after other specific plugins as a custom setting. -Dubious- Edited January 30, 2018 by dubiousintent Link to comment Share on other sites More sharing options...
Recommended Posts