Forum Discussion
After upgrade to build 17035 BAD POOL CALLER
Now I'm stuck, can't roll back to 17025 because I deleted it, tried everything under the sun. I found out that disabling the network driver extend the duration before the crash by 10-15 min. So i downloaded the iso for 17040 hoping to do an offline upgrade but it ALWAYS results in the BAD POOL CALLER right after i click "Accept" on the terms and agreements. Don't know what to do. Would greatly help if the Windows Team tell us the root of the issue was in 17035 so that we can troubleshoot around it.
- 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...- 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.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
