BSOD error 0x19 (BAD_POOL_HEADER) and 0x1000008E doing anything

Hi.
Whenever I do just about anything on my PC (this has happened 3 times, first I was managing files, second I was YouTubing and third I was playing RCT3) I will get a BSOD. The first was a KERNEL_MODE_EXCEPTION_NOT_HANDLED_M error which occurred in aswndis2.sys (the Avast! kernel mode filter driver) however the second 2 were BAD_POOL_CALLER errors, one was caused in fltmgr.sys (bog standard Microsoft driver) and the other was caused in atikmdag.sys (GPU driver). It seems to me that something is badly wrong with my PC, but I have no idea what it is... Usually I can figure these things out but I don't want to mess up my PC
Thanks for reading, and your help is appreciated,
-Toby
P.S. In case you need them I'll attach kernel dumps as they come :)

Attached is my minidumps and my WhoCrashed log...
Sorry for the double post!

* Your Avast can be a contributing cause of BSOD'S.
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows


* These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have raid > update its Driver.


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users

First we dont recommend Who crashed because of its tendancy to incorrectly blame OS files as in your case


Please do the suggested ideas by JMH first and after that update these drivers from as far back as 2007

Code:

XPVCOM.sys    3/21/2007 1:45:59 AM    0x9482b000    0x94830000        0x00005000    0x4600d4a7                        
TVALZ_O.SYS    11/8/2007 10:07:46 PM    0x8b1c3000    0x8b1c7180        0x00004180    0x4733cf02                        
VMNetSrv.sys    1/16/2008 6:51:44 AM    0x94881000    0x94892000        0x00011000    0x478defd0                        
hamachi.sys    2/19/2009 5:36:27 AM    0xa3832000    0xa3836c00        0x00004c00    0x499d362b                        
Rt86win7.sys    2/26/2009 4:04:22 AM    0x93b85000    0x93baa000        0x00025000    0x49a65b16                        
rtl8192se.sys    3/20/2009 8:09:53 AM    0x93af6000    0x93b85000        0x0008f000    0x49c395a1                        
vmm.sys    4/7/2009 8:25:32 AM    0x9367b000    0x936b6000        0x0003b000    0x49db544c                        
AtiPcie.sys    5/5/2009 10:00:16 AM    0x8b029000    0x8b031000        0x00008000    0x4a005480                        
GEARAspiWDM.sys    5/18/2009 7:16:53 AM    0x943e3000    0x943e8280        0x00005280    0x4a1151b5                        
RtHDMIV.sys    5/20/2009 5:04:37 AM    0x99e61000    0x99e85d40        0x00024d40    0x4a13d5b5                        
STREAM.SYS    7/13/2009 6:50:57 PM    0x9492c000    0x94939180        0x0000d180    0x4a5bc861

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Thanks people.
My drivers do seem to be up-to-date (very poor driver support).
Overclocking and RAID are out of the question as this is a laptop (even though I said PC, universal term).
I do have a reason to believe Avast is bogging me down, it's been running stable ever since I disabled it so I'll try MSE now.

WhatsAUserName said:

Thanks people.
My drivers do seem to be up-to-date (very poor driver support).
Overclocking and RAID are out of the question as this is a laptop (even though I said PC, universal term).
I do have a reason to believe Avast is bogging me down, it's been running stable ever since I disabled it so I'll try MSE now.

I dont know what method you are using to check if they are up to date but for at least two of the drivers there are updates.

Well, at the moment it doesn't matter to me. Sorry for the slow reply, but I've been running on MSE for a while and so far so good! No more BSOD... So I tried a Windows update, installed Avast again and once again the system is unstable. Well, guess I found my problem. Thanks for pointing out my epic failure in driver updates, lol.
Now, to mark as solved...

Good luck!