Vortex crashed and corrupted installed mods

[theFuzzyWarble]

Just an FYI, I've crashed 4 times in less than a day doing the normal routine of trying to play. This is a new one for me.

 

The crashed began, appearing as Vortex got hung-up, it blurred slightly and I got a prompt to close it eventually.

Only once, did I get a Low on Memory error prior to hanging. So I rebooted and continued. It happened again sometime after reboot.

 

Each time, I crashed and restarted I got an option to backup and repair but it salvaged nothing complete.

I leadrned down the line each time I had to reinstall each broken mod and re-prioritize it.

[rmm200]

You did not ask for support, so I won't go with the standard "Provide more information".

I will comment it is not necessary for Vortex to be running to play your games.

Don't use Vortex unless you want to install a new mod. It sounds like you have enough computer issues without it.

[theFuzzyWarble]

I didn't ask, no.

 

I don't have any issues using my machine apart from this, so when this is all I'm really doing when it happens I come here.

I've followed best practices I've read. The steam/vortex/the game aren't installed in the program files\[x86], everything is on a secondary ssd.

So, I'm just merely reporting my experience using Vortex and hoping it's not just me and maybe finding a pointer to some underlying issue.

 

Vortex is always running, as I'm usually in the middle of testing builds/mods, but good to know it doesn't have to be open for a normal playthrough.

 

I created and run a batch file to dump anything running that takes up memory and gpu resources, especially chrome instances. When I have a bunch of these open while testing, I disregard the warning for obvious reasons. But when it pops up and nothing else is running but what's needed, it's concerning.

 

Additionally concerning is that I've been using Vortex since the public launch, and I've never had these issues.

The crashing issue stopped by the way only to be followed by an occasional freeze up while deploying, then vortex asking for permissions to access files it had no problem accessing for days and weeks prior.

 

I'm weary of the inevitability that the build is compromised on the system level but with no idea where or why, I'm just looking to repeat what's probably an unknown bad practice. So for now, I push on as is.

 

Thanks