I downloaded a 4K texture pack from the Nexus to improve Starfield's graphics, but ever since then the game just crashes straight to the desktop without warning. How can I figure out which mod is causing the problem?
The first thing you need to do is disable the texture mod and see if the game runs normally. If it stops crashing, you know that pack is the culprit. Then enable it again and test it in different playthroughs or situations to confirm exactly when it fails, because sometimes heavy texture mods break only in certain areas or with certain effects turned on.
If the mod is still the problem, try downloading it again or look for lighter versions of the same pack. A lot of times 4K packs are too demanding for the available VRAM, especially if you have other mods active or if your graphics card can't handle it. Also check the comments on Nexus, because people usually warn if a mod causes crashes.
Another thing you can do is use your mod manager (Vortex or whatever you use) to disable mods one by one if you have several, that way you identify exactly which one breaks everything. And before installing anything, clear the cache and verify the game files on Steam, sometimes the installation gets stuck halfway and creates weird conflicts.
The first thing I'd recommend is disabling all your mods at once and then activating them little by little. Go into your mod manager (whether that's Vortex or whatever you're using) and disable the 4K texture pack along with any other mods you have. Once you confirm the game works without them, activate just the texture pack and launch the game. If it crashes again, you've already identified the culprit.
If the problem is the texture pack, try downloading a lower resolution version (2K instead of 4K), because sometimes 4K packs are too demanding depending on your graphics card and available RAM. Also check the mod's requirements: some need specific game versions or specific base mods that you might be missing. Look at the comments on Nexus; usually users report incompatibilities or conflicts there.
Another useful trick is checking if you have load order conflicts between mods. If the texture pack conflicts with another mod that modifies the same files, you'll need to reorder them in your load list or pick just one. And if none of this works, try clearing the game's cache or reinstalling the pack from scratch, because sometimes the download gets corrupted.
When you disable the mod, make sure to delete the game's cache folder (usually in Documents\My Games\Starfield) because sometimes old data stays behind and keeps causing conflicts. 4K texture packs tend to be heavy, and if you don't have much VRAM or your computer can't handle that resolution, the game will keep freezing even if the mod is installed correctly.
Before touching anything, launch the game without mods from the launcher (there's an option to disable all of them at once) and confirm it starts fine, because if it keeps crashing the problem isn't the texture pack. Once you know it's the mod, try downloading it again from Nexus but with the 2K version instead of 4K, because a lot of times those aggressive resolution packs cause memory issues just because they're not well optimized or your system can't handle that overhead; also check the recent comments on the mod to see if other people are reporting the same crash after a game update.
If you've already ruled out that the pack itself is the problem (by disabling it and seeing if the game starts), check the VRAM requirements: 4K texture packs sometimes need more video memory than your card has available, and the game crashes without an error because it just runs out of resources. Try lowering the texture resolution to 2K or less, or check if the mod has options to adjust the file size. It could also be that the pack has conflicts with other visual mods you have active (shaders, lighting), so if none of the above works, disable those too and start adding them back one at a time.
The 4K pack generally isn't the culprit on its own, unless it's from a sketchy source or corrupted. Most likely there's a conflict between that mod and another one you have installed, or the pack requires some dependency you're missing. That said, the most efficient way to figure it out is to disable EVERYTHING in your mod manager, confirm the game starts without issues, and then activate the mods in small blocks (for example, first just the texture pack, then half of the rest, etc.). That way you narrow down the problem using a binary approach instead of wasting hours testing one by one.
Besides disabling, clear the cache like they mentioned. But here's something nobody said: check the game logs. In the Starfield folder there should be error files, and sometimes they tell you exactly which mod is failing or what file it can't find. If the texture pack needs a specific version of some script mod or it's compressed badly, you'll see it there. Also, if the pack is really large (several GB), confirm your GPU has enough VRAM available; sometimes crashes with no message are from memory issues, not actual conflicts.
The 4K pack is usually the culprit because it eats up a ton of VRAM, so try lowering the texture resolution to 2K or even disabling the mod completely to confirm that's what it was. One thing nobody usually mentions: open the StarfieldCustom.ini file in Documents\My Games\Starfield and look for the line `uGridsToLoad=5` or similar, lower it to 3 or 4 to reduce what loads into memory at the same time - sometimes that alone fixes the crashes without needing to ditch the mod entirely.
Don't clean up files or delete folders without being sure what caused the problem first. Something similar happened to me with some texture mods, and it turned out the 4K pack just wasn't compatible with my game version - what worked for other people would hang as soon as I got to the menu. Try disabling just that pack in your mod manager, launch the game and see if it starts normally; if it stops hanging, then you know that's it. After that you can reactivate it but download a different version or an alternative texture pack, because sometimes there are weird compilation conflicts that have nothing to do with your setup.
If the game freezes without throwing an error, it's probably because the 4K pack is too heavy for your GPU or you're running out of VRAM - before you disable mods, open the game log (starfield.log in Documents\My Games\Starfield) and check for warnings about textures or memory, that'll tell you way more than just guessing.
The quickest way is to go straight to the mod manager and disable just the 4K pack without touching anything else. See if the game runs that way. If it launches without crashes, you've found your culprit. Then reactivate it and test in different areas of the map, because sometimes crashes depend on where you are (some texture mods break specifically in certain locations).
If it turns out that's the problem, you've got two options: find a lighter version of the same pack (a lot of creators put out 2K versions or ones with fewer details), or just try a different pack altogether. What nobody's mentioned is that sometimes the issue is a mix of conflicting mods, not the pack itself. If it crashes again when you reactivate it, try disabling any other mods you've got installed too (shaders, general improvements, whatever) and reactivate them one by one. It'll take longer but that way you actually isolate what's causing it.
The cache is what most people forget about and then it gives you headaches. Delete the entire `Documents\My Games\Starfield` folder (or at least the shaders subfolder if you see it), disable the 4K texture pack, and launch the game. If it starts without problems you'll know where the issue was; if it keeps crashing, then the mod might not be compatible with your game version or there's a conflict with another mod you didn't mention.
Log into answer.
