An apparently evident CTD reason

[iXenite]

Update:

 

I've uninstalled Skyrim (it was on "C"; IMPORTANT = My game is not the Special Edition one), then re-downloaded and re-installed it via Steam on a different hard disk ("F").

 

Then I've given the new "Skyrim" folder the name "NewSkyrim", and pasted my old "Skyrim" folder to "common", in order for it to become the one used by my system for gaming.

 

After that, I've told NMM that "Skyrim" was on "F", and used Loot to place my mods in their usual order. Final result: my dear, modded, old Skyrim (the one which had always worked), has started a new life on "F".

 

Problem: I've then launched the game and... usual CTD!

 

30 minutes ago I decided to do a last attempt: installing a new version of SKSE. So I went to the website, and what did I discover? SKSE doesn't exist for the classic version of Skyrim anymore (it only exists for the Special Eidtion)!

And what if a guy has only the classical version? He can't play a modded game anymore?!

 

I read on a website that the Special Edition is a sort of dictatorial command.

 

My idea. My modded Skyrim doesn't work anymore because Steam has, without my permission, sort of updated my Skyrim to the Special edition version, and now the old SKSE and other things don't work anymore.

 

What do you think?

 

If things are like this, I hate Steam: it is like my games are not mine... they decide to update, they decide everything! While my idea of "mine" is something under my control, something that I can protect, hide...

 

There is no public version of SKSE for the Special Edition - you're mistaken. Steam also did not secretly update your Skyrim to the Special Edition because that is not how the Special Edition works. The Special Edition is a 100% separate game from the original Skyrim. The Special Edition is not just a patch update, it was a completely rebuilt Skyrim in the new 64-bit version of Skyrim's "Creation Engine" that they used for Fallout 4.

[Alehnblivion]

Yes, you are right.

I've said a lot of wrong things.

 

I always forget that the S.Edition is the modern one and confuse Legendary Edition with Special Edition.

 

Some days ago I noticed, for example, that it was not possible to download the old unofficial patch anymore: now you can only download a patch for the LE.

And what if someone doesn't have the LE?

[iXenite]

Do you have all of the DLC or do you just have the base game with no DLC's?

Edited January 14, 2017 by DaddyDirection

[Alehnblivion]

I have just the base game.

 

Important update:

 

If you have followed my journey through this beautiful CTD adventure, you'll be glad to learn another piece of the puzzle: using a Vanilla Skyrim folder with my new installation on "F" prevents CTDs, when a new character is used (starting a new game); using my old Skyrim folder with my new installation on "F" makes the game crash, when I load my saves.

 

Recap:

 

Old installation © / Old modded Skyrim folder = Perfectly fine, when playing with my argonian character in 2015; CTDs, when playing now, with the same pc, the same mods, the same load order, the same argonian character, new (2017) saves AND old (2015) saves (memory patches, reinstallation of the same mods, starting a new game with a new character, etc, haven't prevented CTDs).

 

New installation (F) / Old modded Skyrim folder (same, old folder used thanks to the famous trick of changing folder names appropriately) = CTDs when playing with a 2017 save (other saves not tried yet).

 

New installation (F) / Vanilla (unmodded) Skyrim folder = No CTD, when playing with a new character (new game); immediate CTD when loading saves of my argonian character (these saves are unsupported, because all my mods are of course absent in the new folder).

 

Final hypothesis:

 

- New conflict between my hardware and one or more mods;

- Something wrong inside the Old modded Skyrim folder.