System.OutOfMemoryException

[Aravitz90210]

When unpacking the Skyrim - Textures BSA Archive in the Steam>steamapps>common>skyrim>data folder so I can mod the texture files or place mods into the game I get a System.OutOfMemoryException. I've tried BSA Unpacker, BSA Commander, and Oblivion Mod Manager. They worked for all the Skyrim BSA Archives except textures on all 3 programs, 2 of which are larger than the Textures Archive. If you are getting this error or can help me please respond, It's stopping me from being able to put on all the mods I've compiled from SkyrimNexus that I'd like to use.

 

Skype : cravitz33919

msn : guide_senbonzakura@hotmail.com

 

Edit: Also I have .Net Framework 4, and use Windows 7 Ultimate OS.

Edited November 22, 2011 by Aravitz90210

[maboru]

I'm not sure why you're trying to add the texture mods to the .bsa. I just load them in the data/textures files and they all work fine (I've added over 30 at this point.) Even though there isn't an [Archive] section (where bInvalidateolderfiles=1 would be) in the prefs.ini, oddly enough.

[Aravitz90210]

I'm saying I can't extract the Textures in order to make the data/textures files. It didn't come in folder form when I downloaded it, it came in .bsa format, so I need to be able to unpack the BSA files and put the files from it into a textures folder in the Data folder before I can mod anything. Edited November 23, 2011 by Aravitz90210

[maboru]

Hmm, I haven't seen any mods released in bsa form yet, have you tried asking about it in the mod's comments section to see if any other downloaders have run into this problem? Normally bsa mods are just dropped as-is into the data folder and a separate esp or esm calls them from there.

[Aurasoma]

I've seen the same problem.

I tried to extract the files so I could start setting up some alternate armor colors to slip into the game once the CK came out. The best I could get was one .dds file at a time and it still gave me the System.OutOfMemoryException for each one of them.

[maboru]

Maybe the 2gb limit imposed is simply insufficient? The new compression algorithm may be more efficient with textures than the other bsas thus making the textures bsa appear smaller in compressed form but that much larger when decompressed?

[iceburg]

I'm having the same problem. I've been able to extract the meshes bsa and the voices bsa, which are 1.4 gig a piece, but I can't extract the textures.bsa (1.3gig) file because it says "Exception of type 'System.OutOfMemoryException' was thrown." I've tried it on two completely different computers with the same results. I'm using obmm.

Anyone been able to succesfully do this?

[iceburg]

Oh, also, with the textures file it doesn't seem to matter whether the entire bsa is unpacked or even a single file, either way the same error is thrown.

[snufflesms99]

I also had this problem using OBMM, so I downloaded FOMM and it worked beautifully.

[Aurasoma]

I was hoping to find some one had posted a solution to this problem. I'm guessing some additional details are going to be needed.

 

For started I had found BSAUnpack by Timeslip worked at getting the other BSA's open. How ever the System.OutOfMemoryException came up for Textures, under details I got the message below. For some reason FOMM is not an option as my computer will not let me install it.

Hope this helps to get some answers to the problem some of us are seeing.

 

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

at BSAUnpack.BSABrowser.FileEntry.Extract(String path, Boolean UseFolderName, BinaryReader br)

at BSAUnpack.BSABrowser.bExtractAll_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

BSAUnpack

Assembly Version: 0.6.1.0

Win32 Version: 0.6.1.0

CodeBase: file:///G:/steam/steamapps/common/skyrim/Data/BSAUnpack.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5447 (Win7SP1GDR.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

Accessibility

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Edited December 8, 2011 by Aurasoma