Windows 10: BSOD and BAD_POOL_CALLER after connecting to Global Protect VPN

Hi...i am using a Lenovo ideapad slim 3 laptop running Windows 11 home, Version 23H2OS Build: 22631.3593I need to use the VPN called Global Protect from Palo Alto Networks this VPN allows me to access the page for the website for what I work at.However, when I connect the VPN, my laptop will go to a "blue screen" after 10 seconds, every time i try to connect the vpn its goes bluescreenAlso, if I don't start the VPN I can work all day for 8 hours without seeing the "blue screen".I have attached a photo of the blue screen. As you can see, the stopcode is BAD_POOL_CALLER.A

:)

 

BSOD and BAD_POOL_CALLER after starting Global Protect VPN

Hi....

I am using a Dell XPS 13 laptop running Windows 10 Home, Version 21H1.

OS Build: 19043.1052

I need to use the VPN called Global Protect from Palo Alto Networks (this VPN allows me to access patient data at the hospital I work at).

However, when I start VPN, my laptop will go to a "blue screen" . This will sometimes happen 2 or 3 minutes after I start the VPN, and sometimes it does not happen until 30 or 40 minutes after I start the VPN.

Also, if I don't start the VPN I can work all day (for 8 hours) without seeing the "blue screen".

I have attached a photo of the blue screen. As you can see, the stopcode is BAD_POOL_CALLER.

Any advice would be greatly appreciated!

 

BSOD and BAD_POOL_CALLER after starting Global Protect VPN

I'm having the same issue on my new Asus Zephyrus G15 laptop. I updated drivers, ran system file checker, memory verifier, and disk error check with the issues still persisting. My BSOD occurs immediately after connecting to GlobalProtect VPN or sometimes shortly (15-30 mins) after connecting. Similar to others I need this VPN to connect remotely to my work PC. The BSOD error codes I get are "Bad Pool Caller" before i updated drivers, and now most recently "Special Pool Detected Memory Corruption". After analyzing dump files I think it's McAfee task "MMSSHOST.EXE" interfering in some way... but I updated McAfee, again with no luck.

Have others had success rolling back Global Protect version? I might try that next.

Minidump files:

Microsoft OneDrive

Thanks,

 

BSOD - BAD_POOL_CALLER - GlobalProtect VPN

I have a Lenovo ThinkPad P53 (Windows 10 x64 - Version 2004 OS Build: 19041.1165) that is generating a BSOD with the BAD_POOL_CALLER error every time I try to start the GlobalProtect VPN. This is a a corporate laptop and they want to replace it with another P53. I have run all software and hardware diagnostics and everything passes. The computer does NOT generate the BSOD unless I try to start the GlobalProtect VPN. This issue is also being reported by other in the company. This is happening on both a wired and wireless connection.