Haven't played in a while, had to replace my HDD. Install skyrim on a whim, and I'm crashing whenever I quick travel without an error message. Never had this issue before the replacement, but I was running x32 at that time.

I'm running Win7 x64, and am using a Radeon 6800HD series graphics card.

Tried deleting .ini, as well as this fix suggested here (http://forums.nexusm...on-fast-travel/) and neither has solved the problem.

Mods installed inclued the Texture pack (01, 02 and 03), Midas Magic, Moonpath to Elsweyr, and Hunting in Skyrim. Got them all off the workshop, because I didn't feel like going through the hassle of Nexus.

I bet it's the load order of your mods. Download a thing called BOSS; it has a database of mods and changes your load order. Even if this isn't the problem this time, if you load lots of mods you will be glad you got BOSS.

Also, wanted to note that when I use the coc command (IE coc Whiterun) the game doesn't crash.

Sounds like an issue with autosave. This happens to many people in pretty much every Bethesda game. I suggest disabling all the autosaves and make liberal use of quicksave before fast-traveling, loading an area, etc as an alternative if you need it.

Since you are using a few mods, make sure to use BOSS to automatically sort the load order of your mods as well. This can help reduce some conflicts your mods may have. Not all mods that exist are sorted by BOSS (at least not yet, though it knows where to put many thousands of them), so you may have to manually sort some depending on where each mod says it should be placed in its documentation.

I would also suggest to use the Unofficial Skyrim Patch (USKP), as well as the unofficial patches for each official mod you have. The unofficial patches fix so much stuff that I personally feel exposed while playing without them. You can find each one in Arthmoor's Workshop page. Do know that since the USKP changes so much, that you should not try to continue a save game after removing USKP or the other unofficial patches. If you no longer want to use it, you should remove it and use a save from before USKP (or other) was added.

I am not familiar with any of the mods you have, so if after BOSS and disabling autosave you still get crashes, try disabling all your mods and fast traveling a bunch of times to see if it crashes. Then enable one at a time and repeat the traveling bit to see if it is any one mod causing the crashes.

If you find a mod in particular that is causing the crash, it could be either a mod that is out-of-date, or a mod that has dirty edits. Neither the Workshop nor Nexus are immune to either. If you are feeling adventurous and are not afraid of advanced stuff (since you could very well break a mod by accident), you can try to clean each mod[www.creationkit.com]. Just make sure to make backups of the mods just in case. There is a ton of information on dirty mods and cleaning them on the cleaning page if you want to know more details on the what, why and how. If cleaning the mod does not work, then there is probably no helping the mod short of an update from the author.

Do those in order. Hopefully it is just needing BOSS or a disable autosave. Only do the cleaning if you are confident enough with it, otherwise just disable/remove a mod that is causing crashes. I am certain I am missing things, so if nothing works in this list, there is probably other things that can be done.

Well, I disabled auto saves, and it stopped maybe half of the CTD's. So I got BOSS and USKP and.... my crashes in the load screen.Started a new game annnnnd my saves weren't showing up in the game. Did the whole thing to make a new save file, and they show up.But, my save is still crashing. New saves seem fine, but I'm probably just going to stop playing if I have to make a new character.

It''s a ♥♥♥♥♥ when a save file gets corrupted. Before I install any new mod now I make 2 or 3 saves right after one another, so if it crashes and kills the save I have a fallback. I feel for you man; I did a quick search and this youtube guy says to use a windows resore point to get the file back http://www.youtube.com/watch?v=F0103EwIKW4

It''s a ♥♥♥♥♥ when a save file gets corrupted. Before I install any new mod now I make 2 or 3 saves right after one another, so if it crashes and kills the save I have a fallback. I feel for you man; I did a quick search and this youtube guy says to use a windows resore point to get the file back http://www.youtube.com/watch?v=F0103EwIKW4

That's what's bugging me about this. I had a quick save, a regular save at that same point, then a save from a little while back. And none of them are working.

Your post gave me some hope though, and I gave it a shot. Now the saves work... As long as the USKP mod is disabled. Tried to move it around the load order, but it didn't change anything. Disabled all my other mods BUT the USKP, didn't work. So the problem is USKP.

The game's also still crashing, with or without USKP. Decided to try it out on a new character, used console commands to go to Windhelm Stables, and the game crashed when I walked into windhelm.

USKP should normally be directly after the ESM files in the load order. Using BOSS will put it in the correct spot.

Unfortunately, adding and removing mods on a whim is usually a bad idea with Skyrim, unless you completely start over. A save game might build a dependency on a mod, so when the mod gets removed, any number of bad things could happen--up to, and including, crashes. About the only thing that can probably be done is give tips for the future:

If adding a mod to an existing save:

Load up the game and make a new save before adding the mod, so there is something to go back to in case it is later removed.

If there is a compatibility list or a required-mod list for the mod, make sure to take heed.

Install the mod

Use BOSS each time a mod is added to put it in the right spot. Or manually move it with the Skyrim launcher if BOSS does not recognize it according to where the mod author says it should approximately go.

Make sure to test/explore the mod in game to be sure it is working properly before resuming the game.

Uninstall the mod and go back to the previous save if the mod is no longer desired.

If removing a mod from an existing save:

Load up the game and make a new save before removing the mod, so there is something to go back to in case the removal breaks the save game.

Look up the documentation for the mod, and see if there are any special uninstallation steps to remove the mod more cleanly. Depending on the mod, it may ask the user to run some console commands to stop some scripts, make sure an area is unloaded or reset in the save game, dismiss followers added by the mod, remove items added by the mod from the character's inventory, or any number of things. Doing all those things the author asks to do before removal probably will not completely clean the save file, but it will be much better off than not.

Make a new save after following uninstalling steps and uninstalling.

Do know that some mods exist that cannot simply be removed from a save game and require a new game. Any overhaul mod is probably in that category.

Make a new save game every hour or so, or at least at the end of each session. So if a save game suddenly dies for whatever reason, it is possible to go back to a previous save that is hopefully not too old.

Two mods cannot change the same thing. The last mod in the load order overrides any other mod that changes something.

A quick example: someone wants to add two mods that change a particular helmet. One mod simply changes it from a light helm to a heavy helm, while the other only changes its stats. Only the last mod in the load order affects the helmet--not both.

A save game or mod that tries to load an object that is deleted (such as a bad mod deleting a vanilla object) or cannot accessed (such as a save game trying to load something from a mod that was removed from the load order, or a mod loaded before, or without, its dependencies) will, more often than not, cause the game to crash.

The thing is, UKSP is directly causing the crashes. No clue WHY, but it is. Is there something about the mod that makes previous saves unplayable?Thanks for all the advice though, and thanks for the heads up about the load order thing. I've never had it be an issue, but its good to know for the future.

Also, still having the original issue, which is something I care about more. I can just get rid of UKSP if it means playing my current save.

USKP should not be causing crashes if loaded first after the ESMs, since mods that come after should take priority for changing the same things. Though if the save game is crashing with USKP and is working fine without, then definitely play without it. No sense in losing progress if there is no need to. Like I have said, adding or removing mods in the middle of a game can cause all sorts of issues, so even adding something that is supposed to fix a ton of issues can cause issues.