I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

LeChuckle · Post by **LeChuckle** » 2009-08-22 20:40

isnt that what it says when youve mistyped something?

blekis · Post by **blekis** » 2009-09-04 08:49

hmm.. nice!
its works, but after i did so, i have problem whit punkbuster! i got kick by pb"md5tool mismatch len=2048" eny ideas how to fix it????? thx.

and sorry for my bad english! ??:

Post by **Rudd** » 2009-09-04 22:17

do we have to do anything with this for 1.5?

Ferron · Post by **Ferron** » 2009-09-05 16:34

Dr2B Rudd wrote:do we have to do anything with this for 1.5?

nope, its fixed by DICE.

ronxmckernan · Post by **ronxmckernan** » 2009-09-17 06:45

First let me say thanks for your work on this as its seems many suffer from this beguiling problem. Then I should mention that when typing into a command prompt window, spaces are not permitted for folder listings, so one must contain such a listing in quotation marks. For example, ... Program Files (x86) ... contains spaces so your command line must look like this ... C:\>cd "Program Files (x86)\" (hit enter). You can also skip a bunch of navigation steps to the proper folder by typing the following after the prompt (a prompt looks like this... >)

>cd "C:\Program Files (x86)\EA GAMES\Battlefield 2\" (hit enter). ***Notice the quotation marks--won't work without them***

Then use the editbin.exe command typed exactly as stated and you'll get the Microsoft Trademark dealie indicating success. Also, cd stands for change directory, that's all you're doing, it's not that hard to follow really.

Lastly let me say that, as weird as it sounds, I just started having this problem as a result of installing the v1.50 patch (runs fine under v1.41), and the above fix does not work as this patch already performs this fix inherently. Any ideas on this would be greatly appreciated. Thanks!

system notes: running 4 x 1GB DDR2 800 and have tried clean installs of BF2 on clean installs of XP Pro (x86), Vista64, and Win 7 (x64). /working fine up to 1.41 then install 1.50 patch and get memory sanity error loading every map and then CTD.

And thanks Raptor007, will try that ASAP, and report back!

CPU · Post by **CPU** » 2009-09-20 18:02

ronxmckernan wrote:First let me say thanks for your work on this as its seems many suffer from this beguiling problem. Then I should mention that when typing into a command prompt window, spaces are not permitted for folder listings, so one must contain such a listing in quotation marks. For example, ... Program Files (x86) ... contains spaces so your command line must look like this ... C:\>cd "Program Files (x86)" (hit enter). You can also skip a bunch of navigation steps to the proper folder by typing the following after the prompt (a prompt looks like this... >)

>cd "C:\Program Files (x86)\EA GAMES\Battlefield 2" (hit enter). ***Notice the quotation marks--won't work without them***

Then use the editbin.exe command typed exactly as stated and you'll get the Microsoft Trademark dealie indicating success. Also, cd stands for change directory, that's all you're doing, it's not that hard to follow really.

Lastly let me say that, as weird as it sounds, I just started having this problem as a result of installing the v1.50 patch (runs fine under v1.41), and the above fix does not work as this patch already performs this fix inherently. Any ideas on this would be greatly appreciated. Thanks!

system notes: running 4 x 1GB DDR2 800 and have tried clean installs of BF2 on clean installs of XP Pro (x86), Vista64, and Win 7 (x64). /working fine up to 1.41 then install 1.50 patch and get memory sanity error loading every map and then CTD.

And thanks Raptor007, will try that ASAP, and report back!

Very similar story for me (XP with 4G ram): with 1.41 the patched BF2.exe (I didn't editbin but downloaded the pre-patched exe) worked a treat and cleared my problem. Since 1.5 it's back and happens every time the map changes

ronxmckernan · Post by **ronxmckernan** » 2009-09-25 06:33

Update: Thanks again Raptor007 for the info on the /3GB and increase userva switches, but alas they did not work and the memory sanity errors continue with the 1.50 Patch. Interestingly, I am able to run Special Forces maps under v.1.50 without a problem, and also, I can run AIX 2.0 mod 64-player maps with full bots or full multiplayer servers without the error, even when I load remakes of the same vanilla BF2 maps that crash on load (ex. Daqing, Dalian, Dragon). I have not tested with PR yet though because I don't have the newest 1.50 patch compatible version downloaded yet (only 0.85). Given these things, I believe this to be a problem specifically with the patch and not my hardware or config. Have put in a support request to EA, so we'll see if that gets me anywhere. Will post with any results.

Post by **Tim270** » 2009-10-26 00:38

Please sticky this thread!

WhatMan · Post by **WhatMan** » 2010-02-06 23:58

Anyone know the most updated-working solution for this?

Rusty Shackleford · Post by **Rusty Shackleford** » 2010-02-07 00:32

If your problem is memory allocation error, this fix should still work.

seb120 · Post by **seb120** » 2010-02-07 01:28

this worked but now im getting a md5 mismatch

Raic · Post by **Raic** » 2010-02-07 01:52

DO NOT USE THIS! ITS OLD AS HELL! bf2 1.5 has it included and if you go and edit the .exe you get PB problems.

Rusty Shackleford · Post by **Rusty Shackleford** » 2010-02-07 03:03

BF2 1.5 did NOT fix this problem completely.

Nick_Gunar · Post by **Nick_Gunar** » 2010-02-07 09:28

With the 0.874, I didn't have any problems but with the 0.9, sometimes, when I am loading a map I crash to desktop with memory.dll error (my computer is kinda old though, that could be the problem ^^).

As far as I am concerned, the patch 1.5 didn't fix this.

Pesticide · Post by **Pesticide** » 2010-02-07 14:08

set your lighting gfx option to medium, fixes the error for me in win xp 32 bit.

WhatMan · Post by **WhatMan** » 2010-02-07 18:55

,removed. wrong thread

MishMash · Post by **MishMash** » 2010-04-16 00:30

In Vista 32: cd c:\Program Files\ (Hit ENTER) **or** In Vista 64: cd c:\Program Files (x86)\ (Hit ENTER)

http://img.photobucket.com/albums/v448/sopdelta/C3.jpg
then usually it's "cd EA GAMES" (Hit ENTER)
_____________________________________________________________________________________________

I installed BF2 through steam and not by disk so my BF2 files are not located in the usual locations if I had installed with disk. Thus, when i type this --- >> "cd EA GAMES" and hit enter it says "the system cannot find the path specified"

I would appreciate if you would edit or post a new fix using steam directories.

thx in advance

MishMash

Raic · Post by **Raic** » 2010-04-16 00:50

In steam its in should be something like this "C:\Program Files\Steam\steamapps\common\battlefield 2"
But if you read the thread you notice that THIS PATCH IS NOT NEEDED FOR BF2 ANYMORE! 1.5 patch includes it already. If you keep getting memory errors drop your settings, lighting and textures are the first ones to lower.

Post by **Rudd** » 2010-05-08 20:57

before my HD failure I had everything on high and was fine, but now it seems that I'm getting memory problems quite a bit. Does this still help at all and does it result in any PB problems in 1.5?

corp_calqluslethal · Post by **corp_calqluslethal** » 2010-05-08 22:59

yea you will get the md5 mismatch kick on certain severs. The fix works but you'd have to sacrifice playing on some severs. One i remember was constantly being kicked from UK Warfare for the mismatch.

I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

Re: I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.