For me it didn't work. And ive done exactly like u said...
Call of duty 4 crashes in Windows 8.
My COD4PC has stopped working once upgraded to Windows 8, the error I am receiving is caused by a Punk buster malfuction, caused by a faulty module named "PBCL.DLL" in the "C:\Program Files (x86)\Steam\steamapps\common\Call of Duty 4\pb" folder, playing in non punkbuster servers will run fine, then when I go into PB enabled servers the game will result in a crash. *Worked fine in Windows 7.
Error from Event Viewer:
Faulting application name: iw3mp.exe, version: 0.0.0.0, time stamp: 0x4859a219
Faulting module name: pbcl.dll, version: 0.0.0.0, time stamp: 0x50522bb2
Exception code: 0xc0000005
Fault offset: 0x0000d08e
Faulting process id: 0x23b4
Faulting application start time: 0x01cdbec1d13fa23f
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Call of Duty 4\iw3mp.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Call of Duty 4\pb\pbcl.dll
Report Id: 5db6d05a-2ab5-11e2-be6c-4437e60a3958
Faulting package full name:
Faulting package-relative application ID:
Original title : COD4PC Crashing - Punkbuster (PBCL.DLL)
Windows for home | Previous Windows versions | Gaming
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
51 answers
Sort by: Oldest
-
Anonymous
2013-01-10T17:54:47+00:00 -
Anonymous
2013-01-11T00:19:38+00:00 Did not work for me
-
Anonymous
2013-01-12T02:31:50+00:00 It worked perfectly for me cheers, no more problem with COD4 on WIN8
-
Anonymous
2013-01-12T12:10:34+00:00 Glad to know it helped someone.....Ps click "me too" button and "Answer" to which that did so we can help others with the same/similar problems.....Thanks!
-
Anonymous
2013-01-12T13:22:37+00:00 Glad to know it helped someone.....Ps click **"me too"**button and "Answer" to which that did so we can help others with the same/similar problems.....Thanks!
worked for me to!. where the heck did you find this fix?