New
#1
BSOD BAD_POOL_HEADER error 0x00000019
Hi all,
I've been getting hit with Bad pool header BSODs for a few days now. It just started recently, and no new hardware has been installed (aside from plug and play headphones getting plugged and unplugged every so often which never seemed to cause a problem before.
Unfortunately, my expertise is more in the Unix/Max OS X side of things, so I thought I'd come to the experts for some help :)
In my cursory investigations, It looks like the errors are caused by some missing/expected pieces in the fffffa80`0a9a2340 area of memory (in that it's expecting that bit to exist based on my understanding of the bad pool header error). Based on what I could find digging around in the dump files it looks like this driver: em006_64.dat deals with that space (fffffa80`08225000 to fffffa80`08253000). The drive belongs to my AV (ESET NOD 32) and, I assume, updates regularly and without interaction from me. However, the exceptions actually come from the ntoskrnl.exe driver (unsurprisingly) according to Windows.
Am I on the right track here? If not feel free to shoot me down :)
I'm on the verge of reformatting and reinstalling (which I'm not against, it's been a while), but I wanted to make sure if I did that, I wouldn't continue to see the problem.
Let me know what you guys think. I've attached the zip file with the relevant BSODs.
Thanks guys. Much appreciated.