Bad_Pool_Caller New Computer Error

Toggle sidebar Toggle sidebar
D

davidangeleshuaman

Prominent
Aug 19, 2017
2
0
510
Sorry for my English ... I have an error similar to the post.

http://www.tomshardware.com/forum/id-3426687/bsod-bad-pool-caller-computer.html#

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?
 
Solution
J
more likely that the driver e2xw8x64.sys uses a naming convention
e2X (where x is a wild card standing for e2200 e2300 or e2400
w8x is most likely built for windows 8 or 8.1
and 64 is for 64 bit windows.

I would just check the file date and update the driver. These gaming drivers move packets around so you can win at games. They also have a lot of bugs. (they expedite incoming position packets and delay outgoing packets so your opponent in a game ends up shooting behind you, IE you can shoot them they can not hit you if you keep moving)

Sort by date Sort by votes
You don't mention which H270 gigabyte mobo you have, but whichever it is, find out, and then go to its gigabyte support page, and download latest ethernet drivers that they post there. Uninstall the ones you currently have from device manager, and then install these new ones, and see if it helps.
 
Upvote 0 Downvote
more likely that the driver e2xw8x64.sys uses a naming convention
e2X (where x is a wild card standing for e2200 e2300 or e2400
w8x is most likely built for windows 8 or 8.1
and 64 is for 64 bit windows.

I would just check the file date and update the driver. These gaming drivers move packets around so you can win at games. They also have a lot of bugs. (they expedite incoming position packets and delay outgoing packets so your opponent in a game ends up shooting behind you, IE you can shoot them they can not hit you if you keep moving)



 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom