Jump to content

Fuz Ro D-oh MO2 Code 193 error


Recommended Posts

Posted

I downloaded Fuz Ro D'oh, but it's causing a weird problem. In MO2, I get the error "Script extender log reports incompatible plugin.", followed by "Couldn't load Fuz Ro D'oh.dll (Fuz Ro D-oh - Silent Voice). A DLL is invalid (code 193)." I tried reinstalling the mod and trying different versions, but that did nothing. Nothing seems to be interfering with FRD, so that can't be it. Another solution being recommended is to just delete the plugin, but won't that mess it up? Is there some way to fix this, or can I use mods without it? It's listed as a requirement for the mod it's needed for (Destroy the Thieves Guild).

Posted
5 hours ago, RedHeadAngel said:

A DLL is invalid (code 193).

 

ERROR_BAD_EXE_FORMAT

193 (0xC1)

%1 is not a valid Win32 application.

 

5 hours ago, RedHeadAngel said:

Is there some way to fix this...

 

You can't run 32bit applications inside 64bit applications. The fix is to download Fuz Ro D-oh for the correct game.

Posted (edited)
2 hours ago, traison said:

 

ERROR_BAD_EXE_FORMAT

193 (0xC1)

%1 is not a valid Win32 application.

 

 

You can't run 32bit applications inside 64bit applications. The fix is to download Fuz Ro D-oh for the correct game.

If you're saying I installed the version for original Skyrim, I didn't. I installed the correct version. On Nexus, I went to the SSE section and installed FRD for 1.5.97, which is what I have.

 

FuzRoD-oh-SilentVoiceatSkyrimSpecialEditionNexus-ModsandCommunity-GoogleChrome12_28_20255_21_48AM.thumb.png.b059db4fdcc089d296b6b75f1172092f.png

Edited by RedHeadAngel
Posted
4 hours ago, RedHeadAngel said:

If you're saying...

 

Sort of, but it's actually Windows claiming you're trying to shove a 32bit executable into a 64bit executable. Square peg into a round hole.

 

4 hours ago, RedHeadAngel said:

I installed the correct version.

 

Do a sanity check:

  1. Go get CFF Explorer. No install required. Extract anywhere.
  2. Drag-n-drop the SkyrimSE.exe into CFF.
  3. Make sure the File Type field reads "Portable Executable 64" i.e. PE64.
  4. Drag-n-drop the Fuz Ro D-oh dll into CFF.
  5. Make sure the File Type field does NOT read "Portable Executable 32" i.e. PE32.
Posted
1 hour ago, traison said:

 

Sort of, but it's actually Windows claiming you're trying to shove a 32bit executable into a 64bit executable. Square peg into a round hole.

 

 

Do a sanity check:

  1. Go get CFF Explorer. No install required. Extract anywhere.
  2. Drag-n-drop the SkyrimSE.exe into CFF.
  3. Make sure the File Type field reads "Portable Executable 64" i.e. PE64.
  4. Drag-n-drop the Fuz Ro D-oh dll into CFF.
  5. Make sure the File Type field does NOT read "Portable Executable 32" i.e. PE32.

And if it does say that it’s a 32 bit, what then?

Posted
1 hour ago, traison said:

 

Sort of, but it's actually Windows claiming you're trying to shove a 32bit executable into a 64bit executable. Square peg into a round hole.

 

 

Do a sanity check:

  1. Go get CFF Explorer. No install required. Extract anywhere.
  2. Drag-n-drop the SkyrimSE.exe into CFF.
  3. Make sure the File Type field reads "Portable Executable 64" i.e. PE64.
  4. Drag-n-drop the Fuz Ro D-oh dll into CFF.
  5. Make sure the File Type field does NOT read "Portable Executable 32" i.e. PE32.

And if it does say that it’s a 32 bit, what then?

Posted
2 minutes ago, RedHeadAngel said:

And if it does say that it’s a 32 bit, what then?

 

Try a different version and/or message the author.

 

I know Fuz Ro D'oh-15109-2-5-1706039953 is 64 bit and works on Skyrim SE/AE. Dll checksum:

bc011d0ed4858592f9a267ffbc15c7f5  Fuz Ro D'oh.dll

 

See section 5.1 of my Reading Crash Logs blog post if you don't know how to calculate MD5 file checksums.

Posted
30 minutes ago, traison said:

 

Try a different version and/or message the author.

 

I know Fuz Ro D'oh-15109-2-5-1706039953 is 64 bit and works on Skyrim SE/AE. Dll checksum:

bc011d0ed4858592f9a267ffbc15c7f5  Fuz Ro D'oh.dll

 

See section 5.1 of my Reading Crash Logs blog post if you don't know how to calculate MD5 file checksums.

I tried multiple versions of the mod, but I don’t know if that’s one of them. I suppose I’ll check when I get the chance.

Is the one you’re showing version 2.5?

Posted
9 minutes ago, RedHeadAngel said:

Is the one you’re showing version 2.5?

 

Fuz Ro D'oh-15109-2-5-1706039953

 

Nexus mod id 15109, Nexus file id 1706039953.

Posted

@traison

OK, I checked the CFF thing and followed your instructions, and my game is 64-bit, as is version 1.7 of FRD, which is the version of the mod meant for 1.5.97. I also checked version 2.5 of FRD, and it was also 64-bit. Therefore, if your logic is to be believed, I should not be having this problem. However, even after trying every version of FRD available, I am. I left a comment on the mod this morning, but haven't heard anything back yet.

Posted (edited)
1 hour ago, RedHeadAngel said:

... my game is 64-bit, as is version 1.7 of FRD, which is the version of the mod meant for 1.5.97. ... Therefore, if your logic is to be believed, I should not be having this problem.

 

True. I would have to see this problem for myself to figure it out.

 

The only thing I can suggest at the moment is that you Google all the possible situations where LoadLibraryA, LoadLibraryW (macro: "LoadLibrary"), LoadLibraryExA and LoadLibraryExW (macro: "LoadLibraryEx") will return code 193 (0xC1) ERROR_BAD_EXE_FORMAT. My understanding is that it's only thrown when the bitness is wrong, but clearly that's not the case here.

Edited by traison
Posted
24 minutes ago, traison said:

 

True. I would have to see this problem for myself to figure it out.

 

The only thing I can suggest at the moment is that you Google all the possible situations where LoadLibraryA, LoadLibraryW (macro: "LoadLibrary"), LoadLibraryExA and LoadLibraryExW (macro: "LoadLibraryEx") will return code 193 (0xC1) ERROR_BAD_EXE_FORMAT. My understanding is that it's only thrown when the bitness is wrong, but clearly that's not the case here.

The only thing I could find is the file is corrupted. If that's the case, then all of the FDR files are corrupted, which doesn't make sense.

Posted
6 minutes ago, RedHeadAngel said:

If that's the case, then all of the FDR files are corrupted, which doesn't make sense.

 

I posted the checksum of version 2.5 above. You can test yours as well to rule out virus infections and MITM attacks.

Posted (edited)
21 minutes ago, traison said:

 

I posted the checksum of version 2.5 above. You can test yours as well to rule out virus infections and MITM attacks.

How do I check that? I read the blog you made but it didn’t help.

Edited by RedHeadAngel

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