PunkBuster Client: O/S Exception Notice


(GUNSL1NG3R) #1

Been noticing this in the console lately.
PunkBuster Client: O/S Exception Notice (in blue) and
WARNING: (yellow) idGameLocal:: ClientUpdateView: timeleft == USERCMD_MSEC abort (in red)

I see this flowing past with great speed, just repeating over and over until a pb kick.
Wtf is this refering to? I’ve reinstalled and no change.
Running win7 pro 64 bit on OCZ vertex 2’s in raid0.


(xTriXxy) #2

PB update may help


(Nail) #3

you’ll probably have to run as admin


(Brainless) #4

idk what it is. But a reboot helps. Had it a couple of times.
Or like Nails is telling update it. If nothing help goto evenbalance.com and send a ticket.
They will help or post it on a pbbans or punksbusted.


(GUNSL1NG3R) #5

Proir to posting earlier I updated PB, reinstalled the game and PB and updated both again.
Been running as admin all along. I’m always rebooting pc, router = no change.
This even occurs playing offline with bots but no kick.
IDK, may just do a secure erase on the drives and reinstall everything in a month or so.


(Crytiqal) #6

I think it happends when the punkbuster services arent started as an administrator. Try installing punkbuster as admin?

I have had it a few times aswell, had to reboot pc to get it working again, but I never had the problem when I explicity start the game as administrator.

PS: O/S means Operating System and it refers that you have no sufficient rights to run punkbuster as an exception on that rule that you have to be admin (as far as I can make out of it)

So in short, try installing PB itself with administrator priveleges. (Right mouse, run as admin)


(DrpPlates) #7

I get this error, often. have been for years… starting with RTCW MP… doesnt matter how many times i have updated PB or re-installed it… something for some reason gets all wacky with PB…

only known cure, that i found that works… Re boot your PC… allow the services to refresh and re start…

sucks but it works…

good old PB!


(brbrbr) #8

PBsetup and PB service setup have options to alllow you manually update them.
its very helpful in some cases[like interference with AV products, rooted PC’s, weird SW enviroment and etc].


(GUNSL1NG3R) #9

umm, yeah O/S = Operating System :tongue:

I reboot my pc several times a day. Have been running as admin all along.
As stated, reinstalled and updated both the game and PB.

I deleted binds, profile and auto exec (all saved on thumb drive) and set everything up as default. Problem remained. Then I thought about a change made 2 weeks ago. To clear my desk a bit I took a kvm switch out of storage and put it to use and included this rig.
Disconnected and plugged the keyboard/mouse straight into the pc and problem solved.

I then copied my binds and profile back and all was still well. Added my auto exec and started getting 1/2 that messege back again.
WARNING: idGameLocal:: ClientUpdateView: timeleft == USERCMD_MSEC abort

this,

PunkBuster Client: O/S Exception Notice 

no longer apeared.

Deleted everything again and then copied binds and profile back. no problem.
Started manually adding in the auto exec cmds 1 by 1 and the messege reapeared as soon as I entered
r_useThreadedRenderer “2”
It just spewed WARNING: idGameLocal:: ClientUpdateView: timeleft == USERCMD_MSEC abort
WARNING: idGameLocal:: ClientUpdateView: timeleft == USERCMD_MSEC abort
WARNING: idGameLocal:: ClientUpdateView: timeleft == USERCMD_MSEC abort

etc.
Set it to 0 and it stopped. I notice no difference wherever its set.
This auto exec was carried over from an 'ol p4 system so I guess thats a cmd I no longer need.

Anywayz, just got off a server (no pb kicks) everythings good now. Dam PB / KVM switch.
:mad::wink::smiley:


(brbrbr) #10

try sticking r_useThreadedRenderer “1” then.
both “2” threaded renderer[async mode] and unlock_timing_method “0” cause serious problems both server and client-side.
and even some cheats try to camo himself this way[by generating excessive amounts of “high FPS” traffic with crap in].


(Ashog) #11

Don’t need to reinstall PB again. Simple reboot solves the problem.