What kind of error is this?

[Jonathan_Archer_nx01]

AMD X2 6000+
2GB RAM
Geforce 8800 GTS 384 MB RAM
Windows XP

I play on medium settings. And I often get this after just 2 or 3 map loadings:



So what should I upgrade now? Should I upgrade to 4GB RAM? I heard Win XP won't recognize it anyway.
Or is 384 MB of memory my video card has just not enough?

[karambaitos]

You could reinstall BF2 and PR.
Your ram gets overloaded probably, so you could get 4GBs of ram, XP will recognize 3-3.5Gb but youll still have some extra if you decide to upgrade.
I was getting a simmilar error until I did this
https://www.realitymod.com/forum/f358-s ... users.html
(then you get kicked for MD5 tools on some servers).
A new GPU would do you well of course if you have the moniez...

Try running it without dynamic lighting, shadows and AA see what happens.

[SnipingCoward]

setting lighting to medium has fixed it for some ppl

the problem occures when there is not enough ram available

- you can try to increase the page file size
- deactivating visual themes in xp is probably not as effective as in vista but still might help a bit
- go all the way to low settings for testing purposes

note: there are already alot of threads regarding this issue - maybe you can find better help in there
also: this is prettry pr related since it rarely happens on vbf2 (uses alot less ram) therefore this forum would be right for you too (search in there): PR Support - Project Reality Forums

[Jonathan_Archer_nx01]

Thanks guys!
You think upgrading my video card would help? I'd go with Radeon HD6850 1GB.

[SnipingCoward]

I do not believe that getting a GFX card with more GPU-RAM will solve your memory.dll issue as there is a difference between GPU-RAM and regular RAM.
I still think upgrading RAM (I prefer 3x 2GB sticks running in tipple channel = 6GB) or boosting your page file would be in order.

A new GFX-Card will probably increase your FPS though.

[JohnnyPissoff]

I don't know, I used to run PR on XP with only one gig of ram and never got that error message. This may sound crazy, but try pulling one stick of ram out and running with one gig at a time. (it's gonna stutter a bunch on map loading but you should be able to at least stay in game to test this. What I'm getting at here is you may have a bad stick of ram. You're playing along nicely then you hit a bad spot on one of your sticks and get the error?

The point of this is; even if you bought a couple more gigs of ram, if you had a bad spot on one of your original sticks you'd still get the error eventually. If I'm correct the worse case is you'd only need to buy/replace one gig instead of buying two extra.

[SnipingCoward]

This may sound crazy, but try pulling one stick of ram out and running with one gig at a time. (it's gonna stutter a bunch on map loading but you should be able to at least stay in game to test this. What I'm getting at here is you may have a bad stick of ram.

While this is a quite decent method to find RAM defects I prefere using software tools like "Windows Memory Diagnostic" (since Win7) and MemTest (on almost every linux bootable disc) for preliminary tests.

If these tests show errors I usually resort to your hardware base method to check which stick is defective. However in some very rare occasions you can be fooled namely when a bank/slot and/or bus and/or multiple sticks are broken. But just keep these possibilities in mind and you should be fine. I like to cross check the sticks on a second PC too.