Windows d3d11 Game freeze and Crash

Visionaires said:
recently I started getting this d3d11: Failed to create staging 2d texture error at the end of my logs (see attached) I imagine that is causing my crashes but the errors are... not very informative.. Hopefully someone here can lend a hand!
Click to expand...
GPU errors can often be fixed by completely uninstalling your GPU drivers (use DDU) and then downloading the most recent GPU driver directly from either AMD or Nvidia and installing it (don't install it from Windows Update). In some cases, a new driver causes problems and you may need to install an older driver from AMD or Nvidia until they release an updated version that doesn't cause problems.

Since you do have multiple mods installed, it is possible that a mod is the cause of the problem, but that isn't too likely. You could try playing a new save without any mods installed and see if you get this error to see if it might be related to mods. But I'd at least start with the driver.
 
Riamus said:
GPU errors can often be fixed by completely uninstalling your GPU drivers (use DDU) and then downloading the most recent GPU driver directly from either AMD or Nvidia and installing it (don't install it from Windows Update). In some cases, a new driver causes problems and you may need to install an older driver from AMD or Nvidia until they release an updated version that doesn't cause problems.

Since you do have multiple mods installed, it is possible that a mod is the cause of the problem, but that isn't too likely. You could try playing a new save without any mods installed and see if you get this error to see if it might be related to mods. But I'd at least start with the driver.
Click to expand...
Hey! Thank you for replying! I used DDU and installed the newest off Nvidia website. also tried 4 other older drivers, going through the process with DDU each time. Unfortunately to no avail...
 
Visionaires said:
Hey! Thank you for replying! I used DDU and installed the newest off Nvidia website. also tried 4 other older drivers, going through the process with DDU each time. Unfortunately to no avail...
Click to expand...
Well, it was worth trying. Try a test without mods, or even with mods in a new save, and see if either option works without an error. If you still get errors in both cases, then I have no other suggestions and you'll need to wait to see if someone else has some suggestions for you.

I looked through again and noticed this:
Direct3D: detected that using refresh rate causes time drift. Will stop trusting refresh rate until the game window is moved.
Direct3D: detected that vsync is broken (it does not limit frame rate properly). Delta time will now be calculated using cpu-side time stampling until the game window is moved.
Click to expand...

I've seen a support post a long time ago with that, but I don't remember any details about it. But maybe try disabling VSync in your video options.
 
I did a search on the forum and see that someone with that message was using an Alienware computer. Not sure if you also are using one? The suggestions were to make sure you uninstall any "booster" apps that supposedly make games play better since most don't actually do anything and are likely to cause problems. Here is the thread. See the first post from Jugginator for his thoughts.
U

Thread 'Crashing every other night with new PC'

I bought a new alienware pc (I know, stupidly $$$ for the value), but it has been going to a 'blue screen' every few days of playing 7d2d. This is the only game that blue screens. Can I increase the verbosity of the 7d2d logs, or do anything to prep for the next crash, in order to give this community information they might need to help me solve it?

I've upgraded every driver I know to do, including firmware. I didn't see a sticky on this forum about what logs/data people need to see. I may be blind:) Let me know what I need to give you all to help me.

Windows 11 pro.
 
Riamus said:
Well, it was worth trying. Try a test without mods, or even with mods in a new save, and see if either option works without an error. If you still get errors in both cases, then I have no other suggestions and you'll need to wait to see if someone else has some suggestions for you.

I looked through again and noticed this:


I've seen a support post a long time ago with that, but I don't remember any details about it. But maybe try disabling VSync in your video options.
Click to expand...
I noticed the Vsync as well disabled it and literally just crashed a couple minutes ago

last text before log cuts off and crashed.
"d3d11: failed to create staging 2D texture w=128 h=2 d3dfmt=10 [887a0005]"

I also see these not sure if its common or part of the problem
"2026-03-01T12:50:55 2094.879 WRN [MultiBlockManager][Alignment] SetTerrainAlignmentDirty failed; no terrain-aligned block has been registered at the specified world position: 618, 66, 704"

Going to try and disable.... dynamic mesh? I think it was... I've made probably 15 new worlds FULLY uninstalled the game 3-4 times

I built my rig so the computer itself has no alienware parts to it.. though my monitor is a Dell/Alienware. I'll give that thread a read and see if theres something I have not checked out. I appreciate all the help!
 
Visionaires said:
I noticed the Vsync as well disabled it and literally just crashed a couple minutes ago

last text before log cuts off and crashed.
"d3d11: failed to create staging 2D texture w=128 h=2 d3dfmt=10 [887a0005]"

I also see these not sure if its common or part of the problem
"2026-03-01T12:50:55 2094.879 WRN [MultiBlockManager][Alignment] SetTerrainAlignmentDirty failed; no terrain-aligned block has been registered at the specified world position: 618, 66, 704"

Going to try and disable.... dynamic mesh? I think it was... I've made probably 15 new worlds FULLY uninstalled the game 3-4 times

I built my rig so the computer itself has no alienware parts to it.. though my monitor is a Dell/Alienware. I'll give that thread a read and see if theres something I have not checked out. I appreciate all the help!
Click to expand...
That warning shouldn't be a problem. Try without dynamic meshes, though that's mostly just affecting the areas within view of your land claim(s). I wouldn't bother reinstalling the game anymore. That's not going to do anything at this point. But try without mods just in case.

Since you built it, there wouldn't be any bloatware installed unless you installed it yourself. But if you did install any apps to improve performance in games, that could be the problem. The post I linked above also suggests that maybe the GPU is loose, which could be possible when building it yourself, or that the GPU might be failing. Unfortunately, unless you have a different GPU, you can't easily test that without buying a new GPU. Though you could run something like 3DMark to test your computer/GPU and see if you have any issues.

The person with the problem in that thread never responded to say if they solved the problem, so we don't know how they solved it (if they did).

Since it's Nvidia, you can also try disabling (or enabling) DLSS just in case it's related.
 
Riamus said:
That warning shouldn't be a problem. Try without dynamic meshes, though that's mostly just affecting the areas within view of your land claim(s). I wouldn't bother reinstalling the game anymore. That's not going to do anything at this point. But try without mods just in case.

Since you built it, there wouldn't be any bloatware installed unless you installed it yourself. But if you did install any apps to improve performance in games, that could be the problem. The post I linked above also suggests that maybe the GPU is loose, which could be possible when building it yourself, or that the GPU might be failing. Unfortunately, unless you have a different GPU, you can't easily test that without buying a new GPU. Though you could run something like 3DMark to test your computer/GPU and see if you have any issues.

The person with the problem in that thread never responded to say if they solved the problem, so we don't know how they solved it (if they did).
Click to expand...
Doesnt hurt to check my GPU and make sure its secured and hasnt gotten loose over time. No bloatware or "make my game faster and better" programs... I'll run a benchmark see where it stands never hurts. I've been in IT far to long to not at least try everything once while troubleshooting lol
 
Visionaires said:
Doesnt hurt to check my GPU and make sure its secured and hasnt gotten loose over time. No bloatware or "make my game faster and better" programs... I'll run a benchmark see where it stands never hurts. I've been in IT far to long to not at least try everything once while troubleshooting lol
Click to expand...
I added a note at the bottom of what you quoted in case you didn't see it.... try without DLSS just to see if maybe that is related. You can also try other graphics settings to see if anything makes a difference. Maybe even look at any settings in the Nvidia control app if you installed it when installing the driver.
 
Riamus said:
I added a note at the bottom of what you quoted in case you didn't see it.... try without DLSS just to see if maybe that is related. You can also try other graphics settings to see if anything makes a difference. Maybe even look at any settings in the Nvidia control app if you installed it when installing the driver.
Click to expand...
Great suggestion I'll look at DLSS as well. I disabled V sync from the Nvidia control panel. need to start the game up and let it run for abit before I keep digging I got a handful of new things to try so I appreciate that! Can't be changing to many things without going back to test cause who knows what actually worked if it does begin to work. Troubleshooting 101 lol
 
One last
Visionaires said:
Going to let it run but the direct D3d vsync issue didnt appear in the log where it normally does during initialization and what not. progress maybe?
Click to expand...
If you don't have it happen again, please post whatever change it was that worked once you know. It'll be helpful for others.
 
Riamus said:
One last

If you don't have it happen again, please post whatever change it was that worked once you know. It'll be helpful for others.
Click to expand...
Of course I’ll edit my original post with a write up and additional testing to verify whatever change did in fact work and that when I reverted back the change I was able to replicate the crash again!
 
You must log in or register to reply here.
Back
Top