Papyrus Script CTD

[ripple]

Other than the memory tweaks, your ini files look ok. So after you go back to stock ini settings and start a new game:

 

- Set papyrus logging to disabled unless you start experiencing CTDs again (bEnableLogging=0).

- I turn off timed autosave completely. Although I manual save meticulously, every 10 - 15 minutes or so.

[hentaishinri]

Other than the memory tweaks, your ini files look ok. So after you go back to stock ini settings and start a new game:

 

- Set papyrus logging to disabled unless you start experiencing CTDs again (bEnableLogging=0).

- I turn off timed autosave completely. Although I manual save meticulously, every 10 - 15 minutes or so.

Same. I manually save every 5-10 minutes, every time on a new save.

I don't have any form of autosave on.

And okay, I'm practically leaving papyrus as it is and the only tweak to the ini files is the mouse acceleration thing

[ripple]

You've got timed autosave set to every 15 minutes

 

 

fAutosaveEveryXMins=15.0000
 

Set it to '0.0000' and it will only autosave as per your other settings (on travel, on wait, etc.) and when the game is scripted to do so (e.g. Helgan tutorial).

Edited March 29, 2013 by ripple

[hentaishinri]

Okay, so far so good - i've been playing for over 6 hours now - no ctd (hoorah, hoorah! But I've played more than 6hours before and still got a crash later on, but it looks stable for now)
I started all the mods one after another, tried them all and so far everything is completely normal.
I removed some of the mods that induce more scripting.
I even removed UFO (ultimate followers overhaul), because i learned from the forums that it writes NPC script directly and I had NPC issues before, some of them were idle when they weren't supposed to be, some of them were in the wrong place etc.
For now the game runs okay, I used same stuff as before - Mod Organizer, Wrye Bash, a fairly simple injfx injector and the enb antifreeze patch (though idk if i need that anymore?).
I'll update with the first CTD i get

[hentaishinri]

I had a CTD last night, but I wasn't able to play after it, in order to enable the log and reproduce the CTD
But this is how it happened: I was in Morthal(outdoors) and i was doing the quest to kill the nearby vampire nest, when I got to the entrance of the cave and i talked to the npc, that was waiting outside to help me, the game lagged a little and then it crashed.
I will try it again tonight, but now I'm 100% sure the CTD's are all with npc script, because there's always an npc around - it either makes a sound, or draws his weapon, or dies and i get crash

[korun]

enb antifreeze patch (though idk if i need that anymore?)

it depend on which Enb you have

[steve40]

The only, ONLY thing I did to the INI files is to change the default iMaxAllocatedMemoryBytes to iMaxAllocatedMemoryBytes=2147483647 that's the ONLY thing I touched there.

If there's ONE thing you could do to kill your Papyrus script stack, THAT WAS IT.

iMaxAllocatedMemoryBytes is NOT your system RAM, it is the script stack buffer. The default value is only 75kB ffs. That should tell ya somethin', wouldn't ya think? :facepalm: :ohdear:

So many times I see this mistake over and over again in people's logs, yet people still won't learn. I know the CK Wiki says the max value that can be set is "2147483647", but just don't do it!!! It is wrong.

Setting an extreme value like that simply breaks the stack buffer ("stack smashing") - THAT IS WHY YOU WERE GETTING STACK OVERFLOWS AND GAME STUTTERING, and finally CTDs.

Read here if you want to learn what is a stack buffer and what happens when it gets messed up.

Now, how to fix this. Set iMaxAllocatedMemoryBytes back to default (76800, iirc) and start a new game. Do not use a saved game that was made with the "2147483647" setting because ALL THOSE SAVES ARE NOW CORRUPT.

I can't emphasize this strongly enough, I've seen this problem crop up so many times now.

Edited March 30, 2013 by steve40

[hentaishinri]

 

enb antifreeze patch (though idk if i need that anymore?)

it depend on which Enb you have

this one http://enbdev.com/patch_tesskyrim_antifreeze_v0096.htm

 

 

The only, ONLY thing I did to the INI files is to change the default iMaxAllocatedMemoryBytes to iMaxAllocatedMemoryBytes=2147483647 that's the ONLY thing I touched there.

If there's ONE thing you could do to kill your Papyrus script stack, THAT WAS IT.

iMaxAllocatedMemoryBytes is NOT your system RAM, it is the script stack buffer. The default value is only 75kB ffs. That should tell ya somethin', wouldn't ya think? :facepalm: :ohdear:

So many times I see this mistake over and over again in people's logs, yet people still won't learn. I know the CK Wiki says the max value that can be set is "2147483647", but just don't do it!!! It is wrong.

Setting an extreme value like that simply breaks the stack buffer ("stack smashing") - THAT IS WHY YOU WERE GETTING STACK OVERFLOWS AND GAME STUTTERING, and finally CTDs.

Read here if you want to learn what is a stack buffer and what happens when it gets messed up.

Now, how to fix this. Set iMaxAllocatedMemoryBytes back to default (76800, iirc) and start a new game. Do not use a saved game that was made with the "2147483647" setting because ALL THOSE SAVES ARE NOW CORRUPT.

I can't emphasize this strongly enough, I've seen this problem crop up so many times now.

I did, I did reset it. The default ini file doesn't have a imaxallocatedmemory typed in, right? That's what my ini file looks like atm - no imaxallocatedmemory lines(i mean, the setting is still there, but because it's default it doesn't need to show, no?) i re-installed the game, deleted the 'my games -> skyrim' ini files, I basically started anew and i still got CTD

The most recent one is 10 minutes ago

here is the papyrus log

http://s000.tinyupload.com/index.php?file_id=51695661376601895216&gk=hotel

[korun]

this one http://enbdev.com/pa...reeze_v0096.htm

 

 

i know the patch, but it has been made for a ENB, if you are running , let say Enb 0.119 or greater no you don't need it anymore

 

@@

 

edit : and if your are not running any Enb, you don't need it at all

 

Edited March 30, 2013 by korun

[steve40]

@hentaishinri: did you start a new game from scratch? Your log is still full of stack dumps, and to me it does not look like a game that was started afresh from Helgen. Even if you set the ini values back to default, the broken stack is saved into your old save games and cannot be repaired by setting the ini values back to vanilla. You need to understand that. Edited March 30, 2013 by steve40