Jump to content
  • 0
Sign in to follow this  
swiftfoxmark2

Mod Organizer cannot load external EXEs

Question

So last night while I was putting together a profile, Mod Organizer started to crash the external executables that are required to load.  Thus far, both WyreBash and LOOT crash when being loaded from Mod Organizer.  In the Event Log, I get the following error entries:

 

Faulting application name: Wrye Bash.exe, version: 305.0.0.0, time stamp: 0x49180193
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x70ebfff6
Faulting process id: 0x2a58
Faulting application start time: 0x01d07656f5c368ac
Faulting application path: D:\Games\Steam\SteamApps\common\Skyrim\WyreBash\Mopy\Wrye Bash.exe
Faulting module path: unknown
Report Id: 337692fe-e24a-11e4-a30d-94de80613480

 

Faulting application name: LOOT.exe, version: 0.6.1.0, time stamp: 0x54974be1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x70ebfff6
Faulting process id: 0x227c
Faulting application start time: 0x01d07657720bcdca
Faulting application path: D:\Games\Steam\SteamApps\common\Skyrim\LOOT\LOOT.exe
Faulting module path: unknown
Report Id: b0709776-e24a-11e4-a30d-94de80613480

Share this post


Link to post
Share on other sites

2 answers to this question

Recommended Posts

  • 0

You will be better served with an issue like this one I think, if you create a new issue in the Bug Genie.

If you detail the steps to replicate this issue and provide links to the logs and any other pertinent details, @Tannin will be able to see why you are getting these crashes.

 

As most users are not seeing these crashes, you will need to be as specific as possible: OS versions, paths to programs, any Anti-virus software, stuff like that. The more you initially provide, the quicker the resolution may present itself.

Share this post


Link to post
Share on other sites
  • 0

I managed to fix it.

 

I uninstalled MO from the directory I had it in and moved it to another.  It works fine now even though I had to set up all my executables again.

 

There may have been a malicious trojan attached to MO.  It definitely didn't come from the MO devs, of course, probably just something that latches on to the most used program.  That may have been causing issues.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.