BSOD Bad_Pool_Caller New Computer

[Ruben Talpes]

Not sure what category to post this under. 4/29/17 I bought and built a gaming tower from scratch with no previous experience and using a few online guides. To my surprise everything seemed to work perfectly. Then randomly once per day while browsing using Firefox or chrome I'd receive a BSOD with Bad_Pool_Caller. I quit using those and uninstalled Firefox and chrome. Since then I've been using Internet explorer with no issues at all.

Everything I thought I narrowed out was useless because after much time with no issues I got another BSOD today while playing a game, non-intensive and no internet (although I did have 1 page open in the background).

All of my drivers are up-to-date, BIOS is as well, and I don't overclock. I've made sure all my connections are intact with no metal to metal contact. I was told the "default" thermal paste that's usually pre-applied isn't of great quality so I cleaned that off correctly and applied some that I bought (pea-size dot). When building I also made sure to cleanly separate all cords to behind the motherboard so airflow would be good.

Using Windows 10 64-bit
Processor: Intel i7-7700 @ 3.60GHz
Graphics Card: GTX 1060 6G
Motherboard: Gigabyte H270
Storage : Samsung 250gb ssd & 1tb hard drive
Ram: 2 8gb dr 2400
PSU: Corsair 650W
And ESET Smart Security (had a few issues with certificates and blocked websites)

 

[Colif]

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

 

[Ruben Talpes]

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 5/28/2017 9:10:08 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052817-4453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xC2 (0xB, 0xFFFFCC0BF017D4B8, 0x0, 0xFFFFCC0BF017D798)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/28/2017 9:10:08 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: e2xw1.sys (e2xw10x64+0x8A0D)
Bugcheck code: 0xC2 (0xB, 0xFFFFCC0BF017D4B8, 0x0, 0xFFFFCC0BF017D798)
Error: BAD_POOL_CALLER
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e2xw1.sys .
Google query: e2xw1.sys BAD_POOL_CALLER



On Sun 5/28/2017 8:25:15 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052817-4531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xC2 (0x7, 0x0, 0x281E53, 0xFFFFA088CF9BB0E8)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 5/18/2017 9:33:32 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\051817-5718-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x66250)
Bugcheck code: 0xC2 (0x7, 0x1, 0x3F0000, 0xFFFFB4035FE0FE08)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 5/17/2017 6:28:29 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\051717-4640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0xC2 (0x7, 0x1, 0x0, 0xFFFFA90EDD925328)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Ruben Talpes]

Ok so weird thing is, I found your response to someone else's thread with about the same issue except I ran live update 6 and everything is up-to-date and I also already installed the latest driver from killer networking. I tried this a couple weeks ago but ill go ahead and do it again.

 

[Colif]

sometimes simply removing the killer drivers can fix things. tcpip.sys is internet, probably caused by lan drivers again

I see my old answers are helping again

 

[Ruben Talpes]

sometimes simply removing the killer drivers can fix things. tcpip.sys is internet, probably caused by lan drivers again

I see my old answers are helping again

If I uninstall the killer Ethernet driver or uninstall the app will I still be able to connect to the internet? Or do I need to download/install anything in place of it?

 

[Colif]

OK, the sometimes it works without the drivers might be cases where PC has 2 ethernet connections on back of box.

if you only have the one, you can try to get newer drivers direct from killer: http://www.killernetworking.com/driver-downloads

 

[davidangeleshuaman]

Sorry for my English ... I have an error similar to the post.

The characteristics of my pc:

Using Windows 10 64-bit
Processor: Intel i7-7700 @ 3.60GHz
Graphics Card: GTX TI 1050 4G
Motherboard: Gigabyte H270
Storage : 1tb hard drive
Ram: 8gb dr 2400
PSU: 450W

System errors:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 19/08/2017 12:03:45 a.m. your computer crashed
crash dump file: C:\Windows\Minidump\081917-12859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x0, 0xFFFFE001F913A638)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 19/08/2017 12:03:45 a.m. your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e2xw8x64.sys (e2xw8x64+0x88ED)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x0, 0xFFFFE001F913A638)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\e2xw8x64.sys
product: Killer e2400 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2400 PCI-E Gigabit Ethernet Controller
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e2xw8x64.sys (Killer e2400 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. BAD_POOL_CALLER



On Fri 18/08/2017 11:58:14 p.m. your computer crashed
crash dump file: C:\Windows\Minidump\081817-14015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x19 (0x20, 0xFFFFE0019B3A6238, 0xFFFFE0019B3A7088, 0x84E5B48E)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 18/08/2017 11:53:23 p.m. your computer crashed
crash dump file: C:\Windows\Minidump\081817-14609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x99463558, 0xFFFFE000994635E8)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 18/08/2017 04:31:31 p.m. your computer crashed
crash dump file: C:\Windows\Minidump\081817-15875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xC2 (0x7, 0x1200, 0x0, 0xFFFFE000ADE81D78)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Conclusion:

7 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

e2xw8x64.sys (Killer e2400 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.



*** My pc does not have the Killer e2400 driver. It has the Killer e2500 driver. Is it possible that there are two controllers?

 

[Colif]

@ davidangeleshuaman

1. there is more than 1 model Killer -

: Includes Killer Control Center software and drivers for Wireless-N, Killer Wireless-AC 1525/1535/1435, Killer E2200, Killer E2400, and Killer E2500.
Version: 1.3.1350

http://www.killernetworking.com/driver-downloads
but they all use the same driver

2. I would start your own thread, and follow the next bit so we can look at errors more
Can you look in c windows/minidump
copy the minidump files to documents
upload the copy from documents to a cloud server and share the link in your new thread

Someone who can read the dumps will convert the file so its a little easier to read, and help us help you fix it