CTD/hang at launch

[mummeswsh]

Hi, can't find any posts with matching symptoms so here goes -

 

The game crashes or hangs after the bethesda logo (so I don't "do" anything after clicking play in the launcher). It's a fresh install on a clean new machine (built yesterday, installed steam this morning).

 

I discovered how to get logs after a while, and all that ever comes out apart from some lines of init is five lines like:

 

[03/01/2019 - 10:45:05PM] Cannot open store for class "DLC1TestPhilAtronach", missing file?

Is there something I should be installing... somehow? Steam says I don't have any DLC and I certainly didn't edit anything to make it happen - it is literally just "install" in steam and then click Play, and, boom.

Any helpful clues much appreciated...

[gromulos]

Forget papyrus that's not going to help you in THIS instance

 

Your problem is you're either missing a master file for one of your mods or a patch file for one of your mods

 

An instant CTD at startup or after the Bethesda logo is always caused by a missing file

 

Try my guide and follow it STEP BY STEP and use Appendix 1 if you need to, below

 

https://forums.nexusmods.com/index.php?/topic/2235394-beginners-guide-to-modding/

 

Make sure to use the files in the box i made using the *****************

[mummeswsh]

Forget papyrus that's not going to help you in THIS instance

 

Your problem is you're either missing a master file for one of your mods or a patch file for one of your mods

 

An instant CTD at startup or after the Bethesda logo is always caused by a missing file

 

Try my guide and follow it STEP BY STEP and use Appendix 1 if you need to, below

 

https://forums.nexusmods.com/index.php?/topic/2235394-beginners-guide-to-modding/

 

Make sure to use the files in the box i made using the *****************

Thanks but - even if I have zero mods? If I had a bunch of mods I'd be looking at removing them but as it is, that log line is about the only clue I can see

[gromulos]

Run Wrye and see if it pops up an error

 

If not verify your files trough steam, your DLC01 may have been corrupted when downloaded

 

EDIT

 

That log line is specifically telling you there is a problem with DLC01, hence why i suggested verifying

Edited March 1, 2019 by gromulos

[mummeswsh]

Run Wrye and see if it pops up an error

 

If not verify your files trough steam, your DLC01 may have been corrupted when downloaded

Thanks - working on the wrye part. (Verify did say everything was good the first 3 times I ran it though :-/) Did stick that cmd on the start menu though, I can see that coming in handy. thanks again, appreciate it.

[mummeswsh]

I've run the utilities (Loot, wrye, ssedit) and can't see anything that pops out though I confess that might be my lack of understanding of what they're trying to say. Also validated the data files again, uninstalled and did a fresh clean install (still with no cloud save and verified that the saves aren't somehow interfering, and the saves never appeared in my folder), tried again, validated again. Still CTD after logo. No hanging though, dunno when that stopped happening but I haven't had to kill anything for a while. I deleted a couple data files just for the heck of it and did another verify, nothing changed. (and yes, still zero mods installed - there is nothing but a fresh, clean SSE.)

[gromulos]

ok let me get ahold of a friend of mine sine my expertise is not going to be able to help, i know his will

 

HEY DUBIOUS!

[QuagaarWarrior]

If you dont have any mods then you shouldn't need to run anything like LOOT or xEdit.

I would just uninstall through steam, then go to steam/steamapps/common and delete the skyrim special edition folder.

Go to my documents/my games and delete the skyrim special edition folder.

Restart your computer and reinstall skyrim.

I assume you are launching skyrim through steam?

[dubiousintent]

While I'm currently focused on "Fallout New Vegas", many problems that occur before you get to load a saved game are related to Windows and Bethesda games in general. So the appropriate sections from the Wiki articles for FNV can be applicable to other games. You will need to substitute the appropriate game specific versions of mod and tool names and apply other common sense changes, but they should be pretty obvious.

 

The following entries in the wiki 'Fallout NV Mod Conflict Troubleshooting' guide specifically address known Win10 problems:
* 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)'
* 'Issue: Incomplete save game load' (NVSR related)
* 'Issue: Vanilla game Hangs on startup'; specifically "Cause-1" regarding DirectX9 drivers.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (NVSR related)
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed (or not)'. In particular "Cause-4" regarding video card settings. The latest video drivers may not be the best suited to an older game like FNV. All vendors drop testing of old games at some point. Backwards compatibility is never guaranteed, much less "optimization".
Also, "Cause-7" regarding "Superfetch" and "File search indexing". Windows updates will often reset these back on.
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* 'Issue: ENB Support for Windows versions later than Win7'
* 'Issue: Problems using ENB/SweetFx on Windows 10'

Please see the 'Checklist Item #4' entry and the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article. Also, please see the wiki "Missing Masters" article.

* Be aware that one error may mask a number of other errors, which will not appear until those masking them have been resolved. Building a stable game consists of resolving each problem individually until none remain, and then realizing that every change you make thereafter (including updates to mods already installed) run the risk of introducing new problems. Be prepared to revert to a previous save if you do so.

* Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" or "C:\Program Files(x86)" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

-Dubious-

[mummeswsh]

If you dont have any mods then you shouldn't need to run anything like LOOT or xEdit.

I would just uninstall through steam, then go to steam/steamapps/common and delete the skyrim special edition folder.

Go to my documents/my games and delete the skyrim special edition folder.

Restart your computer and reinstall skyrim.

I assume you are launching skyrim through steam?

Thanks - Yeah, I've cycled through install-uninstall several times by now (all through steam and launching through steam), I'd wager substantial money on corrupt files not being the issue. Not really suspecting corrupt saves either, as the crash comes before the continue screen. Which I guess means it's probably related to hardware and drivers and that sort of crap. Like I said, the machine is brand new and modestly high-end so it's thinkable that not very many would trigger some some esoteric bug.

 

I got a cheap SKLE key and installed that just for the heck of it - runs just fine... we'll see what I end up doing with this.