- Aug 24, 2015
- 157
- 0
- 4,680
I didn't used to get this error before but for about a week now it keeps happening none stop. Every two hours or so my computer gets a blue screen that says bad_pool_caller and I have to restart it. I have tried almost everything I could think of but nothing seems to work. I download Memtest86 to see if it was a hardware failure but nothing was wrong. Then I downloaded WhoCrashed it and I was told it was this driver (e1d65x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation) so i downloaded Intel driver update utility but it found no driver update, so i deleted some drivers because i couldn't pin point the one causing the problem and I re downloaded them but i still get the error. I got desperate and downloaded unlocker to delete the file from system32 but it wouldn't delete. I deleted the registry yet nothing, finely i updated the bios but still nothing, the error still happens every so often.
http://pcpartpicker.com/list/tBDs4D (my pc in case this info helps solve the problem)
(Whocrashed file dump analysis)
Welcome to WhoCrashed (HOME EDITION) v 5.51
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: DESKTOP-LPOQRGM
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASRock, Z87 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8522575872 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 6/29/2016 4:08:23 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE000A67D2E98)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x4B00, 0xFFFFE000A67D2E98)
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.
Google query: BAD_POOL_CALLER
On Wed 6/29/2016 3:24:09 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062916-15265-01.dmp
This was probably caused by the following module: e1d65x64.sys (e1d65x64+0x1590A)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x6D006F, 0xFFFFE001767B8858)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\e1d65x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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.
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: e1d65x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation BAD_POOL_CALLER
On Tue 6/28/2016 9:26:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062816-15375-01.dmp
This was probably caused by the following module: e1d65x64.sys (e1d65x64+0x1590A)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x301744F8, 0xFFFFE00030174588)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\e1d65x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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.
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: e1d65x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation BAD_POOL_CALLER
Conclusion
3 crash dumps have been found and analyzed. 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:
e1d65x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation)
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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
http://pcpartpicker.com/list/tBDs4D (my pc in case this info helps solve the problem)
(Whocrashed file dump analysis)
Welcome to WhoCrashed (HOME EDITION) v 5.51
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: DESKTOP-LPOQRGM
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASRock, Z87 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8522575872 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 6/29/2016 4:08:23 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE000A67D2E98)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x4B00, 0xFFFFE000A67D2E98)
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.
Google query: BAD_POOL_CALLER
On Wed 6/29/2016 3:24:09 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062916-15265-01.dmp
This was probably caused by the following module: e1d65x64.sys (e1d65x64+0x1590A)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x6D006F, 0xFFFFE001767B8858)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\e1d65x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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.
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: e1d65x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation BAD_POOL_CALLER
On Tue 6/28/2016 9:26:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062816-15375-01.dmp
This was probably caused by the following module: e1d65x64.sys (e1d65x64+0x1590A)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x301744F8, 0xFFFFE00030174588)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\e1d65x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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.
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: e1d65x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation BAD_POOL_CALLER
Conclusion
3 crash dumps have been found and analyzed. 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:
e1d65x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation)
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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Facebook
Twitter
Instagram