Solved BSOD BAD_POOL_HEADER 0x00000019

[Caroline33]

Hey

So I got my German uncle's laptop, and by default it was in german. I installed Windows live essentials and the English language to change it, it told me to restart and I did. When it opened again the blue screen showed up on the "welcome" screen (which was still in German)
I tried opening in the safe mode and doing a recovery, everything was in German and I was completely lost, my uncle doesn't know anything about computers and he couldn't help me translate. I also tried to uninstall windows live essentials but it only had the option to uninstall a photo program in it, I'm pretty sure it wasn't what I installed.
Anyway even after the recovery I still received the message.

I need urgent help, and please make your answer detailed because this computer is German and I can't understand a word.

I'm sorry I couldn't do the log collector, because the battery died and I am still gonna buy a charger. I need an urgent answer and a solution please.

 

[torchwood]

Hi Caroline,

Dont look german to me.
Read this tutorial
Advanced Boot Options - Windows 7 Help Forums


Any way DOESNT matter
get to that screen again and DO as it says HIT F8.

one of the options is last known good select it
(even if the instructions are in German the placing of the instructions is IDENTICAL.


Roy

Thought Live essentials was gone.

 

[Caroline33]

Hi Caroline,

Dont look german to me.
Read this tutorial
Advanced Boot Options - Windows 7 Help Forums


Any way DOESNT matter
get to that screen again and DO as it says HIT F8.

one of the options is last known good select it
(even if the instructions are in German the placing of the instructions is IDENTICAL.


Roy

Thought Live essentials was gone.

Hey! I tried your suggestion, but with no luck :/
It's still just as it was :/
And yeah the message is English but everything else is german

 

[axe0]

Hi Caroline33,

I'm sorry to disappoint you, but without any dump we cannot provide proper solutions.
This crash is typically caused by drivers, but the screen doesn't mention a driver.

What you could try as a next step is a clean boot
Troubleshoot Application Conflicts by Performing a Clean Startup - Windows 7 Help Forums

 

[dg1261]

Did the BSODs just start recently, for no apparent reason? Does he have antivirus installed? If so, which brand?

I ask because I've been seeing a rash of this exact screen in the last two weeks, and it's been traced to certain versions of Avast and/or AVG. (BTW, AVG is now owned by Avast.) Avast is a Czech company, so it seems reasonable to expect it might be a popular choice for a German user.

If he has Avast or AVG installed, go into Safe Mode and uninstall it. Then see if the computer boots properly without it. If it does, install a different AV product, or the latest Avast Free 2017, which doesn't have the problem.

 

[Caroline33]

Did the BSODs just start recently, for no apparent reason? Does he have antivirus installed? If so, which brand?

I ask because I've been seeing a rash of this exact screen in the last two weeks, and it's been traced to certain versions of Avast and/or AVG. (BTW, AVG is now owned by Avast.) Avast is a Czech company, so it seems reasonable to expect it might be a popular choice for a German user.

If he has Avast or AVG installed, go into Safe Mode and uninstall it. Then see if the computer boots properly without it. If it does, install a different AV product, or the latest Avast Free 2017, which doesn't have the problem.

GOSH THANK YOU! They were about to literally kill me! He had Avast, I uninstalled it as you said and everything became all good again! Tysm!!!

 

[dg1261]

Glad to hear that.

Normally, it would be quite a stretch to jump straight to the av app as your first suspect, but the timing of your post was too coincidental. As near as I can tell, the problem just began about 8-10 days ago, and I've had almost a dozen customers in the past 7 days with this exact problem.

I have several old versions of Avast and was able to replicate the problem on a test machine. While researching the problem I came across a post in some other forum somewhere that seemed to be from an Avast rep, acknowledging the problem. I wouldn't expect them to put out a patch, though, since it only affects some older versions, and Avast can legitimately advise users to just upgrade to the current version. I confirmed with my tests that Avast Free 2017 doesn't have the problem.