Skyrim Unplayable from the get-go

[AlexanderAmnell]

I purchased Skyrim yesterday, and had no problem downloading it or anything. I also downloaded the creation kit and the high res texture pack. Then I started trying to play it. I got to the load screen alright, started a new game and began watching the opening scene. It looked nice, no lagging or any problems indicative that it might be about to crash. Then, as the cart stops and the prisoners begin to get out suddenly I am looking at my desktop background with no warning whatsoever. So I load it up again and it crashes again at the exact same place. After doing this multiple times I notice that the "Now autosaving" appears at the top of the screen just as it crashes, so I turn off autosaves and, oddly the scene continues. I get to make my character and play through the tutorial, however now every time I try to wait/quicksave/manual save the game it instantly crashes to desktop. I've looked online and most topics seem to blame mods for the problem, so I removed the high res texture pack but I get the same problem. Does anyone else have this problem? How could anyone release a game with no method of return that is so heavily bugged that you are incapable of saving? What is wrong with it!?

 

My computer specs are:

 

Intel Core I7 processor

Nvidia GEFORCE GTX graphics card 2gb

8gb RAM

Windows 7 OS

more than 800gb free memory on computer

[Enerzeal]

Are you running as admin? Sounds like it hates the idea of writing files into your C drive.

[nosisab]

What Enerzeal told, and this should be a warning to people still to install Steam itself.

 

Avoid installing it in the default C:\Program Files... it allows choosing another location, even in another partition or disk but even if installing on C: do it on a user created folder or even at the partition root, never in that non blessed directory... ALL your games will thanks you dearly.

 

I don't know how Steam reacts to attempts to change the location once it is installed so I can't recommend changing it. Still, at this point is highly advisable reducing the UAC actuation... maybe even disabling it totally.

 

As may have become clear by now, although UAC "should" be a feature to improve the system security it backfires hardly, starting for forcing things like running applications as administrator... well, it's MS notion of security, it says everything.