Help Reading Crash Logs

[MattTheRagdoll]

So I recently made the jump to AE, got a really good and stable build of skyrim up and running, except for one or two bugs. I and getting a CTD on the roads in a couple of places, I'm fairly certain it's due to errors in facegeom data. Just looking for some help in reading/interpreting the output from the AE crash log to narrow down the culprit. See attached doc which has my most recent log. If anyone can give me some general advice on how to read the log and if/how I can narrow down my search it would be much appreciated!

crash-2022-08-15-09-31-14.log

[davisev5225]

You are correct that it's crashing due to facegen data.  Specifically, it's from Skyrim Immersive Creatures.  There may also be a SMP physics bug at work, since I see hdtSMP64.dll referenced near the top of the stack.

 

There's also a couple instances of invalid form pointers that you should look into.  (Any form starting with 0xFF is invalid.)

Edited August 15, 2022 by davisev5225

[MattTheRagdoll]

14 minutes ago, davisev5225 said:

You are correct that it's crashing due to facegen data.  Specifically, it's from Skyrim Immersive Creatures.  There may also be a SMP physics bug at work, since I see hdtSMP64.dll referenced near the top of the stack.

 

There's also a couple instances of invalid form pointers that you should look into.  (Any form starting with 0xFF is invalid.)

 

I saw Immersive creatures referenced and assumed it must have been something loaded after that, but you could very well have it! I doubt it's SMP as that is only used for capes and the occasional ks hairdo (none of which were in use at the point were I am gettig the crash). Thanks for brining up the pointers, I have noticed it refernced in the console on occasion, need to nail that sneaky little critter down as well!

 

[davisev5225]

15 minutes ago, MattTheRagdoll said:

 

I saw Immersive creatures referenced and assumed it must have been something loaded after that, but you could very well have it! I doubt it's SMP as that is only used for capes and the occasional ks hairdo (none of which were in use at the point were I am gettig the crash). Thanks for brining up the pointers, I have noticed it refernced in the console on occasion, need to nail that sneaky little critter down as well!

 

 

A crash stacktrace will always spit out debug info for the exact memory address(es) that caused the unrecoverable exception.  It's never "what loaded after" what you see in the log, it's exactly what the log shows.  In this case, you're lucky that a couple of the entries in the stack reference the Skyrim form IDs, that should help you narrow things down a little.  Usually you just get memory addresses, which while looking similar to form IDs, actually have nothing to do with them and are semi-random/arbitrary.

[MattTheRagdoll]

15 hours ago, davisev5225 said:

 

A crash stacktrace will always spit out debug info for the exact memory address(es) that caused the unrecoverable exception.  It's never "what loaded after" what you see in the log, it's exactly what the log shows.  In this case, you're lucky that a couple of the entries in the stack reference the Skyrim form IDs, that should help you narrow things down a little.  Usually you just get memory addresses, which while looking similar to form IDs, actually have nothing to do with them and are semi-random/arbitrary.

Thanks for all the advice, I realised vortex had not enabled the esp for the immersive creatures and immersive sounds patch. Enabled it and issue is now resolved! Still looking into the missing object calls.

[davisev5225]

4 hours ago, MattTheRagdoll said:

Thanks for all the advice, I realised vortex had not enabled the esp for the immersive creatures and immersive sounds patch. Enabled it and issue is now resolved! Still looking into the missing object calls.

 

Glad that was easy.

 

Don't worry too much about the invalid form IDs, some mods do that deliberately to store script data/variables.  If you're no longer crashing, you can safely ignore them.