Project Reality Forums

Hey everyone, It seems that when I try and load certain maps (Lakshar Valley, Al Basrah) I error out at about 50 - 65% with two errors.

First:

memory.dll: sanity check: block size 1085767808 (1035.47 mb) doesn't seem sane

Second:

memory.dll: all alloc attempts failed for size 1085767808

Here is a list of some of the things I've already tried.

1. Setting a larger static page file
2. Setting all graphics to low
3. Clearing my BF2 cache
4. Reinstalling PR

Also I wanted to try the unlocked version of Bf2.exe but cant seem to find a download.

My system specs are as follows...

OS: Windows XP Professional (Non OEM)
CPU: Intel Core i5 750
RAM: Corsair Gold 2x2GB DDR3 1333mhz
Mobo: Gigabyte GA-P55-UD3R
HD: 500GB SATA3 7200rpm Western Digital Caviar Blue
GPU: Sapphire Radeon HD 4670 1Gig

If anyone could please help me out it would be much appreciated.

-Andrew

They claim to have solved this problem in here

Check if it works for you. I've never had the problem myself..

Things that I would attempt (at least initially) include

• Set pagefile to managed by O.S.
• Set affinity to a single core (you can do this from task manager)
• Run memory tests like memtest86 (I don't know if the system is new/old)
• Check for BIOS updates for the motherboard
  • I did have a problem with this one about a year ago. I updated my system from 2GB to 4GB (2x 2GB DIMMs) and the system became very unstable. Even though the documentation for the firmware update didn't say anything about memory errors (only CPU compatibility fixes) I gave it a go and the problem was fixed.
• Try killing other background programs/services that have your username on it (task mngr) and allowing PR to run with as few background processes as you can. It could be a problem between some other process and BF2 itself..

Good luck.

~xghost();

Ive tried most of the things you suggested above to no avail. Ive still yet to run a memory test but am planning to do so in the morning. And as for my bios some people seem to have some slight problems with the version shipped with the MOBO. Other than this my system seem fairly stable and BF2 at the moment of typing this is using 1.5 GB of ram, so that seems fine. Anyways I'll post back if I find the solution.

-Andrew

are you sure you tested the low gfx settings ? setting a few to medium on my system helped ( only had to leave the lighting detail to medium , rest high for it to work and not get the memory error anymore)

Ok, here's a list of other things I've tried that haven't helped.

- I ran memtest86+ with two passes and my memory is error free
- Tried different graphics settings from everything on high to everything on low
- Tried different page file configurations
- Tried BF2.exe and PR.exe running on a single core

Right now I'm debating on flashing my BIOS to the latest version, or a full reinstall of BF2 and patches.

Also on a side note Gaza Beach also seems to be affected.

-Andrew

theclaww wrote:Ok, here's a list of other things I've tried that haven't helped.

- I ran memtest86+ with two passes and my memory is error free
- Tried different graphics settings from everything on high to everything on low
- Tried different page file configurations
- Tried BF2.exe and PR.exe running on a single core

Right now I'm debating on flashing my BIOS to the latest version, or a full reinstall of BF2 and patches.

Also on a side note Gaza Beach also seems to be affected.

-Andrew

If I had to pick, I'd choose your BIOS. Keep in mind that you must follow instructions on this to the letter. In fact, I will add that you should have your system connected to a battery to avoid having your BIOS go dead in case of a power outage. These days, MoBos come with a backup ROM for better safety, but it's always better to avoid the potential for a problem altogether.

Regarding your page file configurations, if you're using a manual configuration/setting, the number is usually set to 1.5 times the amount of RAM your system has, but this is not a hard-n-fast rule. You can always allow the O.S. to manage that for you..

~xghost();