Widescreen Gaming Forum

AMDR:

try this first, I jus thad MY game not start(!) and thsi fixed it: in the Skyrim data folder rename the SKSE folder to soemthing else, like tempSKSE , and then try to run the game. Worked for me.

If not,

I can only outline for you what I do when I have a CTD and the game will not start, maybe it will help you:

1) make sure Skyrim Script Extender is version 1.42 or 1.43 since your TESV.exe is 1.31
2) If using Script Dragon make sure it is between 1.3 1 and 1.415
3) download and run the nexus mod manager 0.14.1 and temporarily disable ALL your modes to see if the problem goes away. If it does then add them in a few at a time to find the culprit.

Good luck!

Thanks tonycubed, sadly non of those solutions work.
The patch does seem to want to do something because I it does this everytime

+ Searching for RUNNING Skyrim Process...
+ Skyrim process found...
+ Process opened successfully!
# Image: e:steamsteamappscommonskyrimTESV.exe
# Version: 1.3.10.0 - Support Detected!
+ Executing ASM injection...
+ Allocating additional memory to process...
+ Generating Function 1 (Wrote 64 Bytes)...
+ Generating Function 2 (Wrote 10 Bytes)...
+ Patching Mouse Positioning (Wrote 6 Bytes)...
+ Patching Mouse Handler (Wrote 5 Bytes)...
+ Patching Mouse Sensitivity (Wrote 17 Bytes)...
+ Patching Overscaling (Wrote 17 Bytes)...
+ Patching Model Scaling Values (Wrote 153 Bytes)...
+ Patching completed, Leave running until you exit Skyrim.
+ Skyrim thread exited... we're done!

But the game itself just crashes, even before showing the Bethesda logo

That's normal, Amdr.

Looks like that's running fine.

Trust me, it's Skyrim, itself. For some wierd reason, everybody gets on the bandwagon of Skyrim failing to load/CTD eventually. I'm relieved and happy to say that the beta patch of Skyrim runs rock-solid, in my experience. I wasn't able to play at all, pre-beta.

We'll have to wait on Hayden to come out of hybernation once there's a release-grade patch of Skyrim, to get the menus right...

Just FYi, without activating the Hayden fix Skyrim will just run fine. :)

Just FYi, without activating the Hayden fix Skyrim will just run fine. :)

Heh, if was was just fine we wouldn't need HaYDen's fix, but we know what you mean.

Then look to any MODs that -might- be messing with screens directly, like a Map mod. Or memory getting pushed over a limit somewhere. I have seen a case where the 2nd stick of mem' was no good.

Overclocking on unstable system, turn it down a notch or two.

Both Vid cards running 16x or 8x PCIe and not one of each.. any other game troubles?

..details, details.

_________________
- AMD 965 @3.8 - Gigabyte 790fx ud5 - AMD 7970 Ghz - OCZ Reaper 4GB - OCZ Vetex - Eyefinity 3x Asus vw266h - Samsung t260hd + 226ux - (soundcard) - Sony 5.1 ~700w - PC P&C 750w - Corsair K60 -

Kind of glad HaYDeN hasn't attempted to work a fix for the beta patches yet... they keep rolling them, all the modders can't keep up.

Absolutely, it'd have been a pain to rebuild that patcher for each one, just more of looking forward to having such a patcher available for when the dust settles that's all.

_________________
6700K, 2x1080s, 32GB DDR4 etc etc.

It makes sense to wait for the release, but hopefully Hayden has not gotten sick of making them. His user stats shows he has been away for over two weeks. I wish I could program so I could help with this...

Take a look at this.

http://www.ign.com/blogs/bethesda_softworks/2008/01/24/inside-the-vault-erik-deitrick

The email might be fake, but I took time to email him, asking for his help...

They just released the final version. Hayden, if you are too busy could we perhaps beg off you the notes on what settings need to be hunted , and any other hints would help another programmer to duplicate your great work? Maybe the programmer just contacted can help. I have not coded since using assembly language on a 6502 based system, the commodore 64. Made a copy of PAC-man from scratch while skipping classes in high school. What version of c would be used for skyrim?