theSLCberg

0.14.1 is now up and apparently fixed the prob

same here. crash on startup...

I see. You may be running out of ram or something then. Maybe this ini mod will help. Also, to anyone using Skyrim4gb, as of today it is no longer needed. Update 1.3.10 just released and it has the LAA flag checked on its own. Finally, YAY!!!

habaar, glad to see that you got it to work. That is funny that you were able to play at all with both Proudspire mods at the same time. Just remember, detecting problems with multiple mods installed can be tricky. I don't know why Proudspire didn't cause its crash on save problems until after several hours of gameplay, but it sounds like that is the case for most people. I was able to play with that mod for about 2 hours, then took a carriage from Solitude to Windhelm and could no longer save. After I played around with it for a while it seemed that I could do almost anything and still save except for riding in carriage, like the carriage ride triggered the issue for me... Very weird. My suspicion regarding what's causing that mod to have problems is that it has something to do with the form id's. If you read the description, the modder says something about recycling form id's from items Bethesda had removed. I don't know for sure, and I may be completely wrong, but that does not sound like a good idea. I know he claims, "As a result, unexpected results MAY occur if you have been doing a lot of terrible "markfordelete" behaviour via the console," but I'm pretty sure that you do not need to have marked anything for delete via console to run into problems like this (I know didn't). Never before have I heard of a modder using recycled codes like this. Maybe it has something to do with the fact that the real dev kit (creation kit) has not been released yet, so this mod was made using other tools that don't work as well. Either way, I agree that it is a shame this mod doesn't work. It was a great addition to the house. Maybe in January when the creation kit comes out he'll be able to fix the problem. @ coldarra: The crash you're experiencing sounds different, like maybe you are overworking your hardware? What graphics card do you have? And are you using the Skyrim4gb Loader (recommended if you have a 64-bit OS and more than 2 gigs of ram)? You may also want to double-check the comments section on each of the texture mods you're using to see if anybody else has had the same problems

Thats very weird. The thing is, something is causing this and its not Bethesda. It must be one of the other mods you've installed. First thing you should do is re update the game to 1.3. Secondly, I would try disabling any mods you have, launching it with only the Skyrim.esm checked. Then make sure you can save. If it still doesn't work then there is something else wrong entirely and you may want to try reinstalling it again. If it does work, then re-enable each mod one at a time, checking to see if you can still save after each one is enabled. That way you'll be able to figure out which one(s) is/are causing the problem. The other Proudspire mod does the same basic thing, but its a little different.

Hmmm. If you disabled the mod correctly then it should be able to save right away. Did you go to data files and uncheck the box next to the .esp for that mod? Or are you using the Nexus Mod Manager? If so, it should do all the work for you when you deactivate the mod. If you did disable it correctly but you still cannot save, then there is another problem... :\ To correctly disable it, launch the game via Steam, not the Skryim4gb Loader (if you have it), so that you get the menu with "PLAY, OPTIONS, DATA FILES, TECH SUPPORT, EXIT" and select "DATA FILES." Uncheck the box next to Proudspire.esp and click okay, then "EXIT." Start the game however you normally would and see if you can save. One of the comments on the mod page states that if you turn off all the Autosave settings, then you should be able to enter the house and it will supposedly let you manually save again for approximately 24 in-game hours: If that works as hanli427 describes, you should be able to turn off autosave, enter the house, remove any items you wish to keep from areas added by the mod (the smithy room, the new housecarl room, new chests, weapons rack, weapon mounts, etc. Item in areas that the mod did not change should be ok). Then leave the house and manually save (again this is assuming that what hanli427 said works). Then exit the game, uninstall the mod, reload the previous save, and you should be good. If you cannot get it to work like Hanli427 said, then I'm afraid you will just have to live without those items :(. But at least you'll be able to play the game without having to redo a bunch of quests :)

I bet that mod has everything to do with your CTDs. Disable it and see if you can save. A lot of people have been experiencing the same problem after a few gaming hours with that mod installed. It never happens right away, so you wouldn't know right away that its causing it, but it is. I was able to play just fine for a few hours. It wasn't until after I used a carriage to travel with that mod installed that it started crashing for me. I removed the mod and my game is fine. You won't even have to start a new character. Just uncheck that mod in your load order.. I really liked that mod too. It was the best Proudspire mod out there, but unfortunately it breaks the ability to save...

You wouldn't happen to be using this Proudspire mod, would you? I just started experiencing crash on saves today after installing that mod yesterday. After trying a bunch of other things to no avail, I finally tried uninstalling that mod and everything works fine again, no more ctd on save. If not, try uninstalling any other esp mods you may have installed.