Windows 10: Laptop using VPN : BSOD - Bad_Pool_Caller

We have recently deployed Dell laptops out to our staff and when working remotely we are using an Azure VPN connection back to the office. We are seeing a small number of users who are getting a BSOD when working at home - these all seem to be using Ethernet via the provided Dell dock which uses a Realtek driver.Windows 11 on latest updates, latest drivers/firmware for both laptops and docks.Looking at the memory dump I can't verify that its a driver issue or where to look at the cause, how can I determine the cause of the BSOD?memory dump header shows:BAD_POOL_CALLER c2The current thread

:)

 

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.

 

Vpn ( trusted Vpn)

Hi everyone.
I am not an expert about Vpn and that's why I would like to know if someone could list me a few trusted Vpns, I would really appreciate any suggestion/ advice.

Thanks.

 

Bad_Pool_Caller


I have read quite a few "Bad_Pool_Caller" posts and none that I've read have been any help. It really is getting frustrating; as many as three times in a day. I've tried safe mode, but couldn't figure anything from that. In fact as I write here I'm expecting a crash. Jeez this really is a backward step. I don't remember windows 3 crashing like this with no explanation as to what is causing the crash. I have a Dell Studio 1747 laptop (six years old now). I installed a 240GB SSD drive a week or so ago. I can't remember if I had these BSOD's with the old drive. I've attached the suggested system file from previous posts. I notice ads to repair this problem, but hesitate to try them; any suggestions on that.

Thanks, Allan