Windows 10: BAD_POOL_CALLER in Chrome, DRIVER_VERIFIER_DETECTED_VIOLATION

Hello forum dwellers!

I have put together a new PC and am getting BSODs with the BAD_POOL_CALLER stop code, almost always triggered when using Google Chrome (and, for some reason, very often triggered when opening the Cyanide & Happiness webcomic, but happened on other sites as well).

I tried turning on the driver verifier, this resulted in me getting a DRIVER_VERIFIER_DETECTED_VIOLATION stop code (along with this: GDRV.SYS) always a few seconds after logging into Windows, leaving me in an endless BSOD loop.

Any clues as to what I can do to remedy the situation? Any help would be much appreciated.

:)

 

Win 10 random freezes/crashes with and without BSODs.

Hello.

Recently I've been getting random freezes/crashes of my newly built PC.

Sometimes it will just freeze, the picture and the sound will "crash" having the same sound, like a freeze, you know what I mean - causing me having to reboot.

And sometimes it will BSOD randomly, sometimes one after another.

I've used BlueScreenView for the BSODs and I had a couple of tries on fixing this. The first BSODs from today (one after another) were:

BAD_POOL_CALLER afd.sys 061917-6437-01.dmp

BAD_POOL_CALLER fwpkclnt.sys 061917-6062-01.dmp - fwpkclnt.sys

They've led me to verifier, which I've used. The program led me to:

DRIVER_VERIFIER_DETECTED_VIOLATION dtliteusbbus.sys 061917-4328-02.dmp

Which suggested Daemon Tools - which has been removed afterwards. The next reboot pointed to:

DRIVER_VERIFIER_DETECTED_VIOLATION I2cHkBurn.sys 061917-4250-01.dmp

This on the other hand pointed somewhere in the google search to MSI Gaming App - I've removed this as well, and did another reboot.

Then I've got yet another BSOD, this time with:

DRIVER_VERIFIER_DETECTED_VIOLATION vhidmini.sys 061917-4343-01.dmp

Which apparently most likely leads to an IVT Corporation BlueSolei Bluetooth HID Mini driver

However I was not able to remove anything here, because it's not visible anywhere under the installed programs, and the file it self is not removable for some reason.

I will greatly appreciate any help given to resolve the problem!

Best regards,

Adam

 

Windows 10 Critical Process Died

I use only 1 ram per time to run the verifier, and after restart it will bsod with DRIVER_VERIFIER_DETECTED_VIOLATION.

but,

first time bsod with DRIVER_VERIFIER_DETECTED_VIOLATION

ram 1 in slot 4, no minidump

second time bsod with DRIVER_VERIFIER_DETECTED_VIOLATION

ram 2 in slot 3, got minidump

third time bsod with DRIVER_VERIFIER_DETECTED_VIOLATION

ram 2 in slot 4, no minidump

forth time bsod with DRIVER_VERIFIER_DETECTED_VIOLATION

ram 1 in slot 3, got minidump

 

It looks like your Killer Network Driver, e2xw10x64.sys, is the cause of the bugchecks.

Code: 00 fffff803`f7510638 fffff803`f5496f87 nt!KeBugCheckEx 01 fffff803`f7510640 fffff806`bc097d98 nt!ExFreePoolWithTag+0xf67 02 fffff803`f7510740 fffff806`bc8127f9 NETIO!NetioFreeMdl+0x136e8 03 fffff803`f7510790 fffff806`bc0617d5 fwpkclnt!FwppInjectComplete+0x59 04 fffff803`f75107d0 fffff806`bc0616b9 NETIO!NetioDereferenceNetBufferList+0xa5 05 fffff803`f7510810 fffff806`bd3696d9 NETIO!NetioDereferenceNetBufferListChain+0x289 06 fffff803`f7510890 fffff806`bc6c1d36 tcpip!FlSendNetBufferListChainComplete+0x59 07 fffff803`f75108c0 fffff806`bc6c1b03 ndis!ndisMSendCompleteNetBufferListsInternal+0x136 08 fffff803`f7510990 fffff806`bf16892d ndis!NdisMSendNetBufferListsComplete+0x213 09 fffff803`f7510a80 ffffd283`c13461a0 e2xw10x64+0x892d[/quote] Go ahead and disable driver verifier for now. If you are still stuck in the bootloop, follow this guide.

You are running a driver from March of this year, there have been a number of updates and fixes to the driver since then. Try updating to the latest release of the killer network drivers.

 

1) Gdrv.sys is a Gigabyte driver and was not seen in the 1 BSOD mini dump.

2) Please post into the thread a memory dump:
memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMPUse file explorer > this PC > local C: drive > right upper corner search enter either of the above to find results.
Post the file into the thread using a one drive or drop box share link.


3) In addition to the above steps please update this misbehaving driver:
RfeCo10X64.sys
RN Traffic Control Rivet Networks or Killer Networks

Updating a driver: Microsoft Community

4) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials


Code: Event[252]: Log Name: System Source: Service Control Manager Date: 2017-06-24T15:58:17.519 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-4LFA4AO Description: A service was installed in the system.Service Name: RfeCoSvcService File Name: \SystemRoot\system32\DRIVERS\RfeCo10X64.sysService Type: kernel mode driverService Start Type: auto startService Account:[/quote] Code: Event[132]: Log Name: System Source: Service Control Manager Date: 2017-06-24T15:57:09.118 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-4LFA4AO Description: A service was installed in the system.Service Name: NDIS Miniport Driver for Killer PCI-E Gigabit Ethernet ControllerService File Name: \SystemRoot\System32\drivers\e2xw10x64.sysService Type: kernel mode driverService Start Type: demand startService Account:[/quote] Code: RfeCoSvc RfeCoSvc RfeCoSvc Kernel Auto Running OK TRUE FALSE 0 57ÿ344 0 09.09.2016 22:37:34 C:\WINDOWS\system32\DRIVERS\RfeCo10X64.sys 4ÿ096[/quote] Code: KillerEth NDIS Miniport Driver f NDIS Miniport Driver f Kernel Manual Running OK TRUE FALSE 0 122ÿ880 0 14.09.2016 22:52:26 C:\WINDOWS\system32\drivers\e2xw10x64.sys 4ÿ096[/quote] Code: Name [00000001] Killer E2500 Gigabit Ethernet ControllerAdapter Type Ethernet 802.3Product Type Killer E2500 Gigabit Ethernet ControllerInstalled YesPNP Device ID PCI\VEN_1969&DEV_E0B1&SUBSYS_E0001458&REV_10\4&3657540C&0&00E2Last Reset 13.09.2017 19:08Index 1Service Name KillerEthIP Address 192.168.0.103, fe80::28:7377:852c:3ef9IP Subnet 255.255.255.0, 64Default IP Gateway 192.168.0.1DHCP Enabled YesDHCP Server 192.168.0.1DHCP Lease Expires 14.09.2017 19:03DHCP Lease Obtained 14.09.2017 17:03MAC Address ‪1C:1B:0D:91:89:01‬Memory Address 0xEF200000-0xEF2FFFFFI/O Port 0x0000D000-0x0000DFFFIRQ Channel IRQ 18Driver c:\windows\system32\drivers\e2xw10x64.sys (9.0.0.42, 142,50 KB (145 920 bytes), 18.03.2017 21:56)[/quote] Code: Event[963]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-06-26T15:36:05.538 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-4LFA4AO Description: Windows failed fast startup with error status 0xC00000D4.[/quote]

 

Thanks for replying.@Spectrum: you said I was using a driver from march, but when I look into device manager and look at the network adapter driver, it says it's from 31.8.2017 and offers no updates. I did download the new Killer Control Center from your link, but the network adapter driver itself remained the same, 31.8.2017 (version 9.0.0.46).
So I used the device manager to uninstall the device. Then I also removed the whole Killer control center, and restarted the system.
After the restart, my ethernet was working again (even though I did not install any drivers) and upon inspection in the device manager, I found that there was a Killer network adapter driver installed, although it was a version from 2016. So I ran the Killer Control Center installer again and this successfully updated my driver to the 9.0.0.46 version (same as I had at the start). So I'm not sure this actually solved anything, but fingers crossed @zbook: here is the memory dump: Dropbox - MEMORY.DMP for the Killer network driver, see above.
I have also turned off fast startup, as per your instructions.

I will keep using the computer and see if the BSODs disappear, but is there anything else I might provide you that would help?

 

The memory dump debugging displayed: RfeCo10X64.sys
This misbehaving driver was fixed in post #3.

At this juncture you can:
1) close the thread having fixed the misbehaving drivers.
2) keep the thread open to monitor for the rest of the week.
3) reopen the thread in the future if there are any more bsod.
4) turn on windows driver verifier to see if there are any other misbehaving drivers.

 

Well, I turned the driver verifier on again, and no BSOD so far, after about an hour in. Before, it would only take a few seconds after login, so I'm going to assume the problem has been fixed.

I shall mark this problem as solved and reopen it later, should any BSODs arise again. Big thanks to you both, @zbook and @Spectrum

 

Your welcome.
We generally run windows driver verifier for 36 hours to conclude there are no more bsod.
If there are any other bsod lets us know and we will troubleshoot them.

 

I'm glad to hear everything is running well, good luck in the future.