How to Diagnose a Blue Screen of Death (BSOD) with Bad Pool Caller in Windows 11?
Asked by
CuriousGiraffe99
I've been experiencing Blue Screen of Death (BSOD) errors on my Windows 11 system with the 'Bad Pool Caller' message. I've read that this could be related to issues with drivers, applications, or RAM, but figuring out the exact cause without analyzing the dump files is proving to be a challenge. If anyone could assist by checking my dump files, that would be amazing! Here are the links to my dump files: [Dump File 1](https://files.catbox.moe/q269e8.dmp), [Dump File 2](https://files.catbox.moe/k44obq.dmp), [Dump File 3](https://files.catbox.moe/8tlcle.dmp).
Answers
I ran a memory test to check my RAM, and everything came back good. I also uninstalled NordVPN since it seemed to be causing the issue for me. So far, my system seems stable now, but I’d still like to confirm if NordVPN was really the problem or just a coincidence. Anyone else having similar experiences?
Reply to this answer
A lot of these crashes seem to link back to Wireguard. I’ve seen it trigger BSODs too, even though it doesn’t have a big user base. If you’re using it, try reinstalling Wireguard. If that doesn’t help, you might want to keep it uninstalled and reach out to their support for further assistance.
Reply to this answer
To get a proper diagnosis of your BSOD, you’ll need to locate the dump files. If you can access Windows normally or boot into Safe Mode, check the C:WindowsMinidump folder for any dump files. It’s best to copy these to your desktop, zip them up, and then upload them to a file-sharing site. Make sure to check for more than one dump file if possible, as it helps with analysis. A couple of options for sharing are catbox.moe or mediafire.com since Reddit tends to blacklist certain hosts.
Reply to this answer
Add your answer
Answers are reviewed before publication.
VPNWarrior88: Yes! I noticed that my BSOD would stop showing up when I closed NordVPN. It's really frustrating! Does anyone know what's causing this?
TechieToby77: I’ve had the same issue on my desktop. It’s happening across devices!