"out of memory" crash with FNV4GB

[Guest deleted10460550]

I also get this mesage and I also use 4gfnv but I don't have a large amount of mods and I Have A very good computer.How do I fix this and how do I Reduce Memery Take up?

Also I'm Not very good with modding.

[Sarge198]

I also get this mesage and I also use 4gfnv but I don't have a large amount of mods and I Have A very good computer.How do I fix this and how do I Reduce Memery Take up? Also I'm Not very good with modding.

 

I don't use FNV4GB, I've edited FalloutNV.exe directly with a hex editor to enable Large Address Aware. Not sure if it makes a difference or not. I just don't like how FNV4GB works, it causes xfire to not detect Fallout New Vegas and record my game play hours.

 

What mods are you using? any large texture packs? Fallout Stutter Remover?

 

Disable any mods, run the game, see if the message pops up. Best thing to do is process of elimination, its annoying I know. Just disable mods 1 by 1 until the problem goes away. I would guess its a badly formatted mod with a memory leak, improperly sized texture, etc.

 

Try installing New Vegas Anti-Crash, It could help you never know. :laugh:

 

Sarge198 :ninja:

[JoKelly]

It turns out on my system it was the Underground Hide out Mod, which was causing the out of memory errors. As cool as it is, it had to go.

[5and3r5]

In my case it was the NMC's Texture Pack that caused those errors. I was using the Medium quality package. After uninstalling it, the game stopped crashing. Right now I'm downloading the Small pack to see if it'll work without errors.

 

edit: I can confirm, that the game does not crash on me with NMC Small Texture Pack installed.

Edited December 7, 2014 by 5and3r5

[Weetly]

I found the soloution completely by chance. My FONV ENB kept crashing due to an incompatibility with Windows 10, and being the total programming ignoramous I am,

I figured, "Durrr... Skyrim ENBs work on Windows 10, so I'll just move my d3d9.dll from my Skyrim folder to my FONV folder, durrr-herp-hurrr."

 

Obviously the FONV ENBs won't work with it, but, lo and behold, the Skyrim ENB combined with the 4GB exe-thingy and the stutter removal, I'm rockin' over 120 mods at 60fps on 1080p, including NMC's medium settings retextures, AND the flora overhaul, AND the more grass mod with grass set to 40 (default 80), EVE, FOOK, PNV, WMX, etc-etc-etc.

 

I feel like such a jerk for figuring out the fix, like it should have been Gopher or some super tech savvy modder. The catch? You can't use any ENB. Boo-hoo, cry me a river; I can actually play my game now. :smile:

Besides, FNV Realistic Wasteland Lighting emulates the feel of an ENB pretty well.

 

Enjoy actually playing your game now!

 

PS:

I'm running a 3rd gen i7-3770 up to 3.9GHz, 12GB DDR3 SDRAM @1,600MHz, and 1x Gigabyte Overclocked Edition 4GB GDDR5 VRAM Nvidia GTX 770. Nothing too fancy by today's standards in PC gaming.

 

EDIT:

Just copy the d3d9.dll Borris made for Skyrim into your FONV Steam directory (no other files), run the launcher, make sure fallout.ini in the My Games directory has "read-only" UNCHECKED so as not to have archive invalidation issues (to customize the INI, do all of the edits in the Steam directory's fallout_default.ini, and CHECK the "read-only" tick box for the file AFTER you save).

In your My Games directory, you'll get a proper "RendererInfo.txt" that has your actual modern GPU listed.

 

For example, my RendererInfo.txt reads:

 

Renderer Device Information:
NVIDIA GeForce GTX 770
nvd3dum.dll
RenderPath : BSSM_SV_2_A
PSversion : 300
VSversion : 300
VStarget : vs_2_0
PStarget : ps_2_a
PS2xtarget : ps_2_a
maxPS20inst : 512
3.0 Support : yes
3.0 Lighting : yes
Nonpowerof2textures : yes
FP16ARGB blending : yes
FP16ARGB filtering : yes
High dynamic range : yes
Bloom lighting : no
Refraction : yes
2.0 hairw : yes
SLI mode : no
Water shader : yes
Water reflections : yes
Water displacement : yes
Water high res : no
Multisample Type : 1
Transparency MS : no
Shader Package : 13
HW Thread Count : 8

It used to max out at some primative card (7700 or some such non-sense).

This file (THE ONE YOU GENERATE; DON'T COPY+PASTE THAT QUOTE) is what will end up making FONV squeal for you like a mole rat over a barrel. :smile:

Edited August 9, 2015 by Weetly

[WillemDaphoney]

 

 

Having a similar issue with out of memory crashes quite randomly, usually when entering a building.

PC Specs- Quad Core i5 3.33 ghz

GTX 750 Ti 2gb DDr5 VRAM

8gb DDR3 RAM

Used both BOSS and LOOT for load order, cleaned all dirty edits with FNVEdit, deleted all unused .esps and .esms from data folder, checked for conflicts with FNVEdit, using the latest FNV.4gb

Load order is-

Any help/advice would be much appreciated.

(And yes, I have edited the falloutnv ini for the Quad Core fix.)

 

 

Just going to add my two cents, I had pretty much the exact same issue when trying to enter an interior from the a world of pain mod. Black textures and other oddities started popping up. At first I thought I had reached the "mod limit" ~ 200 in Fallout 3 and about ~160 to ~180 in New Vegas. Then BAM "Out of memory error". Well this is a new one... :geek:

 

I had also been fiddling with the new version of Fallout Stutter Remover, I had not used it in a long time since I can't seem to notice a difference. I'm running a very powerful system:

 

AMD FX 8350

GTX TITAN

16GB RAM

SSD Drives

 

Well to the the point, the "bReplaceHeap" setting in the "sr_Fallout_Stutter_Remover.ini" seems to cause more harm than good. If you have it enabled try disabling it and see if it makes a difference. It worked for me but it may or may not help for you, since PC setups are different for everyone.

 

Fallout sure has some strange bugs..... :sick:

 

Just thought I'd share my opinion.

 

-Sarge198 :ninja:

 

thank you, this fixed my problem immediately.

[SirTwist]

First of all, did all of you set up your ini files first, before doing anything to your game? That is one thing to do. Next thing is to uncheck the read only on the ini files, and run your graphic's card setup program for games. Nvidia users, it's GeForce Experience. For ATI/AMD, not sure, but you should have the same thing. Then add in NVSE, and making it's ini file. Then the rest of your stuff, up to and including the 4GB launcher. I don't know if it's just my version of windows 10, or what, but every time I try the updated version of 4GB launcher, my games becomes corrupted, and can't access the game, at all. This could be anything from a missing ini file, to bad ini settings, to almost anything. If someone knows the fix, let me in on it. I digress.

 

Second, I recommend to leave the FNV4GB until after you are sure your game is running. (Make an archive copy of your game first, though, to save on downloading everything again.) I would recommend adding Stutter Remover and Anti-Crash before the 4GB. Make sure you are golden at that point. (This is where you would make the archive copy of your game.) Then the 4GB. Run it. If it works, then you are good to go. If not, then delete all local files, unpack, or copy over, your archive copy, checking with steam, and making sure it works, and try the other 4GB launcher.

[Shadowwynnd]

 

 

 

Having a similar issue with out of memory crashes quite randomly, usually when entering a building.

PC Specs- Quad Core i5 3.33 ghz

GTX 750 Ti 2gb DDr5 VRAM

8gb DDR3 RAM

Used both BOSS and LOOT for load order, cleaned all dirty edits with FNVEdit, deleted all unused .esps and .esms from data folder, checked for conflicts with FNVEdit, using the latest FNV.4gb

Load order is-

Any help/advice would be much appreciated.

(And yes, I have edited the falloutnv ini for the Quad Core fix.)

 

 

Just going to add my two cents, I had pretty much the exact same issue when trying to enter an interior from the a world of pain mod. Black textures and other oddities started popping up. At first I thought I had reached the "mod limit" ~ 200 in Fallout 3 and about ~160 to ~180 in New Vegas. Then BAM "Out of memory error". Well this is a new one... :geek:

 

I had also been fiddling with the new version of Fallout Stutter Remover, I had not used it in a long time since I can't seem to notice a difference. I'm running a very powerful system:

 

AMD FX 8350

GTX TITAN

16GB RAM

SSD Drives

 

Well to the the point, the "bReplaceHeap" setting in the "sr_Fallout_Stutter_Remover.ini" seems to cause more harm than good. If you have it enabled try disabling it and see if it makes a difference. It worked for me but it may or may not help for you, since PC setups are different for everyone.

 

Fallout sure has some strange bugs..... :sick:

 

Just thought I'd share my opinion.

 

-Sarge198 :ninja:

 

thank you, this fixed my problem immediately.

 

I also wanted to report that my problem was immediately solved by deactivating "bReplaceHeap" (set to 0) setting in the "sr_Fallout_Stutter_Remover.ini". Thank you so much Sarge198.

[Nems87]

CFF Explorer help me out, after i set use more then 2048mb to NVSE.exe, launcher, and FalloutNV.exe. https://www.youtube.com/watch?v=QYh5mA6NvdA here is example.

[sr383]

There are more than one kind of out of memory error. For each of you, more information is needed. How many plugins are you running (if more than 100 or so, this can be the problem). Badly made mods can also cause the issue. Textures which have the incorrect dimensions can give this error also. Bad meshes can cause the error. Running out of HEAP memory is probably the most common issue. The game has issues purging old CELL's, this can also be addressed. Not enough Video memory can also cause this issue, a common cause of this error is when using a laptop or desktop with built in graphics or low end video card.

 

There are several ways you can try to address this.

 

1) Install NVSE and read the readme on how to create an .ini for it and to add an entry which allows increasing the initial HEAP size. A size of 256 is a good start, you can try also 384, above a certain amount also causes crashes so don't try to put it too high.

 

2) After doing the above, if you have New Vegas Stutter Remover, make sure Heap Replacement is disabled, it's broken and causes OOM.

 

3) Install New Vegas Anti Crash, this plugin for NVSE is just essential and everyone should use it.

 

:EDIT:

 

Removed faulty information. -RB 5/11/2016

 

---------------

 

Additionally setting the LAA flag on nvse_loader.exe will do nothing, it's also not used when using FNV4GB.

 

Suggestion 2 fixed it! Thanks so much!