Page 1 of 1

Crash To Desktop

Posted: 2010-02-25 17:16
by Scorpac
Hello guys,

i searched the internet several times tested a lot of things to fix that problem but nothing helped. Now youre my last chance.


My Problem:

When i play PR i dont know how long it will keep me in-game. Sometimes it crashes after 2min of playing, at another time after an hour or later... dont know why or when it will happen, when it happens.

I run my game on High settings 1680x1050 display.

My PC:
Windows Vista Home Premium 64bit
Intel I7-920 @ 3ghz
geForce GTX295 @ 2gb ram
6gb DDR-3 Corsair ram.
Asus Rampage 2 Extreme Mainboard

i read about a BF2 problem which only allows a special amount of ram to use...

i found this in the FAQ:
____________________________
Q: I am crashing to desktop when loading/changing levels.
Q: I am getting a lot of lag on levels.

A: The most common cause of this is that you are running out of memory (though there are other causes). BF2 was a memory intensive game, and PR only increases on that.

First, you can try lowering your video settings, in particular, Textures.

If that doesn't help or fix your issue, you can try increasing your virtual memory.
____________________________

so how can i push my virtual memory?


maybe this could be a fix?


It would be cool if you give me some tips step by step to fix and sorround the problem



I hope you can help me :(

Re: Crash To Desktop

Posted: 2010-02-25 19:44
by SnipingCoward
run in windowed mode and see if your ground texture disappears - if so this thread applies:
https://www.realitymod.com/forum/f27-pr ... sktop.html

(although noone confirmed on a solution) I assume that the last suggested fix is one - since ppl in that thread stopped responding (prolly to busy gaming)

Re: Crash To Desktop

Posted: 2010-02-25 19:52
by Kosari
Try run as adminstration

Re: Crash To Desktop

Posted: 2010-02-26 05:11
by Nobomaun
I actually had the same exact problem. I checked and googled everything I could find on the net and the forums. There were a lot of fixes and checks to do. I spent the majority of almost two weeks working on it. Only to find this one out.

Check all your drivers. And I mean ALL your drivers. In my case, it turned out that it was my On-board (Motherboard) HD Audio Driver that was causing the problem. Instead of going on-line, check your Utility CDs and see if they have the ability to check for current drivers on line. I guess my current one at the time was the wrong one. I used my Utility / Installation CD, and set it to automatically check for Driver updates. It found one. I thought that it shouldn't have bee the case because I thought it was a VGA driver, RAM, etc... issue. I even spent a couple of bucks to buy an 850 Watt PSU (I needed one anyway).

Anyway, I installed it as it requested. When I did mine, it said that I had a newer version installed and asked if I want to overwrite it. I clicked "Yes" to every single one. Just figured this out last night. Restarted the comp. Vuala!!! I played last night and practically all day today without crashing.

Try it out. See what happens. It's worth a shot.

Check out my ranting after piggy backing on someone else's thread. It doesn't carry the solution that I mentioned above. It just notes most of the things that I did. Thanks to everyone by the way.

https://www.realitymod.com/forum/f360-g ... -card.html


Hope this helps.

Nobo

Re: Crash To Desktop

Posted: 2010-02-26 07:19
by weixman
Had the same problem. I just increased my paging file: Start> My Computer> leftclick> Properties> Advanced> On performance klick settings> Advanced> On virtual Memory klick Change. I set my paging file to max. Helped me.

Re: Crash To Desktop

Posted: 2010-02-26 17:39
by Scorpac
now i updated all my drivers and set my paging file to 9.2gb....


but still, how to incrase my Ram for Battlefiel? it looks like its only project reality... on bf2 i dont get a crash to desktop

Re: Crash To Desktop

Posted: 2010-02-26 19:25
by weixman
hmmm... I don`t think that lack of ram could cause CTD, but im not sure. And the only way to get more RAM is.... Buy more :-)

Re: Crash To Desktop

Posted: 2010-02-26 20:21
by Scorpac
you dont understand


has anybody else some tips ?


would be really cool... i play pr since 0.5 and im losing the fun cause everytime when the teamplay makes most fun i crash to desktop

Re: Crash To Desktop

Posted: 2010-02-27 00:32
by SnipingCoward
what was the result of running in windowed mode? - reply to suggestions or no more will come - as we cant narrow the problem down


as for how to increase BF2 memory usage/allowed allocation size:
check this thread https://www.realitymod.com/forum/f27-pr ... ost1268245
- but i believe you will get an MD5 kick for that modded bf2.exe so make a backup first
- also I believe since 1.5 EA got that fixed


another approach is to decrease BF2's ram requirement: lower your video settings

Re: Crash To Desktop

Posted: 2010-02-27 13:41
by Scorpac
on windowed mode i dont have ground textures.

disabled desktop comparison

now im going for further tests with my resolution settings.

Re: Crash To Desktop

Posted: 2010-02-27 14:13
by Nicolo_Tracchia
I was experiencing CTDs during map loading or a moment after that. Changing textures setting to Medium fixed this.

Re: Crash To Desktop

Posted: 2010-02-28 08:13
by Scorpac
i really dont like to play at low settings... there are enough guys who play at high settings without experiencing the CTD problem...

there must be a fix

i fixed the resolution and window mode thing but after about 4 houres of playing another CTD...

what i did until now:

-Updated Chipset driver for mainboard
-Updated Sounddriver
-Set the paging file of my virtual memory in the system management to 14-9200mb
-Disabled Desktop Comparison
-Fixed the Texture bug in Window mode.

Re: Crash To Desktop

Posted: 2010-03-01 08:53
by Scorpac
running as administrator doesnt make any change...

getting these CTD's after not an hour alle the time

im losing the fun of this game :(

Re: Crash To Desktop

Posted: 2010-03-03 01:33
by SnipingCoward
someone reported that he had to use an older nvidia driver -> try with first updating with the latest gfx drivers then try using lower versions of it

how did you fix "the resolution and window mode thing"?