bad_pool_header

  • 2
  • Problem
  • Updated 5 years ago
  • Acknowledged
I recently started receiving a bad_pool_header blue screen of death message (I'm using Windows 7, current on service packs) under very specific circumstances after making a recent upgrade to Covenant Eyes to address another issue. Here is my combination:

1) Chrome browser (current)...
2) Avast AV (free version, current)...
3) ...and here's the kicker: visiting the Amazon website

I can browse all day long if I don't go to Amazon, but within two or three clicks/pages on the Amazon site, I get the BAD_POOL_HEADER error and all is lost. I am above my pay grade at this point, but I'm guessing there's some sort of memory conflict kicking up between the browser, CE, and whatever tracking/analytics Amazon might be up to.

Would love to see if this could be replicated and then addressed, if CE is the culprit.
Photo of Bret Hern

Bret Hern

  • 4 Posts
  • 0 Reply Likes
  • concerned

Posted 6 years ago

  • 2
Photo of Bret Hern

Bret Hern

  • 4 Posts
  • 0 Reply Likes
Just a quick add-on; generated an uninstall code to confirm that the scenario is correct, and indeed it is. Without CE engaged, I can visit Amazon and have no issues. Really wish this would get some attention from CE to evaluate and potentially fix.
Photo of John

John, Official Rep

  • 439 Posts
  • 79 Reply Likes
Hey Brett,

Sorry to hear about you having these issues. Let's see what we can do to help.

After doing some reading up here:

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-appear-with-bad-pool-h...

It seems like a bad pool header error is associated with memory problems. (memory corruption). Apparently running that specific combo has your computer trying to access a piece of memory that is corrupted/damaged. I would look at some of the options in this thread and see if they can help.

From our end there are a few pieces of information that we will need to get you going in the right direction. 

What I would like to see is if you could go download our newest version of Covenant Eyes onto your machine, (506.41) from the downloads page

https://covenanteyes.com/myaccount/downloads

Once installed I would be interested to know if the error persists. 

Also, it helps us to know what services you are using with Covenant Eyes. Looking you up I found a couple usernames that match your name, which one in particular are you using when you experience the error?

Thanks

- John
Photo of Bret Hern

Bret Hern

  • 4 Posts
  • 0 Reply Likes
John,

Thanks for your response, and sorry for the slow reply on my side -- we were traveling the last week.

Yes, I have gone through all of the relevant memory corruption diagnostics, and so far, every test has come up clean -- CHKDSK found no issues, the memory diagnostic didn't report any problems, drivers were verified, SFC was clean, etc. Through it all, I have not seen a recurrence of the bad_pool_header blue screen.

I'm about to download the latest version as you recommend above, and I'll see what comes of that. This is for username wbhern.

Blessings,

Bret
Photo of Bret Hern

Bret Hern

  • 4 Posts
  • 0 Reply Likes
I downloaded the latest beta, installed, and within 30 seconds of hitting Amazon's home page, received the BAD_POOL_HEADER blue screen of death. I'm uninstalling it once more.
Photo of John

John, Official Rep

  • 439 Posts
  • 79 Reply Likes
Hey Brett,

Sorry to hear that changing versions had no effect on what was happening. It certainly is a strange bug for you to be experiencing. There are tens of thousands of people on similar Covenant Eyes versions and as far as I can tell there has ever only been 1 other case of a bad pool headed issue cropping up. 

In that guys case he was on Windows 8 and we simply upgraded him to 8.1 to get a clean install of Windows and the issue went away. 

I have tried (unsuccessfully) to replicate what is going on with your machine and have exhausted test computers to try it on. 

A couple more thoughts:

1: Does this issue only persist in Chrome?

2: Have you run something like ADWCleaner or Malaware bytes recently?

3: The issue seems like it is device specific, so perhaps uninstalling and re installing Chrome (making sure to delete all personal data) could help resolve the issue.

Hopefully we can get this figured out for you. Thanks for your patience

- John

Photo of John

John, Official Rep

  • 439 Posts
  • 79 Reply Likes
Update: More research on Google provides the suggestion of updating your drivers, as an out of date driver can be known to cause this kind of crash. 
Photo of Dr P

Dr P

  • 2 Posts
  • 0 Reply Likes
Hi,

I've had exactly the same issue Brett.

Win 7, Avast. I repeatedly get blue screen with bad pool header message. I can't be sure that it is the Amazon webpage, but i am a regular user of the site.

MY IT guy reckons that the CE program is not releasing the RAM. I uninstalled and the problem was resolved. When i reinstalled latest software the problem persists. I repeated  the uninstall etc etc.

I suspect the issue is more wide spread than CE are letting on! Waiting for help from CE. In the mean time I have had to keep it uninstalled.

Please rectify ASAP!


Photo of Dr P

Dr P

  • 2 Posts
  • 0 Reply Likes
Why on earth is this problem marked as solved?
Photo of Patrick Smith

Patrick Smith, Alum

  • 147 Posts
  • 21 Reply Likes
Hi guys,

Thanks for chiming in. I don't know why this bug was marked "solved." I assume it was an accident; I'm sorry about that.

As for the frequency of the issue, we have you two on GetSat and one or two documented instances in our bug tracking software. Dr. P, I am not sure why you assume we're attempting to minimize the issue. We only earn distrust with that tactic, and in our business distrust is the enemy.

In terms of working toward a solution, I'll likely ask John--the CE Rep who wrote above--to contact you guys to get as much detail as possible. Given the relative scarcity of the issue, pinpointing the source will be the biggest hurdle.  Hopefully we'll be able to make some headway. Thanks.

Patrick Smith
Product Development Manager
CE
Photo of Brandon S

Brandon S

  • 2 Posts
  • 0 Reply Likes
Hi there, I'm seeing this same issue.  We see it with Facebook and Amazon.  Bad_pool_header blue screen.  I'm running Windows 8.1 with AVAST AV.  My wife primarily hits the crash, and she uses IE (not Chrome).  I never hit it, but I almost always use Chrome 64-bit. 

This is the bugcheck analysis I see when I open the crash dump:


BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0010a9699a0, The pool entry we were looking for within the page.
Arg3: ffffe0010a969db0, The next pool entry.
Arg4: 0000000004410011, (reserved)
Debugging Details:
------------------

BUGCHECK_STR:  0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80279561138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffe0010a9699a0 
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER:  from fffff802794a3529 to fffff80279360ca0
STACK_TEXT:  
ffffd001`0f82e1c8 fffff802`794a3529 : 00000000`00000019 00000000`00000020 ffffe001`0a9699a0 ffffe001`0a969db0 : nt!KeBugCheckEx
ffffd001`0f82e1d0 fffff801`a025b249 : 00000000`00000000 ffffc000`8082b7e0 ffffe001`0a9699b0 00000000`30707252 : nt!ExFreePool+0x8d5
ffffd001`0f82e2a0 00000000`00000000 : ffffc000`8082b7e0 ffffe001`0a9699b0 00000000`30707252 00000000`00000400 : cewd64r+0x2249

STACK_COMMAND:  kb
FOLLOWUP_IP: 
cewd64r+2249
fffff801`a025b249 ??              ???
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  cewd64r+2249
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: cewd64r
IMAGE_NAME:  cewd64r.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  54198cce
FAILURE_BUCKET_ID:  0x19_20_cewd64r+2249
BUCKET_ID:  0x19_20_cewd64r+2249
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x19_20_cewd64r+2249
FAILURE_ID_HASH:  {dc9d6e8a-8d6c-b16f-b44c-3e13b7b92e4e}
Followup: MachineOwner

It always indicates the driver file:  cewd64r.sys as the issue.  This is how I knew CE was the issue.  Please feel free to contact me for any more details.  

Regards

  Brandon Stiff
Photo of Jared Burkeen

Jared Burkeen, Software Engineer

  • 23 Posts
  • 4 Reply Likes
Hi Brandon,

This issue has been fixed in the latest beta release of Covenant Eyes (5.1.5.42).  Please give that a try and let us know if you still run into issues.  Thanks for bearing with us on this issue.

Thanks,
Jared
Photo of Brandon S

Brandon S

  • 2 Posts
  • 0 Reply Likes
I installed it a few days ago, so far no crashes. I'll keep you posted.  Thanks!
Photo of Joe R.

Joe R.

  • 1 Post
  • 0 Reply Likes
I'm running 5.1.5.52 (previously running 5.0.4.280 with same issue) on Windows 8.1 and I am getting a BAD_POOL_HEADER BSOD. For me, it's when I'm using IE, primarily on Microsoft websites (windowsazure.com, visualstudio.com). The crash dump reports "Probably caused by : cewd64r.sys ( cewd64r+2249 )."

Unfortunately, completely avoiding these sites on IE is not an option for me.

I'd be happy to send any additional info that would be helpful.

All the best,

Joe
Photo of Jared Burkeen

Jared Burkeen, Software Engineer

  • 23 Posts
  • 4 Reply Likes
Hi Joe,

We have developed a potential fix for this issue, but are still testing it. We hope to release a beta soon that includes the BSOD fix.

Thanks,
Jared