Windows 10: BSOD, Bad Pool Header

Acer Aspire ES1-711-P14W with Windows 10. I had Windows 10 since Insiders builds and a few weeks ago it started BSODing frequently, mainly DPC_WATCHDOG_VIOLATION and BAD_POOL_HEADER, I thought a reinstall would fix the issue but it didn't, I still had 2 BSODs with the BAD_POOL_HEADER message, one was before I installed the Anniversary Update and one after, both while using Chrome. Running Windows 10 Version 1607 Build 14393.10

Attachment 94327

:)

 

Win10 BSOD, Help.

One other thing when I did see the BSOD at random, it said BAD POOL HEADER.

 

Guys I really need your help. I'm getting BSOD (Bad Pool Header) so many times.

Click HERE for a really good thread on Bad Pool Header BSOD.

The thread is based around Windows 8, but the solution from Nannya Podder holds true for WIndows 10

I hope this Helps resolve your BSOD issue!

 

Hi AvidSurvivalist,

Sorry for the delay, thought I had already replied here

Please disable hardware acceleration in chrome if it is enabled

• In the right upper corner, click on
  
  and choose settings.
• Scroll below and click on 'advanced settings', scroll all the way to the end of the settings.
• In the part 'system' is the option to enable/disable hardware acceleration.
• If this option is enabled disable it

Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

I think I found the problem, I used a program called NetWorx to monitor my data useage because of HughesNet, I uninstalled NetWorx and my problems have stopped for now.

 

Aaand spoke too soon! Just had BSOD! "WHEA_UNCORRECTABLE_ERROR"

 

BSOD Posting Instructions

 

Crash List

Created by using BlueScreenView

Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time 081316-29187-01.dmp 8/13/2016 2:55:36 PM 0x00000124 00000000`00000000 ffffaa09`895e6028 00000000`b6000000 00000000`0004010a hal.dll hal.dll+3620f Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.14393.0 (rs1_release.160715-1616) x64 ntoskrnl.exe+149f90 C:\WINDOWS\Minidump\081316-29187-01.dmp 4 15 14393 303,260 8/13/2016 2:57:19 PM

 

BSOD Posting Instructions

Bluescreen Viewer, WhoCrashed and similar programs are useless with this crash, they don't provide anything useful.

 

Okay, lemme go back downstairs and get some info for you!

 

Let's attempt driver verifier again






Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.