Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About RevReese

  • Rank
  • Birthday 01/29/1983

Profile Information

  • Gender
  • Location
    Southampton, UK
  • Interests
    Gaming, Modding, Reading, Writing

Contact Methods

  1. 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!.
  2. 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.
  3. 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
  4. Thank you for your reply though there are no updates waiting. Thank you for your reply, I have uploaded the logs you requested here: https://www.dropbox.com/s/fpdqaufdp9s6x9u/logs.7z?dl=0 Hope this helps!.
  5. Does that help?. i must admit to not looking forward to moving all my mods back to FOMM! (considering Fallout New Vegas and Skyrim work perfectly with MO).
  6. Thanks for the replies, here is my appmanifest_22370.acf: [spoiler=appmanifest_22370.acf]"AppState" { "appid" "22370" "Universe" "1" "name" "Fallout 3 - Game of the Year Edition" "StateFlags" "4" "installdir" "Fallout 3 goty" "LastUpdated" "1429610479" "UpdateResult" "0" "SizeOnDisk" "9474203596" "buildid" "252141" "LastOwner" "76561198017432836" "BytesToDownload" "7699376448" "BytesDownloaded" "54330576" "AutoUpdateBehavior" "0" "AllowOtherDownloadsWhileRunning" "0" "UserConfig" { "language" "english" } "MountedDepots" { "22371" "6752416544246981300" } }
  7. Yes, my fallout3.exe is Large Address Enabled, but still same error (P:0000065432). I am also using MO 1.3.5 but still the same error.
  8. No, there is nothing odd about it, just the Steam GotY version bought during a sale. I used FileAlyzer. Fallout3.exe CRC 32 - 0B3862DB MD5 - 6AC349AB0980C713CD8FFB37199443F3 SHA 1 - 7A6D3948B6D0BD7BE97B71769A14D3C084609331
  9. I have tried running vanilla FO3 via MO but have the same issue with the same error. Using the FO3 launcher causes the same error (5:0000065434) but using fose_loader loads the game fine (though obviously without mods). I have tried running Steam as Administrator and MO as Administrator (steam is not installed in a UAC directory) but crashes with the error: P:0000065432. I have the latest version of Steam updated today. Latest log (ModOrganizer_15_05_16_13_40_2.log):
  10. Thank you all for your posts!. I am unsure about using a "crack" though I have heard that it has worked for others, maybe I will try it if nothing else works. fose log: launching: Fallout3.exe (D:\Steam\SteamApps\common\Fallout 3 goty\Fallout3.exe) crc = FE5B82AE hook call addr = 00C05F61 load lib addr = 00D9B0F0 dll = D:\Steam\SteamApps\common\Fallout 3 goty\fose_1_7.dll remote memory = 001E0000 old winmain = 006EE300 launching Running through steam loads the game, loading by clicking fose_loader loads the game, but neither of these notice my mods. I tried this and immediately get the crash and accompanying error: P:0000065432. That's a shame but thank you for finding that bug report. I have tried this and the application load error does not appear but loading FOSE simply loads up the fallout launcher (again no mods but better than an instant crash). EDIT: I tried this again and immediately get the crash and accompanying error: P:0000065432 That could be the problem then, maybe back to FOMM?. Thanks again for all your advice, but it looks I will have to back to FOMM (which loaded fine) or use a crack (which I don't really want to do).
  11. No, Steam is installed to C:\Steam to avoid the UAC issue. I have MO working perfectly with Fallout New Vegas and Skyrim,, it is just Fallout 3 that has this problem. I have posted about this in the Steam forums too as it appears to be a steam error rather than an MO error (the bar across the top of the error says "steam error"). I have heard of this problem with others if they are using pirated copies of the game (which I am not). Is there any other information I could provide to help?
  12. Thank you for your reply. I did make backups of the game files before cleaning so I can just pop them back in if something goes wrong!. I moved the game from my SSD to my HDD as I have needed to do with several older games in the past and the error message no longer pops up. ...However, upon running FOSE from within MO it locks MO as it should to run the exe but then quits without an error, if it helps, when this happens the message log at the bottom reads "setting file times on esps". Clicking on fose_loader manually loads the game up no problem, as does clicking the steam shortcut. EDIT: Now clicking FOSE Run brings up the application load error again, not sure why as i changed nothing.
  13. Thank you for your reply!. I have had a good read through the linked guide, but the problem persists. I tried to run the fallout launcher but the Application load error popped up immediately, both within MO and externally and non of the other suggestions seemed relevant except for the Fallout 3 Dual-Core and Multi-Core Fix ini tweak which I have already done. I have also cleaned the DLC esm's as per the guide. Now they do not appear on the left pane but the plugins still appear on the right pane. Also, the cleaned esm's now appear in my "overwrite" mod along with "FO3Edit Backups". What do I need to do with them now?. I don't know what else to try.
  14. 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.
  • Create New...

Important Information

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