Constant Memory Crashes with 4GB & HEAP

[Guest deleted29886875]

My memory crashes have started since the very beginning of the game and haven't ceased since, and I'm permanently trapped within the purgatory of Doc Mitchel's house with no means of escape. I managed to get into the Mojave once but the game immediately crashes upon entering a building or walking too far from Goodsprings, where I'm met with black textures.

I've tried making merge files, disabling big mods like the Flora overhaul, I've edited the HEAP ini files, and of course I'm using NVSE, the 4GB enabler, and fake full screen mode. Here's my load order:

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 YUP - Base Game + All DLC.esm

7 7 Project Nevada - Core.esm

8 8 Project Nevada - Equipment.esm

9 9 Project Nevada - Rebalance.esp

10 a Project Nevada - Cyberware.esp

11 b oHUD.esm

12 c WMVM.esm

13 d NevadaSkies.esm

14 e FCOMaster.esm

15 f mojavereloaded1.esp

16 10 Interior Lighting Overhaul - Core.esm

17 11 Interior Lighting Overhaul - L38PS.esm

18 12 ELECTRO-CITY - CompletedWorkorders.esm

19 13 ELECTRO-CITY - Highways and Byways.esm

20 14 YUP - NPC Fixes (Base Game + All DLC).esp

21 15 FCO + YUP.esp

22 16 FCO - Race Addon.esp

23 17 FCO - OHSB NPC Edits.esp

24 18 FCO - NPC Changes.esp

25 19 Project Nevada - Dead Money.esp

26 1a Project Nevada - Old World Blues.esp

27 1b Project Nevada - Honest Hearts.esp

28 1c Project Nevada - Lonesome Road.esp

29 1d Project Nevada - Gun Runners' Arsenal.esp

30 1e WeaponModsExpanded.esp

31 1f Project Nevada - WMX.esp

32 20 Vurt's WFO.esp

33 21 NCRTrooperOverhaul.esp

34 22 Interior Lighting Overhaul - Ultimate Edition.esp

35 23 WMX-DLCMerged.esp

36 24 christinecos.esp

37 25 The Mod Configuration Menu.esp

38 26 DYNAVISION 3.esp

39 27 WMX-ArenovalisTextures.esp

40 28 LFox Bottle That Water.esp

41 29 LeatherBackpack - eng.esp

42 2a TFH 1st Recon Helmet.esp

43 2b ammoingredientsloot.esp

44 2c MTB.esp

45 2d NCR Ranger Helmet Neck Cover.esp

46 2e TrooperOverhaul-Dragbody.esp

47 2f FCO + TOD.esp

48 30 Factions Reloaded Legion.esp

49 31 ILO - Nevada Skies Patch.esp

50 32 ILO - YUP Patch.esp

51 33 Zan_AutoPurge_SmartAgro_NV.esp

52 34 M1897.esp

53 35 Millenia_Tokarev.esp

54 36 TOZ66.esp

55 37 TOZ34.esp

56 38 KP31.esp

57 39 StenMkII.esp

58 3a PPSh41.esp

59 3b AK47.esp

60 3c M16A2.esp

61 3d FNFNC.esp

62 3e G3SG1.esp

63 3f HomemadeSMG.esp

64 40 Galil.esp

65 41 Uzi.esp

66 42 KS23.esp

67 43 LeeEnfieldNo4.esp

68 44 M14.esp

69 45 M1903A3Springfield.esp

70 46 M37Ithaca.esp

71 47 Makarov.esp

72 48 My Little Model of 1940 - Non Caliber.esp

73 49 PB6P9.esp

74 4a Mateba.esp

75 4b PKM.esp

76 4c NevadaSkies - Darker Nights.esp

77 4d NevadaSkies - Ultimate DLC Edition.esp

NevadaSkies - Basic Edition.esp

ILO - New Vegas Bounties.esp

NevadaSkies - TTW Edition.esp

Leather backpack - rus.esp

78 4e Merge Patch .esp

If there is anything you think could help, I would be more than appreciative. I've played new vegas multiple times on the same computer using way more mods so I'm really at a loss for what's happened.

[dubiousintent]

Did you upgrade to Win10? New set of problems not found on an older system. Try the following in order:

 

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.

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 NVSE 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.

 

Move any "inactive" plugins out of the game "Data" folder. They get loaded by the game engine if found, and can cause "Missing Master" problems (which is what your problem sounds like). Then see the wiki "Missing Masters" article.

Please see the 'Towards Game Stability' section of the wiki "FNV General Mod Use Advice" article. You don't mention NVSR, which is usually needed as well.

Please see the 'Solutions to Starting the game problems' section; and "Cause-2:" of the 'Issue: Application load Windows error(s)' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide, which discusses setting the "iNumHWThreads=" entry to the number of cores your CPU has. This setting solved one recent user's CTDs.

-Dubious-

Edited September 16, 2017 by dubiousintent

[Guest deleted29886875]

Thank you for all your help dubious and the help sent to others on this forum, this place would be a lot worse without people like you. I installed NVSR and edited a ton of .INIs and installed a few compatibility patches but I'm still having issues. My main issue now is that all loading screens always end with a freeze. It's not an automatic ctd but a 'new vegas has stopped responding.' I've also uninstalled my ill informed auto-purge mod and I've also reinstalled most of my mods fresh. All of my inactive mods have also been removed from the data folder as instructed and FNVedit reports no important missing files. Here is my revamped load order atm:

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 oHUD.esm

7 7 FCOMaster.esm

8 8 YUP - Base Game + All DLC.esm

9 9 Project Nevada - Core.esm

10 a Project Nevada - Cyberware.esp

11 b Project Nevada - Equipment.esm

12 c Project Nevada - Rebalance.esp

13 d WMVM.esm

14 e NevadaSkies.esm

15 f ELECTRO-CITY - CompletedWorkorders.esm

16 10 ELECTRO-CITY - Highways and Byways.esm

17 11 mojavereloaded1.esp

18 12 YUP - NPC Fixes (Base Game + All DLC).esp

19 13 FCO - Race Addon.esp

20 14 Unofficial Patch Plus.esp

21 15 FCO - OHSB NPC Edits.esp

22 16 FCO + YUP.esp

23 17 FCO - NPC Changes.esp

24 18 The Mod Configuration Menu.esp

25 19 Project Nevada - Dead Money.esp

26 1a Project Nevada - Honest Hearts.esp

27 1b Project Nevada - Old World Blues.esp

28 1c Project Nevada - Lonesome Road.esp

29 1d Project Nevada - Gun Runners' Arsenal.esp

30 1e Vurt's WFO.esp

31 1f WeaponModsExpanded.esp

32 20 WMX-ArenovalisTextures.esp

33 21 WMX-DLCMerged.esp

34 22 YUP - WMX PN.esp

35 23 Project Nevada - WMX.esp

36 24 NevadaSkies - Darker Nights.esp

37 25 DYNAVISION 3.esp

38 26 Factions Reloaded Legion.esp

39 27 NCRTrooperOverhaul.esp

40 28 TrooperOverhaul-Dragbody.esp

41 29 FCO + TOD.esp

42 2a christinecos.esp

43 2b NevadaSkies - Ultimate DLC Edition.esp

44 2c CASM with MCM.esp

The only thing I've not done so far is move my steam folder (and btw, I do use windows 10)

[dubiousintent]

Hanging after the loading screens is a classic "Missing Master" symptom. Phrases like "FNVedit reports no important missing files" make me shudder. There is no such thing as an "unimportant missing file" as far as FNVEdit is concerned. If it says a file is missing, then it is important. It only takes one missing or out of sequence to hang the game. (That's why it's important to get inactive plugins out of the "Data" folder: so they don't cause missing file errors.) I don't recall a single instance reported back to me in the last two years that wasn't traceable to one of those two causes.

 

You have too many mods I am not familiar with to tell if there is anything obviously wrong with that LO. Regardless of your opinion of it, give LOOT a try and see if that re-arranges any of them before trying to start the game again. It does just fine for most mods, and can be "customized" for the few instances that need to be adjusted. But the big thing is it examines plugins at a level the typical player won't unless they take the time to examine each plugin with FNVEdit and manually work out the necessary LO on their own. If it says one plugin needs to go before another, I believe it unless I can show why it's wrong.

 

Assume you've done those relatively easy things, but still can't get into the game. Now it gets more painful.

 

Everybody balks at moving the default Steam folder, and yet it's been known since Vista to be an issue. (Only the underlying cause took a while to determine.) I don't see anything in that LO that screams "THIS" except that it's still in the "C:\Program Files" tree. I tried working around the issue back when I upgraded to Win7 (skipped Vista completely), and after investigating realized it was a useless, never ending battle. It only got worse with Win10. Bite the bullet, get it done once and don't let any game install there again (always use "custom install"). It's just one more thing you don't want to have to worry about.

 

When you do move Steam, take the time to install and test your mods one at a time (as per the wiki "FNV General Mod Use Advice" article). You have a number of "overhauls", which make sweeping changes to the game. Combining them can have problems unless the authors specifically tested them in combination. You need to prioritize first and decide which are most important, "can't live without", and install them first. See 'Mod Conflict Isolation' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

-Dubious-

[Guest deleted29886875]

I think I might have phrased my previous post badly. NVEdit detects no missing files whatsoever and completes its loading 100% normally. I realize I have quite a few large mods installed but around this time last year I was running a perfectly stable game with double the mods, many of which were a lot large including things like WOP, NV Bounties, and dozens more. At first I though the root of my problem was the Interior Lighting Overhaul, the only mod on my list that I haven't used before (Besides the ncr armor overhaul, but that's purely armor and leveled list integration, enough to raise an eyebrow but after being tested doesn't seem to bother anything.) That playthrough lasted at least 80 hours all on windows 10 without moving my steam folder and it ran perfectly fine. I hope I don't sound too condescending and I really do appreciate your help a lot, there's nothing I know that has helped me thus far.

Oh and update: LOOT makes zero changes to the load order so either we're both wrong or I finally did something right.

Edited September 17, 2017 by AStoryAboutYou

[dubiousintent]

Welp, since it doesn't seem to be any of the usual causes (LO sort order or missing masters), let's go back to your initial description of the problem and see if we can refine it a bit.

 

Interpreting what you said for clarification: the game is mostly CTDing while still in Doc Mitchell's house, even before you can exit. (For the moment let's set aside that you did manage to exit the house once, but CTDed before going very far.)

 

Is the CTD consistent as to when or where you are in Doc's when the CTD occurs?

 

Then you reported that it was not really (or any longer) a CTD but that the loading screen (for a save or a new game?) hangs. Are both those things still occurring? Can you force one or the other to occur by doing something at will?

 

Now for some more obscure possibilities:

 

Are you running Steam in "off-line" mode (avoids getting interrupted by internet activity stealing CPU cycles)? Have you shutdown all unnecessary background applications such as "anti-virus", printer monitors, and any multiplayer overlays or the Steam Overlay?

 

Do you have the game running in "Vista SP2" compatibility mode?

 

One of the major reasons for moving Steam out of the default location is that MS OS updates tend to reset "protected system assets" and update security settings on that folder tree. So things that worked previously in that location last year won't necessarily after the updates over time are applied. And a 7 year old game does not understand or know how to deal with "shadow files". But if you want to hold off on that until you have exhausted all other possibilities, that's up to you.

 

You said you are using the "4GB enabler". Which one? Have you tried the FNV 4GB Patcher? You haven't given your hardware, so please confirm you have more than 4GB of System RAM and 1GB of VRAM.

 

-Dubious-

Edited September 17, 2017 by dubiousintent

[Guest deleted29886875]

My game always crashes during the loading screen from Doc Mitchel's house into the Mojave without fail. Everything inside of his house seems to work fine, I can access MCM, Dynavison, Project Nevada, WMX, and all gun mods I had installed earlier were in their proper positions inside his house. Problems only start when I tired to leave.

While testing my mods I was able to get outside a few times but still no problems were fixed as I could not enter any building. Oddly enough one time I was able to get into Chet's store where I learned that the Interior Lighting Overhaul was screwing up, so I decided to uninstall it thinking I had fixed the problem. It didn't.

As for the obscure issues I was running steam offline for unrelated reasons but after testing with it as normal nothing seemed to change. I don't know if the game is running in Vista SP2 Compatibility mode so it's probably not.

If and probably when I have to move my steam folder what guide do you recommend I follow? Will I have to redownload everything or is it a simple move? Keep in mind I do not have a second or external harddrive.

[Guest deleted29886875]

At this point my problems have to be tucked away in some weird file somewhere so are there any ini files I should check or something?

[Mktavish]

Maybe dubious knows of a better tutorial , but steam has one ... https://support.steampowered.com/kb_article.php?ref=7418-YUBN-8129

 

And as far as .ini files ... you could go to "User/documents/MyGames" And rename the "FalloutNV" folder there.

Then relaunch the game , having it check your video , and recreate the file path and all in it.

Then copy paste the save from the old you are using , or just make a new game. And give it a test.

 

That will tell you if there is an .ini problem.

Edited September 17, 2017 by Mktavish

[Guest deleted29886875]

Well renaming the FalloutNV folder did nothing, so I guess its not an ini problem.