Official CoD Thread.

[wz1]

Sorry wrong thread

[jasongst]

my problem before was the game would just randomly FREEZE the screen i could still hear sound effects even the end of dialog that a chracter would be saying.. but i could not controll anything or hear windows ding if i tried to alt tab out.. (effectively the game sort of froze).. this would happen anywhere from 2 minutes to 1 hour... USUALLY within an hour..

I have a fix. This fix might apply to you, and in fact it might apply to MOST people who are having CoD crashes. It's at least worth a shot:

I spent a lot of time (like the rest of you) trying to identify the source of my CoD crashes. I tried all sorts of driver versions, power supplies, and whatnot. I actually narrowed it down to one SETTING in the game itself that can fix the problem. Okay, you know those two detail settings in the menu that you can set to "Extra"? I set the top setting (the one that affects the gun model) one notch down to "High" or whatever, and it eliminates the freeze (I get that same freeze as you, where the screen stops moving but the sound goes on; it's a video card freeze, that's why the rest of the system continues on normally).

I am CERTAIN this adjustment is why the crashes no longer occur. I can set it to "High", go crash-free for months (forever, actually; I've had zero crashes), then set it to "Extra" just for kicks and get a crash within 30 minutes. I can leave the second setting on "Extra" with no problems. Evidently this crash has to do with certain high-resolution textures (or models perhaps?) with OpenGL apps. Doom 3 has the same problem for me.

I have a 9700pro and 512MB of system RAM. My board is a KT133 with an Athlon XP running at 2Ghz (20x100). I'm running Windows98SE. The driver version doesn't seem to make a difference for the crashes; hopefully the fix I posted affects all drivers versions.

[DTW]

I have a Pentium IV 3.2Ghz computer with a Radeon 9800 All-In-Wonder Pro installed. RAM is 1 Gb, Sound card is Audigy. It runs WinXP Home edition SP1.

Anyway, its a new computer. I figured that because its brand spanking new, it could play all the latest games! Wrong!!

I installed Call of Duty, and Doom 3. The games start OK, but when I try to "Start New Game", the box that comes up asking me to select level of difficulty is redundant. I click on any one, it just pauses, then puts me back into the main menu again. This "select difficulty level" box should have a border around it, judging from looking at my friend's computer, which works fine. Mine doesn't have the border.

So, what have I done so far?

1) Installed DirectX 9.0c. No good.
2) Went to ATI site and downloaded their "C.O.D (Call of Duty) fix". Name of the file is wxp-w2k-catalyst-8-042-040803a-016701c.exe. So the driver version for my video card is now 6.14.10.6467. Still no good!
3) I tried various places, asking this question, and they keep telling me to check the driver. Well, I have done that.

I know it has to be something thats easy peasy to fix. But I can't wrap my finger around it! Is it the BIOS? Is the card fubar? Have I installed the drivers wrong? I really do not want to take the computer back to the shop, looking like a jackass!

I know there are some real experts here in this forum that can offer some help here. I would be really, really grateful if you could help.

[Wedge_manaic]

Wow, slicker than snot...that's umm...what we all want

Seriously, glad you spotted another culprit in this CoD conspiracy to drive us all mad. This info might help somebody.

[cyberized]

Like many here I thought my COD problems were due to my Video Card or Drivers and/or the makers of COD - - - - I found out the problem was like "closer to home" = ME and my own System. I had been CRASHING like crazy - was searching for da answer, along the way, someone said, since I am OC"d try running Prime95 to see if my 'puter is stable to begin with.
I ran Prime95 - w/in 1-2 minutes it STOPPED - said a hardware problem caused it to cease running. I decided to go into my BIOS and raise my VCore again and see what would happen.
I raised it from 1.6V to 1.66V. re-booted and ran Prime95 all night w/o a hick up. Today - after that I am back in the Battle - COD runs now slicker than snot - Thank GOD!

More Juice - Bruce!

Carry ON Soldiers!

[drho]

yeah, i'm new to the PC world (a mac user here) so i didnt even think to scan the computer for viruses, trojans etc (i've been using macs for like 14 years an d not one virus!) so i scaned it, and there it was, it infected like 384 system, and system related files. fixed it, re-intalled the apps that it had crippled and everything is working right again. you live and learn i guess..

[Furious]

Thanks for posting and admitting the actual problem. Too many find out that it was something totally unrelated to their video card and drivers but never post that fact.

It takes guts to do that.

[drho]

hmm...well it turns out that i had a virus on my machine. now the game is running with no problems...BTW: helluva game!! wish it was longer though....MP rocks!! been playing 5 hours a day now! curse work!!

[drho]

hmm....cool i'll try that.

another thing. i couldnt get Single Player working for a long time. and frankly i had given up, and was going to wait until activision released a patch or something. but at the same time cod sp was crashing i was also getting WMI errors. So i stoped the service and disabled it. uninstalled COD, reinstalled COD with no Direcx9b and voila! i playerd for like 3 hours straight!! BTW i am using 3.10, have fast writes off, VPU recover off, etc. saved the game quit the game. watched some tv. loaded the game and BAM crashed again. same way: game screen will load then immediately the PC will reboot. well then...i uninstalled COD again, re-installed and loaded my saved game and..guess what? it worked, played for another 2 hours then went to sleep. ok then maybe i will have to uninstall the game and re-install again to play tonight? who knows....this is a bit irritating..but oh well at least i can play for a while longer wonder why it does this?

[2Drunk2Funk]

Originally posted by drho
ok tried multiplayer and when i try to give my unknown soldier a name, the game crashes. it tells me "CoDMP.exe has encountered an error.....: i press the dont send button and the PC reboots itself. wtf?

Couple of ways around having to key it in;

If you use ASE browser then just do CTRL/N to set name and ASE will load COD with it.

Or
Locate your MAIN directory where you installed COD
Create a file called autoexec_mp.cfg
Edit the file and add
seta name "Yournamehere"

COD checks this file every Multiplayer map load.

May help

Also, use Cat 3.10

[Electricview]

well i'm fed up here.. i re-installed windows and installed 3.7 cats (which i'm sure i got originally becuase I bought the card mid september and thast what was out at the time, and i downloaded them off their website)... and it SITLL ccrashe...


BUT i tried some things from the front of this post.. i changed a setting in my bios from "assign irq to vga" to no... then i also set the apature agp size to 64 meg from 128 that i used to have it at... i think i changed one more thing but i thinkthe irq thing was the biggest thing, and now the game has been playing for 3 hours without a lock up or crash.. i THINK maybe i've gotten somewhere, but i'm NOT calling it fixed yet.. it could still easily crash..(i might have changed one other thing i cant remeber right now)


oh yea the other thing i did was before its power cable (the radeon) was being split between 2 fans AND a hard drive, so i got it on just itself and the hard drive sharing the cable.. (best i can do)...

So i'm not sure if all of those things together did it or what.. but so far so good.. like i said i'm not counting it fixed.. but it seems to be working SO FAR for 3 hours..


my problem before was the game would just randomly FREEZE the screen i could still hear sound effects even the end of dialog that a chracter would be saying.. but i could not controll anything or hear windows ding if i tried to alt tab out.. (effectively the game sort of froze).. this would happen anywhere from 2 minutes to 1 hour... USUALLY within an hour..

if you have a similar problem start with your bios. it SEEMS to have fixed things for now.. but only time will really tell.. if it locks up in 5 minutes i'll be so discouraged becuase i have no idea what could be next.. i'm also feeling like not jinxing it and staying with 3.7's and not going to 3.10's.. even IF the problem was the bios.. i just want it to keep working!

[slats]

no more lockups

this is crazy.......experienced at one time or another all the listed lockups and freezes with this game. Finally dropped FSB from 200 back to 166 and all was well. Not satisfied that this was the only game that wouldnt run in this config I not to eagerly updated to win xp sp2 beta today and whala!!!! 16x12 8x ani with everything including sound maxed and smoth as silk. I am not advocating people attempt to run beta software espicially windows to fix this problem but I was fed up with dealing with this particulary issue and was willing to try anything I thought could help.......and it did.....strange.....very strange...


Epox 8RDA+ v 1.0 nvidia 3.13's
XP 2400+ @ 200x10 aggresive cpu settings
2x256 Corsair [email protected]
Gigabyte 97Pro default

This is with cat 3.10's vpu recover on and fast writes on.

[TiTaNiUm]

Man i just Re-Installed this game...Damn its Cool..I read in a prior post that the Game runs OGL..Is this true??..i think so, becouse this time i cranked up my OGL tab, and (i dont know if its me), but Damn it looks Awsome..Especially the Fire and Smoldering wood in the first mission....I dont recall it looking like that before....I see alot of people are still having issues..Not Good...I guess there isnt a Cure All for everyone...

[Furious]

Originally posted by slats
i tried a lot of different items all that has been listed and the only thing that has helped was taking my system back to a 166mhz bus instead of 200 here is my setup

Epox 8RDA+ rev1 Nvidia 3.13's
XP 2400+ @ 200x11
Corsair [email protected]
Gigabyte Radeon 9700 Pro default
Cat 3.10
windows xp pro


Before dropping bus back to 166x12 I replaced the 9700 with my 9500Pro and got same lockups. I'm gonna try going back to 200 FSB and up the cpu voltage a little although I really think its the 1.6v chipset voltage that killing thats killilng me at high FSB. Just a thought cause I've run out of other solutions and dropping to 166 fsb made the game run.

Yeah I've got the same board and couldn't get it to run at all at 200mhz fsb. I wish I had the 8RDA3+.

[slats]

i tried a lot of different items all that has been listed and the only thing that has helped was taking my system back to a 166mhz bus instead of 200 here is my setup

Epox 8RDA+ rev1 Nvidia 3.13's
XP 2400+ @ 200x11
Corsair [email protected]
Gigabyte Radeon 9700 Pro default
Cat 3.10
windows xp pro


Before dropping bus back to 166x12 I replaced the 9700 with my 9500Pro and got same lockups. I'm gonna try going back to 200 FSB and up the cpu voltage a little although I really think its the 1.6v chipset voltage that killing thats killilng me at high FSB. Just a thought cause I've run out of other solutions and dropping to 166 fsb made the game run.

[PHATandy]

Firstly my problem is not with the actual game CoD but the probablem is with the CoD radiant editing tools. They worked perfectly when i had the 3.8 ctlyst drivers but now i have the 3.10 when i load a map in the editor its crashes to desktop with no error, just a clean crash to desktop. I have had no problems with my ATI Radeon 9600 xt, before just this one.
i dont want to revert back to the 3.8 drivers, so does anyone know the fix for this, any help appreciated, thx,PHATandy.

[Electricview]

Tried Directx re-install.. no change..


so a friend pointed me to a COD hotfix file.. some 20 meg file which i suspect was just the 3.9 drivers..


installed those.. and guess what.. my moniter no longer works...

when i turn it on all i get is a BRIGHT line down the center of the moniter (I can see see things inside this line like windows booting) i even took a picture with my digital camera..

I think ati has something to answer for since their hotfix driver seems definately to be hot, becuase it fried my friggin 900 dollar monitor..

[Electricview]

Its a radeon 9800 flash upgraded to a pro is all.. with installed heatsinks on the ram.. but like i said i played for 5 and 8 hour gaming sessions with no lockups before i got the bright idea of upgrading the drivers ..


I hope a reformat isn't in the cards =(


I have the 10's downloaded i guess i cant loose much installing them, but i cant help thinking ONE thing got installed or changed that isnt' getting changed back hence why i'm crashing so randomly.. would a directx re install do anything?

[The Colonel]

Re: crashy washi

Originally posted by Electricview
I'm pretty sure i tried the 3.10's with no fix luck, i might have to try them again..



first had 3.7's (i'm pretty sure) from the beginning.. played this game all the way through
not one single lock up or crash, in this or any of my games!

decided it was smart to upgrade to 3.8 and then 3.9 (Tried both) now i get RANDOM crashes in call of duty and have had similar crashes in BF1942... I'll be runnin around after anywhere from 25 minutes to 1 hour or so, and the screen just FREEZES.. but i have game voice running in the background i can still talk to my friends but cant get back to windows, it just hangs there on the screen, after about 2 or 3 minutes, the moniter shuts off.. the only way to fix is a HARD REBOOT.. SOMETIMES the screen just shows scramble mumbo jumbo instead of shutting off this tells me DRIVER PROBLEM not game problem.. i tried fast writes OFF In 3.9's still did nothin for me..

recently removed anything that ATI in the filename and re-installed cat 3.7's..

still crashing.. woe is me..

I also have a sb audigy 2.. but like i said everything worked PEACHEE before upgrading
my drivers.. i have since then tried 22khz ... eax 3.. still crashing randomly.. (multiplayer)
kt266 chipset mobo..

maybe i'll try 3.10's again, but i'm not hopeful...

A reformat my be on the cards

[Furious]

I'd try a clean install of the 3.10's. Also are you overclocking anything?

[Electricview]

crashy washi

I'm pretty sure i tried the 3.10's with no fix luck, i might have to try them again..



first had 3.7's (i'm pretty sure) from the beginning.. played this game all the way through
not one single lock up or crash, in this or any of my games!

decided it was smart to upgrade to 3.8 and then 3.9 (Tried both) now i get RANDOM crashes in call of duty and have had similar crashes in BF1942... I'll be runnin around after anywhere from 25 minutes to 1 hour or so, and the screen just FREEZES.. but i have game voice running in the background i can still talk to my friends but cant get back to windows, it just hangs there on the screen, after about 2 or 3 minutes, the moniter shuts off.. the only way to fix is a HARD REBOOT.. SOMETIMES the screen just shows scramble mumbo jumbo instead of shutting off this tells me DRIVER PROBLEM not game problem.. i tried fast writes OFF In 3.9's still did nothin for me..

recently removed anything that ATI in the filename and re-installed cat 3.7's..

still crashing.. woe is me..

I also have a sb audigy 2.. but like i said everything worked PEACHEE before upgrading
my drivers.. i have since then tried 22khz ... eax 3.. still crashing randomly.. (multiplayer)
kt266 chipset mobo..

maybe i'll try 3.10's again, but i'm not hopeful...

[Killdozer]

I'm getting crazy graphics corruption and I'm using cat3.10, any ideas?

[Hardflip]

Still crashing here. I can play under safe mode with up to a 1024x768 resolution, but the moment I increase a texture to a 'high' setting it crashes the game.

I have a 9700 Pro, 768MB DDR SDRAM, SB Audigy 5.1 and ASUS A7N8X deluxe and I ran the first COD demo fine, 1280x1024 maxed out settings back when it first came out.

Problems with the textures, perhaps.

[Emig5m]

Well I don't know if you guys read my post in the official 3.10 thread but I fixed my constant CoD crashing problem once and for all. I had my cpu OC'd from 2700+ to 2800+, not a big OC I know, but was using stock voltages becuase I like my system nice and quiet. Anyway... Clocking my cpu back to it's defualt speed cleared up my all my crashing in CoD. Fastwrites are on, AGPx8 is on, 4Xfsaa, and aniso maxed out on quality and not one crash yet. Funny how the system seemed perfectly stable for a year at that setting until CoD, lol. Something you might wanna try out if you're OC'ing anything.

[drho]

ok tried multiplayer and when i try to give my unknown soldier a name, the game crashes. it tells me "CoDMP.exe has encountered an error.....: i press the dont send button and the PC reboots itself. wtf?

[drho]

ok i just bought the game yesterday. game crashed on the obstacle couse. i'
m using:

Athlon XP 2000+
Radeon (7200) 64MB
HotFix Catalist Drivers. 3.10
256mb ram
Soundblaster Live! Card
Win XP Pro

ok when it first crashed i figured i un-install then re-intall without using the Direx 9b drivers since well...my Radeon card is not a DX9 card , did that and was able to get through a few levels. now i'm stuck on the German alps level. at the start of the level after taking out the first german machine gun post the computer restarts itself (same thing it was doing in the obstable course) i try again in safe mode, and still at the same exact spot , the PC reboots itself. ok so i read on this thread and tried a few things, turned off Fast Write, did the dll exchange thing, re-installed the hotfilxx drivers, havent tried it with VPU Recovery off yet. but will try it. so far no luck. kind of annoying. game is freaiking awesome! but the fun really takes a hit when i have to keep rebboting, and i get no damn explanation!!

[Hozmoney]

I just want to say that the 3.10 hotfix has totally worked for me. I'm near the end of the dam level and I haven't had a single crash. The game is smooth and fast. Thanks to Catalyst Maker for the fix. The game is so fun when you're not constantly reseting.

I'm running at 1280x1024 and have all textures on High.
Fastwrites off in BIOS (always have been)
AA @ 2X
VPU recover is on

[Emig5m]

Originally posted by barred
G.i>Bro I had tried the fotfix that you had lionked to befor posting above, Unfortunatly no difference with fast writes turned off in the BIOS.

What bios version does your 9700pro have? It's a long shot perhaps, but I think our bios version might have something to do with it. I just don't feel like flashing my bios, uninstalling/reinstalling new drivers and testing a game I've already finished right now until I have some extra time with nothing else to do.

[Furious]

Originally posted by Jager
http://www.rage3d.com/board/showthre...post1332420448

Oops, looks like firingsquad doesn't like that.

[Furious]

Originally posted by Mister_Frosty
omg...somebody read the "read me" ??? good thought though... I got a 128 card and have details maxed out

Yes it's a good point although I also have the details maxed without a problem.

[Furious]

Originally posted by Mister_Frosty
I know I was surprised... lol... I am still messing with my multi and fsb settings... that is why I was using 3dmark2001se to begin with. everything worked fine before the patch and 3dmark2001se didnt run after... I hadnt made any changes though...fsb and multi were still the same... so strange... I went back to stock settings just to see if that helped and it still crashed.

You might try reinstalling 3dmark. I've had those problems periodically with 3dmark and a reinstall has fixed it for me before.

[Jager]

http://www.rage3d.com/board/showthre...post1332420448

[Mister_Frosty]

omg...somebody read the "read me" ??? good thought though... I got a 128 card and have details maxed out

[vick1000]

I apologize if this has been posted already,but I don't have time to read all the pages in this
thread......

In the "Read Me" file that came with my COD demo,it states that 128MB card owners should
use Normal General Textures or lower,and that only owners of 256MB cards should use the
High setting.When I first played the demo I cranked all the settings up and the game started
crapping out hard after engaging the gunner on the halftrack,and the sound went out
completely,when I exited by way of the menu,I got a corrupted screen,and a hard reset
was neccisary to recover.So,I checked out the Read Me,and found the above,changed to
Normal General Textures,as well as the 2d sound driver,and completed the demo all the way
through smooth as silk.Driver is 3.9 default settings,DX 9.0(not a or b),Win98se,1024x768x32.

BTW,Fastwrites disabled in BIOS,Mainboard supports AGP 4x only,and both ATi background
services are disabled.Also I have no option to disable or enable VPU recovery with Win 98se,
apparently it is a XP/NT exclusive feature.No instabilities with this system,used for games,
DVDs,and net surfing,primarily.

[Mister_Frosty]

I know I was surprised... lol... I am still messing with my multi and fsb settings... that is why I was using 3dmark2001se to begin with. everything worked fine before the patch and 3dmark2001se didnt run after... I hadnt made any changes though...fsb and multi were still the same... so strange... I went back to stock settings just to see if that helped and it still crashed.

[Furious]

Considering that 3dmark is DX and not OGL that is surprising.

[Mister_Frosty]

I was able to play COD for a while with no errors after installing the hotfix, although 3DMark2001SE wont run... whats up with that?... it ran fine just prior to the hotfix

[barred]

G.i>Bro I had tried the fotfix that you had lionked to befor posting above, Unfortunatly no difference with fast writes turned off in the BIOS.

[MrThc]

The hotfix has definately worked for me. I had no stabilty problems with Cat 3.7, but I had to disable fastwrites for the game to run with 3.8\3.9. The 3.10 Hotfix works perfectly for me without having to disable Faswrites

[tiredguy]

I installed the new drivers , installed COD , configured it , did the training and proceeded to the first missions welcome screen where I was blue screened.

I had to hit the reset button. There wasn't even any text with my blue screen - just a blue screen and sound looping.

I'd say I had problems sooner with the new drivers which are supposed to fix the issue than I did when I had the older ones.