• 0
chrisbruwer0

BSOD Bad_Pool_Caller

Question

Hi,

Like most of the recent ones, I tried with PUBG and got this error. Happy to help with the logs if needed.

Interested to see if this works

1

Share this post


Link to post
Share on other sites

12 answers to this question

  • 0

Update!

We now have a help guide to assist with this problem:

Follow the steps on that page to workaround the issue. Our dev team has identified a fix for this, and they are working on implementing it quickly into a future release. Stay tuned for more updates!

0

Share this post


Link to post
Share on other sites
  • 0

Hey @chrisbruwer0!

Sorry to hear that's happening! I reached out to you via email to get a support ticket started. I will need to collect some info from you in order to properly troubleshoot the issue. Appreciate your willingness to send logs! Hope to hear from you on the ticket soon.

0

Share this post


Link to post
Share on other sites
  • 0

@Nick im getting same error . plse email me . here are my logs

[2017-08-29 08:11:25,602 I] <4424> Checking if any IP to traceroute has been enqueued...
[2017-08-29 08:11:25,602 I] <4428> Checking for upgrades...
[2017-08-29 08:11:25,618 I] <4312> BugSplat initialized
[2017-08-29 08:11:25,618 I] <4312> Initial logging level 7 
[2017-08-29 08:11:25,618 I] <4312> Libwebsockets version: 2.1.0 datafoundry\doug@LP-3662-v2.0.0-177-g5fb3277 
[2017-08-29 08:11:25,618 I] <4312> IPV6 not compiled in 
[2017-08-29 08:11:25,618 I] <4312> libev support not compiled in 
[2017-08-29 08:11:25,618 I] <4312> libuv support compiled in and enabled 
[2017-08-29 08:11:25,618 I] <4312>  Threads: 1 each 30000 fds 
[2017-08-29 08:11:25,618 I] <4428> Testing api server at 'api.nyc.gfpnet.com'
[2017-08-29 08:11:25,618 I] <4312>  Compiled with OpenSSL support 
[2017-08-29 08:11:25,618 I] <4312>  SSL disabled: no LWS_SERVER_OPTION_DO_SSL_GLOBAL_INIT 
[2017-08-29 08:11:25,618 I] <4312> Creating Vhost 'default' port 8640, 2 protocols, IPv6 off 
[2017-08-29 08:11:25,618 I] <4312>    mounting file:// to / 
[2017-08-29 08:11:25,618 I] <4312>  Listening on port 8640 
[2017-08-29 08:11:25,618 I] <4312>  mem: per-conn:          944 bytes + protocol rx buf 
[2017-08-29 08:11:25,634 I] <4312>  canonical_hostname = KevGamin-PC 
[2017-08-29 08:11:25,634 I] <4312>  Using foreign event loop... 
[2017-08-29 08:11:25,665 I] <4508> lws_protocol_init 
[2017-08-29 08:11:25,727 D] <4428> Received curl error response for <https://api.nyc.gfpnet.com/gaming/self> (32 ms)
[2017-08-29 08:11:25,727 I] <4428> API server at api.nyc.gfpnet.com did not successfully reply to a /self/ api call
[2017-08-29 08:11:25,727 I] <4428> Testing api server at 'api.lax.gfpnet.com'
[2017-08-29 08:11:25,743 I] <4312> Waiting for JWT ...
[2017-08-29 08:11:25,790 D] <4428> Received curl error response for <https://api.lax.gfpnet.com/gaming/self> (46 ms)
[2017-08-29 08:11:25,790 I] <4428> API server at api.lax.gfpnet.com did not successfully reply to a /self/ api call
[2017-08-29 08:11:25,790 I] <4428> Testing api server at 'api.ams.gfpnet.com'
[2017-08-29 08:11:25,837 D] <4428> Received curl error response for <https://api.ams.gfpnet.com/gaming/self> (31 ms)
[2017-08-29 08:11:25,837 I] <4428> API server at api.ams.gfpnet.com did not successfully reply to a /self/ api call
[2017-08-29 08:11:25,837 I] <4428> Testing api server at 'api.sgp.gfpnet.com'
[2017-08-29 08:11:25,852 D] <4428> Received curl error response for <https://api.sgp.gfpnet.com/gaming/self> (8 ms)
[2017-08-29 08:11:25,852 I] <4428> API server at api.sgp.gfpnet.com did not successfully reply to a /self/ api call
[2017-08-29 08:11:25,852 E] <4428> Exception updating upgrade cache: APIService_HTTP::find_working_api_server could not identify a working api server in the provided list.: iostream stream error
[2017-08-29 08:11:25,852 E] <4428> Upgrade check failed due to exception: APIService_HTTP::find_working_api_server could not identify a working api server in the provided list.: iostream stream error
[2017-08-29 08:11:25,852 I] <4428> Checking for upgrade failed with error: APIService_HTTP::find_working_api_server could not identify a working api server in the provided list.: iostream stream error
[2017-08-29 08:11:54,872 I] <4312> Still waiting for JWT ...
[2017-08-29 08:12:24,910 I] <4312> Still waiting for JWT ...
[2017-08-29 08:12:54,921 I] <4312> Still waiting for JWT ...
[2017-08-29 08:13:24,931 I] <4312> Still waiting for JWT ...
[2017-08-29 08:13:54,942 I] <4312> Still waiting for JWT ...
[2017-08-29 08:14:24,955 I] <4312> Still waiting for JWT ...
[2017-08-29 08:14:54,967 I] <4312> Still waiting for JWT ...
[2017-08-29 08:15:24,979 I] <4312> Still waiting for JWT ...

 

Edited by kmcpike00
0

Share this post


Link to post
Share on other sites
  • 0

@kmcpike00 - Thanks for the info. I went ahead and reached out to you via email on your existing ticket.

0

Share this post


Link to post
Share on other sites
  • 0

@Nick I did instructions in email for complete dump etc. I am on windows 10 and i attached the outfox.log file in the email for you to look over, thanks . talk to you soon. 

0

Share this post


Link to post
Share on other sites
  • 0

@MrTrane Thanks for reporting it! I reached out to you via email as well to collect some data.

0

Share this post


Link to post
Share on other sites
  • 0

I am going to lock this thread as troubleshooting and data collecting for this problem will need to be done via email ticket (exchange of files).

If anyone else is having this particular issue, please email support@getoutfox.com with a description of what's happening and we can further investigate. Thanks!

0

Share this post


Link to post
Share on other sites
  • 0

Just FYI to everyone affected by this -- a fix has been identified and we're hoping to get it fast-tracked as quickly as possible.  It's a kernel driver, however, and that involves working with Microsoft for Windows 10 goodness.  Stay tuned!

1

Share this post


Link to post
Share on other sites
  • 0

I'm going to have to remember from almost two years ago, but if I recall correctly this was a bug in a third-party library that we use for hooking into the network stack on the Windows operating system.  This bug was eventually fixed within the 3rd party library and the Outfox 1.1 update provided that fix.

 

0

Share this post


Link to post
Share on other sites
  • 0

Thanks for the info, as i was getting the same info on my citrix vdi, and i was not able to shook it off. So took help of their tech support team to take care of the issue.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now