spar117

I doubt that this is an issue seeing as how the input of the game has a strong correlation to both components breaking down. I don't think there was anything running in the background on the HDD device (the E:// drive) that would cause these damages.

Update: The power supply seems to be the main an issue. All other components seem to work just fine. Lack of power must have been insufficient for normal operation. The GPU was damaged as well. I am still left to assume the modifications I had made lead to both devices to be damaged. Despite this revelation, I would prefer to keep this discussion open for the sake of relevance. I find myself rather inexperience when it comes to optimizing mods for performance. I want to better understand how to adjust any modification in this regard. Any and all feed back is still greatly appreciated.

GPU: 780 GTX Nvidia EVEGA Mother board: Gigabyte z97x-ud5h CPU: Intel i7 (4770k?) Cooler: Hyper 212 EVO Storage Devices: SSD 250 GB, HDD 1 TB OS: Windows 10 RAM: 32 GB The OS will not boot. It will reboot to the emergency boot screen on startup or after each failed storage-drive reset. The video feed is inconsistent on startup, sometimes displaying a single color/black screen for minutes until deciding to restart or upon a manual shut down. After several tries, it ((((may)))) display the emergency boot screen. About 1 minute into the game I was walking from Fort Independence into Boston city, coming into view of a ghoul. Around at that point the video feed stuttered (like hell) and flashed green as I was shooting its arm off. Before this, I made another run a few days prior to test out the few mods I had on. I believe I had ENB 283, FO Script Extender, some of the "core" and a few graphic mods (I think, though I highly doubt it was any of the major texture/graphic packages) from that guide. At that point the game seem to be running just fine being in the same area for, roughly, 30 minutes walking through the city and into BOS attack on a Mutant outpost. I was able to safely shut down the game after that test run without incident. 2-3 years ago I had played FO4 with only one modification concerning settlements. It was purely a default setup. Only now was I getting back into the game with mods in mind. Edit: Not sure if this is relevant or not, but just before the crash I updated Nvidia software to its latest version (as of 11/30/18)

Not too long ago I was gearing up Fallout 4 with a selection of mods posted here. But not being cautious enough, I had not tested the game with each batch of mods that I would download and install through Mod Organizer. When I had all most of the mods from the selection down, I ran the game... and it completely crashed my computer. I was in a frantic to try and get working again, running windows fix and resets, which all promptly failed to carry out. At the moment my rig is toast. Though I am not sure of the exact problem, my best guess is that I overloaded my GPU. The sudden addition of heavy texture mods combined with ENB boost--v. 283(?)--along with some enblocal.ini file adjustments to video memory--the limit extended to 28000 under the 32000(?) gpu max as given from the DX11 video memory size test. Right now I am looking for help or advice to avoid this f*#@ up in the future. Until I get my rig diagnosed and going again, I will have no way to know what the exact issue is. I am pretty sure (from the nature of the crash and modifications) that the GPU was the is the issue. Should I avoid ENB boost and/or heavy graphics mods, or is something else I should account for?

What about your memory block allocation? Are you using SSME? Your crashing can be the result of having texture packs installed. Never mind what I said, already mentioned above.

Never dealt with something like this. Defiantly some missing mesh files there, or perhaps skyrim can't detect them.

So I have the infamous CTD on save issue on saving, auto saving, and quick saving. I traced this issue back to my save file, where instead of having normal saves and the SKSE save (as the most present saves should be) the saves have an extension with .ess.temp. The saves would not even have an SKSE version also. I have done some research into this. There is a claim that this is due to the interaction between the OS and Skyrim, where the OS fails to completely convert the save into a usable format for the game. This is said to be caused by instability of the game itself. I can do the double load of the same save, I can do the kill yourself method, and even revert to an old save to fix the CTD save issue temporarily. I say temporarily as reloading my game from the corrupted save or any saves based off of it still crashes, and forcing me back to the previous methods to fix it. I am afraid that if I continue on with the corrupted save I may no longer use those solutions in the future. Has anyone been able to solve this issue besides using the former solutions? Is there anyway to force the temporary saves to convert to proper ess. forms? If it helps, here is my load order: I have already cleaned the mods using LOOT and TESVEdit. I am pretty sure it's a single mod doing this, but if it is please let me know.

Was in a rush, apologize about that. As with what Fiewiel said, perhaps disable your quest mods until arriving to Whiterun. This would ensure a strong start. Mods that add, change script, or are just script intensive, such as deadly dragons, can make your game unstable. The more you add, the less stable it becomes. However unstable saves for me happen in late game, but it's still a possibility in this case. With that said, you could try and uninstall your texture mods. I remember having an issue in Winterhold where I would constantly crash in the city. Uninstalling a few texture mods ceased the crashing for me. I believe it was the high res texture packs that were giving me the trouble, the same ones you have installed.

This may likely be a texture conflict or a memory block issue. Since you have already disabled your mods to solve the problem, it's likely the ladder. Here is a link to video that may lead to your fix: https://www.youtube.com/watch?v=37xAMUQc1oY. Skyrim has been known to not handle memory transfer that well, and often crashes when one memory block crashes.

Looking at my saves, the corrupted one seems to have no skse save version, and the .ess extension is followed by .temp. I assume converting it to a normal .ess extension would suffice, but would that fix anything? On top of that, what do I do about the missing .skse save?

I have concluded that the crashing is the result of saving in any form, not from loading or fast traveling. Loading any save from the corrupted one works fine. But, when loading the same corrupted save, I am then able to properly save. However, when closing the game, opening again, reloading a save from saving in that corrupted save, it still crashes. I should mention that this problem started occurring after reloading a save multiple times. This resulted from a situation where brawls would bug out on me, even with the brawl bug plugin installed. I was trying to fix it, which had me reload the save countless times. But, I have feeling this is justa problem with saving in cities, specifically in Winterhold as of right now. @saurusmaximus, any idea what the saving problem results from?

Doing a bit of research. There is a likely case that two or more mods maybe interfering with each other. I will look through TesVedit again to examine

I use the TESVEdit to clean mods and do error checking.

I am absolutely defeated by this problem. I have tried ENboost, SSME, Safety Load, uninstalling textures, reinstalling and organizing my game, and even starting a new save. I used LOOT and TES V Edit, but to no avail. I have checked my Papyrus log, though I couldn't find anything of notice, except at the end of the log: From the Papyrus log, I can guess that I have some missing files. However, I have not removed a single mod since starting a new save. I am begging for help. If anyone can help isolate and help solve/fix the issue, please do. I will post my load order or a list of mods upon request. Edit: After going into some investigation, I have concluded that this problem does not include loading cells, sleeping, fast traveling or anything within the frozen VM state. This is a saving problem that causes the CTDs.

In response to post #24731924. #24732119, #24732384 are all replies on the same post. It makes me realize just how under appreciated and under-rewarding mod developers are. Steam/Valve wanted modders rewarded for their work but went around it the wrong way. That system should have had a donation button in its place. I would certainly donate, but I am not that rich... **** it, I am going donate.