Unrecoverable Error when starting Vortex 1.1.14

[HadToRegister]

Sorry I couldn't report this the proper way, as there is no log of the error, and instead just a pop up screen.

I think the problem MIGHT be, that while Vortex was still 'getting ready' when I clicked to go somewhere else in the program, caused it to 'overload' and caused an error

Started vortex the first time, ...the circles were spinning next to the MODS and PLUGINS entry, I clicked on MODS and got the error pop up.
Quit to the Desktop, started Vortex again, while the circles were spinning in front of MODS and PLUGINS, I clicked SETTINGS, and got the pop up again.
Quit to the desktop, started Vortex again, and while the Circles were spinning in front of MODS and PLUGINS, I didn't touch ANYTHING, and Vortex started without error.

So, maybe I was asking Vortex for too much, too soon?

Anyway, here's the Unrecoverable Error pop up.

[Guest deleted34304850]

i'm going to suggest - power down your machine - start it up - try vortex again. what i'm going for here is a clean deck scenario.

 

if - you get the similar spinning wheels (i got this on my recent issues with weirdly random disabled plugins), let vortex run and run until it gets to where it's caught up with itself - if you have sysinternals tools (free from microsoft) - you can fire up process explorer and have it filter on vortex to see what its doing, while the wheels are spinning - you may be able to get an understanding of what its working on.

 

also one other thing - the disk where your mods/plugins/data resides, is that a solid state or a hdd? if its the latter you may wanna throw a defrag at it - you can download and use a program called defraggler which can be used to defrag a specific file rather than an entire disk which can help.

 

give those a go and see what occurs?

 

if there is no change it may be that your vortex install has developed a problem - i'd attempt a re-install of it - then a restart and see what occurs?

[Tannin42]

Thanks for the report. Yeah, apparently it's trying to access the data structure storing file conflicts at a time where those conflicts haven't been determined yet.

There is no solution right now except giving it a moment after startup.