Page 1 of 1

why do I still have memory.dll crashes?

Posted: 2010-03-20 20:29
by duduc1986
I installed pr 0.9 over and over, and it still continues.
I'm using windows 7, my computer has really good permformance in all aspects.

this is how I install PR:
first installing BF2 vanilla
update to 1.41
update to 1.50
installing pr part 1, then part 2
uninstalling PB and deleting the folder inside the game's dir, then install it again and update.

The game keep on crushing cause of this memory.dll problem, and some of the maps arent even working correctly.
it is very annoying, help please!

Re: why do I still have memory.dll crashes?

Posted: 2010-03-20 23:02
by Pesticide
did you try the maps that crash with lower detail settings ? Its because the maps take so much memory a 32bit operating system cant handle some of them. Set your lighting detail to medium and textures and retry. go for low first, and crack em up one at a time.

Re: why do I still have memory.dll crashes?

Posted: 2010-03-20 23:22
by SnipingCoward
Please post:
Operating System (OS) [32 or 64 bit?]
systems specs (MoBo, GFX, Audio, generally hardware)
And a brief history before and after problem started. (Did you change anything? new drivers, new Anti-Vir...)
Precise description when your problem hits and what you have already tried.
what you mean by "crash" (CTD, reboot, error sound, freez or bluescreen/BSOD)

I agree with pesticide.

Here are three more things that come to mind:
  1. Corrupted installer files:
    Verify that your files are not corrupted:
    https://www.realitymod.com/forum/f10-pr ... rrupt.html

    I suggest you use a download manager like FDM, GetRight or FlashGet or a BitTorrent client like µTorrent or Azureus. Those programs are generally able to resume interrupted downloads and this way prevent data corruption. I believe they are essential for large downloads like the pr installers. Also you can use them to "resume" the corrupted download - this might have them redownlaod only the broken bits instead of the whole thing again.
  2. Hardware failure (RAM or Motherboard): run Win 7's memory diagnostic
  3. too few RAM: close unneeded programs before playing