CTD loading save

[donttouchmethere]

6 minutes ago, surothedeath said:

i have done this. but i dont know if it working for i se noting in the right corner

You only see a message on game start.

In Skyrim main menu you see some information in the upper left corner for a while (while Skyrim is still loading mods).

ENBoost only provides Skyrim 32bit with more available vram and ram (and some other fixes).

 

What do you expect to see in the right corner and when?

[Guest]

On 6/3/2020 at 10:23 PM, Hawk9969 said:

Papyrus logs don't help with debugging crashes at all because crashes are unhandled exceptions, which as the name says, was not handled by the program (either because the program didn't expect it or because the program couldn't handle such an exception in the first place).

Load orders can only give a clue on a possible known crash.

If you want people to accurately give you a solution for crashes, you need to share your SKSE minidump of the crash in question.

Plus, I recommend disabling VSync entirely and using the FPS limiter instead. If, however, you do have an adaptive sync monitor, you want to turn VSync and the FPS limiter off, and enable G-Sync or FreeSync in your driver's control panel.

EnableCompression should be false unless you are really low on VRAM (having the GPU decompress textures each time it needs to read them for rendering when you've enough available VRAM to store them uncompressed is simply a waste).

For VideoMemorySizeMb, you can use Boris' tool, if you don't want to have it auto detect.

ENB AA settings are up to your performance, in my case with a GTX 1660, the only one that doesn't have a significant FPS impact for me is TemporalAA, which does cause some blur, but overall is better than FXAA or no AA at all (supersampling causes a bigger performance impact aswell).

[Furryfurry]

1 hour ago, donttouchmethere said:

What do you expect to see in the right corner and when?

well last time i got it working few yers ago it howed numbers and like "hackspeed enable"

 

1 hour ago, Hawk9969 said:

SKSE minidump of the crash in question.

ok here you go

Vsync? you mien in enboost?

2020-06-05_08.53.37.dmp

[Furryfurry]

2 hours ago, donttouchmethere said:

• d3d9.dll
• enbhost.exe
• enblocal.ini

i have only put this 3 in the skyrim folder is that right i mean they so menny more files in enboost

[Guest]

Your crash happens on function TESV.exe+0x866D50, which seems to be a PapyrusVM cleanup function (that resets the bits of Papyrus data).

The crash happens due to a buffer overflow caused by an invalid buffer size. The cleanup code zeroes out the data, 4 bytes at a time, with the total number of bytes to be zeroed being EAX*4. In your minidump, EAX is 0x3FFFF328, which means 4294954144 bytes to be zeroed (more than the theoretical maximum address range of a 32-bits application), obviously an invalid or corrupted value.

Since this function is called by the PapyrusVM, I would assume some script mod you've is causing the crash. Start renaming some "scripts" folder to "scripts.old" and try loading until you find out which script is causing the crash.

[donttouchmethere]

1 hour ago, surothedeath said:

"hackspeed enable"

It shows this information only once on gamestart in the main menu.

 

15 minutes ago, surothedeath said:

i have only put this 3 in the skyrim folder is that right i mean they so menny more files in enboost

yes, you got the right files there

 

 

[Furryfurry]

9 minutes ago, donttouchmethere said:

It shows this information only once on gamestart in the main menu.

it dosent for me

 

25 minutes ago, Hawk9969 said:

Start renaming some "scripts" folder to "scripts.old" and try loading until you find out which script is causing the crash.

ok i will try that

[donttouchmethere]

39 minutes ago, surothedeath said:

it dosent for me

guess that means it isn't installed correctly ?

 

[Furryfurry]

1 hour ago, donttouchmethere said:

guess that means it isn't installed correctly

???????????

hmm strange i did what it said i put the 3 files in my skyrim folder and type and chance all things need to what did i do wrong?! the only thing i can think of is the light thing he dowloded on the video but it was optemal he said

 

2 hours ago, Hawk9969 said:

Start renaming some "scripts" folder to "scripts.old" and try loading until you find out which script is causing the crash.

do i need to go in and type old scrip or can i just turn off the plug in?

[donttouchmethere]

15 minutes ago, surothedeath said:

hmm strange i did what it said i put the 3 files in my skyrim folder and type and chance all things need to what did i do wrong?! the only thing i can think of is the light thing he dowloded on the video but it was optemal he said

If you only added the 3 files from the ENBseries,

but followed the video for setting up a fully working ENB (instead of only ENBoost),

I have no clue what can happen (or not).

[Furryfurry]

21 hours ago, donttouchmethere said:

ENBseries

well inboost dident work still ctd i am renaiming atm spcrit.old i try too uff plug all plugins with no sucsses "sigh"

[donttouchmethere]

21 hours ago, surothedeath said:

well inboost dident work still ctd i am renaiming atm spcrit.old i try too uff plug all plugins with no sucsses "sigh"

ENBoost works? I mean does it show up in main menu at least?

Great!

That was only one part of the fixes.

 

Next install Crash fixes v12 with the configuration from my blog.

At the end you have 3 things installed:

> SKSE.ini

> ENBoost is installed

> get Crash Fixes v12

 

those steps are only to make your base game more stable.

If you have bugged mods or compatibility issues in your game the fixes won't help.

 

You would need to remove mods until you have a stable game. (it's a bit like that script.old tactic but easier to do I guess)

 

 

[Guest]

I don't think that "engrish" translated to "it worked".

 

In any case, if you are going by renaming the scripts folder of your mods, you must do it with a new save, since your current save will probably have that baked corrupted data in it.

Easy way to do it is to rename half of it and then continue as the crash continues. Easy to do with a script.

 

rename.py:

MODS    = r"C:\...\Mods" # Mods base folder.
START   = 1 # Mod number to start renaming.
PERCENT = 0.5 # Percentage of mods with a scripts folder to rename (0.0 to 1.0).
PREFIX  = ".something.unique" # Prefix to rename scripts to. Ala, scripts.something.unique

# DO NOT EDIT FROM HERE.
import os
import math

all    = [mod for mod in os.listdir(MODS) if os.path.isdir(os.path.join(MODS, mod, "scripts"))]
rename = int(math.ceil(len(all) * PERCENT))

renamed = 0

for (renamed, mod) in enumerate(all[START - 1:START - 1 + rename], 1):
    path = os.path.join(MODS, mod)
    os.rename(os.path.join(path, "scripts"), os.path.join(path, "scripts" + PREFIX))

print("RENAMED: {} mods".format(renamed))

restore.py:

MODS   = r"C:\...\Mods" # Mods base folder.
PREFIX = ".something.unique" # Prefix to rename scripts from. Ala, scripts.something.unique

# DO NOT EDIT FROM HERE.
import os

restored = 0

for mod in os.listdir(MODS):
    path = os.path.join(MODS, mod)
    path_prefix = os.path.join(path, "scripts" + PREFIX)

    if os.path.isdir(path_prefix):
        os.rename(path_prefix, os.path.join(path, "scripts"))
        restored += 1

print("RESTORED: {} mods".format(restored))

Call rename.py from a CMD prompt and note down the number of mods renamed.

 

If the crash continues, call restore.py and now call rename.py again with the printed number of renamed mods from the previous call to rename.py as the value for "START".

If the crash stops, call restore.py and reduce the value of PERCENT until you find out which mod is causing your crash.

 

P.S. Make sure you backup the base folder pointed by "MODS", just in case it screws up.

[Furryfurry]

i thin i found it SexLab - Submit + Devious Devices

ty for helping me it was great help and sorry for my stupididty

 

thank you Hawk9969 and donttouchmethere

[Furryfurry]

nvm its ther again. it is strange i got all mods working and i cud reloda and then all the suden it dont work again