Fallout nv crashing on load

I obtained this difficulty where FNV practically constantly crashes in a loading screen after an 1,5 hour of playing or so, periodically it can be shorter and also occasionally it can go much longer. I don"t usage any kind of 4gb patcher or anything like that. I"m on Victory 10, might that have somepoint to perform through the worries I have?

 

Load order:FalloutNV.esm=1DeadMoney.esm=1HonestHearts.esm=1OldWorldBlues.esm=1LonesomeRoadway.esm=1GunRunnersArsenal.esm=1ClassicPack.esm=1MercenaryPack.esm=1TribalPack.esm=1CaravanPack.esm=1SaxxonsQuestPack.esm=1Project Nevada - Core.esm=1More Perks.esm=1SomeguySeries.esm=1Project Nevada - Equipment.esm=1Project Nevada - Cyberware.esp=1WMVM.esm=1outsidebets.esp=1More Perks Update.esp=1PerkEveryLevel.esp=1The Mod Configuration Menu.esp=1WeaponModsExpanded.esp=1WMX-DLCMerged.esp=1WMX-POPMerged.esp=1NewVegasBounties.esp=1DLC Weapon Integration - WMX.esp=1Immersive Minigames.esp=1Better Casinos.esp=1Grunt Perk Expanded.esp=1CASM through MCM.esp=1 

Edited by mkvamm1, 11 November 2017 - 10:17 PM.

You watching: Fallout nv crashing on load


#2
*
Premium Member
*
Supporter237 posts

Most definitely.  By default 32-bit games gain a maximum of 2 GB of memory.  You require the 4GB patch in order for them to use even more, yet ragardmuch less of how much RAM you execute have, it will never before have the ability to use even more tha 4GB.  That is a builtin limitation of the 32-bit addressing plan.

 

Don"t install eincredibly optional file for a mod.  Read the install instructions closely.  Optional documents need to be schosen on a "instance by case" basis.  For example: through any type of mod you normally just require one ESP (and also perhaps one ESM) "base" file depending upon whether you have actually all the DLCs active or not.  Only if you don"t have them all active execute you have to install any kind of certain DLC versions if there is an "Ultimate Edition/All/Merged DLC" variation. 

Please check out the "Vanilla "Load Order"", "Towards Game Stability", "Third Rule: The Rule of One", "Smaller Plugin Cap", and "Merge Patch file" sections of the wiki "FNV General Mod Use Advice" write-up, at a minimum.  You require a "Bash/Merge Patch" through that "pack order".  Strongly indicate you read the whole article.

 

In enhancement, please watch the "Solutions to "Crash To Desktop" (CTD) problems" section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide concerning raising your "heap size". 

-Dubious-


Don"t you require even more than 4 gb ram to usage the 4gb patcher? Or am I simply dumb?

Edited by mkvamm1, 12 November 2017 - 12:11 PM.


#4
*

*
dubiousintent

Not dumb.  It"s a technical concern a lot of aren"t initially aware of, and the name offered is not totally accurate: it"s the limit that have the right to be utilized by a game.  The 4GB Patcher functions if you have actually everywhere from 3GB on up.  It"s simply has a decreased impact (much less memory to provide to the game) through less than 4GB of RAM.  But every bit little bit helps.  Windows itself does still should keep some "mechanism memory" for it"s own use.  That"s why the original "default" of only 2GB for 32-little bit games.  For even more detail check out the "2-4GB memory borders and solutions" write-up in my signature.  It covers older Windows units too.

 

-Dubious-

Edited by dubiousintent, 12 November 2017 - 01:21 PM.


Not dumb.  It"s a technological issue most aren"t initially mindful of, and also the name provided is not entirely accurate: it"s the limit that deserve to be utilized by a game.  The 4GB Patcher functions if you have almost everywhere from 3GB on up.  It"s simply has a decreased impact (less memory to give to the game) through less than 4GB of RAM.  But eexceptionally bit little bit helps.  Windows itself does still should store some "system memory" for it"s own usage.  That"s why the original "default" of only 2GB for 32-bit games.  For more detail see the "2-4GB memory limits and also solutions" write-up in my signature.  It covers older Windows systems too.

 

-Dubious-


Albest thanks, I did the NVSE heap thing and also I"m gonna try the 4gb patcher as well to see if tright here is some effect. Thanks for the assist dude. Question though, I set the heap amount to 240, do I need to transform that once I obtain the 4gb patcher? I recognize it shelp somepoint around it in the appropriate category yet I simply desire to make certain.

See more: Steam Error Failed To Load Overlay Localization File, Steam Failed To Load Overlay Localization File

 

Update: Got a weird crash as soon as I was close to Red Rock Canyon, especially a runtime error. Also I got a normal crash before in about the exact same area.

Edited by mkvamm1, 12 November 2017 - 04:46 PM.


Re: "Heap size".  With 4GB or less of RAM, you have to remember that any kind of establishing is "robbing Peter to pay Paul".  "Heap" comes out of memory.  So once you boost the heap size, you reducing what the game has available for rendering everything else.  But "heap" is vital for a smooth game.  The 4GB patcher is taking some "mechanism memory" to make it obtainable to the "game memory".  The heap provided by the NVSE plugins originates from the "game memory".  It"s all a balancing act, so you have to tweak the sizes to suit your total setup.  Just maximizing settings is counter-fertile.

 

Re: CTD.  Please view the "Windows Error Messages" area of the wiki "How to check out the majority of Bethesda game error logs" write-up.  I"m going to make a guess that you are having the most prevalent error: "Windows Exception code: 0xc0000005".  The "Faulting Application" is often the victim of another regimen quite than the actual culprit, making it practically difficult for the user to map the source.  Any recent upday because the last time it was functioning correctly is suspect, as are virsupplies even if you have anti-virus (AV) running.  Run AV from multiple resources as soon as checking for infections.

 

If it isn"t that, please provide the relevant "Windows Error" indevelopment outlined in that initially post.  In addition, please provide ALL the information requested in the wiki "How to ask for help" short article. 

-Dubious- 


Re: "Heap size".  With 4GB or much less of RAM, you need to remember that any kind of establishing is "robbing Peter to pay Paul".  "Heap" comes out of memory.  So when you boost the heap size, you reducing what the game has actually available for rendering whatever else.  But "heap" is crucial for a smooth game.  The 4GB patcher is taking some "device memory" to make it easily accessible to the "game memory".  The heap offered by the NVSE plugins originates from the "game memory".  It"s all a balancing act, so you need to tweak the sizes to suit your full setup.  Just maximizing settings is counter-fertile.

 

Re: CTD.  Please check out the "Windows Error Messages" area of the wiki "How to check out most Bethesda game error logs" short article.  I"m going to make a guess that you are having actually the the majority of common error: "Windows Exception code: 0xc0000005".  The "Faulting Application" is regularly the victim of an additional routine fairly than the actual culprit, making it virtually impossible for the user to trace the resource.  Any recent update because 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.

See more: Solved: Re: Battlefield 5 Crash To Desktop, Battlefield 5 418

 

If it isn"t that, please administer the relevant "Windows Error" information outlined in that first write-up.  In addition, please provide ALL the indevelopment asked for in the wiki "How to ask for help" short article. 

-Dubious- 


I"m founding over via a fresh install, feel favor I"ve messed some points up in the FNV folder.