Crashing On New Game

[KnightOfWarCrime]

crash-2026-10-05-10-36-48.log Load order.txt

Edited Monday at 06:07 PM by KnightOfWarCrime

[deff.]

Let me guess. Wabbajack? Don't believe that you added so many mods without test...

[KnightOfWarCrime]

no wabbajack, ive played with these mods and more but i cut out a bit. ive been disabling mods and reinstalling in small batches and testing, ive verified my files in steam, uninstall and installed the game. im still missing the issue, ive been at it for awhile so my brain fried, plus i haven't come across this crash before and cant find anything on the internet related to it 

[deff.]

10 hours ago, KnightOfWarCrime said:

haven't come across this crash before

 

Yes, I checked you crashlog and I haven't seen something like that. Unfortunately I can't suggest anything, only thing that comes in my mind is - disable almost all mods (keep base) and start new game. Then add them back in small batches but in organized way, let's say, in first batch add back personal character mods (hairs, face change, skin etc)...next batch other things...you know what I mean...At some point crash might appear so, good luck 

[Samhsay]

16 hours ago, KnightOfWarCrime said:

crash-2026-10-05-10-36-48.log 43.61 kB · 1 download Load order.txt 19.09 kB · 1 download

Try to disable textere mods. 

However, it is possible that meshes or materials went missing or paths were specified incorrectly in one of the non-texture mods.

Edited yesterday at 10:13 AM by Samhsay

[judge007]

On 10/5/2026 at 11:00 AM, KnightOfWarCrime said:

crash-2026-10-05-10-36-48.log 43.61 kB · 1 download Load order.txt 19.09 kB · 1 download

AI analysis of your crash:

 

Short version: this is a texture-loading crash, not a bad plugin or script. Your load order isn't the likely culprit. A texture file is.

What the log shows

• The game crashed 3 minutes into the session, on a background render thread, in BSD3DResourceCreator::Flush → BSGraphics::RegisterD3DTexture.
• The game asked Direct3D to create a texture, it failed, and the game didn't check for the failure. It then read through a null pointer.
• Register RAX holds 0x80070057, which is E_INVALIDARG. That means Direct3D rejected the texture's parameters, which points to an invalid or unsupported texture file. It is not an out-of-memory error, which would be 0x8007000E, and GPU memory was only 0.5 of 7.13 GB at the time.
• No mod is named in the stack. The game's own code is the only thing on it, plus a d3d11.dll that loaded at a different address from the system one. That is a wrapper or proxy DLL sitting in your Fallout 4 folder.

Likely causes, most to least likely

1. A malformed DDS texture. Common problems are dimensions that aren't a multiple of 4 for a block-compressed format (BC1/BC3/BC5/BC7), a bad mip chain, an unsupported format, or a corrupt file. The usual sources are newer or recently updated texture and parameter mods. Your list has Vivid Fallout (AiO, Complex Parallax, LODs), Vivid Weathers, and many outfit, body and overlay packs.
2. The d3d11 proxy or graphics-hook stack. I see d3dcompiler_46e.dll, la_D3D11.dll, AAAFrameGeneration.dll, and the AMD FidelityFX DLL alongside the NVIDIA Flex/Godrays libraries. Any of these can interfere with texture creation.
3. System RAM pressure. You had 14.93 of 15.96 GB physical memory in use, and the game's private memory was about 12.5 GB. That doesn't explain this error code, but it leaves no headroom with a heavy texture load. Closing other apps helps.

What I'd do

• Note what you were doing at the 3-minute mark, such as loading a save, entering a cell, or a fast-travel. Then see if it crashes in the same spot every time. A consistent spot means a specific texture, and you can bisect from there.
• Temporarily remove the d3d11.dll (and d3dcompiler_46e.dll, if it's from ENB or ReShade) from the game folder. Then try again with frame generation off.
• If it still crashes, disable the most recently added or updated texture, outfit and body mods first, then Vivid Fallout Complex Parallax. Test after each batch.
• Run your texture folders through a DDS checker, or reconvert them with Cathedral Assets Optimizer, to catch bad dimensions and formats.

What did you change or update just before this started? That would narrow it down a lot.

 

 

My own take on this:

Disable ENB, Frame generation, Upscaling, ReShade and any other Graphics intensive mods

Try starting again.

If no Crash re-enable the above one at a time, til you start crashing again.

If you are still crashing, leave the above disabled, and start disabling mods that have textures, until you no longer crash.

 

Advice: Your system has apparently 16GB Ram and 8 GB VRAM ---you don't have the horsepower to run all (any) of the Graphics mods I listed.