Project Reality Forums

This is just an announcement to let people know we're working on figuring out the cause of all the CTD's that are happening in 0.95.




So far, we've figured out what is causing lots of crashes on German maps and a fix for it will be implemented in a bug fixing patch. We're doing our best to figure out what's causing crashes on other maps as well. Lots of people have posted their error logs in the bug section, but we're of the opinion that none of the errors coming up in the log are the cause of ctd's.




So here's how you, forum goers, can help. The simplest way to find a cause for a CTD error is to run PR in windowed mode. In the vast majority of cases, when a CTD occurs, anyone playing in windowed mode will get an error message upon crash which will contain the details of what has caused the crash.

So here's the steps required,



1. Run PR in windowed mode,

• right click your PR shortcut and go to properties
• In the Target section, add a space and then "+fullscreen 0" (if it's already there and set to 1, just set it to 0)
• To switch back to full screen, just set it to 1 instead of 0

2. Play PR!!!



3. If you get a CTD and an error message pops up,

• Press "Ctrl+C" to copy the error message
• Reply to this thread letting us know what server you were on, what the last thing you did was, and paste in the error message into a quote block.
• Alternatively, you can hit "print screen" and upload the image of the CTD + error window for us.
• If you get no message, please still report but clearly state you got no message.

As for how long you play in windowed mode, it's completely up to you. Personally, I will be playing in windowed mode for the next few days (so will a few other devs and testers). Hopefully, we'll be able to figure out the cause of all these annoying CTD's and have them all fixed

Description:

Describe what happened right before the CTD occurred and list how many people you know of that CTD'd

Error Message:

Show the error message you got upon crash

Tested On:

List the server and map you were on. Include the map layer if you can.

System Specs

List your system specs or link us to where we can find them

Played in window mode. I seem to ctd when ever the german HAT is fired near me or when using an attack chopper for over 15 minutes.

Weirdest part is I never get an error message. The game just shuts down when the previously said things happen

Tested on TG

Windows Vista

I CTD'd the first time I got this error, now I had it again but I didn't CTD.

Error: Unable to find BF2Audio.dll module.

Can't remember the first map I had it on, the second time was Fools Road, standard map layer. Tacticamgamer server.

Windows 7

I know I am not following the template but when I ran PR .95 (for , say, the fifth time) I also got 'Error: Unable to find BF2Audio.dll module' just like Robbie. This error did not effect the game audio in anyway (or other ways for that matter and it ran fine). I have not received this error since. Also note I did not install/uninstall anything new, or have anything new running.

Description:

Just CTD'd. Multiple times. One BSOD, but i think that might be my computer...
Also CTD'd on a Co-op server.. and BSOD in a Local Server I was hosting.. probably due to High Textures...

Error Message:

None. (for some reason i never seem to, even in Windowed)

Tested On:

49th - Every 3 minutes- Fixed (had to restart)
TG - 3 minutes with 64 players
UKWF - Ramiel (Round is ending)
*NWA* - Wanda Shan

System Specs

OS: Windows 7 Ultimate 64-bit
Bios: Pheonix - AwardBIOS v6.00
Processor: AMD Athlon 64 X2 Dual Core 6000+ ~3.0GHz
Memory: 3072MB RAM
Page File: 5291mb Used, 1932MB available

Display
Device: ATI Radeon HD 4890
Approx. Total Memory: 2297MB
Display Mode: 1920 x 1080 (32) (60hz)

Sound
Creative X-Fi XtremeGamer
Using beta test drivers for fixing BSOD. Worked on Ultra High throughout .91. No BSOD's whatsoever.

Description:
I was standing on a balcony on Al Basrah, none of my squad crashed which usually is the case.

Error Message:



Tested On:
NWA Server and the map was Al Basrah.

System Specs

Nvidia GTX 295 gfx card
6 GB RAM
Intel i7 920 CPU
Vista 64 OS

Description:

after 4 rounds CTD i were speaking trough BF2 voip

Error Message:

None.

Tested On:

- server - i dont remember

System Specs all STOCK

OS: Xp sp3
Processor: i7 Xeon 3520 -aka 920
Memory: 12gb RAM
Page File: ~6000mB Used, 2500MB
gfX nVIDIA 8800 gtx 768 MB
Display Mode: 4300X1000 - i don't remember right now 3x22` monitors

Sound
Creative SOUNDBLASTER zx

NOTES:
its seams that turning off Threaded optimization in nvidia graphical settings helpt a lot
before that i had ctd every 30 min,

Description:
1st map to load works fine, and plays fine. My problem occurs at map change.
Consistent crash at at 13% of new map loading. I have made it from Lashkar(skirmish) to Kokan(64) and a map change on muttrah only server without crashing once.

Error Message: the 2 i've caught.

and
hmm, only shows one Screenshot. look for next post
Tested On:

TG server: TG-server (iron eagle), and BW-server(Kokan)
System Specs

Win 7, 32 bit, Quad core CPU, 4 gigs Ram, GTX460

other error msg

Hi from Alpha PR here.

Yesterday we were playing on 10th community, we didn't get mass crashes and we played for over 3 hours maps in Fools road and Baracuda.

Description:
While Loading In on every map except for Karbala, Kashan I CTD at 60 % load in. Every time very disappointing.

Error Message:
No Error Message, Literally Just tried 5 times, no message each time.
Tested On:

List the server and map you were on. Include the map layer if you can.
Hardcore Gaming Clan Server, IRon Eagle.
System Specs


Windows Vista, 4 gigs ram, ATI Graphic Card 3500 i believe.

Side note: CTD when on mortars, if i dont CTD the whole screen is distorted, same things happen when gunning/driving certain vehicles on certain maps.

I got the same issue except I CTD around 80% (textures). Tried few times but always the same problem. Goodbye to PR?

Something interesting just happened to me.

I was AFK for ages (seeding) and when I finally spawned in at MEC main on Muttrah I saw 4 or 5 guys insta die, I assume they CTDed.

I've got no idea if its relevant or just coincidence.

Description:

CTD or Bluesreen on Kakon/Burning Sands/Iron

Error Message:

Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7600.2.0.0.256.48
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 50
BCP1: FFFFFFFF80F70000
BCP2: 0000000000000000
BCP3: FFFFF80002ADA690
BCP4: 0000000000000005
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\101910-13572-01.dmp
C:\Users\Holger\AppData\Local\Temp\WER-36987-0.sysdata.xml




Tested On:

ABC Server and NWA UK

System Specs

Operating System: Windows 7 Professional 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)
Processor: AMD Athlon(tm) II X2 250 Processor (2 CPUs), ~3.0GHz
Memory: 2048MB RAM
Available OS Memory: 2048MB RAM
Page File: 1039MB used, 5102MB available
DirectX Version: DirectX 11
Graphic: Ati Radeon 5770
Sound: Xfi Extreme

W4chhund, your Problem sounds more like the X-Fi problem.

Was it the Second map you where playing on?

if so, the problem might most likely bee your Soundcard. I got the same and i actually close the Game on every mapchange and restart it. If i don't do that i get a Bluescreen on the second Map.

Hate to report that UKWF server just had a MASS CTD on the Brit team. They are running 0.957b

I Was not on the Brit team. So I can not show a log. But I felt that I should point it out as 0.57b is meant to fix the MASS CTD

v0.957b is meant to fix all of the known causes for CTD's. Obviously there are still some problems we haven't been able to track down and identify. Of course, once we figure out the root problem, a fix will be issued. Until then, keep posting those error logs.

Description:

Iron Eagle was loading, as soon as it was about to click over to "94% Textures" the game crashed

Happened to some people, although they may have crashed during different parts of the loading process (I have previously crashed anywhere between "90%" and "Squad Deployment"

Error Message:

No error message given upon crash

Tested On:

Local Server (for sake of test, same problem occurs on every server running the map - also on .957b) - Iron Eagle 64 Std

System Specs:

Intel Core 2 Duo T5550 @1.833GHz
3.00GB Ram (plus 4GB readyboost)
Mobile Intel 965 Express Chipset
Vista 32bit

^For reason or another this problem was fixed when playing in windowed mode. Don't know what caused that.