call of duty 2 crashes

Associate
Joined
3 Jan 2006
Posts
1,942
hi as the title suggests, when i'm playing call of duty 2 after 5 mins the pc crashes. the monitor turns black and says no signal however the music continues to play. If I try to shoot as i would in the game there's nothing just music that sounds like background music.

specs
ATI x1950 pro 6.11 drivers
intel celeron 3.2 cpu
460 anatec psu
1.5 gig ram

patched the game to version 1.3 but still has issues.
this doesn't happen with other games like FEAR and battlefield 2.

can anyone help me?
Thanks :confused:
 
this is a long shot, but in your display box have you unticked the box that says "hide modes that this monitor cannot display" :)
 
drivers, always used to happen to me

running an x800 i just went back to the drivers that came with it, but since you're on a later card im not sure,

but it will be drivers yeah, or maybe some software thats running in the background
 
yeah maybe as the cards new call of duty doesn't support it yet. maybe they'll bring a new patch out. any other ideas??? All software running in background doesn't interrupt other games like far cry and battlefield 2.
 
I think I had the same as you but it deleted/corrupted my whole operating system.

Was playing COD 2 on a server, then as im moving along it freezes I can't move but I still hear the sound, my keyboard locked up as I know because I press the capps button etc and the light doesn't turn on, also pressing like 4 keys down and not hearing the internal speaker.

So I turned it off and on and then it was all laggy on the desktop and it crashed to a bsod then turned off and on again and the operating system deleted/corrupted, recovered fine with a new OS install though.
 
That PSU is fine, 30a is way overkill, thats just an over estimation to cover themselves, im running my rig with an old GlobalWin SuperSilent 520w 1.3 version PSU, only has 1x 12v Rail at 20a, powers all my rig fine, and my x1800 XT uses more power than the x1950pro. :)

Trouble is theres only the 6.11's, or the drivers that came with the card that will work with these as being so new. :(
 
Last edited:
brilliant, so the general idea is to wait for 6.12's and hopefully these problems could have been reviewed and sorted out. After reading some threads on the sapphire forum it seems like this is happening to quite a few people.
thanks
 
Back
Top Bottom