[SOLVED] [Win10ProV1703Build15063 x64] Bad Pool Caller

[Masterchiefxx17]

Starting yesterday, I have been getting multiple Bad Pool Caller BSODs on my Windows 10 PC. This happens when I am browsing MS Edge. Attempting to upload the Perfmon file told me that the forum does not support the file size.

· OS - Windows 10
· x64
· What was original installed OS on system? Windows 8.1
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full Retail
· Age of OS installation - have you re-installed the OS? No.

· CPU: i5-4690k
· Video Card: GTX 960
· MotherBoard - G1.Sniper Z97
· Power Supply - XFX 650W

 

[writhziden]

Re: BSOD - Bad Pool Caller

Have you tried removing ESET and seeing if the problem persists? I'm not saying ESET is to blame (it's rare for ESET to cause blue screens), but since crashes are network related, it might be worth troubleshooting. Maybe something became corrupted with the ESET software.

The crashes are also showing your Ethernet driver in the stack.

Product Type	Killer E2200 Gigabit Ethernet Controller

Check for any updates for the Ethernet device or try reinstalling the current driver.

 

[Masterchiefxx17]

Re: BSOD - Bad Pool Caller

Sorry about that, I could have sworn I put this in the original post. :huh:

I recently updated the Ethernet driver on this system (Figured it may be a problem) and thought it may be the problem here. I'll reinstall it and report back.

 

[xilolee]

Re: BSOD - Bad Pool Caller

Hi everybody. :wave:

Cpu says: DDR3-1333/1600, DDR3L-1333/1600 @ 1.5V
MB says: Support for DDR3 3000(O.C.) / 2933(O.C.) / 2800(O.C.) / 2666(O.C.) / 2600(O.C.) / 2500(O.C.) / 2400(O.C.) / 2200(O.C.) / 2133(O.C.) / 2000(O.C.) / 1866(O.C.) / 1800(O.C.) / 1600 / 1333 MHz memory modules

Raminfo.html says: speed 1866
Therefore it seems there's a xmp profile enabled: you could try to set the speed to 1600.
The environment variable (system) path shows some doublets; I'm not sure it could help, but you can remove them (the doublets):

c:\windows
c:\windows\system32
c:\windows\system32\wbem
c:\windows\system32\windowspowershell\v1.0\;

Suspect drivers present:
- GPCIDrv64.sys (gigabyte easy boost - OC guru)
- etdrv.sys (gigabyte tools)
- etocdrv.sys (gigabyte easytune)
- gdrv.sys (Gigabyte Easy Saver - gigabyte easy tune - gigabyte tools)

Indeed gigabyte EasyTune is downloadable from the motherboard webpage, but gigabyte OC GURU seems installed instead of it: are they the same software?

DriverqSi shows: ASUS Xonar DG Audio Device oem72.inf NOT SIGNED
DriverqFo (and also windbg) shows very strange dates for the drivers, from 1970 to 2105. How's this possible?

 

[Masterchiefxx17]

Re: BSOD - Bad Pool Caller

Yes, I do have an XMP profile set on this PC.

Turns out that after reinstalling the Killer Network driver, I have yet to have another BSOD. I'd assume this has been solved by that.

However, since you responded with the last post, I will dive a little deeper if something doesn't look right. :smile9:

The environment variable (system) path shows some doublets; I'm not sure it could help, but you can remove them (the doublets):

I'm not sure what you mean by this. Could you explain a little more on it?

Suspect drivers present:
- GPCIDrv64.sys (gigabyte easy boost - OC guru)
- etdrv.sys (gigabyte tools)
- etocdrv.sys (gigabyte easytune)
- gdrv.sys (Gigabyte Easy Saver - gigabyte easy tune - gigabyte tools)

Indeed gigabyte EasyTune is downloadable from the motherboard webpage, but gigabyte OC GURU seems installed instead of it: are they the same software?

I should get rid of EasyTune as it's something I do not use. As for OC Guru, this is the monitoring tools I use for the GPU. Overclocking profiles can be applied as well as GPU temperatures/fan curves. They are not the same software.

DriverqSi shows: ASUS Xonar DG Audio Device oem72.inf NOT SIGNED

I blame Asus for only giving me a beta driver for Windows 10! :eek4:

DriverqFo (and also windbg) shows very strange dates for the drivers, from 1970 to 2105. How's this possible?

I have no clue, your guess is as good as mine. Is there something we could look into for this?

 

[writhziden]

Re: BSOD - Bad Pool Caller

DriverqFo (and also windbg) shows very strange dates for the drivers, from 1970 to 2105. How's this possible?

I have no clue, your guess is as good as mine. Is there something we could look into for this?

The driver dates look normal through msinfo32 and through the sys list collected with the file collection app. I'm guessing it's an issue with Windows versions. Some of the Creators Update symbols may not be loading properly, or the Creators Update is handling something odd with the timestamp data for some drivers. I've seen similar in nearly every Creators Update .dmp I've come across.

 

[xilolee]

Re: BSOD - Bad Pool Caller

The environment variable (system) path shows some doublets; I'm not sure it could help, but you can remove them (the doublets):

I'm not sure what you mean by this. Could you explain a little more on it?

Control Panel\System and Security\System - advanced system settings, (click yes in the UAC window that should appear if you didn't disable it), click environment variables, double-click path under the system variables pane (or click it once and then click edit), remove the doublets, click ok, click ok.

I also observed in the past that some environment variables inside other environment variables could cause strange behaviours, therefore I'd also substitute the text of those variables.
Example: %systemroot%\system32 would become c:\windows\system32.

 

[Masterchiefxx17]

Re: BSOD - Bad Pool Caller

DriverqFo (and also windbg) shows very strange dates for the drivers, from 1970 to 2105. How's this possible?

I have no clue, your guess is as good as mine. Is there something we could look into for this?

The driver dates look normal through msinfo32 and through the sys list collected with the file collection app. I'm guessing it's an issue with Windows versions. Some of the Creators Update symbols may not be loading properly, or the Creators Update is handling something odd with the timestamp data for some drivers. I've seen similar in nearly every Creators Update .dmp I've come across.

Seems to make sense. If you are seeing this across multiple computers here, I'll happy disregard it and carry on.

The environment variable (system) path shows some doublets; I'm not sure it could help, but you can remove them (the doublets):

I'm not sure what you mean by this. Could you explain a little more on it?

Control Panel\System and Security\System - advanced system settings, (click yes in the UAC window that should appear if you didn't disable it), click environment variables, double-click path under the system variables pane (or click it once and then click edit), remove the doublets, click ok, click ok.

I also observed in the past that some environment variables inside other environment variables could cause strange behaviours, therefore I'd also substitute the text of those variables.
Example: %systemroot%\system32 would become c:\windows\system32.

I removed the doublets under the Path setting. Thanks for that. I'll monitor the system and see if anything ends up changing.

As for the BSOD, it's been gone now since the driver reinstall. I'll mark this thread as solved and thank you for all of the help.