Updated, now crashing (Crashlog included)

[Scautura]

Because I'm tearing my hair out after upgrading to 1130 (because I want to see if the newer version of RaceMenu will fix random crashing I'm having), I figured I could ask the smart people of LL. Here's a crashlog (well, two: one from Crash Logger, one from Trainwreck; two different attempts to start Skyrim, so they're not interfering with each other). Essentially, Skyrim crashes at the start, before the menu even shows up. I think I've done everything I should (changed settings in Engine Fixes, but also tested without, and without Display Fixes, disabled Upscaler because that doesn't work as far as I can tell?)

CrashLogger:crash-2024-01-03-00-51-10.log

Trainwreck:2024-01-03-01-07-06.log

 

And now to head to bed before my head explodes! If nobody can figure it out, I'll continue working on it (binary search is such a boon, but with this many mods, oof!) and see where I get to.

Edited January 3, 2024 by Scautura

[Shonen17000]

If you used the best of both downgrade patcher, the engine of the game is missing the support for the new file header, but the new versions of several masters use this new file header, result the game's engine can't load those masters and crashes, installing https://www.nexusmods.com/skyrimspecialedition/mods/106441 fixes those crashes by bringing to the engine the missing support of the new file header.
Besides you're already the 3rd one i explain that on loverslab.

Edited January 3, 2024 by Shonen17000

[Scautura]

28 minutes ago, Shonen17000 said:

If you used the best of both downgrade patcher, the engine of the game is missing the support for the new file header, but the new versions of several masters use this new file header, result the game's engine can't load those masters and crashes, installing https://www.nexusmods.com/skyrimspecialedition/mods/106441 fixes those crashes by bringing to the engine the missing support of the new file header.
Besides you're already the 3rd one i explain that on loverslab.

 

The first line of the crashlog states:

Skyrim SSE v1.6.1130

Considering I didn't mention using Best of Both, nor any sort of downgrade after updating, and I've been recommending that to anyone on prior versions, that's most definitely not the issue. 640 works perfectly fine (bar the weird random skee64.dll crashes I'm getting). Swing and a miss! ?

Edited January 3, 2024 by Scautura

[Shonen17000]

Then that means you have to check all your dlls to see if they need updates.
And some popular mods like quick loot re / ee, and additemmenu (even the ng version) are known to cause ctds on 1.6.1130. Aaaand you do have quick loot ee. oslaroused isn't compatible either.
Look here: 

ALL RED LINK are not compatible yet.
"before mocking someone, make sure you're not the real idiot"

Edited January 3, 2024 by Shonen17000

[traison]

EXCEPTION_ILLEGAL_INSTRUCTION smells like your CPU doesn't support something, but considering it came from SkyrimSE.exe that leaves 2 options:

1. You got a really silly CPU, or...
2. ...a mod modified that memory to include instructions your CPU didn't understand.

Huh, well this is interesting. Gonna have a look at this in the debugger, back in a bit.

 

Edit: Also the crash logger didn't bother to print the instructions at the faulting offset. Even weirder.

 

Edit again: Nothing weird going on at that faulting offset, at least in an unmodified 1130 exe:

       1406414bf 48 83 3d        CMP        qword ptr [DAT_1420eb640],0x0                    = ??
                 79 a1 aa 
                 01 00

 

Edit again: I can't find official documentation for this exception. The error code seems like it might be 0xc000001d. If you know how to use a debugger, suspend the SkyrimSE.exe process and attach to it. Make sure you have the same instructions as I do (posted above) at the faulting offset.

 

Edit again: There it is, found it:

Quote

EXCEPTION_ILLEGAL_INSTRUCTION

The thread tried to execute an invalid instruction.

 

Line 2579 in winnt.h:

Quote

#define STATUS_ILLEGAL_INSTRUCTION       ((DWORD   )0xC000001DL)   

Edited January 3, 2024 by traison

[Scautura]

1 hour ago, Shonen17000 said:

Then that means you have to check all your dlls to see if they need updates.
And some popular mods like quick loot re / ee, and additemmenu (even the ng version) are known to cause ctds on 1.6.1130. Aaaand you do have quick loot ee. oslaroused isn't compatible either.
Look here: 

ALL RED LINK are not compatible yet.
"before mocking someone, make sure you're not the real idiot"

 

OSL Aroused is on me. I took it out during testing with no difference to the results. Quick Loot EE isn't even noted on the compatibility tracking (nor the Hunterborn Support version), and RE already has a working (but lacking, for "reasons") fix. On top of that, Papyrus Tweaks NG is noted as working on its own page, but in red on the tracking. However, this is far more useful information (even with missing/incorrect information) than something that looked to me like you hadn't paid attention to what I'd written. Thank you. I let my frustration get away from me, and for that I apologise.

 

1 hour ago, traison said:

EXCEPTION_ILLEGAL_INSTRUCTION smells like your CPU doesn't support something, but considering it came from SkyrimSE.exe that leaves 2 options:

1. You got a really silly CPU, or...
2. ...a mod modified that memory to include instructions your CPU didn't understand.

Huh, well this is interesting. Gonna have a look at this in the debugger, back in a bit.

 

Edit: Also the crash logger didn't bother to print the instructions at the faulting offset. Even weirder.

 

Edit again: Nothing weird going on at that faulting offset, at least in an unmodified 1130 exe:

       1406414bf 48 83 3d        CMP        qword ptr [DAT_1420eb640],0x0                    = ??
                 79 a1 aa 
                 01 00

 

Edit again: I can't find official documentation for this exception. The error code seems like it might be 0xc000001d. If you know how to use a debugger, suspend the SkyrimSE.exe process and attach to it. Make sure you have the same instructions as I do (posted above) at the faulting offset.

 

Edit again: There it is, found it:

 

 

I had a feeling you'd show up with more information than I could glean from the log. Unfortunately, my debugging skills are lacking, despite developing in various languages for almost forty years now (it's been that long? Yikes!) so I wouldn't be able to attach a debugger (not without a little learning, and that's not something I'm up to at the moment).

 

It's probably one (or more) of the mod DLLs I've got causing funky issues, because I don't think a 5820K is really that silly. Old and decrepit maybe, but not silly! I was hoping for more of a pointer to one of them, but I've gotten that sort of pointer from Shonen17000 above.

Edited January 3, 2024 by Scautura

[traison]

Yup, I agree with Shonen17000, you have something throwing weird bytecode patches around. A mod with a dll is what you're looking for. I would however add that, it does not need to be one that is incompatible with SKSE, nor one that is incompatible with the game. This is something that is incompatible with your hardware unfortunately.

 

Looking at your CPU, it seems fine when it comes to supported instruction sets:

Intel® SSE4.2, Intel® AVX2

 

If AVX2 would have been missing there, or SSE 4.1/4.0 only then that would have been your problem. AVX512 you may run into but as far as I know its still rare and apparently sets Intel cpus on fire or something hilarious like that.

[Scautura]

10 minutes ago, traison said:

Yup, I agree with Shonen17000, you have something throwing weird bytecode patches around. A mod with a dll is what you're looking for. I would however add that, it does not need to be one that is incompatible with SKSE, nor one that is incompatible with the game. This is something that is incompatible with your hardware unfortunately.

 

Looking at your CPU, it seems fine when it comes to supported instruction sets:

Intel® SSE4.2, Intel® AVX2

 

If AVX2 would have been missing there, or SSE 4.1/4.0 only then that would have been your problem. AVX512 you may run into but as far as I know its still rare and apparently sets Intel cpus on fire or something hilarious like that.

 

There's a 'hilarious' ? turbo penalty for Intel cores when using heavier AVX2 and AVX512 commands (with the penalty being higher for the latter; being very simplistic here). The only Skyrim related item I'm aware of that uses anything above AVX is FSMP (and PureDark's Upscaler at one point used AVX2 but dropped back to AVX with a later release), for which I only installed the AVX version (the AVX2/512 issue is noted in the FOMOD).

 

I did decide to go back to 640 this morning, and I'm not in the mood to fight with 1130 at the moment, so I'll keep those in mind (and hope that there are updates for them). Once I get a crashlog for the skee64 error, I'll probably post that to see if someone can point me in the right direction there (but sometimes it's just a freeze with no log).

Edited January 3, 2024 by Scautura

[Shonen17000]

Well, as far as i can tell, the creators of those dlls have been way more reactive than on previous updates, that said, i have a bad new, another update is planned (mainly bugfix) for early 2024.

That said, that makes me appreciate my ryzen 7 3700x, even if it doesn't have avx512, it's avx2 works quite well.

Edited January 3, 2024 by Shonen17000