MBP OSX Bootcamp Game stutter

Ok... I have had 5-6 MBP's all 17" except one 15" back in 2007. I also have a Macpro that is going bye bye. Every MBP I have owned all running XP in boot camp with all latest drivers for video etc. I really only play COD2 and it s OLD game so should be to big of a deal. I now have a 2011 17 MBP I7, 8gb ram 7200 RPM HD, 1gb ATI video card etc. I am now running winnows 7 Pro in bootcamp. THIS MACHINE DOES IT TO! every few seconds randomly and it seems to happen right when a firefight breaks out the machine will do a quick little freeze or stutter and wham Im dead.

The Macpro doesn't do it. I tried wireless and wired networking, both does it. I have turned A band off on my wireless adapter found that somewhere else, did not fix it. It does it will all games and has on all the MBP's. There isn't a game I have played that runs completely smooth without a slight pause or freeze randomly and when I say stutter or pause it is just a split second but enough to get you killed.

I have searched the net HIGH AND LOW and haven't found much about it. I am now at the point of about to build a $800 PC to play COD2 because my $2700 MBP can't..... That doesn't mean I'm leaving Mac behind, I use it for my photography and graphics business and daily use...

Any ideas?

 

Are you running the 64-bit version of Windows 7 Pro? I really have no idea why COD2 is stuttering especially since, under Windows 7 Pro 64-bit on my 13" MBP (which has a slower processor with not as many cores and only Intel graphics), I can run COD2 at the highest settings and my MBPs native resolution without any slowdown whatsoever.

Is Windows up to date, are you using an external mouse/keyboard or the ones built into the MBP, and is this only for online play or does it happen even in the single player campaign?

 

Everything is up to date via M$ website. It is 64bit Windows 7 Professional. It runs great then just before i get in a fire fight shutter------>dead. I am using a Logitech g9 mouse and a Belkin n52 gamepad my longtime combo even back form my PC only days. I haven't tried single player campaign as I NEVER play games that way always online. But I will give it a shot and see what happens.

 

Is Call of Duty 2 so old that it doesn't run properly in Windows 7? I have Rise of Nations and I have to emulate XP to run it properly in Windows 7.

Even then it isn't great. That may be your issue (so building a PC may not fix it).

If you don't have trouble with other software its probably not your MBP, I mean if its running Windows its running Windows its very unlikely that unless your MBP is broken that it shouldn't be able to do everything any other computer that runs Windows can do. Its most likely just something with W7 and an old game.

 

I'm no troll. Cod2 plays fine on new pcs with windows 7. I for the life of ne can't figure thus out. I don't appreciate this troll crap. I've been using Macs since the first intel chip incarnation. It seems simple but yet not... :/

 

The underlying hardware (GPU, CPU, Ram) in a Mac is the same as a Windows PC.

Hence if you install Windows 7 (which supports EFI naturally) on a Mac you have a PC running Windows 7. The only thing is Windows 7 is not as resource efficient so you run hotter. That is about it. There is no difference. Apple supplies all of the drivers so Windows can talk to the hardware. Most of those drivers are supplied by the part manufacturer and/or you can get them from the part manufacturer, e.g. ATI drivers. Those are the same drivers supplied with a W7 PC.

Windows 7 supports all of the hardware in the MBP.....

Edit: I thought you were the other guy.

Nobody is calling you a troll.

 

Lol, we weren't calling you a troll, we are calling the member, Win7SP1 a troll.

You have a legit question/problem.

Really, as long as the video drivers are updated, I'd try re-installing Windows 7. I'd also only use the drivers from the Mac OS X disk.

 

The troll comment was directed at Win7SP1, not you.

I suggest you upgrade to Win 7. A lot of newer computers have issues running XP because the hardware manufacturers aren't putting effort into XP drivers anymore. It might not fix your problem, but at least you'll have the latest drivers and the hope of finding somebody else who plays CoD2 on the same setup.

EDIT: What the Joker said. He/she beat me to the submit button.

 

I read Mr. MM response as being pointed towards me being a troll, may have read it wrong.

It's fresh install. I stared with the bootcamp drivers then I uninstalled the ATI drivers ran driver cleaner a couple times then installed the latest ATI drivers. Same result.... I am using a cooler master sf-19 cooler, tried it with and without. I had a Alienware m17x with crossfire 5870's, ran it fine. But it died a horrible death. Thought if stick with my MBP but it ain't happening to well.

 

Dmk2, as the original post states it is win 7 64bit professional, pretty much decked out 17" 2011 MBP with the 1gb ati card.

 

I do not use Windows like that... so I cannot be sure... but Have you been able to get newer sound drivers? I've seen a few games where bad sound drivers caused places where some sound changed or loaded in, or battle music right at certain points would cause a stutter.

 

If it happens on all games that is a bit odd. Try with doh123 said, but maybe you can go into an Apple Store and ask them?

I think they'll help you with bootcamp to an extent especially if its a constant issue.

 

Indeed you read it wrong, I should have quoted the other poster as well to make things more clear.

on the other hand you made me install COD2 again, I never finished that campaign

 

I think on Veteran its one of the hardest COD campaigns.

 

Did you try the single-player campaign? The reason why I ask is that it could help narrow down where the issue is located. A smooth single-player campaign would indicate that there is something wrong with an aspect other than the essential basic hardware (RAM, CPU, GPU, HDD, logic board, etc.). The issue could arise only when you go online. So it would be nice to know if it is the game itself (the problem should show up in the single-palyer campaign if the game or any of the basic hardware is at fault), the basic hardware, or something a little more advanced.