BAD POOL CALLER bsod

[JoannaAmato]

I tried to open League of Legends yesterday and instead it gave me this bsod called bad pool caller. I tried to update my display adapter drivers but it didn't do anything, I also tried reinstalling the game but it gave me the same problem again. Today I tried a system recovery twice to 2 different times but they both were unsuccessful. The screen only pops up when I open that specific game.

My specs are:
Intel i5 6600k 3.50Ghz
Intel HD Graphics 530
MSI B150 PC Mate
Western Digital Purple 1TB
8gb ram 2400Mhz ddr4
Psu be quiet pure power 10 - CM500W

 

[johnbl]

bad pool caller mean you have a device driver that made a system call using a block of memory it does not own. Most of the time it is just a bug in the device driver where it tries to use a memory that it has already released to the system.

Microsoft windows update updates the generic drivers but you have to go to the motherboard website to get any BIOS and motherboard driver updates.

if after applying the BIOS and motherboard driver updates. if you get another bugcheck, you should change your memory dump from a mini memory dump to a kernel memory dump. Then you will want to start cmd.exe or powershell and run
verifier.exe /standard /all
and reboot your system and wait for the next bugcheck. verifier should make the system bugcheck and name the driver that caused the problem. You would then run whocrashed.exe or bluescreenview.exe and read the driver name that needs to be updated. Or, you could put the memory dump file c:\windows\memory.dmp on a cloud server like Microsoft onedrive, share the files as public and post a link.

you may also find the whocrashed.exe or bluescreenview can read the minidump and name the driver but most of the time it will just name the interface to the device driver as the problem (ntoskrnl.exe) if verifier is on there is a good chance it will name the true bad driver.

Note: be sure you know how to get into safe mode in case your machine bugchecks during boot. This is so you can turn off verifier via the
verifier.exe /reset
command (be sure to do this after you finish testing or your machine will run slowly until you do)