FNV frequently crashing in loading screen.

[mkvamm1]

I got this problem where FNV almost always crashes in a loading screen after an 1,5 hour of playing or so, sometimes it can be shorter and sometimes it can go longer. I don't use any 4gb patcher or anything like that. I'm on Win 10, could that have something to do with the issues I have?

 

Load order:

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
SaxxonsQuestPack.esm=1
Project Nevada - Core.esm=1
More Perks.esm=1
SomeguySeries.esm=1
Project Nevada - Equipment.esm=1
Project Nevada - Cyberware.esp=1
WMVM.esm=1
outsidebets.esp=1
More Perks Update.esp=1
PerkEveryLevel.esp=1
The Mod Configuration Menu.esp=1
WeaponModsExpanded.esp=1
WMX-DLCMerged.esp=1
WMX-POPMerged.esp=1
NewVegasBounties.esp=1
DLC Weapon Integration - WMX.esp=1
Immersive Minigames.esp=1
Better Casinos.esp=1
Grunt Perk Expanded.esp=1
CASM with MCM.esp=1

Edited November 11, 2017 by mkvamm1

[dubiousintent]

Most definitely. By default 32-bit games get a maximum of 2 GB of memory. You need the 4GB patch in order for them to use more, but ragardless of how much RAM you do have, it will never be able to use more tha 4GB. That is a builtin limitation of the 32-bit addressing scheme.

 

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.

Please see 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" article, at a minimum. You need a "Bash/Merge Patch" with that "load order". Strongly suggest you read the entire article.

 

In addition, please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding increasing your "heap size".

-Dubious-

Edited November 12, 2017 by dubiousintent

[mkvamm1]

Most definitely. By default 32-bit games get a maximum of 2 GB of memory. You need the 4GB patch in order for them to use more, but ragardless of how much RAM you do have, it will never be able to use more tha 4GB. That is a builtin limitation of the 32-bit addressing scheme.

 

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.

 

Please see 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" article, at a minimum. You need a "Bash/Merge Patch" with that "load order". Strongly suggest you read the entire article.

 

In addition, please see the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding increasing your "heap size".

 

-Dubious-

Don't you need more than 4 gb ram to use the 4gb patcher? Or am I just dumb?

Edited November 12, 2017 by mkvamm1

[dubiousintent]

Not dumb. It's a technical issue most aren't initially aware of, and the name given is not completely accurate: it's the limit that can be utilized by a game. The 4GB Patcher works if you have anywhere from 3GB on up. It's just has a reduced effect (less memory to give to the game) with less than 4GB of RAM. But every little bit helps. Windows itself does still need to keep some "system memory" for it's own use. That's why the original "default" of only 2GB for 32-bit games. For more detail see the "2-4GB memory limits and solutions" article in my signature. It covers older Windows systems as well.

 

-Dubious-

Edited November 12, 2017 by dubiousintent

[mkvamm1]

Not dumb. It's a technical issue most aren't initially aware of, and the name given is not completely accurate: it's the limit that can be utilized by a game. The 4GB Patcher works if you have anywhere from 3GB on up. It's just has a reduced effect (less memory to give to the game) with less than 4GB of RAM. But every little bit helps. Windows itself does still need to keep some "system memory" for it's own use. That's why the original "default" of only 2GB for 32-bit games. For more detail see the "2-4GB memory limits and solutions" article in my signature. It covers older Windows systems as well.

 

-Dubious-

Alright thanks, I did the NVSE heap thing and I'm gonna try the 4gb patcher as well to see if there is some effect. Thanks for the help dude. Question though, I set the heap amount to 240, do I need to alter that when I get the 4gb patcher? I know it said something about it in the appropriate category but I just want to make sure.

 

Update: Got a weird crash when I was near Red Rock Canyon, specifically a runtime error. Also I got a normal crash before in roughly the same area.

Edited November 12, 2017 by mkvamm1

[dubiousintent]

Re: "Heap size". With 4GB or less of RAM, you have to remember that any setting is "robbing Peter to pay Paul". "Heap" comes out of memory. So when you increase the heap size, you reducing what the game has available for rendering everything else. But "heap" is necessary for a smooth game. The 4GB patcher is taking some "system memory" to make it available to the "game memory". The heap used by the NVSE plugins comes 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-productive.

 

Re: CTD. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article. I'm going to make a guess that you are having the most common error: "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. 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.

 

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

-Dubious-

[mkvamm1]

Re: "Heap size". With 4GB or less of RAM, you have to remember that any setting is "robbing Peter to pay Paul". "Heap" comes out of memory. So when you increase the heap size, you reducing what the game has available for rendering everything else. But "heap" is necessary for a smooth game. The 4GB patcher is taking some "system memory" to make it available to the "game memory". The heap used by the NVSE plugins comes 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-productive.

 

Re: CTD. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article. I'm going to make a guess that you are having the most common error: "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. 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.

 

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

 

-Dubious-

 

I'm starting over with a fresh install, feel like I've messed some things up in the FNV folder.

[dubiousintent]

If you are going to start over with a fresh install, then I really recommend you read the entire wiki "FNV General Mod Use Advice" article before you install a bunch of mods.

 

-Dubious-

[Braeburn92]

old topic, but im having this issue as well. Just wanted to make sure im crashing not because im using a 25mb integrated graphics card but because of something else. I did nearly everything short of reinstalling the game. Would hi res replacers make my game freeze at the loading screens?

[dubiousintent]

They might. An integrated graphics card tends to make sacrifices, such not having it's own dedicated VRAM. In that case it has to use "system memory" taken from the total system RAM. I always recommend you get a stable, problem free vanilla game with your preferred "playability" mods before any "beautification" mods like texture replacers. See the 'Improved Texture Considerations' section in the wiki "FNV General Mod Use Advice" article.

 

Please see the 'Solutions to Starting the game problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. "Heap size" is only part of the picture.

-Dubious-