Importing from MO2 that is NOT is AppData?

[AyamePasse]

A bit of history. I've been using MO2 for a long time, and never had problems on my old computer.

 

My NEW computer, however, has been giving me Blue Screens Of Death while playing Skyrim. The repair guy suggested I try Vortex to eliminate conflicts better. I don't think mods conflicts can cause a blue screen. :/ BUT, until I try his suggestion, and it doesn't help, I can't get much more from him.

 

 

 

 

If I MUST switch to Vortex, I'd REALLY prefer not to have to switch manually, but Vortex REFUSES to believe my MO2 Skyrim setup is anywhere but in AppData on my C drive. My C drive is TINY and can't FIT my Skyrim mod setup. So how do I make Vortex acknowledge my REAL Skyrim MO2 directory?? I browsed to it, and Vortex said "No valid MO2 installation found at this location"

 

Please help! I don't want to do it manually when I'm 99% sure it won't even help my problem!

 

I know it's pretty crummy of me to ask for help while simultaneously saying I don't even want to use the program. I'm willing to accept the possibility that I'd make the switch and like it, but so far, I'm not happy due to issues like this. :(

[HadToRegister]

I think you need to find a new repair guy, how in the heck can switching to Vortex fix your BSOD problem, and Mod Conflicts CERTAINLY don't cause BSODs

Problems I had with Games causing BSOD had to do with SOUND or Graphics

It's also possible you have a bad stick of memory

[AyamePasse]

Ignore this.

[AyamePasse]

I think you need to find a new repair guy, how in the heck can switching to Vortex fix your BSOD problem, and Mod Conflicts CERTAINLY don't cause BSODs

 

Problems I had with Games causing BSOD had to do with SOUND or Graphics

 

It's also possible you have a bad stick of memory

 

 

 

Somehow managed to reply to myself. Lol dumb.

 

100% my thoughts exactly. Unfortunately, I have to choose: stick with the people who honor my 3 year service plan and get it worked on for free, or pay out the wazoo for repairs... Which is unfortunately impossible. They say they ran diagnostics and hardware was fine, so I'm thinking about my Nvidia drivers...

 

Thank you for your reply. :smile: I figured out how to get Vortex to acknowledge my MO2 installation (when I told MO2 to point elsewhere for Skyrim, it didn't copy the ModOrganizer.ini that Vortex looks for from my AppData folder), but so far, its 50% done and only imported 100 of my 500+ mod folders. >.<

[HadToRegister]

 

I think you need to find a new repair guy, how in the heck can switching to Vortex fix your BSOD problem, and Mod Conflicts CERTAINLY don't cause BSODs

 

Problems I had with Games causing BSOD had to do with SOUND or Graphics

 

It's also possible you have a bad stick of memory

 

 

 

Somehow managed to reply to myself. Lol dumb.

 

100% my thoughts exactly. Unfortunately, I have to choose: stick with the people who honor my 3 year service plan and get it worked on for free, or pay out the wazoo for repairs... Which is unfortunately impossible. They say they ran diagnostics and hardware was fine, so I'm thinking about my Nvidia drivers...

 

Thank you for your reply. :smile: I figured out how to get Vortex to acknowledge my MO2 installation (when I told MO2 to point elsewhere for Skyrim, it didn't copy the ModOrganizer.ini that Vortex looks for from my AppData folder), but so far, its 50% done and only imported 100 of my 500+ mod folders. >.<

 

 

 

Honestly you should just stick with what was working for you.

 

It could be something as Mundane as your Video Drivers, but I've never heard of a Load Order causing a BSOD.

[AyamePasse]

 

 

I think you need to find a new repair guy, how in the heck can switching to Vortex fix your BSOD problem, and Mod Conflicts CERTAINLY don't cause BSODs

 

Problems I had with Games causing BSOD had to do with SOUND or Graphics

 

It's also possible you have a bad stick of memory

 

 

 

Somehow managed to reply to myself. Lol dumb.

 

100% my thoughts exactly. Unfortunately, I have to choose: stick with the people who honor my 3 year service plan and get it worked on for free, or pay out the wazoo for repairs... Which is unfortunately impossible. They say they ran diagnostics and hardware was fine, so I'm thinking about my Nvidia drivers...

 

Thank you for your reply. :smile: I figured out how to get Vortex to acknowledge my MO2 installation (when I told MO2 to point elsewhere for Skyrim, it didn't copy the ModOrganizer.ini that Vortex looks for from my AppData folder), but so far, its 50% done and only imported 100 of my 500+ mod folders. >.<

 

 

 

Honestly you should just stick with what was working for you.

 

It could be something as Mundane as your Video Drivers, but I've never heard of a Load Order causing a BSOD.

 

Unfortunately, because my computer is only a few months old, it's only had a few drivers installed. And because I didn't start playing Skyrim again until semi recently (and Skyrim seems to be the best way to experience whatever's causing these BSODs), I'm not even sure if any of my previous drivers were much better. :/ All I can do is install the first one I ever had and work from there.

[Guest deleted34304850]

that's some next level bullshit your repair guy is selling you.

i swear changing a mod manager won't cure a BSOD.

If I were you, I'd get onto the supplier and request they send out someone competent.

Things to try - if you're confident in yourself.

1. ensure everything is connected firmly - no possible loose cables etc

2. ensure the power supply is capable of providing enough power for your system.

3. you may need to reset windows back to default - removing everything from your new system, thus allowing you to start over.

4. run your various driver update programs and make sure everything is updated, including drivers from your pc manufacturer.

5. ensure the bios is up to date.

6. if you have several sticks of ram - remove them, swap them around, make sure they're all seated correctly.

7. run as many diagnostic checks as you can including memtest checks.

 

if - after doing all that you still have issues then you may need to send the unit back to have them check out the cpu/gpu for faults.

 

but the last thing - the very last thing you should be doing, is converting from one mod manager to another in order to resolve your issue.

[Pickysaurus]

MO2 uses significantly more memory than Vortex AFAIK (Inherent to the VFS implementation). As others have said there may be hardware problem of some kind.

[AyamePasse]

that's some next level bulls*** your repair guy is selling you.

i swear changing a mod manager won't cure a BSOD.

If I were you, I'd get onto the supplier and request they send out someone competent.

Things to try - if you're confident in yourself.

1. ensure everything is connected firmly - no possible loose cables etc

2. ensure the power supply is capable of providing enough power for your system.

3. you may need to reset windows back to default - removing everything from your new system, thus allowing you to start over.

4. run your various driver update programs and make sure everything is updated, including drivers from your pc manufacturer.

5. ensure the bios is up to date.

6. if you have several sticks of ram - remove them, swap them around, make sure they're all seated correctly.

7. run as many diagnostic checks as you can including memtest checks.

 

if - after doing all that you still have issues then you may need to send the unit back to have them check out the cpu/gpu for faults.

 

but the last thing - the very last thing you should be doing, is converting from one mod manager to another in order to resolve your issue.

And therein lies my frustration. I'm NOT confident in myself. I know software to an above average degree. But only slightly. I don't have the least bit of confidence that I can find updates for my drivers manually and actually get the correct ones (thus not making my problem WORSE). I don't have confidence that I can open my computer, tinker with its insides, and not screw something up. I don't have confidence that I can do ANYTHING to the BIOS without breaking anything.

 

The support team that I got my service plan through ran diagnostic SOFTWARE, but they didn't look at the hardware at all, and I'd THOUGHT when bringing it in for repairs the second time, that that was what they would do. Look at the hardware, since their driver updates didn't help. Instead, he had me run Skyrim for 5 minutes, which of COURSE didn't crash immediately, then sent me home with a Vortex recommendation.

 

If they can't fix the problem, they THEMSELVES can send it to the manufacturer (which I prefer, because if anything happens to it, they'll cover it, but if I send it in without going through them and something happens to my computer, I'm screwed). But for some reason, they just DIDN'T, so all I can do is try Vortex (which I'm REALLY not liking so far!!), and when it doesn't help, bring it back in with an 'I told you so' and hope they'll FINALLY look at the hardware. Either that, or have the silly thing Blue Screen during something OTHER than Skyrim, which it seems to refuse to do.

[Guest deleted34304850]

i'd love to know what diagnostic software they ran that suggests your problems start and end with vortex.

let me assure you - it absolutely doesn't.

the issue is almost certainly hardware related. stand up to these bozo's and demand they take the correct action. a mod manager - any mod manager canot, by itself, cause a bsod. it can be the victim of a bsod - but a cause? windows doesn't work that way.

 

what they should do if they are in any way competent, is go back to default windows - you can do that yourself very easily if youre on windows 10 - and then diagnose the system. tell them to do that.