johntrine Posted August 22, 2023 Posted August 22, 2023 (edited) here it is, baby. i dont understand it (other than... maybe there is too many mods?) https://pastebin.com/09Y3zUad Edited August 22, 2023 by johntrine
lisander68 Posted August 22, 2023 Posted August 22, 2023 (edited) 3 hours ago, johntrine said: here it is, baby. i dont understand it (other than... maybe there is too many mods?) https://pastebin.com/09Y3zUad Game version 1.5.97....SKSE? Edited August 22, 2023 by lisander68
johntrine Posted August 22, 2023 Author Posted August 22, 2023 24 minutes ago, lisander68 said: Game version 1.5.97....SKSE? yep. i'm not using AE and the skse is installed for the non AE version
traison Posted August 23, 2023 Posted August 23, 2023 (edited) The callstack is corrupted. Nothing can be done with that log unfortunately. I recommend disabling crash logging in .Net and getting this thing instead. Edited August 23, 2023 by traison
johntrine Posted August 23, 2023 Author Posted August 23, 2023 1 hour ago, traison said: The callstack is corrupted. Nothing can be done with that log unfortunately. I recommend disabling crash logging in .Net and getting this thing instead. so, i turned off .net script crashlogs and used the suggested one and it seems to create no crash log in skse folder in my document.
lisander68 Posted August 23, 2023 Posted August 23, 2023 4 hours ago, johntrine said: ? Skyrim 1.5.97= SKSE 2.0.20 Your crash log shows SKSE 1.5.97
johntrine Posted August 23, 2023 Author Posted August 23, 2023 (edited) that's weird. i ran the game using skse from folder and not mo2 (ie without any mods) and the menu (when you press escape) show 1.5.97.0.8 (SKSE64 2.0.20 ref 6) so the skse version is correct. ( i mean i can try reinstalling it. one min) nothing changed. here is the newest crashlog Crash_2023_8_23_18-9-31.txt Edited August 23, 2023 by johntrine
anjenthedog Posted August 23, 2023 Posted August 23, 2023 you're using a one drive for skyrim? I'll admit that I don't keep up too much with a most of the newer ways of doing things, but Isn't that a remote "cloud" resource?
johntrine Posted August 23, 2023 Author Posted August 23, 2023 12 minutes ago, anjenthedog said: you're using a one drive for skyrim? I'll admit that I don't keep up too much with a most of the newer ways of doing things, but Isn't that a remote "cloud" resource? no. when i updated windows forced onedrive on my pc. i uninstalled it but it did some weird thing where it made a onedrive folder and moved documents and a few other folder in there. consider it as a folder name and not the "cloud" version since i uninstalled onedrive.
anjenthedog Posted August 23, 2023 Posted August 23, 2023 (edited) idk...doesn't the (local) one drive folder operate under different security protocols than normal folders? I thought there was some sort of "Native" corralling in there. (could be wrong...easily... like I said, I hain't kept up) Edited August 23, 2023 by anjenthedog omitted detail... and a typo
johntrine Posted August 23, 2023 Author Posted August 23, 2023 12 minutes ago, anjenthedog said: idk...doesn't the (local) one drive folder operate under different security protocols than normal folders? I thought there was some sort of "Native" corralling in there. (could be wrong...easily... like I said, I hain't kept up) i mean if that was an issue, then the game wouldnt have worked when i ran it without mo2 or mods. the game works without them. 1
traison Posted August 23, 2023 Posted August 23, 2023 There's some bigger issue going on here, considering Crash Logger isn't producing a crash log. Like for instance, the plugin may not be loading at all or then this is just another thread of someone that can't get Crash Logger working. Not necessarily saying it's user error, but rather something interfering with it - the unfortunate thing is that none of the previous threads have ever gotten past this exact point; crash logger doesn't produce a log, end of thread. Be the first out of these unfortunate souls to get crash logger working, post the log, and we can get back to work on the actual issue. Otherwise we'll just be stumbling around in the dark, throwing guesses at eachother and getting nowhere.
Scautura Posted August 23, 2023 Posted August 23, 2023 (edited) Even when Crash Logger crashes, it will leave a log that looks like this: Skyrim SSE v1.6.640 CrashLoggerSSE v1-8-0-0 Feb 1 2023 00:20:05 And even when that happens, it will go "alrighty, let's try that again" and produce a full crashlog for the original crash anyway (the above crashlog file will usually be labelled a minute or so after the valid crashlog, and be 1kb in size). Go ahead, ask how I know this! Edited August 23, 2023 by Scautura
johntrine Posted August 23, 2023 Author Posted August 23, 2023 btw. to add a few things. the mod mentioned a no esp mod, which i added to for an auto unequip ammo mod. i disabled it and here is what i got --------------------------- Precision.dll --------------------------- Settings.cpp(553): Failed to load settings. This might be an indication of your game being unstable, try installing SSE Engine Fixes. --------------------------- OK ---------------------------
johntrine Posted August 23, 2023 Author Posted August 23, 2023 1 hour ago, traison said: There's some bigger issue going on here, considering Crash Logger isn't producing a crash log. Like for instance, the plugin may not be loading at all or then this is just another thread of someone that can't get Crash Logger working. Not necessarily saying it's user error, but rather something interfering with it - the unfortunate thing is that none of the previous threads have ever gotten past this exact point; crash logger doesn't produce a log, end of thread. Be the first out of these unfortunate souls to get crash logger working, post the log, and we can get back to work on the actual issue. Otherwise we'll just be stumbling around in the dark, throwing guesses at eachother and getting nowhere. dev seems to have mentioned on his mod bug tab that the crashlog isnt always produced in some rare cases... so.... 49 minutes ago, Scautura said: Even when Crash Logger crashes, it will leave a log that looks like this: Skyrim SSE v1.6.640 CrashLoggerSSE v1-8-0-0 Feb 1 2023 00:20:05 And even when that happens, it will go "alrighty, let's try that again" and produce a full crashlog for the original crash anyway (the above crashlog file will usually be labelled a minute or so after the valid crashlog, and be 1kb in size). Go ahead, ask how I know this! i mean... i looked in my documents- my games- skyrim SE- skse folder.... Spoiler
traison Posted August 23, 2023 Posted August 23, 2023 Those rare cases would be when the exception was handled and the result was to terminate the process. Visually identical, technically very different. Since .Net created a crash log, and it works on the same principal, Crash Logger will create a log as well. You never mentioned checking if Crash Logger is even loading: skse64.log
johntrine Posted August 23, 2023 Author Posted August 23, 2023 21 minutes ago, traison said: Those rare cases would be when the exception was handled and the result was to terminate the process. Visually identical, technically very different. Since .Net created a crash log, and it works on the same principal, Crash Logger will create a log as well. You never mentioned checking if Crash Logger is even loading: skse64.log hmmm. ok. so tested a few more things. 1) removing a few mods. these few being any 15 or so mods, seems to stop the crashing. i am assuming for some reason, 'too much' mods or dll is causing some of them to not load which is weird since ANY type of mods removed seem to work. yes this mean armor or preset for face or body or skin, anything goes. which is funny since i tried loading the game with all plugin disabled and that did nothing 2) having a few extra mods that seem to cause crash shows the error i mention above. the settings.cpp one, which makes me think if some dll are not loading. 3) crashlogger.log says it successfully loaded in both, crash and non crash version. 4) checked skse64.log and the crashlogger seems to have loaded. i am uploading both crashlogger.log and skse64.log skse64.logCrashLogger.log
johntrine Posted August 23, 2023 Author Posted August 23, 2023 (edited) 28 minutes ago, traison said: Nothing weird going on in those logs. so i was right about crashlogger not logging... also, was the other infos any useful? Edited August 23, 2023 by johntrine
traison Posted August 23, 2023 Posted August 23, 2023 3 minutes ago, johntrine said: so i was right about crashlogger not logging... We already knew that. Question is why. See my 2nd post in this thread. 40 minutes ago, johntrine said: removing a few mods. these few being any 15 or so mods, seems to stop the crashing. i am assuming for some reason, 'too much' mods or dll is causing some of them to not load which is weird since ANY type of mods removed seem to work. yes this mean armor or preset for face or body or skin, anything goes. which is funny since i tried loading the game with all plugin disabled and that did nothing This statement is already far too random to make sense. There is nothing I can do here until you get Crash Logger going.
johntrine Posted August 24, 2023 Author Posted August 24, 2023 well... hopefully someone could help me.
anjenthedog Posted August 25, 2023 Posted August 25, 2023 (edited) Unfortunately, crashlogs are not *guaranteed* to be created. Some abnormal terminations or screen freezes seem to avoid logging. When I experience freezes and CTDs, all freezes go without log, and at least half of the "CTD-to-desktop" CTDs do too. It's not optimal, but that's life. What I do when all else fails is begin peeling back the layers of installed mods, removing them in reverse order of their installation (last installed, first uninstalled), then checking with either a very old save from back when the number of mods was countable on one hand, or with a new game. The reason I say last first is because uninstalling mods with intermediary positioning can and often does result in a general reordering of the load order, which can leave save files floundering when they attempt to access info no longer referred to by a given id (when first installed), and thereby result in ctds or other "misbehavior". I also think about answering the question (to myself) of "when the F did this start happening?" and trying to get an idea in my head of the literal when (dates, maybe even time) when things started going wrong. It's often (MOST often, in my own personal experience) the changes we made after or around the time of that memory, so screwing with a mod installed 14 months ago (for example) would likely be chasing the wrong rabbit, if you started noticing the problem "about a month ago or so"... It'd likely be something you did about a month ago or so, give or take a few days or week, right? Edited August 25, 2023 by anjenthedog
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now