Suddenly my game started crashing every time on switching to 3rd person view or even moving, becoming unplayable.
Issue is not in mods, earlier saves with same mods show no problem, and bad save with all mods disabled still crashes.
I got extremely disappointed after this happened, lost days of time...
I can upload corrupted save file if you interesting in checking what is problem and solve in future patch...
But I'm not going to buy any of youe games in future, so hard that has disappointed me!!!

Corrupted saves happen for every game for a variety of reasons. This is not game specific. Heck, I've had Gameboy games with corrupted saves. Don't point fingers, it doesn't do any good.

Who should point his finger at! He paid his money and he's entitled to his opinion. I look at these boards almost every day and shake my head at the latest complaints of this POS not working properly for a multitude of reasons WITH NO REAL EXPLANATION OF WHAT IS WRONG OR A BULLETPROOF WAY TO FIX IT! What a lame ass response on your part. This game is full of problems, like it or not. I have NEVER seen a game with so many problems that were so bad that people had to start over several times or had issues with it running very differently compared to the first run-thru, or not working properly to excessive buggy quests, crap textures, HD textures that not everyone can use, Beth's patches that actually make things worse or not work at all. I will say that the first mods, imo, were to blame for a lot of ctds and save corruption due to being made with incompatible tools culminating in corrupt saves, constant ctds, in-game anomalies and who knows what else. To the people who say they have no problems whatsoever, good for you, but don't get on your highhorse and start saying that people who are having obvious troubles are a victim of themselves and their [censored] XP or Vista OS or due to 32 bit instead of 64.

I do know 1 thing: this game is a mess and in one way or another, sooner or later it will screw up for you. Beth rolled the dice at putting out a product that was half-baked, not intended for a PC, poorly coded, poorly tested, and when they got your money, they laugh all the way to the you-know-what. And the chances of you getting your money back, or even a portion thereof, HAHAHA. If there ever was a game that a class action suit should launch for in order to create a law where consumers could get some of their money back for a bad product, this should be right up there. Classic bait and switch; you were promised quite a game and got shafted with a product that has way more problems than it should ever have. BTW, corrupt saves, constant CTDs, bugged quests to no end, quests that bug just because you picked an item up or had it in your inventory or didn't " play the game in a linear manner " (show me that in the instructions!) is somehow normal for every game is BS plain and simple. If you want to sit there and tell me that my computer or my AV or some other aspect of my PC is to blame for mine and EVERYONE elses problems of all these different and varied types, then I guess PC gaming has finally met it's end. If this passes for a game that runs properly, we're all screwed.

So feel free to point your finger at whomever you like; you paid for the product and you earned the right to express to others about your experiences.
" who put out that game that had so many problems " (points) ---------> Bethesda like it or not.

I've been building PCs since the early '90s and I can tell you without a doubt that AV is your problem. Only grannies use AV. In the old days we called AV progs like Norton and Mcafee viruses in themselves because of the horrible way they dominate your system. My advice? If you feel you need AV go freeware and open source, and don't use real time protection - EVER. Follow simple security etiquette and do the occasional scan with a good, lightweight, open source, AV app and you'll be fine... provided you're not a complete idiot.

http://www.gamesas.com/user/763175-bigcountry/, I agree completely with you


More detail about my crash has been revealed: it happens every time when view changes to 3rd person (zooming off, using horse/alchemy table etc)
Re-installing vanilla game doesn't help, old saves still work normally.

Here we go again...

Anyway, what you can learn from that is to use multiple saves (esp. in Bethesda games).

Is the error happening on older auto-saves, too?
Which version is your game on?
How many hours have you played on that save?
How big is it (in MB)?

Among the things you did mention that i agree with..... i highlighted 2 things that are definitely note worthy in that your opinion is your own, but facts state otherwise on what should be accepted.

Here let me explain a few things first.

While the current DLC HD pack is a bit of a joke in terms of how it hard internal errors (normal maps in place what the real name should be, naming errors...etc) the HD pack was intended for a specific group of people that are more than capable of running it. Most definitely not everyone should be able to, that would be absurd.

Additionally, the current trend is this:

If your running windows xp/vista/7/8 32bit, your essentially limited to specifically vanilla mode, very little to no texture mods to speak of, and very few other mods as well. The game rides the limits of 32bit therefore any form of expansion or detail/quality that also increases the requirements that exceed what running under a windows 32bit environment can provide, obviously creates a problem. This is no more the fault of the game or windows, as it is the manufacturer of the computer that installed it unless of course it never supported 64bit or 64bit wasn't available at the time. OR in the case that the user strictly specified the installation of 32bit only. At which point the problem vs solution is quite obvious. Either stick to your vanilla install and attempt to keep the CTDs to a bare minimum working with what you have, OR make the upgrade to 64bit to remove almost guaranteed, 99% of your issues in a single leap. Coming with that several clear advantages that can not be argued against other then to make opinions about it.

Surfice it to say, when i first got the game i was completely unhappy due to the lack of the LAA function making those with windows x64 (most commonly) CTD more frequently then would be acceptable (although shouldn't be acceptable at any level personally). This was with a vanilla install making it impossible to resolve short of enabling the LAA flag. Those with 32bit continued to play unhindered however due to the nature of how the memory address system worked, only they were frequently experiencing even today, problems with CTDs when additional mods are installed... where as those with x64 and the LAA flag.... did not.

Even today with skyrim packing in at about 3.2-3.6gb total memory addressed... i have no CTDs... meanwhile the 32bit user would never see this number of mods in use.. it's not possible.

Yes, I am saving every 2 hours now... all 3 autosaves were corrupted(they were close in time), 62h save was ok.
Corrupted saves were 11Mb, playtime about 80+ hours. Game version is 1.4.21.0

it's rare.. but the autosaves/quicksaves have only fallen apart on me twice in the entire 225 hour range I've played.

This is likely due to a hardrive error issue i was having at the time.... not likely the game.

Memory errors or issues can contribute to this as well.

Otherwise have never had a problem outside of those hardware issues.

you really should be saving more frequently... NEVER EVER EVER trust a quicksave/autosave.

Hm, unfortunately corrupted saves are known to happen.
A pity that all your autosaves are affected.
Auto-/Quicksave did cause problems in the older games for some people, too (never for me, though).

As to what is the reason, that's hard to say. 11 MB is not very big yet.
If you are able to pull this off without the game crashing first, try this:
Fast travel away from wherever you are, enter an interior cell, with as few npcs as possible (e.g. player home) and rest/wait for 31 days (I think that's the time for cell reset in Skyrim).
If you are lucky, it might get fixed by that. Optimally you would try to do this without any mods active.
Then save an re-enable your mods.

This was the method to create a clean save in Oblivion and Fallout3/NV.
It was quite useful in that games, but I cannot guarantee that it helps you.

I have seen less posts about corrupted saves with this game, but it can still happen. Not sure if it was the delay in the CK that delayed the corrupted save reports or not. However it does seem that more folks are reporting issues with their saves when mods are involved.

Since up until about a week ago, mods were being made with editors for other games and the new scripting in this game I am surprised there have not been more reports of corrupted saves with mods.

The best save advice I can give is to turn off the Autosave features, especially on Travel and Cell Load. Making a save when the cell is rendering is the worst time to make save. I always make a save before I enter a new cell or go to a different place. I only make in cell saves when I have been in the cell for a minute or so.

I still don't overwrite saves more than 5 to 10 times in most cases, after that, I make a new slot. I also keep a save from before I start a quest, maybe another one during it after a major stage completion, along with any other saves I might be making along the way.

And, most importantly, make a forked save before installing or testing any new mod and getting the load order or the mod mix right.

Waiting 30 days didnt help me, so I have to re-do from 62 hour save now...
As many of you have said, I'll save a lot
Anyway, thanks for advices everyone ^^

What complete and utter nonsense to generalise like that. Sure Norton and Mcaffe are bloated rubbish, but plenty of other good anti virus software out there that run perfectly fine.

I use Eset NOD32, very minimal cpu and memory hit, constantly running realtime, makes no difference to performance of any of my software and I use this PC for intensive DAW use with a wireless usb stick. My DPC latency stays below 30.