Jump to content
  • 0

MO Error


iAmJase

Question

Recommended Posts

  • 0

Okay, let's go back to basics.

Have you ensured that SKSE is installed into the Skyrim folder? This must be done outside of the MO environment.

If yes, then does the game start from the desktop?

If yes, create a new empty profile with no mods at all and try that.

Yes, SKSE is in the Skyrim folder and yes, it starts from the desktop as vanilla Skyrim. I still get the same error through MO. I also tried Skyrim and got the same error except it said TESV.exe. I even tried Skyrim Launcher and it gave me the exact same error except it said SkyrimLauncher.exe.

Link to comment
Share on other sites

  • 0

Those links don't work. Don't worry about fixing them as I don't need to see the errors.

 

One last question, this is the original Skyrim we are discussing isn't it, not Skyrim Special Edition?

The only other time I've seen this error is when the user was trying to run SSE, which is 64bit, in MO 1.3.11.

Link to comment
Share on other sites

  • 0

Those links don't work. Don't worry about fixing them as I don't need to see the errors.

 

One last question, this is the original Skyrim we are discussing isn't it, not Skyrim Special Edition?

The only other time I've seen this error is when the user was trying to run SSE, which is 64bit, in MO 1.3.11.

No, it's the legendary edition.

Link to comment
Share on other sites

  • 0

 

 

[General]
selected_profile=Default
ask_for_nexuspw=true
gamePath=C:\\Games\\steamapps\\common\\Skyrim
motd_hash=2327740679
first_start=false
mod_list_state=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\a\x1\0\0\0\0\0\0\0\0\0\0\0\bT\0\0\0\x3\0\0\0\x4\0\0\0\n\0\0\0\x6\0\0\0\n\0\0\0\x2\0\0\0\n\0\0\x2G\0\0\0\b\x1\x1\0\x1\0\0\0\0\0\0\0\0\x1\0\0\0\x14\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\b\0\0\x1\x15\0\0\0\x1\0\0\0\0\0\0\0P\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x41\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0V\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0K\0\0\0\x1\0\0\0\0\0\0\x3\xe8)
plugin_list_state="@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x2\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x1\x82\0\0\0\x4\x1\x1\0\x1\0\0\0\0\0\0\0\0\x1\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x4\0\0\0\xa1\0\0\0\x1\0\0\0\0\0\0\0\x32\0\0\0\x1\0\0\0\0\0\0\0;\0\0\0\x1\0\0\0\0\0\0\0t\0\0\0\x1\0\0\0\0\0\0\x3\xe8)"
group_state=0
window_geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x2\0\0\0\0\x3m\0\0\0\n\0\0\av\0\0\x2\xf6\0\0\x3u\0\0\0)\0\0\an\0\0\x2\xee\0\0\0\0\0\0\0\0\a\x80)
window_split=@ByteArray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\x3\xde\0\0\x2\xa8\x1\xff\xff\xff\xff\x1\0\0\0\x1\0)
log_split=@ByteArray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\x2\x62\0\0\0\x64\x1\xff\xff\xff\xff\x1\0\0\0\x2\0)
browser_geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x2\0\0\0\0\0\0\0\0\0\0\0\0\x3\xef\0\0\x2\xed\0\0\0\0\0\0\0\0\0\0\x3\xef\0\0\x2\xed\0\0\0\0\0\0\0\0\a\x80)
filters_visible=false
manage_bsas=true
selected_executable=3

[PluginPersistance]
Python%20Proxy\tryInit=false

[customExecutables]
1\title=SKSE
1\custom=false
1\toolbar=false
1\ownicon=false
2\title=Skyrim
2\custom=false
2\toolbar=true
2\ownicon=false
size=3
3\title=Skyrim Launcher
3\custom=false
3\toolbar=false
3\ownicon=false

[recentDirectories]
size=1
1\name=installMod
1\directory=C:/Users/Jason/Desktop/Skyrim Stuff

[settings]
style=dracula.qss
log_level=0
compact_downloads=false
meta_downloads=true
nexus_login=true
offline_mode=false
use_proxy=false
load_mechanism=0
nmm_version=0.52.3
hide_unchecked_plugins=false
force_enable_core_files=true
display_foreign=true
nexus_username=yagamijase
nexus_password=Removed by Admin

[Plugins]
BSA%20Extractor\enabled=false
Basic%20diagnosis%20plugin\check_conflict=true
Basic%20diagnosis%20plugin\check_errorlog=true
Basic%20diagnosis%20plugin\check_font=true
Basic%20diagnosis%20plugin\check_missingmasters=true
Basic%20diagnosis%20plugin\check_modorder=true
Basic%20diagnosis%20plugin\check_overwrite=true
Basic%20diagnosis%20plugin\ow_ignore_empty=false
Basic%20diagnosis%20plugin\ow_ignore_log=false
FNIS%20Checker\enabled=false
FNIS%20Checker\sensitive=false
Fomod%20Installer\enabled=true
Fomod%20Installer\prefer=true
INI%20Editor\associated=true
INI%20Editor\external=false
Python%20Proxy\enabled=true
Python%20Proxy\python_dir=
Simple%20Installer\enabled=true
Simple%20Installer\silent=false

[pluginBlacklist]
size=0

[CompletedWindowTutorials]
InstallDialog=true

[servers]
CDN=@Variant(\0\0\0\b\0\0\0\x5\0\0\0\xe\0p\0r\0\x65\0m\0i\0u\0m\0\0\0\x1\0\0\0\0\x12\0p\0r\0\x65\0\x66\0\x65\0r\0r\0\x65\0\x64\0\0\0\x2\0\0\0\0\0\0\0\x10\0l\0\x61\0s\0t\0S\0\x65\0\x65\0n\0\0\0\xe\0%\x81\x88\0\0\0\x1a\0\x64\0o\0w\0n\0l\0o\0\x61\0\x64\0S\0p\0\x65\0\x65\0\x64\0\0\0\x6\x41\x42V\xf7\x80\0\0\0\0\0\0\x1a\0\x64\0o\0w\0n\0l\0o\0\x61\0\x64\0\x43\0o\0u\0n\0t\0\0\0\x2\0\0\0\x2)

 

Link to comment
Share on other sites

  • 0

Nope, nothing out-of-the-ordinary there. Last thing. Bring up the Windows start menu and choose Settings -- System -- About and then check the version number please. If it's 1703 then this is another Microsoft stuffup with their "Creator" update. I have no solution for that.

If it isn't 1703 then unfortunately I'm still at a loss and have nothing for you, sorry.

Link to comment
Share on other sites

  • 0

Nope, nothing out-of-the-ordinary there. Last thing. Bring up the Windows start menu and choose Settings -- System -- About and then check the version number please. If it's 1703 then this is another Microsoft stuffup with their "Creator" update. I have no solution for that.

If it isn't 1703 then unfortunately I'm still at a loss and have nothing for you, sorry.

It's 1703. What if I removed the creator update?

Pardon the intrusion, but I haven't seen this mentioned or posted. What version of MO is in use? Version 1.3.1.1 should be used for the classic Beth games, Skyrim, FNV and so on. MO 2.0.7 and greater for Fallout 4 and skyrim special Edition.

It's version 1.3.1.1

Edited by iAmJase
Link to comment
Share on other sites

  • 0

Firstly go to this link, and follow the steps to remove all the Microsoft data mining stuff and see if that helps. Then if that doesn't you have the choice to rollback to a previous version.

Sadly there is no one with the requisite knowledge to code a "fix" for this still working on the project. All the contributors lack the advanced C#/C++ skills needed to patch MO/MO2, which means it may be the end of this software.

Link to comment
Share on other sites

  • 0

Firstly go to this link, and follow the steps to remove all the Microsoft data mining stuff and see if that helps. Then if that doesn't you have the choice to rollback to a previous version.

Sadly there is no one with the requisite knowledge to code a "fix" for this still working on the project. All the contributors lack the advanced C#/C++ skills needed to patch MO/MO2, which means it may be the end of this software.

I got windows 10 for free when it was offered, so I don't have an actual CD to use.

Link to comment
Share on other sites

  • 0

I got windows 10 for free when it was offered, so I don't have an actual CD to use.

Where did the edit button go? Weird...anyway, could my problem be that my computer is 64 bit and that SKSE was designed for 32 bit? I read that was a problem for some people.

Link to comment
Share on other sites

  • 0

You can rollback any update that MS installs. Google it to see what to do. However they will keep on pushing updates at you until everybody, including me, is on whatever is their latest version.

 

SKSE works perfectly well on 64bit machines so... no that's not the issue. You are, sad to say, in the boat that soon I will be in where MO is rendered useless by MS's updates. When that day arrives I will endeavour to see if there are any tweaks to the install that may circumvent this problem but I'm not feeling hopeful. Sorry.

Link to comment
Share on other sites

  • 0

You can rollback any update that MS installs. Google it to see what to do. However they will keep on pushing updates at you until everybody, including me, is on whatever is their latest version.

 

SKSE works perfectly well on 64bit machines so... no that's not the issue. You are, sad to say, in the boat that soon I will be in where MO is rendered useless by MS's updates. When that day arrives I will endeavour to see if there are any tweaks to the install that may circumvent this problem but I'm not feeling hopeful. Sorry.

Google wasn't much help. Thanks anyway.

Link to comment
Share on other sites

  • 0

Unless a patch for MO/MO2 get's done I believe anyone on Win 10 will be out of luck once the Fall update rolls out to the public. Tannin commented on the issue on this topic as to what's the failure in this thread https://github.com/TanninOne/modorganizer/issues/1124 I just wish I had the dev time and knowledge to address the issue as he hints at it only would take a few hours to fix. Chrisbro-MSFT "With help from Tannin and another MS developer we've tracked down the issue in MO. In the current preview releases of Win10, the FindFirstFileExW hooks in MO's hook.dll aren't getting called.Those methods were refactored in the Windows kernel."

 

Tannin "Exactly. So there are 4 FindFirstFile functions in the windows api: FindFirstFileA, FindFirstFileW, FindFirstFileExA and FindFirstFileExW.
Previously, the first 3 were implemented as "proxies" to FindFistFileExW, so they would convert their input parameters, call ...ExW then convert the output back to what they needed.
To save myself time and avoid bugs I only implemented a hook for ...ExW even though the gamebryo games actually call FindFistFileA because this way I caught all FindFirstFile requests and this worked in WinXP all the way to Windows 10, up to this latest release. Now the FindFirstFileA call no longer goes through FindFirstFileExW.

To fix it, you want to add a hook to FindFirstFileA and implement the hook the same way windows did in the past: convert the input parameter (the search path) to a wide string, call FindFirstFileExW_rep with that parameter and a temporary output variable, then transfer the values from the temporary output variable to the "real" output, again converting string parameters back to ansi. This way the ...ExW hook still does all the rerouting.

Ideally you should also implement FindFirstFileW and FindFirstFileExA hooks in a similar manner, although the latter would probably be a bit more complicated because it can have three different types of output formats, so you'd need three code paths for the conversion of the output parameter."

 

Above comments are paraphrased read the above link for more detail needless to say looks like I'll be dual booting instead of enjoying the dx9 fix to Win 10, did not run across this issue until I hit the S.T.E.P. 2.10.0 Part 2.N Patches installing the Extended version (sucks when you hit the end of an install) when it reared it's ugly head on the FNIS Install at the end and got a "Windows Exception (e0434352). Origin: "C:\WINDOWS\System32\KERNELBASE.dll" (76f60212). Last hooked call: int __stdcall GetFileAttributesExW_rep(const wchar_t *,enum _GET_FILEEX_INFO_LEVELS,void *) from MO and a ERROR(2012): Could not generate: defaultfemale.hkx defaultmale.hkx weapequip.hkx staggerbehavior.hkx sprintbehavior.hkx shout_behavior.hkx magicmountedbehavior.hkx magicbehavior.hkx magic_readied_direction_behavior.hkx 1hm_locomotion.hkx 1hm_behavior.hkx 0_master.hkx from FNIS"

 

Fun Stuff :) :P

Link to comment
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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.