Searching on Twitter for latest “gripes” regarding bad pool caller resulted in this winning article as the FIRST result:ĭetails in the article identify that the LiveUpdate downloaded Intrusion Prevention signature sequence 4 r61 was to blame, and that the r62 release should be used as a replacement.
Should I check the Event Logs if I can? Should I try to see if I can stay logged in enough to run NirSoft BlueScreenView to review dump or minidump files for additional investigation? Should I begin review of the affected machines in any inventory/configuration management systems? The list goes on…įortunately, we live in a time where simply searching for the answer online is more advantageous – remember, social networks have an unreal ability to index and surface results in real-time. Imagine just finishing your morning iced coffee (yes iced, don’t judge), and hearing reports from multiple users that either upon login attempts OR after 15-20 minutes after logging in, the system experiences a BSoD and reports a stop code of BAD_POOL_CALLER with indication of bugcheck for IDSvia64.sys: BAD_POOL_CALLER = No productivity for you today!Įven the most skilled/trained engineers or support specialists get tripped up on where to start with these types of error reports.
0 kommentar(er)
