BLUE-SCREEN ON ACER ASPIRE V5-552P-X404

Hello all,

I bought an Aspire V5-552P-X404 in October, 2014. It has worked well all these years until a few months ago when I started getting the notorious BLUE SCREEN OF DEATH(BSOD) with an error message "BAD POOL CALLER". This BSOD occurs whenever I plug in the ethernet/LAN cable or connect to the internet with a USB 3G/4G modem. Connecting through wi-fi works well without any issues.

I've taken actions ranging from updating drivers to doing a CLEAN INSTALL of Windows 10 (Creator's Update), but the problem still persists. As a result, I'm suspecting a hardware might be responsible for all the troubles.

Does anyone in the house have a fix for this, or any idea that might help?

Thanks in advance for your kind assistance.

Daniel S.

Accepted answers

All comments

IronFly

download this tool, whocrashed:
http://www.resplendence.com/download/whocrashedSetup.exe

before running it, browse to C:\windows\minidump
delete all files apart the first 2-3 files (newest)
then install whocrashed and run it
click on Analyze
report here the result.

Please report your BIOS version too:

windows logo key + r

type

msinfo32

report BIOS DATE/Version string

Sunnyd77

Hi, here is the test result:

System Information (local)

Computer name: DESKTOP-US56BKI
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\Windows
Hardware: Aspire V5-552P, Acer, Dazzle_RL
CPU: AuthenticAMD AMD A10-5757M APU with Radeon(tm) HD Graphics AMD586, level: 21
4 logical processors, active mask: 15
RAM: 7996719104 bytes total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 13/09/2017 2:02:07 PM your computer crashed
crash dump file: C:\Windows\Minidump\091317-30250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xC2 (0x7, 0x5C0065, 0x630069, 0xFFFF880F517FFC78)
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 Wed 13/09/2017 2:02:07 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: l1c63x64.sys (L1C63x64+0x959C)
Bugcheck code: 0xC2 (0x7, 0x5C0065, 0x630069, 0xFFFF880F517FFC78)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\l1c63x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 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: l1c63x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. BAD_POOL_CALLER

On Wed 13/09/2017 1:58:43 PM your computer crashed
crash dump file: C:\Windows\Minidump\091317-39906-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x4E39)
Bugcheck code: 0xC2 (0x7, 0x7FFD, 0x11D1E000, 0xFFFFCB847387C338)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
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 13/09/2017 1:53:09 PM your computer crashed
crash dump file: C:\Windows\Minidump\091317-31687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFFDA87A1EEC978)
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 Wed 13/09/2017 1:50:31 PM your computer crashed
crash dump file: C:\Windows\Minidump\091317-30656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xC2 (0x7, 0x960, 0x0, 0xFFFFBC08710BF978)
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

6 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:

l1c63x64.sys (Killer e2200 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.

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.

IronFly

ok

download the 64 bit driver:

http://www.killernetworking.com/driver-downloads/category/other-downloads

install it and then check if it BSOD again.

Sunnyd77

Hi, I installed the driver but BSOD still comes on.

IronFly

re-do Whocrashed scan and report, just with the last 2 minidump files.

Any antivirus installed?

Sunnyd77

System Information (local)

Computer name: DESKTOP-US56BKI
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\Windows
Hardware: Aspire V5-552P, Acer, Dazzle_RL
CPU: AuthenticAMD AMD A10-5757M APU with Radeon(tm) HD Graphics AMD586, level: 21
4 logical processors, active mask: 15
RAM: 7996719104 bytes total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 14/09/2017 10:20:27 AM your computer crashed
crash dump file: C:\Windows\Minidump\091417-31359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xC2 (0x99, 0xFFFFE68EE8209AE8, 0x0, 0x0)
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 14/09/2017 10:20:27 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: l1c63x64.sys (L1C63x64+0x96CC)
Bugcheck code: 0xC2 (0x99, 0xFFFFE68EE8209AE8, 0x0, 0x0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\l1c63x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 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: l1c63x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. BAD_POOL_CALLER

On Thu 14/09/2017 10:19:37 AM your computer crashed
crash dump file: C:\Windows\Minidump\091417-48937-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

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:

l1c63x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.)

I deleted previous dump files and allow the BSOD to come up twice. On running the test, this is the result I got. When I go to Device Manager to update Drivers, I don't find the Killer E2200 driver among the others, I only see the Qualcomm Atheros drivers.