Bad Pool Caller on Windows 10, only gets BSOD when playing Overwatch

jorma

Reputable
Aug 16, 2015
13
0
4,510
Whenever I boot up Overwatch, it takes between a few seconds in the menu screen to sometimes a few minutes when I'm in-game when it gives me the BSOD. The code it keeps giving me is Bad_Pool_Caller.

This only started happening today, but I noticed over the past few weeks that whenever I played any "intensive" game (it's really only been DS3 and mostly Overwatch), I would get these "mini-freezes" either every few seconds or just occasionally in game.

I looked online and saw that the code means that it might be a problem with my drivers or RAM, so I ran Windows Memory Diagnostics and it found no errors. I tried to manually check for updates for each of my devices (GPU, SSD, printer, keyboard, etc) but I didn't check every single one.

I'm not really sure what to do now. Should I keep checking my drivers? Any help at all would be appreciated

EDIT: I forgot to mention that my computer is pretty good, I have an i7 and GTX 1070 so I don't think it's the result of insufficient hardware. If you need a full list of my components I'm happy to give it.
 
Solution
how to do what John suggested

1. Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create Kernel Memory Dumps

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and john will read it


2. how to run driver verifer: driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again...
pool is just memory that is shared between device drivers. often this bugcheck happens when a driver frees up the same memory block twice. The first time is ok because it owns the memory block, the second free results in a bugcheck because the driver no longer owns the memory block. Problem is these frees are done during cleanup and the system does the clean up maybe several minutes after the calls are made.
To find the bad driver you have to change the memory dump to kernel and you often have to run verifier.exe to set debugging flags to force the system to bugcheck when the call is made.

when you do this, the memory dump will contain the name of the driver making the bad call and the memory dump file can be read with the windows debugger or a memory dmp reading tool like
whocrashed.exe or bluescreenview.exe. The fix will be the same, update the BIOS and motherboard drivers
but at least you will know the name of the driver that should be updated.
 
I'll be honest, I'm not that tech-savvy, so I don't know what most of the terminology you used means. This is the first PC I've built, so I'm still new at this. Is there a software I can use to see what driver was corrupted, or do I have to do it that way?

Is the fix to just update my BIOS and mb?
 
how to do what John suggested

1. Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create Kernel Memory Dumps

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and john will read it


2. how to run driver verifer: driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again. Also helps to run system restore before hand to create a backup to roll back to if necessary. Download the Windows 10 media creation tool and use it to make a win 10 installer on USB
Once it bsod, run Who crashed and see what driver it reveals

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC
 
Solution

TRENDING THREADS