Jump to content

Phantom alias/quest causing CTD?


Rayblue

Recommended Posts

Posted

Is there some way to kill this damn thing from crashing up my game? I did every update and nostrum, but to no avail as it keeps on spamming the Papyrus log:

 

[03/12/2013 - 01:04:45AM] Error: Unable to call GetReference - no native object bound to the script object, or object is of incorrect type
stack:
[<NULL alias> (0) on <NULL quest> (00000000)].SwapJobAliasScript.GetReference() - "<native>" Line ?
[<NULL alias> (0) on <NULL quest> (00000000)].SwapJobAliasScript.GetActorReference() - "ReferenceAlias.psc" Line 37
[<NULL alias> (0) on <NULL quest> (00000000)].SwapJobAliasScript.GetActorRef() - "ReferenceAlias.psc" Line 47
[<NULL alias> (0) on <NULL quest> (00000000)].SwapJobAliasScript.OnUpdate() - "SwapJobAliasScript.psc" Line 20
[03/12/2013 - 01:04:45AM] Error: Unable to call GetReference - no native object bound to the script object, or object is of incorrect type
stack:
[<NULL alias> (0) on <NULL quest> (00000000)].SwapJobAliasScript.GetReference() - "<native>" Line ?
[<NULL alias> (0) on <NULL quest> (00000000)].SwapJobAliasScript.GetActorReference() - "ReferenceAlias.psc" Line 37
[<NULL alias> (0) on <NULL quest> (00000000)].SwapJobAliasScript.GetActorRef() - "ReferenceAlias.psc" Line 47
[<NULL alias> (0) on <NULL quest> (00000000)].SwapJobAliasScript.OnUpdate() - "SwapJobAliasScript.psc" Line 20

 

Note to mods: move this to the Technical Support section; I was so PO'ed about the crash that I didn't notice I posted this here.

Posted

I got it: I first deactivated and reactivated Hearthfire in an attempt to reset everything, but this resulted into this problem that eventually came to the point it was causing CTDs.

  • 8 months later...
Posted

I recently noticed the same problem but not the same mod issue. This problem seems caused by SKSE, the ClearInvalidRegistration=1 setting. I found that if you put the SKSE INI tweak into work, you could never properly uninstall any mod with scripts included. If you do, the skyrim log turns crazy messing up with so many null error records relating to the mod reinstalled or updated.

 

I cannot figure out how to solve the problem exactly. The only way to get rid of this is back to the former saves or clean up the entire script content of your current save. Searching for someone could solve this problem.

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

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