Khayla Crash

[tlrd]

Another day another issue, This time with the khajiit named Khalya. I've had a crash when going to Markarth and now upon exciting Whiterun. The only mod affecting her is the unoffical patch.

crash-2025-08-24-20-57-22.log crash-2025-08-23-03-12-57.log

[traison]

Your issue is coming from Papyrus. Post the Papyrus log from a session that crashed.

[tlrd]

33 minutes ago, traison said:

Your issue is coming from Papyrus. Post the Papyrus log from a session that crashed.

I didn't have logging enabled so I'll post if it crashes again like that. got another crash though that i think is related to hdt-smp. Also do you have a way to donate to you? You've helped me out alot and are always on the technical forum helping people just wanted to give back.

crash-2025-08-24-05-36-34.log

[traison]

 

4 minutes ago, tlrd said:

Also do you have a way to donate to you?

 

Donations should go to LL or Crash Logger. They're the ones providing the platform and tools.

 

5 minutes ago, tlrd said:

...got another crash...

 

It's having issues with a BSLightingShaderMaterial node in a BSTriShape named " (4E061BEF)[1]/ (4E061BEE) [ 0%]". This was worn by reference id 0xFF0014FB "Thalmor Justiciar" in form id 0x000099F7 "Wilderness".

 

Since this is a shader issue, I'd start by disabling CS/ENB, then if it's still not working:

1. prid 0xFF0014FB
2. inv
3. Make a list of all worn items.
4. Go through these items in xEdit.
5. Find their associated ARMA records.
6. Make a list of the meshes in these records.
7. Consider either looking at these in NifSkope to try to spot a problem, or if the meshes were altered by mods, change or remove those mods.

[tlrd]

Again thank you got some things to look into, and if I crash again with Khalya I'll post the logs.

[traison]

4 minutes ago, tlrd said:

...and if I crash again with Khalya I'll post the logs.

 

If it's the issue I think it is, you can post any old log too.

[tlrd]

4 hours ago, traison said:

 

If it's the issue I think it is, you can post any old log too.

I guess I've never turned logging on since I started getting my load order up to date so I've got no papyrus logs unfortunately. I have been playing for like 4 hours with no crash going through the load door where I've experienced that Khalya crash. If you have an Idea what might be causing it let me know, I can try it out.

[tlrd]

8 hours ago, traison said:

 

If it's the issue I think it is, you can post any old log too.

Here's my most recent Log

Papyrus.0.log

[traison]

You got over 1400 errors about missing scripts and script properties. XPMSE is also looking for the FNIS scripts and you're most likely using Pandora.

 

So:

1. Sort out those missing scripts and script properties.
2. Install FNIS alongside Pandora, copy the scripts from FNIS into Pandora or reinstall XPMSE such that it doesn't use FNIS features.

While this Papyrus log is a mess, it doesn't contain anything that would crash the game (as far as I know). But like you said, you haven't managed to get it to crash as it did previously, so that makes sense. Fixing the things above may not fix the crashing issue, but those should still be done.

[tlrd]

On 8/25/2025 at 5:47 AM, traison said:

You got over 1400 errors about missing scripts and script properties. XPMSE is also looking for the FNIS scripts and you're most likely using Pandora.

 

So:

1. Sort out those missing scripts and script properties.
2. Install FNIS alongside Pandora, copy the scripts from FNIS into Pandora or reinstall XPMSE such that it doesn't use FNIS features.

While this Papyrus log is a mess, it doesn't contain anything that would crash the game (as far as I know). But like you said, you haven't managed to get it to crash as it did previously, so that makes sense. Fixing the things above may not fix the crashing issue, but those should still be done.

Two question for sorting out the missing scripts and script properties should I look for errors such as "Error: Script QF_HRI_Events_Quest_WEWerebe_0402904A cannot be bound to HRI_Events_Quest_WEWerebearVsVigilants (4602904A) because the script does not exist or is not currently loaded" ?  and would the XPMSE issue cause this crash it refences "ninode" and xpmse?  Sorry to keep bothering you my knowledge when it comes to scripting and animation stuff is...lacking to put it politely. Once again thank you so much for the continued help!

crash-2025-08-27-02-27-21.log

Edited August 27, 2025 by tlrd

[traison]

5 hours ago, tlrd said:

...should I look for errors such as "Error: Script QF_HRI_Events_Quest_WEWerebe_0402904A cannot be bound to HRI_Events_Quest_WEWerebearVsVigilants (4602904A) because the script does not exist or is not currently loaded" ?

 

That's one of them yes. Mod index is 46, form id within that mod is 2904A. It's most likely a quest. The easy way out of it is to open this in xEdit and remove the script reference. The way to fix this properly is to first determine whether or not this *should* exist, or if its perhaps leftovers from refactoring. If it should exist, then obtain or create the script:

• Maybe it's part of a dependency you missed?
• If the script is essential for the mod's functionality, but it can't be obtained from anywhere, you'd have to create the script and its functionality yourself.

5 hours ago, tlrd said:

...would the XPMSE issue cause this crash it refences "ninode" and xpmse?

 

No.

 

5 hours ago, tlrd said:

<crash log>

 

This is a different problem from what you posted before.

 

In this one it looks like something is doing a recursive walk over the entire skeleton, and something went wrong when it came to an NiNode named "NPC R Finger10 [RF10]". I would disable the following dlls and test again. Maybe do it one at a time, otherwise you won't know which one it is if something changes. hdtSMP64.dll is looking the most suspicious, but it was probably ImmersiveEquipmentDisplays.dll that started it.

 

ImmersiveEquipmentDisplays.dll
BetterThirdPersonSelection.dll
hdtSMP64.dll