crashing. What does this log mean?

[Farm98765]

attaching my modlist, too

crash-2026-06-16-23-08-31.log

test1.txt

Edited June 16 by Farren421

[pinky6225]

Running the log through google AI gives

This crash log pinpoints a failure caused directly by the Advanced Animation Framework (AAF) mod (AAF_1_11_221.DLL) attempting to push a Papyrus debug message to the screen via the game engine.

The immediate culprit is a broken dialogue/notification string inside a mod dependent on AAF. The game engine expected a numeric variable to fill a placeholder, but it received a standard text phrase instead ("Well, People are a lot more Friendier Nowadays"). This caused a memory instruction failure (EXCEPTION_ACCESS_VIOLATION), resulting in an instant crash to the desktop.

Apply the following steps to resolve this crash:

1. Re-install or Disable Outdated AAF Add-ons

The crash is stemming from a broken script or XML configuration file in an AAF sub-mod, rather than base AAF itself.

• Look through your active mod list for any mods that introduce dialogue, custom NPC interactions, or companion comments that might use the line "Well, People are a lot more Friendier Nowadays".
• Ensure that any translation patches, dialogue overhauls, or character pose/animation packages are entirely up to date and match your current AAF build.

2. Force Papyrus to Handle Script Loads Safely

Your log shows that standard memory allocations for scripts are disabled (FixScriptPageAllocation: false). Turning this option on gives the script engine breathing room to recover from bad formatting rather than crashing the game outright.

1. Navigate to your Fallout 4 installation directory: Fallout 4/Data/F4SE/Plugins/
2. Open Buffout4.toml using a text editor (like Notepad).
3. Find the line FixScriptPageAllocation = false and change it to true.
4. Save and close the file.

 

The bit of dialogue it mentions is from AAF_AutonomyEnhanced.esp so trying without that would be my first step to make sure that is the issue

 

Then you could try what the AI mentions with buffout4 setting to see if it lets you get around it

[Farm98765]

12 hours ago, pinky6225 said:

Running the log through google AI gives

 

  Hide contents

 

This crash log pinpoints a failure caused directly by the Advanced Animation Framework (AAF) mod (AAF_1_11_221.DLL) attempting to push a Papyrus debug message to the screen via the game engine.

The immediate culprit is a broken dialogue/notification string inside a mod dependent on AAF. The game engine expected a numeric variable to fill a placeholder, but it received a standard text phrase instead ("Well, People are a lot more Friendier Nowadays"). This caused a memory instruction failure (EXCEPTION_ACCESS_VIOLATION), resulting in an instant crash to the desktop.

Apply the following steps to resolve this crash:

 

1. Re-install or Disable Outdated AAF Add-ons

The crash is stemming from a broken script or XML configuration file in an AAF sub-mod, rather than base AAF itself.

• Look through your active mod list for any mods that introduce dialogue, custom NPC interactions, or companion comments that might use the line "Well, People are a lot more Friendier Nowadays".
• Ensure that any translation patches, dialogue overhauls, or character pose/animation packages are entirely up to date and match your current AAF build.

 

2. Force Papyrus to Handle Script Loads Safely

Your log shows that standard memory allocations for scripts are disabled (FixScriptPageAllocation: false). Turning this option on gives the script engine breathing room to recover from bad formatting rather than crashing the game outright.

1. Navigate to your Fallout 4 installation directory: Fallout 4/Data/F4SE/Plugins/
2. Open Buffout4.toml using a text editor (like Notepad).
3. Find the line FixScriptPageAllocation = false and change it to true.
4. Save and close the file.

 
 

The bit of dialogue it mentions is from AAF_AutonomyEnhanced.esp so trying without that would be my first step to make sure that is the issue

 

Then you could try what the AI mentions with buffout4 setting to see if it lets you get around it

 

So it wasn't that, I THINK? uhhhhh, i did some fiddling so here's another crash log. Crashed just after the animation for sex started

crash-2026-06-18-04-59-56.log

[Farm98765]

added update, I downloaded some dependencies i was missing. Here's the newest crashlog

crash-2026-06-19-02-26-32.log

[deff.]

33 minutes ago, Farm98765 said:

added update

 

Well. . xSE Plugin Preloader must be placed manually in Fallout 4 root folder, not installed with mod manager. 

 

I assume that you have AE game version and you followed The Fcking manual. That your ctd - it appears when you launch animations manually? Or crash appears when mod triggers? If animations playing fine manually then you have to look which mod triggers animation when you have ctd. 

[Farm98765]

On 6/18/2026 at 11:17 PM, deff. said:

 

Well. . xSE Plugin Preloader must be placed manually in Fallout 4 root folder, not installed with mod manager. 

 

I assume that you have AE game version and you followed The Fcking manual. That your ctd - it appears when you launch animations manually? Or crash appears when mod triggers? If animations playing fine manually then you have to look which mod triggers animation when you have ctd. 

I'm doing a fresh install, again, I'm 100% sure i followed the guide fully, but i guess something still went wrong. will update again later

[dav42]

20 hours ago, Farm98765 said:

I'm doing a fresh install, again, I'm 100% sure i followed the guide fully, but i guess something still went wrong. will update again later

 

AAF is the problem, it's a known issue the notification bug.  The keyword issue is probably a different bug in AAF, but at least in both cases the stack trace shows immediately on the stack is AAF's DLL.

[Farm98765]

4 hours ago, dav42 said:

 

AAF is the problem, it's a known issue the notification bug.  The keyword issue is probably a different bug in AAF, but at least in both cases the stack trace shows immediately on the stack is AAF's DLL.

I've reinstalled AAF and it still happens. What's the fix, if any?

[dav42]

5 hours ago, Farm98765 said:

I've reinstalled AAF and it still happens. What's the fix, if any?

 

I would use an older version of AAF, or report the problem on AAF Discord/support thread and wait for an update.  AAF 0.171beta - 1.1.5 all work fine on latest AE update, you just have to replace the bundled LLFP DLLs with the latest versions from the LLFP thread.

[Farm98765]

On 6/22/2026 at 4:33 AM, dav42 said:

 

I would use an older version of AAF, or report the problem on AAF Discord/support thread and wait for an update.  AAF 0.171beta - 1.1.5 all work fine on latest AE update, you just have to replace the bundled LLFP DLLs with the latest versions from the LLFP thread.

i can't seem to find the old version on their discord or elsewhere. Know anyplace to find it?

[judge007]

6 hours ago, Farm98765 said:

i can't seem to find the old version on their discord or elsewhere. Know anyplace to find it?

 

AAF_V1-1-5.7z