Updated Skyrim fixed all skse .dll plugin problems but

[ARO57]

 

 

Edited September 7, 2025 by ARO57

[traison]

Same issue as here.

[Tron91]

I had the same problem. Launched the game from steam. Changed the settings and the game loaded my last save game. Freaky Bethesda Shit

Edited January 3, 2024 by Tron91

[traison]

If you look at the offsets given in that callstack using a disassembler you could see that all other callstack entries match, except for the topmost (most relevant) entry. The offset points into the middle of an instruction in the unmodified code, and the instructions are diferent, meaning some mod (with a dll) made a bytecode edit there.

 

To know which mod it was that made it, you'd have to:

1. Bypass DRM.
2. Attach a debugger.
3. Avoid the traps.
4. Set a hardware breakpoint (write) on SkyrimSE.exe+06446D1.
5. Wait for the breakpoint to trip and figure out where the operation originated from (probably in RIP at this point).

Most people just rip their setups apart and trial-n-error their way through it.

[Tron91]

I was having the same issue. Started game from steam from the launcher. Changed the game settings and the problem went away.

 

SkyrimSE v1.6.1130
trainwreck v1.3.1

Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x7FF7DBF146D1 SkyrimSE.exe+06446D1

SYSTEM SPECS:
    OS: Windows 10 Home Single Language 22H2 19045.3693
    CPU: GenuineIntel Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    GPU #1: NVIDIA GeForce GTX 1050 Ti
    GPU #2: Intel(R) HD Graphics 630
    GPU #3: Microsoft Basic Render Driver
    RAM: 16.25 GiB/31.87 GiB
    PAGE FILE: 22.73 GiB/36.62 GiB

PROBABLE CALL STACK:
    [0] 0x7FF7DBF146D1 SkyrimSE.exe+06446D1
        add [rax],al
    [1] 0x7FF7DBF16E2C SkyrimSE.exe+0646E2C
        test r15b,r15b
    [2] 0x7FF7DBF0EFC5 SkyrimSE.exe+063EFC5
        test bl,bl
    [3] 0x7FF7DCE0348E SkyrimSE.exe+153348E
        mov ebx,eax
    [4] 0x7FFC44757344 KERNEL32.DLL+0017344 BaseThreadInitThunk
        mov ecx,eax
    [5] 0x7FFC456426B1    ntdll.dll+00526B1 RtlUserThreadStart
        jmp short 0000000000000022h

Edited January 4, 2024 by Tron91

[Shonen17000]

6 hours ago, ARO57 said:

how do i know which mod is which?

PROBABLE CALL STACK:
    [0] 0x7FF6C5E546D1 SkyrimSE.exe+06446D1
        add [rax],al
    [1] 0x7FF6C5E56E2C SkyrimSE.exe+0646E2C
        test r15b,r15b
    [2] 0x7FF6C5E4EFC5 SkyrimSE.exe+063EFC5
        test bl,bl
    [3] 0x7FF6C6D4348E SkyrimSE.exe+153348E
        mov ebx,eax
    [4] 0x7FFE59907344 KERNEL32.DLL+0017344 BaseThreadInitThunk
        mov ecx,eax
    [5] 0x7FFE5ACC26B1    ntdll.dll+00526B1 RtlUserThreadStart
        jmp short 0000000000000022h

kernell32.dll and ntdll.dll aren't coming from mods, both are important dlls belonging to windows.

[traison]

4 minutes ago, ARO57 said:

ok thats strange somehow isnt it. i will try to repair them

 

Be very careful what you do now...

 

This is what you should be focusing on, nothing else, especially not core Windows dlls:

Quote

Most people just rip their setups apart and trial-n-error their way through it.

 

Find all your mods that contain dll files, disable them one by one until the problem goes away. Post the mod name here once you know it, if you can't figure out a "proper" fix going forwards from there.

Edited January 4, 2024 by traison

[Tron91]

Let skyrim launcher detect your video card and adjust it's settings. Set accordingly it to high or low. Save settings, exit launcher. Start from skse loader. Done

[Shonen17000]

1 hour ago, Shonen17000 said:

kernell32.dll and ntdll.dll aren't coming from mods, both are important dlls belonging to windows.

Better not, seeing them in the log doesn't mean they are broken, it just means they were loaded, which is absolutely normal, windows needs them, almost if not all crash logs will show them. Trying needlessly to repair them is at the risk of totally breaking your windows installation.

Reread me and you'll see i never said they were the cause of your issue.

Edited January 4, 2024 by Shonen17000