BF2:PunkBuster kicking you

From BattleWiki

bascnado An uber annoying bug is when all of a sudden you get booted via PunkBuster.

There are a variety of different error codes associated with a PunkBuster kick; an information window will tell you what your infraction was after you are kicked from your game.

Steps to resolve violations are given below with each violation category. Any player who has problems resolving a violation should fill out a trouble ticket at the EvenBalance PunkBuster Battlefield 2 website. The support team are generally knowledgable and helpful.

Technical Violations: (Resolution: Reinstall PunkBuster from the latest game update patch)

  1. 101 - Communication Failure
  2. 102 - Communication Failure
  3. 131 - Initialization Failure
  4. 132 - Protocol Error
  5. 141 - Distress (This indicates a problem trying to update to the latest version of PunkBuster - it may indicate a problem reaching one of our Internet-based Master PB Servers which can be caused by firewalls, router problems, etc.)

Miscellaneous Violations:

  1. 111 - Bad Name (Resolution: Change player name or play on a different server)
  2. 112 - Too Many Bad Names
  3. 113 - Too Many Name Changes (Designed to eliminate name change spamming)
  4. 114 - Protected Name (Resolution: Change player name or play on a different server)
  5. 121 - Negative Score Too Low (usually from Killing Teammates)
  6. 151 - Extended ASCII Characters in Player Name (Resolution: use regular letters, numbers and symbols in the player name or play on a different server)
  7. 9001 - CVAR value failed range check (see the FAQ for more info)

Integrity Violations: When PunkBuster is unable to verify that a player's gaming environment is functioning properly and/or has not been alterred, an Integrity violation is raised. This also involves the detection of modified game or PunkBuster files. These violation numbers are between 10000 and 29999.

Cheat/Hack Violations: When PunkBuster detects a cheat or hack by repeated positive identification on a player's computer, a violation is raised. These violation numbers are 50000 and higher. Families of cheats are listed below. Resolution: Remove cheats and hacks from the computer.

  1. 50000s - Aimbot
  2. 60000s - Wallhack
  3. 70000s - Multihack
  4. 80000s - Gamehack
  5. 90000s - 'Cheat' Video Drivers
  6. 100000s - Speedhack
  7. 110000s - Autofire
  8. 120000s - Game Hook
  9. 130000s - Attempted PunkBuster Hack


The error code has something to do with the win32 module list. This may refer to DLLs loaded into the BF2 process. Some trainers or other apps work by having a DLL loaded into the target process. There are some cases of programs loading things all over the place, and an anti-virus scanner might do this as well. At least one Shacker reports not having had problems since disabling his McAfee virus scanner.

A recurring problem reported by many players is that of a 507/508 "insufficient O/S priviliges" error. This is because BF2 has not been started by an administrator account. In cases where there is a single account on a computer, a password must be used to secure the account. There may also be an issue with a virus/adware item called VX2betterinternet.

If you're using a ramdisk and there's a message in the log (may have to be enabled) about OS exception, disable the ramdisk. (I don't remember what the error message was in game. It certainly gave no hint through the error message.)

One way to fix this is to manually update pb: http://www.punkbuster.com/index.php?page=updatepb.php

Or use the PBSETUP Tool: http://websec.evenbalance.com/downloads/windows/pbsetup.exe

Retrieved from "http://www.battlewiki.com/wiki/index.php/BF2:PunkBuster_kicking_you"