Jump to content
  • 0
Sign in to follow this  
RevReese

Fallout 3 GOTY Application load error 5:0000065434 When Launching FOSE from within MO

Question

Hi all!.

 

I have recently switched to MO from FOMM after a Windows Reinstall (Win7 64bit) and have had no problems with it whatsoever with Skyrim (so far).

 

But when I try to run Fallout 3 with a handful of mods through the FOSE link in MO it crashes instantly with the above Steam error ("Application load error 5:0000065434").

 

I have posted in the Steam forums about this problem and will feedback anything useful here.

 

The game loads fine from Steam (obviously mod-free) and from FOMM (though my mods do not appear when using FOMM).

 

It also appears to load fine when I click on the fose_loader in the game folder though that will not load my mods will it? even if I have MO open in the background.

 

I have tried all the standard fixes (editing the Fallout.ini and fallout_default.ini files with bUseThreadedAI=1
iNumHWThreads=2).

 

Used LOOT to set my load order.

 

Setting Fallout3.exe, FalloutLauncher.exe and fose_loader.exe to compatibility to Win XP SP3.

 

Running fose_loader as admin.

 

Adding d3d9.dll to the game folder.

 

Running without mods enabled and with (same crash).

 

Renaming ClientRegistry.blob from the Steam install folder.

 

Here is my load order:

 

[spoiler=Load Order]# This file was automatically generated by Mod Organizer.
Fallout3.esm
Anchorage.esm
ThePitt.esm
StreetLights.esm
BrokenSteel.esm
PointLookout.esm
Zeta.esm
Unofficial Fallout 3 Patch.esm
aHUD.esm
EVE.esm
iHUD.esm
Fellout-Anchorage.esp
Fellout-BrokenSteel.esp
Fellout-PointLookout.esp
Fellout-pipboylight.esp
Fellout-Zeta.esp
megalight.esp
Fellout-Full.esp

 

 

I am fresh out of ideas so any help from you guys would be greatly appreciated!.

 

Other than this problem, I am having a blast with MO! I successfully modded my Skyrim back to it's previous state within a few hours!.

 

Thank you for your time.

 

 

 

Edited by RevReese

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

I think your understanding of what the logs are saying is correct. These logs are indeed showing the process of hooking and launching Fallout3.exe is not succeeding and the next executable in line is being called, FalloutLauncher.exe.

 

Can you examine your ModOrganizer.INI, or look a the settings in MO's UI with the 'Executables' list, and see if the Steam appid is applied to any of the Fallout executables, fose, Fallout3 or the launcher? If it is missing, and most likely it is, what happens if you add it to the Fallout 3 exe? That's the field labelled 'Overwrite Steam Appid'.

 

Additionally, just to make it easier for comparisons, can you make a new profile with ONLY the base game files, no mods, run the game and post those logs? Ensure you have MO managing archives checked in the new profile and all the BSAs are checked in the 'Archives' tab.

Share this post


Link to post
Share on other sites
  • 0

My MO INI file:[spoiler=MO INI File][General]
gamePath=D:\\Steam\\SteamApps\\common\\Fallout 3 goty
game_edition=1
selected_profile=Vanilla
ask_for_nexuspw=true
motd_hash=974411364
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\x2\0\0\0\n\0\0\0\x4\0\0\0\n\0\0\0\x6\0\0\0\n\0\0\x2\x13\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\0\x37\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x36\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\x1Z\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\0L\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\0\xc1\0\0\0\xc6\0\0\x4n\0\0\x3\xb1\0\0\0\xc9\0\0\0\xe4\0\0\x4\x66\0\0\x3\xa9\0\0\0\0\0\0\0\0\x5\0)
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\x5\0)
filters_visible=false
manage_bsas=true
selected_executable=1
mod_info_tabs=@ByteArray(\0\0\0\t\0\0\0\xe\0t\0\x61\0\x62\0T\0\x65\0x\0t\0\0\0\f\0t\0\x61\0\x62\0I\0n\0i\0\0\0\x12\0t\0\x61\0\x62\0I\0m\0\x61\0g\0\x65\0s\0\0\0\xe\0t\0\x61\0\x62\0\x45\0S\0P\0s\0\0\0\x18\0t\0\x61\0\x62\0\x43\0o\0n\0\x66\0l\0i\0\x63\0t\0s\0\0\0\x1a\0t\0\x61\0\x62\0\x43\0\x61\0t\0\x65\0g\0o\0r\0i\0\x65\0s\0\0\0\x10\0t\0\x61\0\x62\0N\0\x65\0x\0u\0s\0\0\0\x10\0t\0\x61\0\x62\0N\0o\0t\0\x65\0s\0\0\0\x10\0t\0\x61\0\x62\0\x46\0i\0l\0\x65\0s)

[PluginPersistance]
Python%20Proxy\tryInit=false

[customExecutables]
1\title=FOSE
1\custom=true
1\toolbar=false
2\title=Fallout 3
2\custom=false
2\toolbar=false
3\title=Fallout Mod Manager
3\custom=false
3\toolbar=false
size=7
4\title=Construction Kit
4\custom=false
4\toolbar=false
5\title=LOOT
5\custom=true
5\toolbar=false
5\binary=C:/LOOT/LOOT.exe
5\arguments=
5\workingDirectory=
5\closeOnStart=false
5\steamAppID=
6\title=FO3EDIT
6\custom=true
6\toolbar=true
6\binary=D:/Steam/SteamApps/common/Fallout 3 goty/FO3EDIT 3.1/FO3Edit.exe
6\arguments=
6\workingDirectory=
6\closeOnStart=false
6\steamAppID=
1\binary=D:/Steam/SteamApps/common/Fallout 3 goty/fose_loader.exe
1\arguments=
1\workingDirectory=
1\closeOnStart=false
1\steamAppID=22300
7\title=Fallout Launcher
7\custom=true
7\toolbar=false
7\binary=D:/Steam/SteamApps/common/Fallout 3 goty/FalloutLauncher.exe
7\arguments=
7\workingDirectory=
7\closeOnStart=false
7\steamAppID=

[recentDirectories]
size=2
1\name=editExecutableBinary
1\directory=D:/Steam/SteamApps/common/Fallout 3 goty
2\name=installMod
2\directory=H:/Patches/Fallout 3/Utilities

[CompletedWindowTutorials]
InstallDialog=true

[settings]
hide_unchecked_plugins=false
force_enable_core_files=true
compact_downloads=false
meta_downloads=true
load_mechanism=0
log_level=0
nexus_login=true
nexus_username=***********
nexus_password=***********
offline_mode=false
use_proxy=false
display_foreign=true
nmm_version=0.52.3

[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
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

 

 

Also the FOSE modify executable dialog has "Overwrite Steam AppID" ticked and 22300 in the box as per advice further up in this thread.

 

Unticking this has no effect, the error (5:0000065434) occurs.

 

I also checked the fallout3 and fallout launcher modify executable dialogs and there is nothing in the box and overwrite steam appid is unticked.

 

I applied the overwrite steam appid to fallout3.exe and the (P:0000065432) occurs.

 

 

I have created a vanilla profile using only the base game files and no mods and the problem still occurs (P:0000065432).

 

Thank you all for the help, this is turning into quite the mystery!.

 

Logs from running FOSE with vanilla profile and overwrite steam appid selected: https://www.dropbox.com/s/jjjj2ohejdn27a4/logs31052015.7z?dl=0

Edited by RevReese

Share this post


Link to post
Share on other sites
  • 0

A mystery indeed!

 

What happens when you assign a working directory to the FOSE settings in MO and also set it to close on launch?

Share this post


Link to post
Share on other sites
  • 0

I do love a good mystery!.

 

I'm not sure what you mean by "working directory", I have it set to the game directory and the fose_loader.exe

Setting it to close on launch still brings up the P:0000065432 error.

Share this post


Link to post
Share on other sites
  • 0

I just meant that the 'Start In' field actually had something in it. Not that it should make a difference, but it can't hurt to try things, we've lucked out on just about every other method! :confused:

 

Sorry to say it, but I'm out of ideas.

Share this post


Link to post
Share on other sites
  • 0

Ah okay i get you!.

 

It is currently empty though trying it with the Fallout directory brings up the P:0000065432 error.

It was worth a shot, thank you to all of you for the help, looks like back to FOMM for now (and hope i don't run into any mysteries there too!).

 

It's just so strange that MO works beautifully with New Vegas and Skyrim! i remember having a similar problem with Oblivion for a while too but that sorted itself out eventually.

 

Seeing as this seems to be a steam problem, I will try the steam forums again and report back here if anything works.

 

Thanks again for all the help!.

 

EDIT: I reverted back to FOMM and it loaded first time and everything is running okay so far! so for anyone reading this who has tried all the above help and still having no joy (please don't let it just be me!), just use FOMM, it worked for me!.

 

I have kept MO installed for FO3 in case an update or something in the future fixes it automagically! :;):

 

A big thank you to everyone above for their help and advice, sadly nothing worked for me, but i am sure any future readers will find something of use somewhere in this thread!.

Edited by RevReese

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  

×
×
  • Create New...

Important Information

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