lendiforma Posted November 25, 2022 Posted November 25, 2022 (edited) Hi, I wonder if anyone can help me to solve my problem. I seem to be continuously having CTD's connected with memory issue, at least as far as I can tell (0xC0000005) Could somebody have a look at my logs and at least say whether I'm right or wrong? To me it sure does seem as a memory issue, because: 1) it's random, but connected with heavy stuff, like a lot of sexlab anims in a row; 2) it's not a load/save related, cause I started new games with different load order many times, trying to find the right one, doesn't help; 3) doesn't seem to be directly mod related (I think?), cause it can be just fine for hours and then bam it's all gone. And I just rebuilt my Skyrim from scratch, and then again because of that same problem Stuff I have: SKSE memory patch Crash Fixes Animation Limit fix FNIS 7.6 XXL with around 80% CTD showing ENB Boost with VideoMemorySizeMb=3862 according to VRamSizeDX9 test What I tried (obviously on separate saves): SKSE Memory patch (DefaultHeapInitialAllocMB=768 (1024, 1280 as well) (ScrapHeapSizeMB=256) instead of UseOSAllocators=0 in Crash fixes UseOSAllocators=1 instead of SKSE with with CustomMemoryBlock=128 (70% block load showing) UseOSAllocators=1 without CustomMemoryBlock Changing virtual memory size - no effect Changing memory section in enblocal in different ways - no effect Lowering the amount of FNIS anims - no effect I managed to reproduce (kinda) the srash by having a long sexlab aniamted session, and it crashes in about 10 minutes or so after beginning. Both SKSE and Crash Fixes memory work for about the same time before crash. But if I don't play animations and just go out to Solitude, I can just walk without any crash. Mostly CTD's are connected to animations, but again, nothing in particular in any particular place. Or, sometimes it doesn't. It drives me crazy. If anyone can lend me a hand at figuring out what's happening here, I sure would appreciate. I could probably just miss something obvious and fail to see it 2022-11-25_17.01.27- WITH Allocators.dmp 2022-11-25_16.37.56 - with SKSE.dmp crash_2022_11_25_23_51_1-with allocators.log crash_2022_11_26_00_14_1-with skse.log modlist.txt loadorder.txt Edited November 25, 2022 by lendiforma
lendiforma Posted November 25, 2022 Author Posted November 25, 2022 Here's a papyrus log. This time it took about 25 minutes of sexlab animating, doing the same thing. Why? Hell if I know. Could be 5, or 10, or 20, that's the problem. It's not possible to play and wait for an CTD every goddamn second 2022-11-25_17.57.37.dmp crash_2022_11_26_01_24_1.log Papyrus.0.log
alex77r4 Posted November 25, 2022 Posted November 25, 2022 (edited) 1 hour ago, lendiforma said: Hi, I wonder if anyone can help me to solve my problem. You can have two problems and locate the exact problem is not easy. One: Be sure you have the last version of the main core mods like PapyrusUtil and JContainer, of course for Legendary, because you are playing in Legendary. Be sure none other mod overwrite a file in that core mods. For example, in your modlist you have PapyrusUtil in line 16. That is very low in your modlist because the file have inverse order. But Jcontainer is in line 333 and that is very, very, very up in the modlist. Verify that is not overwrited by other mod. And of course, be sure you have the last version. Two: You have a mod that is making bad things. Probably is a mod related to SexLab because if you not launch animations you can play some hours. Then, is posible that one mod, one single mod, is causing yours strange and random CTD. The most probably is because the mod have some scripts with arrays that are accesed in an uncontroled way. The arrays are not protected in Papyrus and when two scripts try access the same array in the same nanosecond we have a CTD saying memory can't be read. Of course, the access must be made in the same nanosecond because a bit before or after not cause the CTD. For that is a strange and random CTD and is very dificult to locate and solve. But the only way to locate the problematic mod is, as always, the most horrible way... Disable mods until you find it. Edited November 25, 2022 by alex77r4 1
lendiforma Posted November 25, 2022 Author Posted November 25, 2022 3 minutes ago, alex77r4 said: PapyrusUtil and JContainer Unfortunately they both are of the last version, and not overwritten by anything, made sure of that 3 minutes ago, alex77r4 said: Two: You have a mod that is making bad things Yeah, I guess the only way right now is go one by one. God I wish there was some easy and sensible way to determine what Skyrim doesn't like...
lendiforma Posted November 25, 2022 Author Posted November 25, 2022 (edited) Apparently the problem seems to disappear completely when removing SLSO, which is a complete disaster, since there are too many mods connected to it Now I gotta figure out which one of my mods screws with it any why... upd: Seems there was some kind of a problem between Immersive Hud and SLSO, despite me turning it on during scenes Probably some third party mod involved, maybe SL Survival. Solved by replacing IHUD with Less Intrusive Hud Edited November 26, 2022 by lendiforma
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