Call of duty 4 crashes in Windows 8.

Anonymous
2012-11-15T04:18:36+00:00

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.

0 comments No comments

51 answers

Sort by: Oldest
  1. Anonymous
    2013-01-13T16:57:30+00:00

    hey gravityforce;

     

    Since i see you have a solution that seem to work; i tried clicking your link. It says the page can't be opened. Could you please send a proper link from this new iw3mp.exe so i can test if it works:D?

     

    Great,

     

    Freek

    the download link works. so what is the problem.

    here is it again:

    http://www.mediafire.com/?gtva9wawv84al2g

    good luck.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-01-13T17:04:30+00:00

    hey gravityforce;

     

    Since i see you have a solution that seem to work; i tried clicking your link. It says the page can't be opened. Could you please send a proper link from this new iw3mp.exe so i can test if it works:D?

     

    Great,

     

    Freek

    the download link works. so what is the problem.

    here is it again:

    http://www.mediafire.com/?gtva9wawv84al2g

    good luck.

    i stand corectid. the .exe doesent work. now i get the error mesage again.

    i still think its windows 8 fault. cod worked on xp/vista/ win 7. but not on win 8 and the win rep on this forum says that we have to report the error to activision. well thats just BS. if cod works on all windows versions except win 8 its clearly a windows problem.

    im downgrading back to win 7. i will check this forum frequlently to see if a anser is found.

    greats all.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-01-14T18:47:32+00:00

    Sorry its the 3rd time i write here. I correct my self, this does NOT work. Finds out that i was playing on a server without PB..

    Atleast you tried.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-01-17T00:06:08+00:00

    Hi.

    Give me a little more details on what you did, which level the game crashed......if it crashes on startup......error message(s) etc...... (full error message) Tell me everything you experience with the game.........Details please!.......The more details I get the more help I can provide!!!!!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2013-01-17T17:13:23+00:00

    i have the same issue. my copy is crashing at iw3mp!_l_output +some xxxx offset. the crash is exactly in this routine, on cmp [eax], 0; // eax in this case pointing at kernel area. so first i thought - it would be because of ASLR and static link between CRT and main module. or some misalignment...

    i tried to disable aslr by emet3.5 - it wrote it disabled, but idk precisely - is it working correctly with 9200 [64. so after machine restart the error returned again

    Was this answer helpful?

    0 comments No comments