Project Reality Forums

I reinstalled my punkbuster and it happened again not long after. Any permanent fixes, its really annoying?

Have you tried to update too? Another thing you could check is if Punkbuster B is still running, press CTRL+ALT+DEL and then go to Processes & shut it off manualy in that section. I recommend u to cancel Punkbuster A too.

Check Punkbuster B is set to auto re-start.

=HOG=Romeo_One_Three wrote:Open your Control Panel. Go to Administrative Services.
Click on Services while PR is running.
Select Punkbuster B, right click, select properties, select the
recovery tab and make sure they all say "Restart the service" for all three dropdowns.
Then restart Punkbuster B.
You can do the same for PB A, but generally speaking, it's the B client that stops responding. Any time you update PB, you may need to re-do this step.

W7 users = In services ( inside the 'log on' tab) check box which states “Allow this service to interact with the desktop.
(Note over 90% of PR servers check your PC for Punkbuster A and B )

'[R-COM wrote:thepalerider;1350322']Check Punkbuster B is set to auto re-start.


W7 users = In services ( inside the 'log on' tab) check box which states “Allow this service to interact with the desktop.
(Note over 90% of PR servers check your PC for Punkbuster A and B )

did this and worked for one day, the next day it didnt, i keep on trying and it keeps on kicking me, and reseting itself!!!!!

Mujahideen_Talib wrote:and it keeps on kicking me, and reseting itself!!!!!

I have the exact same problem. It often resets itself between map loads, so everything is going nicely for an hour and then Bye Bye...

slothrop wrote:I have the exact same problem. It often resets itself between map loads, so everything is going nicely for an hour and then Bye Bye...

What kind of compatibility setting you have turned on in bf2.exe, pr.exe and punkbuster executables? None of them are actually needed and punkbuster is even vista compatible by default.

In case of PunkBuster stability issues in Vista & Win7 I suggest removing and completely re-installing PunkBuster Services and then updating it using PBSetup.

PunkBuster enabled games have to be manually added into PBSetup. When doing that, remember to check that your BF2 installation really is located where PBSetup expect it to be:

So if you have installed BF2 to a nonstandard location or you have moved it afterwards, make sure that the highlighted box in the picture above contains correct path. And if the path happens to point to a wrong folder, chances are that you have edit Windows registry in order to get rid off PB issues.

Thanks Clueless, I will try this tonight and let you know how it works out.

Checked PB installs - everything is where it should be.
Checked compatibility - BF2 was set to run in XP mode. Unchecked that.
Successfully logged into Hog Muttrah this morning without running Services or checking that PB is set to restart.
Tried logging in to Big D AU Gaming tonight and was kicked twice - PB failed to initiate PB:B and was not to set to restart when error occurs...

I have now set PB:B to restart, stopped PB:B and will start PR again to see how that works out...

Ok, tried that and failed to log in. Checked PB in Services, PB:B had started but had reverted to its original state, i.e. it did not take any action when an error occurred. The question is, what is going wrong.
I should add that I have map load times of approx 2 minutes.

This is what worked for me.

When you start pr and load a map, alt+tab out and go to Task Manager. Find pnkbstrA and PnkBstrB and set their priority to above high or high. What ive found, it seems pb service b is dropping out due to lack of cpu priority. Try it .

Oh and make sure you updated PB and have services installed ^^

Let me know how it works.

Thanks for the suggestion. This is the kind of thing I have been doing, but PB seems to reset itself every so often between maps ... so I end up getting kicked after a game or two and never know whether I will be in the next game or not.
Any permanent solutions?

could be your ping time with the server causing pb to stop getting checks