Jump to content
  • 0

CTD outside of Riften - Unhandled exception "EXCEPTION_ACCESS_VIOLATION"

TheCashman

Asked by TheCashman,

 Share

Question

TheCashman Citizen

TheCashman

Posted
Posted (edited)

Recently completed the current STEP guide with appropriate adjustments for outdated SKSE plugins where necessary. Got STEP up and running and then added a few mods on top of it:

  • Open World Loot
  • Reliquary of Myth
  • Unique Item Tweaks
  • ArteFakes
  • Morrowloot Miscellania - Item Distribution Module
  • Armor Variants Expansion
  • Reforging - To the Masses (Weapons Expansion)
  • Elsopa HD Shields Standalone
  • vpulse08's Standalone Weapons
  • Believable Weapons Standalone
  • Skyrim Revamped Complete Enemy Overhaul + Rebalanced and Releveled Addon
  • Blade and Blunt Combat Overhaul
  • Mator Smashed Patch

(plus all compatability patches)

I'm not sure if any of those mods are the problem, though. Skyrim launches and runs almost perfectly.

I get CTDs persistently outside of Riften as I try to enter the city.

Every crash returns a crash log with an Unhandled exception "EXCEPTION_ACCESS_VIOLATION" [...] error.

Hardware Specs:

  Reveal hidden contents

Partial Crash Log:

  Reveal hidden contents

PasteBin of Full Crash Log .txt

I can't make heads or tails of the crash log and Google hasn't produced any helpful results - just that the error means that Skyrim is trying to access something it can't...

With some direction I can probably resolve the issue, help would be appreciated. Love this modlist, hope I don't have to alter it too much...

Edited by TheCashman

16 answers to this question

Recommended Posts

  • 0
Mousetick Emperor

Mousetick

Posted
Posted
  On 12/14/2022 at 6:53 PM, z929669 said:

All I know is there's nothing wrong with this particular Glaciers LOD Meshes NIF and DynDOLOD, so it must be some interaction with another asset or plugin reference with this NIF that is causing the issues reported.

Expand  

I think so too. There are no icebergs in Riften, or in the Rift, as far as I know :) Could be a combination of this mesh + another mod (+ ENB) (+ DynDOLOD).

OP should load whole load order in xEdit and look at all the references of 000A98F8 <IcebergSmall02> and 000180E5 <IcebergSmall02_HeavySN>. See if there are any added by mods. In vanilla, there are 98, and 54 references, respectively.

  • 1
z929669 Akatosh

z929669

Posted
Posted
  On 12/14/2022 at 5:13 PM, TheCashman said:

meshes\lod\ice\icebergsmall02_lod.nif is from Glacier LOD Meshes, nothing else touches that file. Ensured I downloaded and installed just the main file as per instructions.

If it's related to lighting shaders, it wouldn't have anything to do with my ENB (Silent Horizons for Cathedral Weathers), since that's post processing, right? Want to make sure I'm covering every potential angle

Expand  

meshes\lod\ice\icebergsmall02_lod.nif from Glacier LOD Meshes should be fine, but your crash report references several nodes that don't exist in this mesh from that mod: 

[RSP+60 ] 0x26D7F12DC00      (BSTriShape*)
        Name: "IcebergSmall02:0"
        RTTIName: "BSTriShape"
        Flags: kSelectiveUpdate | kSelectiveUpdateTransforms | kSelectiveUpdateController | kNoAnimSyncS | kRenderUse | kPreProcessedNode
        Full Name: ""
        File: "lod\ice\icebergsmall02_lod.nif"
        Checking User Data: -----
            Object Reference:
            File: "DynDOLOD.esm"
            Flags: 0x00000009 kDestructible | kInitialized
            FormID: 0x190026F7
            FormType: Static (34)
        Checking Parent: 0
            Name: "IcebergSmall02"
            RTTIName: "BSFadeNode"
            Flags: kSelectiveUpdate | kSelectiveUpdateTransforms | kSelectiveUpdateController | kNoAnimSyncS | kPreProcessedNode
            Full Name: ""
            File: "lod\ice\icebergsmall02_lod.nif"
            Checking User Data: -----
                Object Reference:
                File: "DynDOLOD.esm"
                Flags: 0x00000009 kDestructible | kInitialized
                FormID: 0x190026F7
                FormType: Static (34)
            Checking Parent: 24
                RTTIName: "NiNode"
                Flags: kSelectiveUpdate | kSelectiveUpdateTransforms | kSelectiveUpdateController | kAlwaysDraw | kFixedBound
                Checking Parent: 3
                    RTTIName: "BSMultiBoundNode"
                    Flags: kSelectiveUpdate | kSelectiveUpdateTransforms | kSelectiveUpdateController | kAlwaysDraw | kFixedBound | kPreProcessedNode
                    Checking Parent: 15
                        Name: "ObjectLODRoot"
                        RTTIName: "NiNode"
                        Flags: kSelectiveUpdate | kSelectiveUpdateTransforms | kSelectiveUpdateController | kAlwaysDraw | kFixedBound
                        Checking Parent: 3
                            Name: "shadow scene node"
                            RTTIName: "ShadowSceneNode"
                            Flags: kSelectiveUpdate | kSelectiveUpdateTransforms | kSelectiveUpdateController | kAlwaysDraw | kFixedBound
                            Checking Parent: 1
                                Name: "WorldRoot Node"
                                RTTIName: "SceneGraph"
                                Flags: kSelectiveUpdate | kSelectiveUpdateTransforms | kSelectiveUpdateController | kAlwaysDraw | kFixedBound
        Name: "IcebergSmall02:0"

image.png

I don't fully understand what the report is calling out, but meshes\lod\ice\icebergsmall02_lod.nif from Glacier LOD Meshes uses NiTriShape and not BSTriShape (among several other differences). Step also uses this mod and that specific mesh without issue.

Are you sure there is no other model with that name in your mods?

EDIT: looking at the Nexus source mod page, I don't see that this file is provided in any of the other files out there ... are you running the latest version?

  • 1
z929669 Akatosh

z929669

Posted
Posted
  On 12/14/2022 at 6:42 PM, Mousetick said:

BSTriShape is the internal term used by the engine's data structures/code. It's not the same terminology as the NIF. The name of the node itself in the crash log is "IcebergSmall02:0" (same as the name of the NiTriShape in NifSkope).

Expand  

I just saw "NiNode" and "BsMultiBoundNode" as well as indents rolling up to "IcebergSmall02:0", and those don't exist in that NIF either. So I have no idea why nodes that don't exist in the model are referenced by the report.

Similarly, two flags are also not evident in the NIF (not ticked in the BsFadeNode flags) ... 

kRenderUse | kPreProcessedNode

again, it's likely because I have little idea of what exactly is be referenced in these crash reports.

All I know is there's nothing wrong with this particular Glaciers LOD Meshes NIF and DynDOLOD, so it must be some interaction with another asset or plugin reference with this NIF that is causing the issues reported.

  • 0
duy123a Thane

duy123a

Posted
Posted (edited)
  On 12/14/2022 at 2:13 AM, TheCashman said:

Recently completed the current STEP guide with appropriate adjustments for outdated SKSE plugins where necessary. Got STEP up and running and then added a few mods on top of it:

  • Open World Loot
  • Reliquary of Myth
  • Unique Item Tweaks
  • ArteFakes
  • Morrowloot Miscellania - Item Distribution Module
  • Armor Variants Expansion
  • Reforging - To the Masses (Weapons Expansion)
  • Elsopa HD Shields Standalone
  • vpulse08's Standalone Weapons
  • Believable Weapons Standalone
  • Skyrim Revamped Complete Enemy Overhaul + Rebalanced and Releveled Addon
  • Blade and Blunt Combat Overhaul
  • Mator Smashed Patch

(plus all compatability patches)

I'm not sure if any of those mods are the problem, though. Skyrim launches and runs almost perfectly.

I get CTDs persistently outside of Riften as I try to enter the city.

Every crash returns a crash log with an Unhandled exception "EXCEPTION_ACCESS_VIOLATION" [...] error.

Hardware Specs:

  Reveal hidden contents

Partial Crash Log:

  Reveal hidden contents

PasteBin of Full Crash Log .txt

I can't make heads or tails of the crash log and Google hasn't produced any helpful results - just that the error means that Skyrim is trying to access something it can't...

With some direction I can probably resolve the issue, help would be appreciated. Love this modlist, hope I don't have to alter it too much...

Expand  

Try to remove your Mator Smashed Patch, this is not a plug and play plugin, you need to carefully manual handle it.
If you still crash try to remove all your new mods and test again. Then if it is normal just add them one by one and go to Riften to test it.
Also have you changed any landscape mod after running DynDOLOD ?

Edited by duy123a
  • Like 1
  • 0
TheCashman Citizen

TheCashman

Posted
  • Author
Posted
  On 12/14/2022 at 3:14 AM, duy123a said:

Try to remove your Mator Smashed Patch, this is not a plug and play plugin, you need to carefully manual handle it.
If you still crash try to remove all your new mods and test again. Then if it is normal just add them one by one and go to Riften to test it.
Also have you changed any landscape mod after running DynDOLOD ?

Expand  

I disabled it and still crashed, but I will leave it disabled for now. I learned xEdit and went in to tweak it, but I still didn't really have any idea of what changes to actually make so I just left it as is. I want to go back and learn more at some point.

  On 12/14/2022 at 3:29 AM, Greg said:

It looks as if game is trying to apply a lighting shader to lod\ice\icebergsmall02_lod.nif so do what @duy123a says and re-run DynDOLOD to see if this solves the problem.

Expand  

That reminds me, I forgot to mention I also installed Dawn of Skyrim (cities) and The Great Cities (towns/villages) and made sure to run DynDOLOD after that. I had a few false starts and errors but I got DynDOLOD to complete eventually. I will try rerunning it to see if it makes a difference

  • 0
Mousetick Emperor

Mousetick

Posted
Posted

Check in MO2 where meshes\lod\ice\icebergsmall02_lod.nif comes from. Some of the mods you recently installed may have replaced it with a bugged version.

Also, is this 100% reproducible and the same crash log every time?

  • 0
TheCashman Citizen

TheCashman

Posted
  • Author
Posted
  On 12/14/2022 at 4:58 PM, Mousetick said:

Check in MO2 where meshes\lod\ice\icebergsmall02_lod.nif comes from. Some of the mods you recently installed may have replaced it with a bugged version.

Also, is this 100% reproducible and the same crash log every time?

Expand  

Definitely helpful to know that's the problem file, I'll try that.

Yes, it's the same exact error with that particular .nif file, the numbers will change depending on what area of Riften I'm approaching but it's always the same error.

  • 0
TheCashman Citizen

TheCashman

Posted
  • Author
Posted
  On 12/14/2022 at 4:58 PM, Mousetick said:

Check in MO2 where meshes\lod\ice\icebergsmall02_lod.nif comes from. Some of the mods you recently installed may have replaced it with a bugged version.

Also, is this 100% reproducible and the same crash log every time?

Expand  

meshes\lod\ice\icebergsmall02_lod.nif is from Glacier LOD Meshes, nothing else touches that file. Ensured I downloaded and installed just the main file as per instructions.

If it's related to lighting shaders, it wouldn't have anything to do with my ENB (Silent Horizons for Cathedral Weathers), since that's post processing, right? Want to make sure I'm covering every potential angle

  • 0
Mousetick Emperor

Mousetick

Posted
Posted
  On 12/14/2022 at 5:13 PM, TheCashman said:

If it's related to lighting shaders, it wouldn't have anything to do with my ENB (Silent Horizons for Cathedral Weathers), since that's post processing, right? Want to make sure I'm covering every potential angle

Expand  

No idea, sorry. I don't use any of the ENB and Post-Processing stuff. But it could be related. You may want to explore/experiment in that direction. It could be a waste of time. Have you ever visited that area before in your playthrough? In other words, has it ever worked before you made whatever changes that broke it? Or are you discovering now that it never worked?

Also, have you tried without DynDOLOD? If you have not, I'd suggest you do. Make sure to follow the proper procedure for disabling DynDOLOD. See if you can reproduce the crash once you've made your 'clean save' and disabled DynDOLOD plugins. 

  • 0
TheCashman Citizen

TheCashman

Posted
  • Author
Posted (edited)

Re-running DynDOLOD (without occlusion) did not resolve the issue. Might try with occlusion later.

Update: hiding meshes\lod\ice\icebergsmall02_lod.nif in Mod Organizer resolves the crashes. Obviously that's not a great solution but it helps narrow down the issue. I don't know what effect that will have on the game, I suppose it means DynDOLOD will just use the vanilla mesh for small icebergs?

To me that indicates that the issue is with Glacial LOD Meshes and not DynDOLOD or anything else. I was able to finally find a user with the same issue on the mod's Nexus page, so I'll reach out to them to see if they were able to fix it and keep troubleshooting.

  On 12/14/2022 at 5:46 PM, Mousetick said:

Also, have you tried without DynDOLOD? If you have not, I'd suggest you do. Make sure to follow the proper procedure for disabling DynDOLOD. See if you can reproduce the crash once you've made your 'clean save' and disabled DynDOLOD plugins. 

Expand  

I'm skeptical about ENB so I'll try this first. Thanks!

Edited by TheCashman
  • 0
Mousetick Emperor

Mousetick

Posted
Posted
  On 12/14/2022 at 6:13 PM, TheCashman said:

Update: hiding meshes\lod\ice\icebergsmall02_lod.nif in Mod Organizer resolves the crashes. Obviously that's not a great solution but it helps narrow down the issue. I don't know what effect that will have on the game, I suppose it means DynDOLOD will just use the vanilla mesh for small icebergs?

Expand  

Excellent idea, we should have suggested that earlier. Yes, the game will revert to the vanilla lod mesh for that iceberg, with or without DynDOLOD. It will look slightly different, you may notice the discrepancy with the other glaciers/icebergs viewed in the distance, or not at all :)

Either it's a problem with that particular mesh, though it's strange that no one else here has experienced any issue with it, or it's a side-effect of another problem - the tip of the iceberg, so to speak :)

  • Like 1
  • 0
Mousetick Emperor

Mousetick

Posted
Posted
  On 12/14/2022 at 6:21 PM, z929669 said:

meshes\lod\ice\icebergsmall02_lod.nif from Glacier LOD Meshes uses NiTriShape and not BSTriShape (among several other differences).

Expand  

BSTriShape is the internal term used by the engine's data structures/code. It's not the same terminology as the NIF. The name of the node itself in the crash log is "IcebergSmall02:0" (same as the name of the NiTriShape in NifSkope).

  • Like 1
  • 0
TheCashman Citizen

TheCashman

Posted
  • Author
Posted (edited)

Thanks guys, the additional insight is incredibly helpful. It was just a matter of the crash log being completely foreign to me - now that I have a direction to go in, I should be able to solve the issue. Worst comes to worst I'll just keep the file disabled.

  Quote

OP should load whole load order in xEdit and look at all the references of 000A98F8 <IcebergSmall02> and 000180E5 <IcebergSmall02_HeavySN>. See if there are any added by mods. In vanilla, there are 98, and 54 references, respectively.

Expand  

This is a huge help, I know my way around xEdit well enough now but I wasn't sure where the crash log information fit in. I'll provide any updates in case someone else experiences this problem.

Edited by TheCashman
  • 0
TheCashman Citizen

TheCashman

Posted
  • Author
Posted

Thanks to everyone's guidance I was able to resolve the crash. I found that Dawn of Skyrim referenced 000A98F8 <IcebergSmall02> twice at coc RiftenOrigin within the RiftenWorld space. (See picture)

dosglacierxedit.thumb.png.1a7a39ef26beb0a9fbf533632825c871.png

I'm not quite sure why those are there - I figured it must be a mistake, because as @Mousetick pointed out there are no icebergs in or around Riften. I could coc to RiftenOrigin and play just fine, but found that when I exited into Skyrim and turned toward Riften, I immediately crashed.

I figured it was safe to just remove those references. I ran Skyrim once without running DynDOLOD just out of curiosity, but obviously the crash persisted until I re-generated DynDOLOD (with occlusion just to be safe) 

Turning towards Riften no longer results in an immediate crash - I've played for a few minutes with no problem! In hindsight I suppose the city mod should have been my first guess, but the interaction between it and DynDOLOD + Glacier LOD Meshes was unexpected.

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
 Share
Go to question listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.

  I accept