[SOLVED!] Consistent SSE Launch Failures

[Vyxenne]

My SSE fails to launch most of the time. It takes me 2-8 tries to get it to launch. Tonight, I finally went to the Event Viewer and checked the error logs. Here is one example- the list of this same or similar errors launching SSE is pages and pages long. I am launching via skse64_loader.exe.

 

Although the faulting application in every case is SkyrimSE.exe, sometimes the error message says the faulting module is unknown:

 

Faulting application name: SkyrimSE.exe, version: 1.0.0.0, time stamp: 0x5dcae282
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ffe2fff045f
Faulting process id: 0xbac
Faulting application start time: 0x01d6cb8fab22eef9
Faulting application path: G:\Games\Steam\SteamApps\common\Skyrim Special Edition\SkyrimSE.exe
Faulting module path: unknown
Report Id: f8aaeef2-e9a2-4ec2-9b57-1f9147b20ff5
Faulting package full name:
Faulting package-relative application ID:

 

and other times it says the faulting module is KERNELBASE.dll.

 

Faulting application name: SkyrimSE.exe, version: 1.0.0.0, time stamp: 0x5dcae282
Faulting module name: KERNELBASE.dll, version: 10.0.19041.572, time stamp: 0x1183946c
Exception code: 0xc0020001
Fault offset: 0x0000000000023e49
Faulting process id: 0x2c4c
Faulting application start time: 0x01d6caecc7eedf3a
Faulting application path: G:\Games\Steam\SteamApps\common\Skyrim Special Edition\SkyrimSE.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: ea91001b-ddb2-42a7-b2d5-7b72dff6b016
Faulting package full name:
Faulting package-relative application ID:

 

Does anyone have a clue how I can even begin to find the cause of these persistent errors?

 

Thanks-

[StrangeBread]

Update to the latest version of Win10. Kernelbase.dll is the main MS api executable responsible for hooking .dll scripts to sys ram. If it's anything like what I was experiencing last night, a CPU heavy mod (betting it's CBPC) is causing a runtime error in the module, updating windows and the .NET framework fixes the issue.

[Fotogen]

Reset Skyrim ini files.

[phillout]

Install .Net script framework, its crash log gives you more insights into the real cause of crashes. It can actually point you to a broken asset or NPC.

[anjenthedog]

I'm curious what your "symptoms" are. Lately (past ~2 months),  I've experienced CTDs on game load with the following characteristics (and it might resemble yours idk...)

 

1st attempt: game begins loading, goes to black screen (either crashes to desktop or forces task manager closure ~50:50 chance)

 

2nd attempt: (immediately following successful termination of the skyrim kernel)   game loads, screen shows scene, game hiccups, begins whichever initializations need to be done (for me it's the clock mod and some random SL stuff I don't keep track of), then the game CTDs (sometimes although rarely forces manual termination but usually crashes to desktop after a few screen flickers)

 

3rd attempt: game loads, almost gets there, then dies

 

4th attempt: game loads.

 

This is a pretty repeatable set of symptoms too... 1 then 2  then 3 then 4... sometimes it only take 3... And it usually end with loading the game. Sometimes I have to go back one save, but usually it eventually loads... weird. Something is being overloaded.

 

It *might be some sort of race condition during game initialization or during parsing of the save... or maybe the script engine chokes while processing the data, idk. 

 

PS> this isn't with every single load. But a sizeable proportion, maybe 25% of the time

 

PPS> IFF the game gets to the point where a scene loads (landscape or interior, you, screen stuff loading onto the viewport, etc), I've noticed with some reliability that there's an icon that appears at the time the program seizes up. It's a small disk with some sort of sun or saw blade pattern (wavy flame sort of() around its rim. Shows up along the lower boundary where you'd see stats or the compass (if you use the compass on the low part of the screen) I keep trying to get a snapshot but it has eluded me so far or I'd provide an image. I suspect that whatever mod provides that graphic is a player in the fault but don't know for sure.

 

[ChaosTheorist]

I'm pretty sure this is on her new machine, so out-of-date Win10 stuff is probably not an issue.

 

Unfortunately, Windows Event Log info isn't going to help much; there's just not enough granularity in the Skyrim modules to narrow the focus. As phillout says, the best pointers are going to come from the '.NET Script Framework' mod. On rare occasions, you luck out and the stack info has a string with a specific mesh/texture/whatever name in it. More often, it's more the 'shape' of the info on the stack that suggests where to look for the problem.

[Vyxenne]

6 hours ago, phillout said:

Install .Net script framework, its crash log gives you more insights into the real cause of crashes. It can actually point you to a broken asset or NPC.

Thanks, I have it. I just can't find the logs, they're well hidden.

[Vyxenne]

2 hours ago, anjenthedog said:

I'm curious what your "symptoms" are.

Here is my launch (or not) process and resulting indications:

1. I make sure Steam is running
2. I pound a desktop shortcut to "G:\Games\Steam\SteamApps\common\Skyrim Special Edition\skse64_loader.exe"
3. The usual, expected, 1/6-screen, blank SKSE64 window opens briefly at the upper left of my display and the SSE icon displays briefly on the task bar
4. Both manifestations in #3 above disappear after 3-4 seconds
5. Drive access activity occurs sporadically, with no discernible pattern or predictable duration
6. Either the game launches successfully after 13-17 seconds OR nothing else whatsoever happens- no attempt to launch, no visible CTD, nothing

[Vyxenne]

17 hours ago, StrangeBread said:

Update to the latest version of Win10. [...] updating windows and the .NET framework fixes the issue

In the past, I routinely delayed sweeping updates to my Windows 7 machine until I had spent a few minutes reading the online "buzz" about it to see if it was a bugfest or a stable release (or a stealth installation of Windows 10.) This practice saved my butt several times and also taught me that Microsoft will gladly push bugware and even unwanted Windows versions onto customer machines if they are allowed to.

 

Now, I am on Windows 10 Home, not Pro. Therefore, I am no longer able to skip any updates, or choose which updates MS will shove up my Bunsen Burner- it's either "accept all" or "delay all for up to 4 weeks." My previous max-delay expired last week so now I must accept the absolute latest possible bleeding edge version of Windows 10 (bugs and all) whether I want it or not. Same for .Net Framework.

 

Trust me, everything is up to date.

[Vyxenne]

UPDATE, POSSIBLE BREAKTHROUGH

 

I may have found it! I now suspect, despite my having installed all my games outside of C:\Program Files, that Windows 10 UAC has hunted me down way over on G:\Games! I set SkyrimSE.exe and skse64_loader.exe to run as Admin and I have just done 4 successful (and immediate!) launches of SSE in a row! Why the hell would Windows UAC be screwing with me on a non-system drive and path???

 

More testing is needed but initial indications are promising.

[Vyxenne]

2 hours ago, ChaosTheorist said:

Unfortunately, Windows Event Log info isn't going to help much

LOL, you are no doubt correct, but the Windows Event Log has the distinct advantage of being findable (via the Event Viewer app), not hidden in some dark corner of my machine accessible only via an obscure, undocumented system variable like %SECRETLOGS% or whatever. When I design my new OS  I will include a System folder named "C:\Users\[user]\Documents\Logs" and direct ALL logs of every kind to subfolders of that so users have at least a fighting chance of ever finding them. My NetScript logs are not anywhere near my Papyrus logs, which are nowhere close to my SKSE logs or my SKEE logs or my JSON logs or my SHSE logs or my CBPC logs or my ThisIsHowWeFuckWithYou logs and most of them are not at all intuitive to find.

 

Yes, I'm exaggerating to emphasize my frustration, but not by very much. As it happens, I may have just stumbled upon the actual issue and its solution (see last post). Thanks for your input.

[Just Don't]

58 minutes ago, Vyxenne said:

My NetScript logs are not anywhere near my Papyrus logs, which are nowhere close to my SKSE logs or my SKEE logs or my JSON logs or my SHSE logs or my CBPC logs or my ThisIsHowWeFuckWithYou logs and most of them are not at all intuitive to find.

NetScript logs are in it's own folder inside your \Data folder. You can change the location of the logs in the \Data\.NET Script Framework\NetScriptFramework\NetScriptFramework.config.txt file.

• Debug.CrashLog.Enabled = 1 <- logs enabled
• Debug.CrashLog.Path = "Data\NetScriptFramework\Crash" <- logs location

Weird that you're having UAC issues outside of Program Files or that running the exes as admin (aren't you using an admin account already?) fixes it. Anyways, you should disable UAC completely. I did that the very first day I got W10 in my computer.

[Vyxenne]

20 hours ago, Just Don't said:

Anyways, you should disable UAC completely. I did that the very first day I got W10 in my computer.

Wow, really? I thought UAC was needed as a "last-ditch" safeguard against malware making unwanted changes even though it is arrogantly implemented by Microsoft. I'll read the info at the link you gave me, and thanks.

 

EDIT/UPDATE: I had already turned off UAC notifications as described in the article you linked. However, I don't think that actually disables UAC- just the popup notifications.

 

20 hours ago, Just Don't said:

aren't you using an admin account already?

Yes, of course. Windows doesn't care what users want, though. Microsoft thinks it is a "service" and therefore they still own it even though I paid for it and it's on MY machine.

20 hours ago, Just Don't said:

weird that running the exes as admin fixes it.

Well, more testing is needed before I can declare for sure that running them as Admin actually fixed it, but 4 good launches in a row is very promising.

[Just Don't]

3 minutes ago, Vyxenne said:

I thought UAC was needed as a "last-ditch" safeguard against malware making unwanted changes

Yeah, but it's also a pain in the ass. I guess it's fine for old people or not tech savvy people. You can get away with it disabled if you avoid compromised websites, don't click the first flashing download button and don't accept to save the suspicious "thing_I_was_looking_for.exe" while you're searching for something. I've read Windows Defender is cool and should be enough. I personally use another AV and a malware scanner which I use once every... uh it's been a while. Truth is, I haven't had a virus/malware since I left the uni, worst security offenders are USB drives and public computers.

 

I hope your game behaves and the issues are gone for good, if not check the NetScript logs. 

[Vyxenne]

19 minutes ago, Just Don't said:

I personally use another AV and a malware scanner

Me too. Thanks for your help, I'm off to test my SSE launching with the exe's set to Admin!

[phillout]

6 hours ago, Just Don't said:

 

Weird that you're having UAC issues outside of Program Files or that running the exes as admin (aren't you using an admin account already?) fixes it. Anyways, you should disable UAC completely. I did that the very first day I got W10 in my computer.

This is a really bad advice. 

 

And having UAC issues anywhere is rather common and is a sign of problems with permissions, and that's it. Easily fixed by resetting file permissions. on the game's folder. No, don't ask me "how'. just fuckin' google it.

[Just Don't]

8 hours ago, phillout said:

This is a really bad advice. 

 

Eh, you're right here. I can vouch only for myself and say I haven't had a single issue in all my years with UAC disabled, I know my way around keeping a minimum of security measures and practices in my computer usage. So Vyx should do what she feels right. Setting executables to run as admin may be enough in her case-

[phillout]

2 hours ago, Just Don't said:

I can vouch only for myself and say I haven't had a single issue in all my years with UAC disabled

And I didn't have issues with UAC enabled. My opinion is if you have problems with UAC - you're holding it wrong. It doesn't stand in your way if you aren't trying to screw up the system or didn't misconfigure something.

 

If you don't run your game from Program Files and need to use Admin rights - it means that the permissions are screwed, most probably because you have tried running it as Admin already and there are files owned by admin now.

 

Fixing it is easy.

 

UAC may be not omnipotent, but at least it prevents all those programs you download (partially those related to gaming) from screwing up your system.

[Vyxenne]

UPDATE: Another long-ish night of Skyrimming, with several Quits to BodySlide outfits and/or update various mods, and at least 6 game launches over a period of about 5-6 hours. Every launch was 100% successful, no hung launches, no quiet (or noisy! ) failures to launch. Just 100% perfect, predictable 15-second launches. I am beginning to be very optimistic that setting the exes to Admin privileges has fixed it.

[Vyxenne]

14 hours ago, phillout said:

having UAC issues anywhere is rather common and is a sign of problems with permissions, and that's it. Easily fixed by resetting file permissions. on the game's folder. No, don't ask me "how'. just fuckin' google it.

Other than your presumptuous and condescending stinger at the end  , thanks for your advice. Or not.

 

As it happens, due to Windows' chronic usurpation and overwriting of my Security/Ownership/Permissions settings for the past 10+years, I have a fair amount of experience setting (and then repeatedly resetting) folder permissions. In Windows 7, it was as simple as right-clicking the folder (while logged into my Administrator account, of course) and selecting "Take ownership" then watching the command window interminably scrolling until it was finished. Then, a few hours/days/weeks/months later, I would find that Windows had stealth-reverted the folder permissions/ownership for no apparent reason except that it could, and I would have to do it again.

 

However, since "take ownership" is not a directly-clickable option in Windows 10, I have to use the Properties >> Security tab of the folder itself. In the case of my SSE folder, I found that all three entities (My user account, the SYSTEM account and the "Administrators" group account) had "full control" with all of the children of that umbrella permission ticked for good measure- "Read," "Write," "Modify," etc. Also, there were no "special permissions," and no "Deny" permissions, which of course could have overridden any of the more permissive permissions. Finally, I ticked the "Apply inheritable permissions to children of this object" even though it appeared to have already been applied, based on permissions I found on subfolders, and ran it again just to make sure since I have added a crap-ton of files and folders to that path since setting the permissions.

 

Finally, my understanding of the difference between setting permissions on an executable's home folder and setting the exe to run as Admin is that the latter overcomes any and all permission denials encountered by that/those executables at runtime, both inside and outside their folder of residence.

 

So yeah, I fuckin' know how to set permissions on files and folders, Phil. ?

[phillout]

This is great then.

 

Sorry, I was in a really bad mood for another "have you tried turning on your PC / how do I turn on PC, can you show me?" session which I wouldn't survive, this wan't directed at you personally

[asjflask]

Since he has a profile of Bender, a better response would've been "Bite my shiney metal ass" :D ...sorry just had to do it!

[Vyxenne]

14 hours ago, phillout said:

Sorry, I was in a really bad mood for another "have you tried turning on your PC / how do I turn on PC, can you show me?" session which I wouldn't survive, this wan't directed at you personally

I can't say I've never been the Legendary PEBCAK, but I try really hard not to be. Thanks for your advice (which was on point, as I said) and hope you're having a better day today!

 

For my part, I've had 2+ days of trouble-free SSE launches- 100% reliable 15-second starts with the Load menu 3-4 seconds later. I'm going to edit the title of this chain to indicate that I think it's solved, even though I owned the entire SSE folder when I checked ownership, and found no restrictive permissions in it. Somehow, in ways we'll probably never know, running the two launch exe's as Admin has fixed it.

 

Thanks to everybody that chimed in with helpfulness.