CreateTexture2dwarning crash

[ShangWang1]

Hello,

 

I am recieving the: "CreateTexture2DWarning.cpp(60):
[critical] A call to ID3D11Device::CreateTexture2D failed with error code0x80070057.
This will crash the game." Crash.

 

I have already disabled my entire load order and booted back into my save and the game still crashes consistently at the same exact point on the map with that error. At this point I am stumped. The only thing I can think of is that I may have uninstalled some mod at some point with certain textures that were baked into my save game and now that save is reliant on those textures. I am thinking starting a new save will solve the problem? Any thoughts on that? Any alternative ideas in case starting a new game doesnt work? You will find my load order and last crash log attached. The crash log is outdated though, since this type of crash doesnt generate buffout logs. I get that message instead. Its like a little popup window and the game crashes when I hit okay, on the window. If I don't hit okay, then FO4 just stays stuck on a black screen.

 

The location of the crash is on the train tracks just SW of hardware town. I can reproduce the crash consistently at that location. The crash seems to occur along that latitude a bit further west that my PC is situated at while heading SW toward the glowing sea for the mission where you have to go talk  to that super mutant guy who tells you that you need to teleport to the institute.

 

Despite all of my mods, I have been running the game quite smoothly for a while now and this is the first seemingly unsolvable crash I have run in to. Any input is greatly appreciated. I have not had time to test a new game yet, but I will report my findings when I get a chance. Any ideas to save my save would be great (mainly because i don't feel like re-configuring my entire MCM).

 

The image details the map location that the crash occurs. The video details the point at which the game crashes each time at the location that the PC is right near on the map photo. The video ends just as the screen goes black (though it is not seen in the video as it ends once the screen goes black and the creatTexture2dwarning pops up).

buffout crash.txt crash-2022-06-29-22-34-05-AUTOSCAN.txt loadorder.txt plugins.txt

[ShangWang1]

Update:

 

Okay so I just took a new approach to troubleshooting this and I seem to have made progress. I went into my "C:\Games\Installed\Steam\steamapps\common\Fallout 4\Data\textures" folder and removed all files inside. I placed them in a texture back up folder and reloaded my save. Went to the crash point and voila!!! No crash. I will begin slowly adding the texture files and folder back in batch by batch until i can reproduce the crash so that I can pin point the texture that is causing the issue. I will report back once I do, it is only a matter of time now.

[ShangWang1]

Solved:

 

So it turned out to be a folder called "props" in my "Fallout 4\Data\textures". Tbh I'm even sure what mod it is part of, but I would like to either:

a) Replace the textures with more updated ones on the mod site

b) Remove the mod

 

Only problem is, idk what mod it comes from. I will list the folder contents below. Does anyone know what mod this props texture folder comes from?

 

Also, I wanted to add that if you are having this createTexture2dwarning crash:

1) Create a texture backup folder somewhere

2) Go into your "Fallout 4\Data\textures" folder and cut the entire folder contents

3) Paste the folder contents into the backup folder you created

4) Start adding back the folder contents in small batches until you can reproduce the crash

5) Isolate the batch that causes the crash in your backup folder and add each texture folder back one at a time until you reproduce the error

6) If you can reproduce the error, then you have found the culprit

[GlowingHeart]

Buffout4.dll Warnings/CreateTexture2DWarning.cpp(60): Acall to ID311Device::CreateTextur2d failed with error code 0x887A0005. This will crash the Game.

 

Kann der Fehler auch in Textur BA2 Archiven liegen oder nur in dem losen Textur Ordnern? 

 

Can the error also be in texture BA2 archives or only in the loose texture folders?

[Spyder Arachnid]

4 hours ago, GlowingHeart said:

 

Buffout4.dll Warnings/CreateTexture2DWarning.cpp(60): Acall to ID311Device::CreateTextur2d failed with error code 0x887A0005. This will crash the Game.

 

 

Kann der Fehler auch in Textur BA2 Archiven liegen oder nur in dem losen Textur Ordnern? 

 

Can the error also be in texture BA2 archives or only in the loose texture folders?

 

It can be in a ba2, not often but it can happen, but it's easier to start with your loose textures before attempting to check your ba2s.

 

If you ever get that error, best to remove your textures folder and start from there. Process of elimination. If it is still giving you that same error after you removed your loose files, then it is likely to be ba2 related. Which is going to be a bigger pain to deal with.

 

You'll need to remove your ba2's little by little to find the culprit. Then when you do end up finding it, you got to extract it and then do the process of elimination on its loose files like you did previously on your other loose files. Once you find it, either fix it (via paint or photoshop) or remove it. Most problems stem from wrong dimensions, as Fallout 4 uses the whole 512, 1024, 2048, 4096, etc. technique. So, if fixing it, make sure first if it has the proper dimensions. Otherwise, check its saved format (most are diffuse textures saved in the wrong compression, which is an easy fix (BC3 (Linear, DTX5))).

 

After all that, pack it back up (Archive2 works best for extracting or repacking) and toss it back in and check to see if everything is all good.

 

If it is a ba2, check the mod page as well before going through all that. If it's a texture causing you to crash, then it is more than likely a well-known issue and would have been reported. Maybe even someone already mentioned which file it is exactly in the ba2, so it saves you the trouble of searching yourself. Some might have even uploaded a fix already for it in the comments. Always check first to save yourself the headache of doing it yourself.