Project Reality Forums

Hi!

So... Yeah, I'm getting frequently CTDs without any visible error messages and I'm running out of ideas very soon.

I do play in windowed mode in hope to see error messages. Sometimes playing in windowed mode helps to get less frequently CTDs, at least i think so.

I'm actively cleaning cache with no results. It's not giving any better results when I don't touch cache.

I'm also running a memory cleaning software for sure, but I don't feel getting any results with that. I know it helps for someone, but looks like I'm not in that list. (Koshy John's Memory cleaner software)

What I have seen too is that I'm getting more frequently CTDs on some maps and some maps run quite clean. And there are maps that makes CTD probably once or less in a round. More frequently CTDs making maps aren't always the biggest ones or the new ones.

Specs:
Windows x64
Intel 2 Extreme Qx9650
4x 2GB DDR2-800
Nvidia GTX 460
OS & Game running on SSD
and... 2 monitors + up-to-date drivers.

The game and the OS has been installed under a week ago. I probably should say too that I'm getting pretty weak FPS on most of the maps (<50) and I'm having kind of texture errors when looking in right angle to ground, stripe or something like that.

I'm fairly precise with my hardware and I can say it's not an error in hardware, but could be a compatibility issue of course.


Please, bomb me with ideas or how to debug or something. Right now I'm testing lowering graphics. Anyone have been luck with older drivers?

Edit:
No better results with lowered graphics and/or fully disabled second monitor. Played in windowed mode and I didn't get any error messages, just CTD'd in 10 minutes while playing Fallujah West.

Thank you,
Insomniumer.

Please, don't punish me, I know my english is very weak for my age and so on... I just don't handle it that well.

I think it has something to do with the two monitors and their settings in your graphic drivers. (atleast the texture bugs you mentioned)

I've had something simillar with my computer, first I had two screens but got rid of one because it was useless and used more graphical memory. If you have ATI then just get into Catalyst Control Center or screen properties in Control Panel and somewhere in the settings you'll find some switch you can use to manage your screens.

On my computer for example the standard setting had "display on two screens" on while I was using one, because of this it gave me some errors while playing.

Triggerfinger wrote:I think it has something to do with the two monitors and their settings in your graphic drivers...

Thank you for your comment!

I'm working a lot with two monitors but I'll give it a shot and disable second screen while playing PR.

I'll post results tomorrow after playing/testing several hours with one monitor and lower graphic settings.

-Insomniumer.

The problem is not that you play with two monitors, but the fact that the settings of the computer are set to one monitor only (that's what I think)

It fixed my problem at some point, that was because my computer was "thinking" that I had two screens connected, so he did something with the "graphics data" making these weird black and grey stripes on the ground and so on.

Here's a pic btw.
I don't know sure if I optimized the pic to the right size according to the rules of the forum.


I can not guaranty you, but you can try.

Oh no...

Second monitor fully disabled, low graphics and windowed mode. PR did first CTD in 10 minutes while playing Fallujah West. Not a single error message appeared.

Not sure about the texture glitch.

But...
Does PR write any logs or can i force it to write logs? I'm remembering that BF2 used to write .dmp logs when it crashed. Checked the dmp folder but it was empty.

- Insomniumer.

Insomniumer wrote:Oh no...

Second monitor fully disabled, low graphics and windowed mode. PR did first CTD in 10 minutes while playing Fallujah West. Not a single error message appeared.

Not sure about the texture glitch.

But...
Does PR write any logs or can i force it to write logs? I'm remembering that BF2 used to write .dmp logs when it crashed. Checked the dmp folder but it was empty.

- Insomniumer.

it does but rarely.. look in your battlefield2/mods/pr directory and see if you a log called prerror. That's about all i can think of.

Valleyforge3946 wrote:it does but rarely.. look in your battlefield2/mods/pr directory and see if you a log called prerror. That's about all i can think of.

Yeah, I was looking for something like that before, but I didn't find anything like that. But thanks for your comment and for confirming that PR does write log sometimes!

I think I'm near to resolve this.
Now I'm using WinXP SP3 compatibility mode when launching PR. I haven't seen any random CTDs after changing to WinXP SP3 compatibility mode. This is a little weird when everyone is saying that compatibility modes are bad for Win x64.

The problem got now changed from CTD to Memory.dll error, but looks like memory cleaner is doing great job to prevent memory.dll errors.

Let's see what happens next. If I find a good resolution I'll update it to my thread opening post. I must do a lot of testing before i can say it really works.

Thank you for helping me!

- Insomniumer.

PS. Seriously I have to get some english courses