EXCEPTION_ACCESS_VIOLATION at 0x7FF688070DCF SkyrimSE.exe+02E0DCF

[jntrgf]

Anyone with with crashlogger knowledge willing to help me find out why installing BaC causes this?

2026-06-20-07-01-44.log

[flutie]

have you Forgotten city installed? If so, thet may be the culprit, BGS Story teller is associated with that mod

 

[traison]

23 minutes ago, flutie said:

...BGS Story teller is associated with that mod...

 

This is a vanilla game concept, not specific to any individual mod.

 

3 hours ago, jntrgf said:

Anyone with with crashlogger knowledge willing to help me find out why installing BaC causes this?

 

The answer to your question is in RSP+20, RSP+48 and RSP+90. If you want more, either use a debugger or switch to Crash Logger SSE.

[jntrgf]

Seems to be and issue with an npc or quest going by name.

crash-2026-06-20-22-48-28.log

Edited June 21 by jntrgf

[traison]

It tried to dereference RCX at a time when it was 0x0 - there's a null pointer somewhere. The object it is having issues with is reference id 0x3D010589 from "bac.esp", referenced from form id 0x3D00EA6E "Hammerheart". Since the BGSStoryTeller seems to be involved, you should also consider all relevant SMBN, SMEN and SMQN records. I'd start with the ones in bac.esp.

 

So:

1. Inspect 0x3D010589 in xEdit and make sure there's no null references or unassigned fields that should be properly assigned. Use another REFR record to compare to if needed. I would also follow this reference to the object it is referencing and do the same inspection there.
2. Do the same for 0x3D00EA6E.
3. Inspect the Story Manager records in bac.esp.

[jntrgf]

11 hours ago, traison said:

It tried to dereference RCX at a time when it was 0x0 - there's a null pointer somewhere. The object it is having issues with is reference id 0x3D010589 from "bac.esp", referenced from form id 0x3D00EA6E "Hammerheart". Since the BGSStoryTeller seems to be involved, you should also consider all relevant SMBN, SMEN and SMQN records. I'd start with the ones in bac.esp.

 

So:

1. Inspect 0x3D010589 in xEdit and make sure there's no null references or unassigned fields that should be properly assigned. Use another REFR record to compare to if needed. I would also follow this reference to the object it is referencing and do the same inspection there.
2. Do the same for 0x3D00EA6E.
3. Inspect the Story Manager records in bac.esp.

It's a ZaZ version mismatch. Thanks for all the help.