Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Cod4 SP Won't Start

D

DropShot

macrumors newbie
Original poster
Nov 6, 2008
1
0
I have installed CoD4 on my machine and then tried to play it immediately afterwards. When I try to start the single player version it will not load, simply crashes with an unexpected error. I tried the mp version and it started normally, allowed me to put in the serial number and move through all the menus normally. I tried the sp version several times after that and it still crashes.

Below is an extract of the report data on the error, below that is my system information. I'm not very familiar with the programming code shown. Does anyone know what causes this?

-----------------

Process: Call of Duty 4 [564]
Path: /Applications/Games/Call of Duty 4/Call of Duty 4.app/Contents/MacOS/Call of Duty 4
Identifier: com.aspyr.callofduty4
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [87]

Date/Time: 2008-11-06 08:15:25.227 -0500
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000088
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0x01e13692 0 + 31536786
1 ??? 0x01e13857 0 + 31537239
2 ??? 0x01e13941 0 + 31537473
3 ??? 0x01e13a5d 0 + 31537757
4 ??? 0x01e13c17 0 + 31538199
5 ??? 0x01e12ad3 0 + 31533779
6 dyld 0x8fe12e76 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 246
7 dyld 0x8fe0e723 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 307
8 dyld 0x8fe0e809 ImageLoader::runInitializers(ImageLoader::LinkContext const&) + 57
9 dyld 0x8fe04102 dyld::initializeMainExecutable() + 146
10 dyld 0x8fe07b5f dyld::_main(mach_header const*, unsigned long, int, char const**, char const**, char const**) + 2975
11 dyld 0x8fe01872 dyldbootstrap::start(mach_header const*, int, char const**, long) + 818
12 dyld 0x8fe01037 _dyld_start + 39

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000022 ebx: 0x01e13640 ecx: 0x00000000 edx: 0x0000000f
edi: 0xf60d18db esi: 0xbfffe134 ebp: 0xbfffe0f8 esp: 0xbfffe0d0
ss: 0x0000001f efl: 0x00010206 eip: 0x01e13692 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000088

Binary Images:
0x1000 - 0x3a2fc7 +com.aspyr.callofduty4 1.7 (77195) <fdba00cfe3aa4928a95f2fdd9f9c0743> /Applications/Games/Call of Duty 4/Call of Duty 4.app/Contents/MacOS/Call of Duty 4
0x1e27000 - 0x1e4bff3 +libBinkMachOx86.dylib ??? (???) /Applications/Games/Call of Duty 4/Call of Duty 4.app/Contents/MacOS/libBinkMachOx86.dylib
0x1e5e000 - 0x1e65fff com.apple.agl 3.0.9 (AGL-3.0.9) <aeab67ef267f8295ae80fddc197b52a5> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x1e6c000 - 0x1e6cfff com.apple.Carbon 136 (136) <ec1d4184925e652dbe1b9200a5a552ec> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
(goes on for a long way...)
-----------------------

System Configuration


Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 8 GB
Graphics: kHW_ATIrv630Item, ATI Radeon HD 2600, spdisplays_pcie_device, 256 MB
Memory Module: DIMM Riser B/DIMM 1, 2 GB, DDR2 FB-DIMM, 800 MHz
Memory Module: DIMM Riser B/DIMM 2, 2 GB, DDR2 FB-DIMM, 800 MHz
Memory Module: DIMM Riser A/DIMM 1, 2 GB, DDR2 FB-DIMM, 800 MHz
Memory Module: DIMM Riser A/DIMM 2, 2 GB, DDR2 FB-DIMM, 800 MHz
Bluetooth: Version 2.1.0f17, 2 service, 1 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: ATI Radeon HD 2600, display, Slot-1
Serial ATA Device: WDC WD3200AAJS-41VWA1, 298.09 GB
Serial ATA Device: WDC WD6400AAKS-00A7B0, 596.17 GB
Serial ATA Device: WDC WD6400AAKS-00A7B0, 596.17 GB
Serial ATA Device: WDC WD6400AAKS-00A7B0, 596.17 GB
Parallel ATA Device: PIONEER DVD-RW DVR-112D, 6.8 GB
Parallel ATA Device: PIONEER DVR-113NP
USB Device: Keyboard Hub, Apple, Inc., high_speed, 500 mA
USB Device: Apple Keyboard, Apple, Inc, low_speed, 100 mA
USB Device: Belkin n52te, Belkin, full_speed, 500 mA
USB Device: USB Printer, EPSON, full_speed, 500 mA
USB Device: USB Gaming Mouse, Logitech, full_speed, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed, 500 mA
FireWire Device: built-in_hub, unknown_value, unknown_speed
 
Dropshot, I have the same exact problem and haven't been able to find a fix. The multiplayer works fine, but the single player craps out and gives me the same error message. I have called Aspyr support (several times) and, after 3 weeks of suggestions, they basically told me that I have to reinstall the entire operating system. Which sounds pretty ridiculous, considering you are encountering the same thing.

Here are the things I did do, just to rule them out as suggestions:

downloaded patch 1.7 (retail)
erased everything each time (including Library files)
repaired disk permissions on HD
opened up a new user account and installed there
did a Software Update on my entire system
checked that the formatting was compatible (OSX Extended Journal)

sent disk back to Aspyr and received "new" disk
tried everything again with no luck

I am trying to install on a MacBook Pro, 2.2 C2D, 2 GB, 500 GB, GeForce 8600M GT. If anyone has any other suggestions please post them.

For the time being, I would suggest going to Aspyr's support site (http://support.aspyr.com/) and opening up a ticket or calling them, just so they know this is affecting multiple computers. Hope it works out for you.
 
COD4 crash on a MacPro

Same problem here. COD4 crashed right after the Infinity Ward splash screen. If I press the mouse button really fast, it'll skip that part and successfully get to the menu screen. I can tell it to start a new game, but it immediately crashes.

I just tried a manual reinstall of 10.5.5 like jvanyp suggested above, but it didn't change anything. Now I'm going to try repairing permissions.

I've looked everywhere online, and I've found a ton of people with the same problem, but there are also a ton of people running this game, too. I can't seem to find any consistent factors that the crashing computers share.

My specs:
Model Name: Mac Pro
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3 GHz
Total Number Of Cores: 8
Memory: 2 GB
Video: NVIDIA GeForce 7300 GT

Maybe it's something else like the audio setup. I'm using the Audio/MIDI control panel to configure a 5.1 output through an RME audio interface. Maybe thats it?
Is it the graphics? Is anyone else that has it working using the 7300?

Lucien.
 
I almost thought i figured it out...

I unplugged the Digidesign MBox I had on a USB port. I was able to launch the game and make it through the 'training'. It crashed again with it started to load the briefing on the first mission.

Ugh. I am so pissed. What a waste of $55.
 
SP won't start, ASPYR no help

Same problem on my Macbook Pro. I tried everything ASPYR suggested, and nothing worked. I installed the game on a different Macbook pro with exactly the same specs but running OS 10.4 (which is not supported according to ASPYR) and guess what? It runs! There's a strange glitch when the game starts: the graphics are inverted top to bottom and left to right. I have to start the game that way, but as soon as I hit Esc, then return to the game, the graphics are fine.
 
I fixed it!

I noticed in the crash log that the game was accessing some CoreAudio functions when the crash happens.

So, I reassigned the Mac OS audio output to it's internal sound (it was assigned to my RME Multiface PCIe audio card), and now the game works! No problems at all!

It's kind of annoying, but Since I usually play with my headphones on, I'm not too pissed off about it.

Unfortunately, this probably won't help you guys with MacBook's.

Next time it crashes, tell it to send a log to Apple, then copy and paste the crash information into a post here.
 
Call of Duty 4 unexpectedly quits on launch - Macbook Unibody [9400M]

I recently bought Call of Duty 4 for my new Macbook Unibody (Nvidia 9400M). I copy it to my Applications folder and then double click the Single player version and it unexpectedly quits after a few seconds of bouncing in the dock.

The multiplayer launches OK and seems to operate as it should.

I installed the 1.7 patch, but it's the still the same.

A few other things I've tried:
* Remove, reboot and re-install COD4
* Repair Disk Permissions in Disk Utility

Aspyr got back to me after a few days and said the only case they've seen of the app crashing on launch is when COD4 is installed from a different user account to the one which is trying to run the game... This wasn't the case for me, but with Access / Permission restrictions in mind I tried a few other things:


1. Deleted the Call Of Duty 4 folder and Preferences file. Created a new admin account in System Preferences, Logged out of my account and then logged into the new account. I then copied the Call of Duty 4 folder from the installation DVD to Applications and double clicked the Call of Duty 4.app, same behavior as before.

2. Tried moving Call of Duty 4 folder to ~/Applications (in the account's home folder) and then double clicked Call of Duty 4.app, same behavior as before.

3. Tried running Call of Duty 4 Single Player.app via Terminal as 'super user': "sudo open /Applications/Call\ of\ Duty\ 4/Call\ of\ Duty\ 4.app" - Same behavior as before, but also returns the error in Terminal: "LSOpenFromURLSpec() failed with error -10810 for the file /Applications/Call of Duty 4/Call of Duty 4.app."

4. Using the Terminal, I also tried:

"chown -R root:admin /Applications/Call\ of\ Duty\ 4" --to set ownership to root:admin
"chmod -R g+rw /Applications/Call\ of\ Duty\ 4" -- to give rw access to all admin users
"chmod -R -N /Applications/Call\ of\ Duty\ 4" -- to strip ACLs which may be interfering

Still the same behavior, so I trashed the new admin account and Call of Duty 4 folder and preferences file, rebooted into my normal account and tried to re-install again, no change, still the same behavior.

With Luci3n's fix in mind, I thought I'd take a look at the Audio MIDI Setup application in Utilities to see what's going on with the sound on the Macbook (i don't have any external devices connected).

I tried changing the internal sound output from Stereo 24bit to Stereo 16bit because I remember this has been an issue in the past with games like DOOM3 (iirc), but it didn't make a difference. I tried a series of different settings here and still no change.

I can't really think of what else to try. I don't understand why the Multiplayer version would work, but not the Single Player?

Here's the output of the crash report on my Macbook:

Code: 
Process:         Call of Duty 4 [294]
Path:            /Applications/Call of Duty 4/Call of Duty 4.app/Contents/MacOS/Call of Duty 4
Identifier:      com.aspyr.callofduty4
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [110]

Date/Time:       2008-11-19 17:47:12.163 +1100
OS Version:      Mac OS X 10.5.5 (9F2114)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000e80c9f0f
Crashed Thread:  0

Thread 0 Crashed:
0   ???                           	0x01e33343 0 + 31667011
1   ???                           	0x01e32972 0 + 31664498
2   dyld                          	0x8fe12e76 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 246
3   dyld                          	0x8fe0e723 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 307
4   dyld                          	0x8fe0e809 ImageLoader::runInitializers(ImageLoader::LinkContext const&) + 57
5   dyld                          	0x8fe04102 dyld::initializeMainExecutable() + 146
6   dyld                          	0x8fe07b5f dyld::_main(mach_header const*, unsigned long, int, char const**, char const**, char const**) + 2975
7   dyld                          	0x8fe01872 dyldbootstrap::start(mach_header const*, int, char const**, long) + 818
8   dyld                          	0x8fe01037 _dyld_start + 39

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0xe80c9f0f  ebx: 0x01e332cd  ecx: 0x00000000  edx: 0x00000000
  edi: 0x01e328eb  esi: 0x00000000  ebp: 0xbfffe1a8  esp: 0xbfffe0e0
   ss: 0x0000001f  efl: 0x00010286  eip: 0x01e33343   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0xe80c9f0f

Binary Images:
    0x1000 -   0x3c8fef +com.aspyr.callofduty4 1.5 (75981) <95f718c201fd07a1485f258a4a627335> /Applications/Call of Duty 4/Call of Duty 4.app/Contents/MacOS/Call of Duty 4
 0x1e47000 -  0x1e47fff  com.apple.Carbon 136 (136) <4177916bbf70e0ddc446f94001d54c95> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
 0x1e4b000 -  0x1e6fff3 +libBinkMachOx86.dylib ??? (???) /Applications/Call of Duty 4/Call of Duty 4.app/Contents/MacOS/libBinkMachOx86.dylib
 0x1e82000 -  0x1e89fff  com.apple.agl 3.0.9 (AGL-3.0.9) <0db495edc2afbed681f3ef6a5ca71741> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
 0x1e90000 -  0x1e90ff8  com.apple.Cocoa 6.5 (???) <a1bc9247cf65c20f1a44d0973cbe649c> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
 0x1e94000 -  0x1f10feb  com.apple.audio.CoreAudio 3.1.0 (3.1) <39633bb5fa20a813719ff43c5ce4fa38> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
 0x1f65000 -  0x1f72fe7  com.apple.opengl 1.5.8 (1.5.8) <1d535f1c426c6cfeb836ba04f896a6a0> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
 0x1f7a000 -  0x229cfe2  com.apple.QuickTime 7.5.5 (995.22.3) <07ffd134d58fdbfe377ba9007f591289> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
 0x2362000 -  0x2486fe3  com.apple.audio.toolbox.AudioToolbox 1.5.1 (1.5.1) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox

<.. and much more of this kind of thing ..>

0xfa100000 - 0xfa17aff8  com.apple.print.framework.PrintCore 5.5.3 (245.3) <98633ef67d419c1b02f56556cb4d843d> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0xfffe8000 - 0xfffebfff  libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780  libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib

Here's my System Configuration:

Code: 
Model: MacBook5,1, BootROM MB51.0073.B00, 2 processors, Intel Core 2 Duo, 2 GHz, 2 GB
Graphics: kHW_NVidiaGeForce9400MItem, NVIDIA GeForce 9400M, sppci_pci_device, 256 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR3, 1067 MHz
Memory Module: BANK 0/DIMM1, 1 GB, DDR3, 1067 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.38.9)
Bluetooth: Version 2.1.2f8, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MHZ2160BH FFS G1, 149.05 GB
Serial ATA Device: HL-DT-ST DVDRW  GS21N, 6.8 GB
USB Device: Built-in iSight, (null) mA
USB Device: BCM2045B2, (null) mA
USB Device: Bluetooth USB Host Controller, (null) mA
USB Device: Apple Internal Keyboard / Trackpad, (null) mA
USB Device: IR Receiver, (null) mA

I've read that the Macbook unibody and the new Macbook Pro machines use a modified installation of Mac OS 10.5.5, which is a different build to the standard 10.5.5 update. Perhaps this is where the incompatibility could be? I guess I'll have to wait for 10.5.6 to see if this fixes it..

Any thoughts?
 
aphotic:

Under Binary Images in your crash log it lists "com.aspyr.callofduty4 1.5". Are you sure the 1.7 update took? I had to manually select the App during the update installation.

Do the new Mac Books have a different version of 10.5.5? Thats very odd. Thats very un-Apple like. If that is true, it could be the culprit. Find out how they differ and that might lead you to why its not working.

Do you know anyone else that is running this on a new Mac Book? My first thought was that the new graphics chips might need an update from Aspyr to be supported. But if other people are running COD4 natively on the new Mac Pro- I'm stumped.

Send your crash log to support@aspyr.com. They didn't solve my problem, but it was chatting with them that got me to think of my audio solution.
 
Thanks Luci3n, I attempted the 1.7 patch several times, it installed successfully, but still no luck with the Single Player app!

I've been in contact with aspyr support who have now palmed me off to a company called SecuROM who apparently do their copy protection system for CoD4 SP (Multiplayer 1.5 and 1.7 still work fine on my macbook). SecuROM sent me some kind of special program that analyses my system and have sent me multiple "patched" copies of the CoD4 SP app to try out, no luck yet, still the same unexpectedly quitting behavior.

I managed to get my hand on a special no-cd "crack" version of 1.7 which I thought might get around the crashing if it's related to copy protection, but that had the same behavior again, so I'm not sure where to go from here.

I have a friend with CoD4 for windows, Maybe I could borrow it, install on bootcamp and then use my Mac CoD4 serial number? Anyone know if the serials are cross-platform? I can't get a refund on my Mac copy, can't say I'd be doing anything unethical in using a Windows copy, but it sure won't be as good as having the product I paid for.
 
Luci3n said:
aphotic:
Do the new Mac Books have a different version of 10.5.5? Thats very odd. Thats very un-Apple like. If that is true, it could be the culprit. Find out how they differ and that might lead you to why its not working.
Click to expand...

Yes the new macbook and macbook pros have a different version of 10.5.5 than everybody else due to the trackpad and the differing graphics cards which require different drivers, etc.

Luci3n said:
aphotic:
Do you know anyone else that is running this on a new Mac Book? My first thought was that the new graphics chips might need an update from Aspyr to be supported. But if other people are running COD4 natively on the new Mac Pro- I'm stumped.
Click to expand...

There are no new Mac Pro's. However they will be coming shortly in the January (I think it's in January) Apple show.
 
aphotic said:
I have a friend with CoD4 for windows, Maybe I could borrow it, install on bootcamp and then use my Mac CoD4 serial number? Anyone know if the serials are cross-platform? I can't get a refund on my Mac copy, can't say I'd be doing anything unethical in using a Windows copy, but it sure won't be as good as having the product I paid for.
Click to expand...

I haven't tried it, but I've read on other forums that your serial will work for Mac or PC. Instead of Boot Camp, you could also try Parellels to run the PC version. Version 3 doesn't work, but they just released version 4 and now it apparently supports Direct X and gaming.

Let us know how it works. I'm been thinking about doing the same just to be able to play some Pc only games.

Hopefully with the release of Open CL in Snow Leopard, Apple will start encouraging game developers. Mac is a brilliant platform for games (3D). It just needs to be supported.
 
COD 2 has same problem

I have a version of COD 2, and I have exactly the same problem...
I`m on version 10.5.3, some friends who are still on 10.4.X have no problems running the game...
 
I never had any problems at all with COD2 on 10.5.1, 2, 3, 4 or 5.

It ran like a champ on all of them. Great game.

I just played it the other day after upgrading my MacPro from the NVidia 7300 to the 8800 GT and it was like playing a new game.
 
10.5.6 update was the cure - COD4 finally works!

I just updated to Mac OS X 10.5.6 using the Combo updater and now COD4 finally works for the first time on my new Macbook!!!

It runs flawlessly. Thanks for your help in trying to get it to work. I guess something changed in the custom Mac OS X 10.5.5 build that shipped with these machines that broke the compatibility with the game..

Graphics and gameplay are very smooth on optimal settings. I think you can safely say that the 9400M is a supported card (on 10.5.6 at least!).

I'll be enjoying some Mac COD4 this weekend, Christmas has come early!
 
Thats great to hear!

If you feel like trying out the multiplayer mode, stop by the LA Domination server and say hi.

Cheers!
 
COPD 4 problem

I have a similar problem. I bought leopard just so i could run Call of Duty 4 for my my macbook and after loading it all it show me only the beginning screen with the picture and than quits on me. I cant get past it.

Someone please help me out. I spent money on leopard and the game it would be such a waste. I'm posting the report on the bottom.

Process: Call of Duty 4 [357]
Path: /Call of Duty 4/Call of Duty 4.app/Contents/MacOS/Call of Duty 4
Identifier: com.aspyr.callofduty4
Version: 1.5 (75981)
Code Type: X86 (Native)
Parent Process: launchd [67]

Date/Time: 2008-12-25 16:24:25.523 -0500
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0000000000 0 + 0
1 libGL.dylib 0x90fe0fe6 glBeginQueryARB + 38
2 com.aspyr.callofduty4 0x002f95b9 0x1000 + 3114425
3 com.aspyr.callofduty4 0x002c472d 0x1000 + 2897709
4 com.aspyr.callofduty4 0x00284c60 0x1000 + 2636896
5 com.aspyr.callofduty4 0x000a1ec9 0x1000 + 659145
6 com.aspyr.callofduty4 0x001b3e88 0x1000 + 1781384
7 com.aspyr.callofduty4 0x001b4aa3 0x1000 + 1784483
8 com.aspyr.callofduty4 0x000242fd 0x1000 + 144125
9 com.aspyr.callofduty4 0x0001f530 0x1000 + 124208
10 com.aspyr.callofduty4 0x0001dcaa 0x1000 + 117930
11 com.aspyr.callofduty4 0x0001dcf1 0x1000 + 118001
12 com.apple.CoreFoundation 0x93de1b25 CFRunLoopRunSpecific + 4469
13 com.apple.CoreFoundation 0x93de1cd8 CFRunLoopRunInMode + 88
14 com.apple.HIToolbox 0x919212c0 RunCurrentEventLoopInMode + 283
15 com.apple.HIToolbox 0x919210d9 ReceiveNextEventCommon + 374
16 com.apple.HIToolbox 0x9197fc6e _AcquireNextEvent + 58
17 com.apple.HIToolbox 0x9197e3cb RunApplicationEventLoop + 207
18 com.aspyr.callofduty4 0x0001d6ee 0x1000 + 116462
19 com.aspyr.callofduty4 0x0001d42a 0x1000 + 115754
20 com.aspyr.callofduty4 0x0001d473 0x1000 + 115827
21 com.aspyr.callofduty4 0x00002892 0x1000 + 6290
22 com.aspyr.callofduty4 0x000027b9 0x1000 + 6073

Thread 1:
0 libSystem.B.dylib 0x932f73ae __semwait_signal + 10
1 libSystem.B.dylib 0x93321d0d pthread_cond_wait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x909acb32 glvmDoWork + 162
3 libSystem.B.dylib 0x93321095 _pthread_start + 321
4 libSystem.B.dylib 0x93320f52 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x9332fb5b flockfile + 46
1 libSystem.B.dylib 0x9332d29e fread + 64
2 com.aspyr.callofduty4 0x002fb28e 0x1000 + 3121806
3 com.aspyr.callofduty4 0x002fbba5 0x1000 + 3124133
4 com.aspyr.callofduty4 0x001ea82e 0x1000 + 2005038
5 com.aspyr.callofduty4 0x0027e49c 0x1000 + 2610332
6 com.aspyr.callofduty4 0x0027e8e4 0x1000 + 2611428
7 com.aspyr.callofduty4 0x00281d1d 0x1000 + 2624797
8 com.aspyr.callofduty4 0x000a86b4 0x1000 + 685748
9 com.aspyr.callofduty4 0x000ac7d4 0x1000 + 702420
10 com.aspyr.callofduty4 0x000aecab 0x1000 + 711851
11 com.aspyr.callofduty4 0x000aed53 0x1000 + 712019
12 com.aspyr.callofduty4 0x000a76d5 0x1000 + 681685
13 com.aspyr.callofduty4 0x000b7f38 0x1000 + 749368
14 com.aspyr.callofduty4 0x002f6d71 0x1000 + 3104113
15 libSystem.B.dylib 0x93321095 _pthread_start + 321
16 libSystem.B.dylib 0x93320f52 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x932f01c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x932f79bc mach_msg + 72
2 com.apple.CoreFoundation 0x93de10ae CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x93de1cd8 CFRunLoopRunInMode + 88
4 com.apple.audio.CoreAudio 0x937c95dc HALRunLoop::OwnThread(void*) + 160
5 com.apple.audio.CoreAudio 0x937c9464 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x93321095 _pthread_start + 321
7 libSystem.B.dylib 0x93320f52 thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x932f0226 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x933221ef _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x93323a73 pthread_cond_timedwait_relative_np + 47
3 com.apple.audio.CoreAudio 0x937d8bc3 CAGuard::WaitFor(unsigned long long) + 213
4 com.apple.audio.CoreAudio 0x937da77e CAGuard::WaitUntil(unsigned long long) + 70
5 com.apple.audio.CoreAudio 0x937d8f23 HP_IOThread::WorkLoop() + 759
6 com.apple.audio.CoreAudio 0x937d8c27 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
7 com.apple.audio.CoreAudio 0x937c9464 CAPThread::Entry(CAPThread*) + 96
8 libSystem.B.dylib 0x93321095 _pthread_start + 321
9 libSystem.B.dylib 0x93320f52 thread_start + 34

Thread 5:
0 libSystem.B.dylib 0x932f020e semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x93322206 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x93367539 pthread_cond_wait + 48
3 com.aspyr.callofduty4 0x000359f2 0x1000 + 215538
4 com.aspyr.callofduty4 0x0001f7d9 0x1000 + 124889
5 libSystem.B.dylib 0x93321095 _pthread_start + 321
6 libSystem.B.dylib 0x93320f52 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x020cb200 ebx: 0x010ef620 ecx: 0x00000000 edx: 0x1b067c80
edi: 0x00000000 esi: 0x24c7a020 ebp: 0xbfffdb38 esp: 0xbfffdb0c
ss: 0x0000001f efl: 0x00010246 eip: 0x00000000 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
 
exact same problem

I'm having the exact same problem, I have a MacBood (black), running Leopard 10.5.6 and i downloaded the 1.7 patch . . . still having the problems

here is the error log . . . any recomendations?

Process: Call of Duty 4 [772]
Path: /Users/NAME/Desktop/Call of Duty 4/Call of Duty 4.app/Contents/MacOS/Call of Duty 4
Identifier: com.aspyr.callofduty4
Version: 1.7 (77195)
Code Type: X86 (Native)
Parent Process: launchd [104]

Date/Time: 2008-12-26 13:10:04.787 -0500
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0000000000 0 + 0
1 libGL.dylib 0x90408fe6 glBeginQueryARB + 38
2 com.aspyr.callofduty4 0x002c98c2 0x1000 + 2918594
3 com.aspyr.callofduty4 0x0029b84e 0x1000 + 2730062
4 com.aspyr.callofduty4 0x0025ec47 0x1000 + 2481223
5 com.aspyr.callofduty4 0x00094f1d 0x1000 + 605981
6 com.aspyr.callofduty4 0x001992b7 0x1000 + 1671863
7 com.aspyr.callofduty4 0x00199dfb 0x1000 + 1674747
8 com.aspyr.callofduty4 0x0001d56f 0x1000 + 116079
9 com.aspyr.callofduty4 0x0001a15c 0x1000 + 102748
10 com.aspyr.callofduty4 0x000189a4 0x1000 + 96676
11 com.aspyr.callofduty4 0x000189e7 0x1000 + 96743
12 com.apple.CoreFoundation 0x96edbb25 CFRunLoopRunSpecific + 4469
13 com.apple.CoreFoundation 0x96edbcd8 CFRunLoopRunInMode + 88
14 com.apple.HIToolbox 0x952d42c0 RunCurrentEventLoopInMode + 283
15 com.apple.HIToolbox 0x952d40d9 ReceiveNextEventCommon + 374
16 com.apple.HIToolbox 0x95332c6e _AcquireNextEvent + 58
17 com.apple.HIToolbox 0x953313cb RunApplicationEventLoop + 207
18 com.aspyr.callofduty4 0x000184be 0x1000 + 95422
19 com.aspyr.callofduty4 0x000181fd 0x1000 + 94717
20 com.aspyr.callofduty4 0x0001823b 0x1000 + 94779
21 com.aspyr.callofduty4 0x00001e06 0x1000 + 3590
22 com.aspyr.callofduty4 0x00001d2d 0x1000 + 3373

Thread 1:
0 libSystem.B.dylib 0x92d103ae __semwait_signal + 10
1 libSystem.B.dylib 0x92d3ad0d pthread_cond_wait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x931f4b32 glvmDoWork + 162
3 libSystem.B.dylib 0x92d3a095 _pthread_start + 321
4 libSystem.B.dylib 0x92d39f52 thread_start + 34

Thread 2:
0 com.aspyr.callofduty4 0x002d43e0 0x1000 + 2962400
1 com.aspyr.callofduty4 0x002d3eec 0x1000 + 2961132
2 com.aspyr.callofduty4 0x002cd8b9 0x1000 + 2934969
3 com.aspyr.callofduty4 0x002cd0dc 0x1000 + 2932956
4 com.aspyr.callofduty4 0x00099b82 0x1000 + 625538
5 com.aspyr.callofduty4 0x000aceb2 0x1000 + 704178
6 com.aspyr.callofduty4 0x000a04af 0x1000 + 652463
7 com.aspyr.callofduty4 0x000a076f 0x1000 + 653167
8 com.aspyr.callofduty4 0x0009a155 0x1000 + 627029
9 com.aspyr.callofduty4 0x000a9af9 0x1000 + 690937
10 com.aspyr.callofduty4 0x002c7305 0x1000 + 2908933
11 libSystem.B.dylib 0x92d3a095 _pthread_start + 321
12 libSystem.B.dylib 0x92d39f52 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x92d091c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x92d109bc mach_msg + 72
2 com.apple.CoreFoundation 0x96edb0ae CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x96edbcd8 CFRunLoopRunInMode + 88
4 com.apple.audio.CoreAudio 0x970825dc HALRunLoop::OwnThread(void*) + 160
5 com.apple.audio.CoreAudio 0x97082464 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x92d3a095 _pthread_start + 321
7 libSystem.B.dylib 0x92d39f52 thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x92d09226 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x92d3b1ef _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x92d3ca73 pthread_cond_timedwait_relative_np + 47
3 com.apple.audio.CoreAudio 0x97091bc3 CAGuard::WaitFor(unsigned long long) + 213
4 com.apple.audio.CoreAudio 0x9709377e CAGuard::WaitUntil(unsigned long long) + 70
5 com.apple.audio.CoreAudio 0x97091f23 HP_IOThread::WorkLoop() + 759
6 com.apple.audio.CoreAudio 0x97091c27 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
7 com.apple.audio.CoreAudio 0x97082464 CAPThread::Entry(CAPThread*) + 96
8 libSystem.B.dylib 0x92d3a095 _pthread_start + 321
9 libSystem.B.dylib 0x92d39f52 thread_start + 34

Thread 5:
0 libSystem.B.dylib 0x92d0920e semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x92d3b206 _pthread_cond_wait + 1267
2 libSystem.B.dylib 0x92d80539 pthread_cond_wait + 48
3 com.aspyr.callofduty4 0x0002da42 0x1000 + 182850
4 com.aspyr.callofduty4 0x0001a38d 0x1000 + 103309
5 libSystem.B.dylib 0x92d3a095 _pthread_start + 321
6 libSystem.B.dylib 0x92d39f52 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x020d0400 ebx: 0x01b3e220 ecx: 0x00000000 edx: 0x1b064050
edi: 0x00000000 esi: 0x24cd6020 ebp: 0xbfffda78 esp: 0xbfffda4c
ss: 0x0000001f efl: 0x00010246 eip: 0x00000000 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
 
so apparently MacBooks with Intel video cards are not supported and only work sporadically . . . sucks but what can you do
 
This is complete BS. I bought COD4 for Mac, played SP once, and now it doesn't work. I have the 1.7 patch installed and I can't figure out how to resolve this.

I'm using the 2.4 unibody MB. Has anyone found a solution yet?
 
What does your crash report say? It might give you a clue as to what the problem is.

On my MacPro, it was just the USB audio interface I was using. Works perfect with built-in sound.

If you don't have anything external connected to your MB, then maybe COD4 might not be updated to work with the new graphics cards in the Unibody MB...?

Lucien.
 
Luci3n said:
What does your crash report say? It might give you a clue as to what the problem is.

On my MacPro, it was just the USB audio interface I was using. Works perfect with built-in sound.

If you don't have anything external connected to your MB, then maybe COD4 might not be updated to work with the new graphics cards in the Unibody MB...?

Lucien.
Click to expand...

I have nothing connected to the MB and I was able to play SP when I first installed it. Aspyr claims that this problem occurs when you install the game using one user account and then try to play it on another. In my case, that's simply false.

I managed to fix the problem about 10 minutes ago. Essentially, I reset the permissions on the SP icon to allow read/write access for all users. After a reboot, it started to work... now let's see how long it takes to crap out again.
 
not working

i have COD 4 but when i try and open it it says WIN_IMPROPER_QUIT_BOD
i have a macbook
 
Figured it out!!!

Several but easy things to do....


As mentioned re-install with "os x extend" after erasing hard drive.

Put in leopard disk and install. It will start you computer over. Go up to the top after selecting english or whatever language, find disk utilities and select hard drive. Erase it and change it to OSX Extended.

MAKE SURE TO BACK UP EVERYTHING ON A EXTERIOR HARD DRIVE FIRST... THEN YOU MAY WANNA UNPLUG EVERYTHING BEFORE INSTALLING OSX LEOPARD

Once it finishes,

Load game on hard drive

Change access permissions to "Read and Write" for all users

(just open hard drive and click "users". open info. unlock and change.)

Also goto SP and check users. i changed it to share everything.

Download 1.7 from aspyr. (make sure you get the right version) If you have the disk or playing a downloaded version

Once you upgrade cod4 single player and then multi-player with 1.7 from aspyr, it works!

Fingers crossed:D
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back