Jump to content

Instant Crash with any mod *Fixed*


Recommended Posts

I have verified my files, created a new profile on vortex, and downloaded a few mods. Immediate crash. Then I had to re verify my files and it says I lost a file and had to recover it. Tried a single mod, also crash. Same thing, 1 file failed and had to be re acquired. 

My game is through steam and I have it downloaded to an external hard drive if that matters. I have tried several different single mods and gotten the same result. 

 

I am leaving this up in case anyone else still has these problems, but I noticed that Nexus fixed it, I think. I didn't even take any of the actions suggested in this thread, just hit the button to reset my load order on Vortex and it seemed to clear it all up. Personally haven't had a problem since. But if you are still having this issue and don't want to read through this thread to fid the answer, it seems to be a load order issue. 

Edited by Emperitor
Fixed
  • Like 4
Link to comment
Share on other sites

I'm having this trouble too, and I'm just installing manually. Put ESP in folder and update the plugin txt file, instant crash if I go anywhere near where the mod touches.

Link to comment
Share on other sites

Ditto. No matter which mod I add, the game crashes instantly. After re-verifying my files, Nexus running but no mods on, the game launches as expected. If any mod is enabled, crash. Please halp!

  • Like 1
Link to comment
Share on other sites

I think I found the problem here.

I deleted the plugins.txt file and restored files from steam, copied that one as a backup, then let Vortex install mods and noticed that Vortex seems to add two extra lines to the Plugins.txt folder that should not be there. Then I tried disabling all the mods in Vortex and those two extra lines are still there?

When I delete those two lines the game loads just fine with all the mods.

Go into the Plugins.txt file and delete these lines:

AltarGymNavigation.esp
TamrielLeveledRegion.esp

  • Like 1
Link to comment
Share on other sites

I'll chime in as another sufferer... Tried earllier this afternoon with a mod and caused a

"Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000050"

Disabled the mod (and removed it actually), re-verified game files and it worked ok. Just went to install a completely different mod and hit same problem.

 

When verifying game files, it seems to download something (1 file I think) which would suggest that Vortex is changing something and not changing it back when you disable the mod, as game still won't start when mod is disabled (before the verify, that is).

Edited by tassaran
Link to comment
Share on other sites

@guillin's fix worked for me lmao

 

Ditto. After a successful modless launch (both Steam and Vortex), then after enabling any 1 mod and crashing the game, disabling the mod and/or closing Vortex and trying to launch through Steam continues crashing on launch until files are revalidated or the game is reinstalled. Something about Vortex' Ob Remastered plugin seems to be making a permanent change to a single game file that is causing this crash even without Vortex, only fixed by replacing the affected file (still not sure which).

The Crash Reporter pop-up contains:

  Quote

 

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000050

OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
OblivionRemastered_Win64_Shipping
kernel32
ntdll

 

Expand  

I've tried some fixes for "EXCEPTION_ACCESS_VIOLATION" as I google them but so far no luck. The program is set to always run as Admin, all users have Full Control. No malware. No security flags seem to trip when running the program. What am I missing?

Edited by MorbusMactabilis
Fix found
Link to comment
Share on other sites

@guillin Thank you so much this worked. took me an hr to find this about the load order. im not very computer savy so i asked microsoft edge AI to help me with this fix and just posted ur post and it told me what to do step by step. I had a hard time finding my plugins.txt file but that was about it.

Link to comment
Share on other sites

yeah happened to me last night after installing remastered in vortex and installing some mods, i suspected it was the loadorder config because of the way the handler worked in Vortex, found the plugins.txt and i had no point of reference so i copied it, then went to verify (Xbox App informs you it'll wipe out your saves and configs, which i didn't want, so i had to find the local cache location of the saves which are obfuscated, but once i had the directory i just zipped the whole thing, ran verify, checked the plugins.txt and lo, the Oblivion Remastered config for Vortex had munched my load order.

sigh...

In the last 12 months I’ve had zero success with Vortex being coherent with new games, its always a cascade of red alerts every time and big unhandled exceptions 😞 on just basic behaviour like _installing the thing_ behaviour - which sounds like its not even been tested.  Does Nexus audit the configurations before sending them live? you'd hope that's where the money goes right? stability was kinda the goal we all signed on for.  Be great if you could make sure nexus creates a staging config before breaking everything and on try-catch of the inevitable exception it rolls back its changes.  Any change in fact, touching load order is pretty awful without a way to revert.

What happened to the new NMM (or whatever you guys were gonna call it), the last you guys spoke on it a year or 2 ago Vortex was being thrown away in favour of some new NMM, i think Vortex was a node app or something and the devs didn't like that and preferred something else.

is that still happening? Am i just a big silly idiot for continuing to use Vortex? Or are y'all just on some fabulous new Vortex/NMM with the very best exception handlers and whistle bells n bell whistles?

(XboxApp didn't kill the saves btw, perhaps because i had previously asked it not to use cloudsaves and it actually listened, a miracle)

Link to comment
Share on other sites

×
×
  • Create New...