Jump to content

CTD when exiting interior


Recommended Posts

Posted

I'm getting a constant CTD when exiting the armorer in Whiterun please help i'm trapped! I will be forever indebted! I tried uninstalling a bunch of the mods I added right before this behavior but I didn't seem to help.

I'm using MO2, LOOT, GOG Skyrim.

 

here is crashlog: https://pastebin.com/s0EK9mN6

 

Also, since day one ( i only started modding a few days ago) I've been getting an error with Racemenu and GOG Skyrim. It was one of the first 5 mods I installed and it's always given me a "skee64.dll" error, not sure what I could have done wrong.

 

Also, when I uncheck an installed mod in MO2, is that the same as uninstalling it effectively (at least as far as game function and errors? Also why when I uninstalled some mods I get notifications that those mods are gone after I load game? 

 

Sorry for so many questions, any help is greatly appreciated! I need a Modfather (UWU) to adopt me since apparently I'm clueless 😄. LMK if there's anything else you need from me.

Posted

Crash occured because it tried to divide AX by R8, and R8 was 0x0 i.e. division by zero. It most likely had something to do with form id 0x001033F3, but without a disassembler/debugger that's about all I can say. I would start by inspecting everything related to that record. Which mods edit it, where are the conflicts. Since its a static, it should have a mesh. Which mod provides the mesh, do you have alternatives? What about the textures associated with this mesh?

Posted (edited)
36 minutes ago, traison said:

Crash occured because it tried to divide AX by R8, and R8 was 0x0 i.e. division by zero. It most likely had something to do with form id 0x001033F3, but without a disassembler/debugger that's about all I can say. I would start by inspecting everything related to that record. Which mods edit it, where are the conflicts. Since its a static, it should have a mesh. Which mod provides the mesh, do you have alternatives? What about the textures associated with this mesh?

Thank you so much for the response! Could you ELI5? I'm willing to do anything needed, but tbh, I'm not really sure of the meaning of anything you said here :(

Edited by Octopussy
Posted
1 hour ago, Octopussy said:

I've been getting an error with Racemenu and GOG Skyrim. It was one of the first 5 mods I installed and it's always given me a "skee64.dll" error, not sure what I could have done wrong.

I would guess that the GOG version of Skyrim has its own version of skee64.dll. Go to the Silverlock site and it will have a GOG version listed if such a beast exists. Alternatively RaceMenu is also picky about which version of Skyrim which version of RM will work with.

You will need to keep an eye open when you download mods to make sure they will work with GOG. Most will and most of the rest will have a GOG friendly version (as I understand it).

 

1 hour ago, Octopussy said:

Also, when I uncheck an installed mod in MO2, is that the same as uninstalling it effectively (at least as far as game function and errors?

Yes.

 

1 hour ago, Octopussy said:

Also why when I uninstalled some mods I get notifications that those mods are gone after I load game?

Because there is info baked into the save including what mods were used. This is one of the reasons why it is generally recommended to start a fresh game when trying to trouble-shoot.

 

You could try rolling back to before you installed the group of mods, and try to exit Warmaiden's. If you can exit without the mods then add one mod at a time and try again until you find a suspect.

Posted
1 hour ago, Octopussy said:

Could you ELI5?

 

I'd rather not. We can't do a 1-on-1 with everyone wanting to get into modding Skyrim. You need to know these things before you start modding:

  1. File conflict resolution with your mod manager.
  2. Plugin record conflict resolution with xEdit.
  3. Mesh inspection/editing with NifSkope.
  4. Texture inspection/editing with Paint.NET, Photoshop or Microsoft's DDS utilities.

So when I say inspect 0x001033F3, you should know this is a job for xEdit.

  • 2 weeks later...
Posted
On 2/27/2025 at 12:10 PM, Grey Cloud said:

I would guess that the GOG version of Skyrim has its own version of skee64.dll. Go to the Silverlock site and it will have a GOG version listed if such a beast exists. Alternatively RaceMenu is also picky about which version of Skyrim which version of RM will work with.

You will need to keep an eye open when you download mods to make sure they will work with GOG. Most will and most of the rest will have a GOG friendly version (as I understand it).

 

Yes.

 

Because there is info baked into the save including what mods were used. This is one of the reasons why it is generally recommended to start a fresh game when trying to trouble-shoot.

 

You could try rolling back to before you installed the group of mods, and try to exit Warmaiden's. If you can exit without the mods then add one mod at a time and try again until you find a suspect.

Thank for being patient with a noob! As for the Racemenu issues, it's still not fixed. I double-checked that the one I downloaded was GOG specific, and it was. I only started Skyrim two weeks ago, so nothing is out of date. Really weird! Any other ideas?

 

 

Posted
On 2/27/2025 at 12:49 PM, traison said:

 

I'd rather not. We can't do a 1-on-1 with everyone wanting to get into modding Skyrim. You need to know these things before you start modding:

  1. File conflict resolution with your mod manager.
  2. Plugin record conflict resolution with xEdit.
  3. Mesh inspection/editing with NifSkope.
  4. Texture inspection/editing with Paint.NET, Photoshop or Microsoft's DDS utilities.

So when I say inspect 0x001033F3, you should know this is a job for xEdit.

Awesome, thank you for giving me stuff I can at least google! I will watch some YouTube videos on this stuff, I don't want to be annoying!

 

Also I posted the same question on the nexus forums, and somebody told me it was Climates of Tamriel that was giving me the issue, so I picked a different weather mod and everything is fine now, except the skee64.dll weirdness.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...