Crash Log ( NetscriptFramework)

[nalwaz]

was wondering if anyone understands in Crash Logs could help me out pls ?

i have been getting frequent crashes just as the game finishes loading my save, it doesn't always occur but happens a lot really and sometimes it persists and i try several old saves for it to work. also starting new game is the only thing that doesn't crash so that's only way i login to my save by creating new character then loading the last save i want to continue from.

lastly, loading any saves after the save has successfully opened doesn't crash, so the crashing only happens after loading a save from the process after the game opens and a save is loaded not when loading a save after another save has successfully opened without crashing.

i don't understand in crash logs so thought anybody here could help me translate it or even find a fix for it i would be very grateful,  i listed the 2 most recent crash logs below

Crash_2024_10_28_2-44-17.txt Crash_2024_10_28_2-52-16.txt

[Sillius_Maximus]

So I had that exact same issue:

EXCEPTION_ACCESS_VIOLATION" at 0x7FF67C9ACE81 SkyrimSE.exe+01ECE81 or rather that's at least very close

 

so unfortunately kind of non descriptive. I was able to start a new game just fine, and play indefinitely.. but the minute i tried to load a save - crash.

In my case, it turns out that - I had installed a mod that was not properly converted from LE to SE/AE.

as soon as i removed it - ive been 100% stable.

It was easy for me to find, as i usually install 4-5 mods at a time, test.. install another few...test.. etc..

 

so my 30 second thought is - (especially if you recently installed a new mod or two) is look at removing those mods maybe and see?

[traison]

These are 2 different crashes, however they happen to both be script related.

 

2-52-16 is coming from slhh_mcm. It has something to do with a variable named _sliderParams.

2-44-17 is coming from Racemenu's MCM most likely.

 

Next time you have issues with crashing, use this crash logger instead. The NetScriptFramework logger rarely unwinds the callstack correctly anymore, and its lacking more modern symbol information. These 2 logs happen to be ok at first glance at least, but these are the exception not the norm - you got lucky.

[nalwaz]

28 minutes ago, traison said:

These are 2 different crashes, however they happen to both be script related.

 

2-52-16 is coming from slhh_mcm. It has something to do with a variable named _sliderParams.

2-44-17 is coming from Racemenu's MCM most likely.

 

Next time you have issues with crashing, use this crash logger instead. The NetScriptFramework logger rarely unwinds the callstack correctly anymore, and its lacking more modern symbol information. These 2 logs happen to be ok at first glance at least, but these are the exception not the norm - you got lucky.

i tried using it before Netscript but it wouldn't post any crash logs, is there a certain location it is posted in i am unaware of ?

[traison]

1 hour ago, nalwaz said:

is there a certain location it is posted in i am unaware of ?

 

This is in the mod description.

[nalwaz]

1 minute ago, traison said:

 

This is in the mod description.

but it doesn't mention where it is, and the old crash logger description just says that this version is obsolete and redirects you to the new one

[traison]

4 minutes ago, nalwaz said:

but it doesn't mention where it is

 

Quote

Crash logs are located in "Documents\My Games\\Skyrim Special Edition\SKSE" or "Documents\My Games\Skyrim VR\SKSE"

 

 

4 minutes ago, nalwaz said:

description just says that this version is obsolete and redirects you to the new one

 

Not seeing that anywhere. There's a link to an old one, and that one is indeed deprecated and links to Trainwreck (not the new Crash Logger). Trainwreck had its moment when Crash Logger was a bit slow to update. If you ask me, these days neither NetScriptFramework nor Trainwreck should be used. Both can be useful, sure, but it really comes down to how much work do you want to do yourself in a debugger/disassembler. Personally unless a crash log is particularily interesting, I'd rather not spend more than 5 minutes on one, certainly not weeks.

[nalwaz]

19 minutes ago, traison said:

 

 

 

 

Not seeing that anywhere. There's a link to an old one, and that one is indeed deprecated and links to Trainwreck (not the new Crash Logger). Trainwreck had its moment when Crash Logger was a bit slow to update. If you ask me, these days neither NetScriptFramework nor Trainwreck should be used. Both can be useful, sure, but it really comes down to how much work do you want to do yourself in a debugger/disassembler. Personally unless a crash log is particularily interesting, I'd rather not spend more than 5 minutes on one, certainly not weeks.

alright, downloaded and will try to test this one out

[nalwaz]

On 10/28/2024 at 5:35 PM, traison said:

 

 

 

 

Not seeing that anywhere. There's a link to an old one, and that one is indeed deprecated and links to Trainwreck (not the new Crash Logger). Trainwreck had its moment when Crash Logger was a bit slow to update. If you ask me, these days neither NetScriptFramework nor Trainwreck should be used. Both can be useful, sure, but it really comes down to how much work do you want to do yourself in a debugger/disassembler. Personally unless a crash log is particularily interesting, I'd rather not spend more than 5 minutes on one, certainly not weeks.

ok installed the Crash Logger and the game did crash 3 times now but no text file was generated in Documents\My Games\\Skyrim Special Edition\SKSE , i am running SE 1.5.97 so i installed the optional file that matches this version what could possibly be wrong here ? should i be downloading the new one or sth else ?

Edited October 29, 2024 by nalwaz

[traison]

Several options:

1. You have another handler for unhandled exceptions (such as NetScriptFramework).
2. The dll didn't load for some reason. Check skse64.log.
3. The exception that occured was not unhandled; the exception handler decided to terminate the application. This will look like what is typically refered to as a CTD, but it is not.

[nalwaz]

8 hours ago, traison said:

Several options:

1. You have another handler for unhandled exceptions (such as NetScriptFramework).
2. The dll didn't load for some reason. Check skse64.log.
3. The exception that occured was not unhandled; the exception handler decided to terminate the application. This will look like what is typically refered to as a CTD, but it is not.

1 is unlikely since i made sure i removed NSF and all its content before installing crash logger
2 how do i check that or where exactly 
3 am not sure i follow what you're saying

[traison]

8 hours ago, nalwaz said:

how do i check that or where exactly

 

%USERPROFILE%\My Documents\My Games\Skyrim Special Edition\SKSE

[nalwaz]

4 hours ago, traison said:

 

%USERPROFILE%\My Documents\My Games\Skyrim Special Edition\SKSE

there are 5 files that matches that name but not entirely. skse64, skse64.log0, skse64_loader, skse64_steam_loader, skse64_steam_loader.log0 . which should i be checking ? i don't run the game from steam so i am guessing the skse64.log0 ? but if it is indeed is this one i don't have an app that can run this kind of log0 type 

Edited October 30, 2024 by nalwaz

[traison]

4 hours ago, nalwaz said:

there are 5 files that matches that name

 

In Windows there will only ever be one file with a specific name in a directory.

 

Do yourself a favor and unhide known file extensions. This is one of Windows' biggest security flaws and for some reason Microsoft keeps doubling-down on it decade after decade. Keeps you from running exe files thinking they are jpg images and other stupid stuff like that.

 

4 hours ago, nalwaz said:

which should i be checking ?

 

 I already specified which file it is.

 

4 hours ago, nalwaz said:

i don't run the game from steam so i am guessing the skse64.log0 ?

 

Irrelevant, but just out of curiosity, what made you think Steam had something to do with log and log0 files?

 

4 hours ago, nalwaz said:

if it is indeed is this one i don't have an app that can run this kind of log0 type

 

You only need 2 applications to open all files ever created by man or machine on Windows:

1. Notepad for files containing human-readable text using a known codepage.
2. A hex editor for everything else.

Ignore option #2 for now, you're not ready for it.

[nalwaz]

2 hours ago, traison said:

 

In Windows there will only ever be one file with a specific name in a directory.

 

Do yourself a favor and unhide known file extensions. This is one of Windows' biggest security flaws and for some reason Microsoft keeps doubling-down on it decade after decade. Keeps you from running exe files thinking they are jpg images and other stupid stuff like that.

 

 

 I already specified which file it is.

 

 

Irrelevant, but just out of curiosity, what made you think Steam had something to do with log and log0 files?

 

 

You only need 2 applications to open all files ever created by man or machine on Windows:

1. Notepad for files containing human-readable text using a known codepage.
2. A hex editor for everything else.

Ignore option #2 for now, you're not ready for it.

this is it i guess ?

skse64.log

[traison]

CrashLogger.dll was not loaded.

[nalwaz]

14 hours ago, traison said:

CrashLogger.dll was not loaded.

any idea what could cause this ?

[traison]

Considering it wasn't even mentioned in the log, I'd say you didn't install it.

[nalwaz]

14 minutes ago, traison said:

Considering it wasn't even mentioned in the log, I'd say you didn't install it.

i did install it via MO2 should i do it manually ? and in MO2 folder or in skyrim original folder ?