FormerHuman

Well clearly it's a massive screw up somewhere, and considering it seems that a sizeable number of users cannot play the game after this update, they'll have to fix it really fast to minimise the effect of this. A lot of people have been getting really, really into this game over the last week - the sheer volume of increasing nerd rage will burn the world to a crisp.

If you mean what I think, that you'll just use the old exe, that might work, but I'm not sure what safeguards Steam has in place to over-write it. As for re-applying the LA mod on the NEW exe, that will probably just break it even more.

From what I can make out from Google's attempt at translating the page, there is a similar error that some people are having that came up with Mass Effect some months ago? As far as I'm aware, the actual error code that comes up is only when the executable is modified to fix the 'large address' problem, after it has been updated by Steam (the hotfix being there to prevent alterations from working). Most people are not getting the error code but simply getting a lot of CTD.

I made a thread about this here: http://www.thenexusforums.com/index.php?/topic/470063-steam-updated-exe-now-game-crashes-over-and-over-again/

It would appear that the update is from Steam and that's where the problem is coming from, apparently in order to prevent modified EXE's from working. http://forums.steampowered.com/forums/showthread.php?t=2244649 Check the 'modified' date on the TESV.exe file, if it's got today's date, you know you've been Tango'd.

Check your TESV.exe file - if it's been modified today, then it's because of the new patch that (apparently) is implented by Steam rather than Bethesda, to make it so that only unmodified EXE's will work. The flipside of that is that it's broken the game for 90% of people. Hopefully they'll fix it quickly. http://forums.steampowered.com/forums/showthread.php?t=2244649

That is the most awesomest piece of knowledge that ever has been shared in the faces of mankind! Thanks man, thanks. I concur - I did not know this! Seeing as V-sync of death has the ever reliable effect of slowing down mouse-movement (and possibly causing a bizarre CTD as well), i've been sticking with the gamepad, which is certainly more comfortable (feet up!)

The update only came today it seems so your issues are probably unrelated, which is unfortunate as it would probably help you to work out what's wrong with it. The issues relating to the update all seem to be during the game. A lot of people altered the exe (myself included) to allow the game to support more than 2gb RAM, which popular theory is what the update is restricting, which might be resulting in all the crashes, however I tried deleting the new TESV.exe file and getting steam to verify the file cache and go on to redownload the file from fresh, with no better results, so there's something in this update that's really screwing things up for a lot of people. I've already had a good 43 hours of gameplay on my character now in just over a week (loving this game) with occasional crashes of a similar nature, but nothing nearly as frequent as this, and I've read some reportsthat the game becomes more unstable as you go along, perhaps in relation to the ever increasing size of the save game file.

I was playing Skyrim happy as Larry with my level 21 character, closed the game to do some email checking and when I went back to it, I noticed Steam was updating it. When it finished and I reloaded the game, it proceeded to crash to desktop. Many, many times. Sometimes during loading sections (which it hadn't done to me so far). Steam forums seem to be saying a lot of this as well. Are people here having this problem too? Normally the auto-update feature on Steam is a blessing, but right now it's broken the game and I can't undo it.

I have a set up with a 22" LCD and a 32" TV linked up to the same Nvidia card, running in dual screen. I just set the primary monitor to the TV and so all games default to that. Picking the right resolution in a lot of slightly older games is a real pain, but most of the time it's workable. I would suggest you just set the other screen to be your primary, and change it back again afterwards, that should work.

That's... a really lame idea.