Can't start Skyrim over SKSE after crush to reboot

[Sunja44]

As topic. I crushed to reboot (not only to desktop), because I guess I have some issues with my power adaptor (not enough power when running two Geforece GTX Titn in SLI). 

 

Now I can't start Skyrim over SKSE. To be on the safe side I installed SKSE v1.06.16 anew, restored all default TESV stuff from a vanilla installation backup (TESV.exe etc.). I installed my ENB anew. My ini files are the same (they werw write protected), no reset to some sort of windowed mods or other resolutions. I even relogged into steam once.

 

I don't even reach the black loading screen. SKSE starts and you get that small black window somewhere appearing on your desktop, then this window greys out and nothing else will happen anymore.

[kalador]

I would suggest that you run Wrye Bash and look for something marked in red.  It sounds like you are missing a required .esm or .esp file.

[Sunja44]

Usually it should just crush to desktop with a missing master, but I get a message window "Skyrim is not working anymore" just about when I enter the loading screen (i have disabled the intro).

[davidporter89]

if you lost power it is possible that some files were corrupted. no easy way to fix that one except a reinstall, and i would suggest reinstalling the os too.

[Sunja44]

I deinstalled some mods with .esm files (SexLab, Jaysu's Swords, Zaz AP etc.) and just left over the DLC.esms and the unofficial patches. Now I can actually watch the loading screen for a second before Skyrim just crushes to desktop without any error message. Now it seems much more like a missing or corrupted master. As I copied all DLC.esms and .bsas from a backup into my folder there should be not the issue. My suspicion is a corrupted unofficial patch, because they count as master files. Will download them again and install once more.

[blindmankind]

i had that one time, and the only way to get it work again was a new install of skyrim...

 

e: i was really pissed :/

[Sunja44]

Puh, I got it solved.

 

The last few times I started it, I didn't even notice that a Lanterns of Skyrim.esp was still in my data folder, although I deinstalled that mod and the master LoS.esm file in WB. No wonder it crushes on the last few times. The fucking crush to reboot brought chaos to my Wrye Bash setup, the installation info of WB did not mirror the real installation. WB lost the info of the last few installations (mostly SexLab stuff). I deinstalled all SexLab mods and all mods with .esm files and looked into my Data folder if they are truly deinstalled now. Then I started Skyrim with all my other installed mods (over 200) and with ENB installed over SKSE and got nicely to the main loading screen and I could load a save.

 

Now I just have to install one mod after the other again to realize if there is anything else corrupted. Those are only a few (10 to 15) instead of almost 300. I guess I had luck.

 

 

i had that one time, and the only way to get it work again was a new install of skyrim...

 

e: i was really pissed :/

 

This was my fear, I just did that over the last two weeks. Ok, it lasted that long because I downloaded all my mods anew from Nexus (to get the newest versions and to give them all the tracking tag, I had missed a few for doing that), repacked them to my taste into WB format and installed them all anew with WB (at last I got rid of NMM and the need of chronological install). 

 

So answer number 1 in this thread was actually at least partially right, thx. A master wasn't truly missing but somehow corrupted and I guess WB is able to show if a master is existent or missing, but not if it might be corrupted.

 

 

PS: After installing the former deinstalled mods one by one I found out that the SexLab framework.esm was corrupted. Even without any dependancies installed, this .esm files can't be loaded at all, Skyrim just crushes to desktop or ends up in an endless SKSE loading window.

 

So now, where do get a SexLab 1.39b version again?

 

PPS: The whole issue wasn't due to a corrupt SexLab Framework installation file. The issue seemed to be a corruption of the StorageUtil.Save that will be created by SexLab and the StorageUtil.dll. I guess my saved animation settings are stored therein and maybe some more stuff (maybe registered animation dependancies to other mods like ZAP, SoS etc.). After just deleting the StorageUtil.Save I could start Skyrim with an installed SexLab Framework flawlessly. I had no idea that this file will be loaded during game start by SKSE. Ok, learnt something new.