skgun Posted January 18, 2024 Posted January 18, 2024 (edited) despite using CLA I cannot for the life of me figure out what is trying to tell me, I uninstalled OStim completely but I keep getting ctd whenever I hit "new game". In addition to that my plugins all get disabled when the game ctd every time without fail. I would appreciate it if someone could explain this to me like I was 3 years old.😭 _________________________________________________________________________________________________________________________________________________________________________________________________________ CLA SSE - Sephs Skyrim Experimental Crash Log Analyzer (1.2.0) / 2023.09.10 --------------------------------------------------------------------------- If you are asking others for assistance / help, ALWAYS provide the crashlog as well! ##################################################################################### Crashlog Tool: CrashLoggerSSE v1-12-1-0 Dec 22 2023 02:20:56 Game Version: 1.6.1130 Script Extender: 1.6.1130 ################################################################################ RAM ################################################################################ RAM Total: 31.93 GB RAM Used: 16.32 GB RAM Free: 15.61 GB Analysis RAM (all good): It is absolute unlikely that the crash was due to RAM. ################################################################################ Mod Count: ################################################################################ Light: 65 Regular: 15 Total: 80 ################################################################################ Header indicators: ################################################################################ Memory: 0x7FFEB4C0C08F count: (2) File: OStim.dll count: (6) Address: 02DC08F count: (2) Assembler: movss [rax+0x34], xmm0 count: (2) [ 0] 0x7FFEB4C0C08F OStim.dll+02DC08F movss [rax+0x34], xmm0 | C:\Git\GitHub\OStimNG\skse\src\Util\Globals.cpp:27 ?setPapyrusUndressing@Globals@Util@@SAX_N@Z -//- count: (1) [ 1] 0x7FFEB49E056C OStim.dll+00B056C jmp 0x00007FFEB49E05D7 | C:\Git\GitHub\OStimNG\skse\src\Events\EventListener.h:29 ??RCheckPapyrusUndressingCallbackFunctor@EventListener@Events@@EEAAXVVariable@BSScript@RE@@@Z -//- count: (1) [RSP+88 ] 0x7FFEB49E056C (void* -> OStim.dll+00B056C jmp 0x00007FFEB49E05D7 | C:\Git\GitHub\OStimNG\skse\src\Events\EventListener.h:29 ??RCheckPapyrusUndressingCallbackFunctor@EventListener@Events@@EEAAXVVariable@BSScript@RE@@@Z) -//- count: (1) OStim.dll 0x7FFEB4930000 -//- count: (1) OStim.dll v1.0.0.6 -//- count: (1) ################################################################################ Missing Masters ################################################################################ 1. Please check the notification of your Mod Manager! 2. If you cant find any entries there, try LOOT. 3. If this yields nothing, you'll have to manualy check every mod of yours if you might have missed a dependency. ################################################################################ Solutions ################################################################################ SkyrimSE.exe: count: (61) This file on its own is not the cause, however, we'll do further parsing... Could not find any known issues related to SkyrimSE.exe. SkyrimSE.exe _might_ be listed for the sole reason of... you're playing this game!! -------------------------------------------------------------------------------- hdtSMP64.dll: count: (9) If this appears often, it might indicate a bad config (rare). However, it might also just indicate that there were NPCs around that were wearing hdt/SMP enabled clothing... Please increase the log level for hdtsmp64 (if you have not done so yet) and check its content. Make sure to have Faster HDT-SMP that suits your Skyrim Version: - https://www.nexusmods.com/skyrimspecialedition/mods/57339 Also make sure you have these installed: - SMP NPC fix: https://www.nexusmods.com/skyrimspecialedition/mods/91616 You are using FSMP version: 2.02.05 Please ensure that this is compatible with your SKSE version: 1.6.1130 Possible FOMOD settings for installation You might want to try different AVX options, because eventhough supported, they might cause shutter/'lag' in populated areas... CPU: avx: True avx2: True avx512: False -------------------------------------------------------------------------------- tbbmalloc.dll: count: (4) Threading Building Blocks Memory Allocator This is either part of: - the CreationKit Fixes: https://www.nexusmods.com/skyrimspecialedition/mods/20061 - the Engine Fixes (part 2): https://www.nexusmods.com/skyrimspecialedition/mods/17230 I do recommend to use Engine Fixes (pick 'part 1' according to your SKSE) This message is shown without a check: Make sure to disable: SrtCrashFix64.dll (Animation Limit Crash fix SSE) as this is handled by the Engines Fixes, which is recommended to use! Either way, make sure to have the 'latest' version variant for your Skyrim edition. However, this probably is not the cause, but the causing mod relies on excessive memory handling. First and foremost, try to close any other application and background processes that might be running that you do not need. Like, but not limited to, game launchers, web browsers with 20 open tabs, Spotify, even Discord. Also, you might want to consider using lower texture mods, aka, use a 2k instead of a 4k texture mod, or just a 1k texture. If the above did not help, you could try apply these config tweaks to: __Skyrim.ini___ Make sure to comment out (#) any existing variants of these, so you can go back if they dont help or make things worse. This is most applicable if you're using 4-8 GB ram or less, you game addicted freak! (said the guy who was playing WoW raids at 3 fps). ================================== [Display] iTintTextureResolution=2048 [General] ClearInvalidRegistrations=1 [Memory] DefaultHeapInitialAllocMB=768 ScrapHeapSizeMB=256 ================================== Last but not least, increasing your pagefile is a good and simple way to avoid this. Best practice: pagefile-size > RAM Example: 24 GB > 16 GB RAM Please read / follow: 1. In the Taskbar Search, type “Advanced System“. ... 2. In System Properties, click Advanced tab. 3. In Performance section click Settings button. 4. Performance Options will open. ... 5. Here, under Virtual memory, select Change. 6. Uncheck Automatically manage paging file size for all drives. 7. Select a Drive that hardly use (as in not often) 8. Set manual size 9. Set value to ~ 150% of your RAM (as shown in example) 10. Confirm with "OK". If you want to read more about (allthough, not related to sharepoint server): https://learn.microsoft.com/en-us/sharepoint/technical-reference/the-paging-file-size-should-exceed-the-amount-of-physical-ram-in-the-system ################################################################################ Success Statistic: (this has been detected/handled, does not mean it's the cause) ################################################################################ Issues Found: 3 Issues Solved: 3 ################################################################################ DEBUG State: ################################################################################ Culprit list content: (just a list) SkyrimSE.exe, hdtSMP64.dll, tbbmalloc.dll, ################################################################################ Random 'Fallback' Checks ################################################################################ How to read these results? - They are simple keywords that may appear when you have a lot of issues. - They do NOT have to mean anything. - Only if the "regular" results / solutions do not help, they might provide an indication to the reason for this crash. RTTIName: "NiCamera" -//- count: (1) [RSP+BD0 ] 0x7FF7F650E9B0 (BGSStoryTeller*) -//- count: (1) [ C] ccBGSSSE025-AdvDSGS.esm -//- count: (1) [RSP+B80 ] 0x7FF7F65301F0 (AnimationFileManagerSingleton*) -//- count: (1) [RSP+BA0 ] 0x7FF7F65301F0 (AnimationFileManagerSingleton*) -//- count: (1) crash-2024-01-18-09-03-24-REPORT.txt Edited January 23, 2024 by skgun
traison Posted January 18, 2024 Posted January 18, 2024 Post the original log if you want me to look into it. 1
skgun Posted January 19, 2024 Author Posted January 19, 2024 20 hours ago, traison said: Post the original log if you want me to look into it. crash-2024-01-18-09-03-24.log
traison Posted January 19, 2024 Posted January 19, 2024 Plugins getting disabled is probably because of 1130/1170. There's been threads about that on these forums. As for the crash, it was caused by OStim.dll, so even if you think you removed it, you didn't. Query your mod manager for what mod is providing that file and go from there. 1
skgun Posted January 20, 2024 Author Posted January 20, 2024 12 hours ago, traison said: Plugins getting disabled is probably because of 1130/1170. There's been threads about that on these forums. As for the crash, it was caused by OStim.dll, so even if you think you removed it, you didn't. Query your mod manager for what mod is providing that file and go from there. thank you for the troubleshoot
skgun Posted January 20, 2024 Author Posted January 20, 2024 On 1/19/2024 at 7:51 AM, traison said: Plugins getting disabled is probably because of 1130/1170. There's been threads about that on these forums. As for the crash, it was caused by OStim.dll, so even if you think you removed it, you didn't. Query your mod manager for what mod is providing that file and go from there. I deleted OStim.dll but now I just get infinite loading screen after I hit new game. I can't get a crash log because it does not crash, also I am running 1130 and have the manifest or whatever its called set to read only so the game does not update. I have all plugins disabled and still get stuck in an infinite loading after hitting new game.
traison Posted January 21, 2024 Posted January 21, 2024 8 hours ago, skgun said: I deleted OStim.dll but now I just get infinite loading screen after I hit new game. I can't get a crash log because it does not crash, also I am running 1130 and have the manifest or whatever its called set to read only so the game does not update. I have all plugins disabled and still get stuck in an infinite loading after hitting new game. The only way to debug a freeze that I know of is with a debugger. Depending on your skillset, it may be easier to start disabling mods until the problem goes away. It may not seem like it, but since you can reliably reproduce it that's already a huge step in the right direction - considerably easier to work with than random freezes.
skgun Posted January 23, 2024 Author Posted January 23, 2024 (edited) On 1/21/2024 at 2:35 AM, traison said: The only way to debug a freeze that I know of is with a debugger. Depending on your skillset, it may be easier to start disabling mods until the problem goes away. It may not seem like it, but since you can reliably reproduce it that's already a huge step in the right direction - considerably easier to work with than random freezes. thats what I ended up doing Ostim was not the problem apparently but the dll file in the behavior data injector,universal support to give it AE support, Animation Motion Revolution, dTry's Key Util, Object Categorization Framework(disables all plugins). When I disable those two mods the game launches and loads but when it crashes the game does not turn off all my plugins. Despite being on version 1.6.1130 and have the manifest set to "read only" so it does not update. I disabled all mods by categories and most if not all mods in the "patches" and "utilities" cause the ctd. 😵appreciate the reply Edited January 23, 2024 by skgun
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