Fallout 4 Memory Allocation Issue

[ff7legend]

It seems the dreaded memory allocation issue that plagued Skyrim for so long has carried over to Fallout 4. I've had the dreaded IFLS (Infinite Loading Screen) & freezes (controls lock up/sound plays/Windows Task Manager shows Fallout4.exe as "Not Responding") hit my game recently. Bethesda really needs to ditch the recycled game engines/Papyrus that date all the way back to Morrowind (16 bit Windows 2000 equivalent coding/programming). This is 2016, not 1999/2000. Has anyone else had the aforementioned issues & are Bethesda/the F4SE Team aware of said issue?

[Nofsdad]

I've had them and I don't see how Bethesda could NOT be aware of them. I had to do a complete game reinstall today and before I even added any mods... with nothing but the two small DLCs active I started having problems. I seriously believe I've bought my last Beth game. I remember sitting and waiting for this thinking they had probably solved the problems that had plagued all their other offerings at release especially since the modding community had taken care of so many of them. Hah! Fat chance! They kept 'em all and added some special new ones.

[RaffTheSweetling]

I've opened many a thread asking for help with CTDs, and most of us really don't know what to do, aside for the generic "check for conflicts", "Is your rig beefy enough?".

 

But I can tell you right now that this "everything just works" game comes with

 

Infinite Loading Screen crashes.

VATS freeze crashes. (frequent)

'Display Driver has stopped working and has recovered' crashes.

'Runtime Error R6025 - pure virtual function call' crashes (seldom).

 

It's the most frustrating title I've ever had to contend with from Beth. I know FO3 crashes regularly, but I could do something about that, with pcb and not carrying to much stuff around. This game "just doesn't work."

 

That said, I am running 182 active mods lol.

[YeOldeSensenmann]

It's the complete opposite for me. Almost 600 hours played and the only crashes I had was when Automatron came out and DEF_UI crashed the game because for some reason Bethesda thought it appropriate to include a new type of compass icon for the mechanists lair. That was easily fixed. 181 active mods, so vanilla this ain't.

 

None of my friends have issues with the game either but we are all using ENB because if there's one thing we learned from Skyrim it's that memory management is apparently something that should be handled via injectors some borderline insane russian guy has hacked together on hardware that punched way below the minimum requirements at that time, not Bethesda.

 

Basically, if you suffer from any kind of crashes that can be traced back to memory issues or driver crashes, give ENB a try.

[RaffTheSweetling]

It's the complete opposite for me. Almost 600 hours played and the only crashes I had was when Automatron came out..

 

Basically, if you suffer from any kind of crashes that can be traced back to memory issues or driver crashes, give ENB a try.

 

Everywhere I see a post from you, I see you promoting EnBoost. This is not a quick-fix issue, and that enb is not a fix for these problems at all. Exactly how is that enboost going to stop the VATS freeze?

 

Well done for having less problems with your game, but informing us of this fact is neither helpful to us, nor a solution to our problems.

[YeOldeSensenmann]

 

It's the complete opposite for me. Almost 600 hours played and the only crashes I had was when Automatron came out..

 

Basically, if you suffer from any kind of crashes that can be traced back to memory issues or driver crashes, give ENB a try.

 

Everywhere I see a post from you, I see you promoting EnBoost. This is not a quick-fix issue, and that enb is not a fix for these problems at all. Exactly how is that enboost going to stop the VATS freeze?

 

Well done for having less problems with your game, but informing us of this fact is neither helpful to us, nor a solution to our problems.

 

VATS is an overlay on a zoomed in target so the game has to render that on top of what's going on already. So yes, this is actually something that ENB might be able to help with as it increases the memory pool the game can use beyond the VRAM size of your GPU by utilizing parts of your system ram the game otherwise will simply not use in ways it should. The Creation Engine has a lousy memory management, that's simply a fact.

 

And I never claimed that ENB is the solution to everything, it's just something one can try. Just because it's not helping you doesn't automatically mean that the same is true for everyone else.

[RaffTheSweetling]

 

VATS is an overlay on a zoomed in target so the game has to render that on top of what's going on already. So yes, this is actually something that ENB might be able to help with as it increases the memory pool the game can use beyond the VRAM size of your GPU by utilizing parts of your system ram the game otherwise will simply not use in ways it should. The Creation Engine has a lousy memory management, that's simply a fact.

 

And I never claimed that ENB is the solution to everything, it's just something one can try. Just because it's not helping you doesn't automatically mean that the same is true for everyone else.

 

 

Hmm.. Those are fair points. I stand humbly corrected.

[Purr4me]

It seems the dreaded memory allocation issue that plagued Skyrim for so long has carried over to Fallout 4. I've had the dreaded IFLS (Infinite Loading Screen) & freezes (controls lock up/sound plays/Windows Task Manager shows Fallout4.exe as "Not Responding") hit my game recently. Bethesda really needs to ditch the recycled game engines/Papyrus that date all the way back to Morrowind (16 bit Windows 2000 equivalent coding/programming). This is 2016, not 1999/2000. Has anyone else had the aforementioned issues & are Bethesda/the F4SE Team aware of said issue?

Post more valid information please such as your PC's setup, spec's and things.

Improper setup will cause all sort of hell with any games that use a lot of VRAM.

 

For instance: post 2 a screen shots of pages 1 and 2 of dxdiag results here. That is considered valid.

what resolution is set for the Equipment ?

 

Last, it is not the games allocation that is the limiting factor ,it's the OS setup..."your configurations made to the PC's operating system."