Forum Discussion
After upgrade to build 17035 BAD POOL CALLER
problem after updating to new build 17035 BADֲ POOL CALLER and green screen count 100% and reboot hp 430 g2 i5 with 8gb ram windows 10 ENT, OPERATING SYSTEM IS LOOK FINE AND RUNNING FOR 10 MINUTS AN...
It has apparently been fixed in 17040:
https://www.google.co.uk/amp/s/blogs.windows.com/windowsexperience/2017/11/16/announcing-windows-10-insider-preview-build-17040-pc/amp/
"We fixed an issue resulting in some Insiders experiencing a green screen on the previous flight with the error BAD_POOL_CALLER."
So now just need to get it to hold together long enough to get 17040 on...
https://www.google.co.uk/amp/s/blogs.windows.com/windowsexperience/2017/11/16/announcing-windows-10-insider-preview-build-17040-pc/amp/
"We fixed an issue resulting in some Insiders experiencing a green screen on the previous flight with the error BAD_POOL_CALLER."
So now just need to get it to hold together long enough to get 17040 on...
I actually had this problem while attempting to upgrade to 17040. It would get to 80% installed or around that, and then it would GSOD with BAD_POOL_CALLER. I never had a problem with 17035 until then.
Right now I have updates paused until the next version. Hopefully that will work better.
Right now I have updates paused until the next version. Hopefully that will work better.
Thanks for the info on 17040. I have the same problem with 17035. I installed it twice, once after reverting to 17025 with no issues. I still have the Bad Pool Call on the second install and am in the Recovery option go back to previous version (again) right now. Once its stable back on 17025 I will try to install 17040 and cross my fingers.
Dennis
HP Touchsmart 610f 8 GB, 1TB
- Oh FFS. So I thought I had set the upgrade settings on my other pc to stop it from upgrading... but no, it decided to upgrade to 17035. And promptly got the bad pool caller error within a minute of login.
How many people had this happened to? Am I just desperately unlucky to get it on 2 machines or is it very common? Do MS have any clue how ******* incompetent this is?
More practically... So how am I supposed to fix either machine when any attempt to do anything crashes it?- Just happened to me after upgrading last night. I went the route of going settings>recovery>roll back to prev version but it crashed during the rollback and so I am no longer able to rollback.
Feels good.
