BSOD with Windows Live Messenger BAD POOL HEADER

I had tried that using the Attach File here in the post comment area, but it only accepts image file extensions, does not allow zip either, please advise.

Upload Minidumps to EE "Expert Area"
. Login http://www.ee-stuff.com using your Experts-Exchange username and password.
. Click on "Expert Area" tab
. Type url link of your Question
. "Browse" your pc to the location of your Minidumps click "Upload"
. Copy the resulting "url" and post it back here.

Or change the extension from dmp to txt. Attach the txt here. I will download the file and rename it back to dmp.

I liked that idea :) attached here.
   
And also, after allot of troubleshooting yesterday I can confirm 100% this only happens when I have Windows Live Messenger launched, if I am not logged in it takes a few minutes, if I am logged into chat it happens pretty quick.

!ll the crashes are relating to APPSTREAM.sys. I have no idea what it is. I will search google to find out more about APPSTREAM.sys.

Mini031108-07.dmp BugCheck 19, {20, e8402b70, e8402df8, c510202}
Owning Process            89ac2d78       Image:         dfrgntfs.exe
 Probably caused by : APPSTREAM.SYS ( APPSTREAM+bc80 )

Mini031208-01.dmp BugCheck 10000050, {e7d6d000, 1, 8052aec0, 1}
Owning Process            89968020       Image:         msnmsgr.exe
Probably caused by : APPSTREAM.SYS ( APPSTREAM+15b43 )

Mini031208-02.dmp BugCheck 19, {20, e5dc6000, e5dc6288, c510200}
Owning Process            89adf3f0       Image:         CTLCMgr.exe
Probably caused by : APPSTREAM.SYS ( APPSTREAM+bc80 )

Mini031308-01.dmp BugCheck 19, {20, e795ca20, e795cca8, c510201}
Owning Process            89ea1b40       Image:         Rtvscan.exe
Probably caused by : APPSTREAM.SYS ( APPSTREAM+bc80 )

AppStream Application Manager - yes I also noticed this window pops up when Windows is logging me in that it cannot initialize, I actually wrote it down in my troubleshooting notes but then forgot to follow up on it, this is a corporate laptop so I think they use that monitor our application installs, I'll check with my IS people on that, thank you very much, it saved me allot of trouble, where I would of had to hand over my laptop to my support group, but since the problem was isolated I have been able to continue working on my project during a critical phase while working to resolve my IM conflicts with you guys. Thanks again!

Do you have any update from your support group?

Actually I figured it out, strange about the appstream as it seemed to be unrelated when we disabled it, still got the BSOD. But what I did find out eventually is that had something to do with Windows Live Messenger Folder Share, was using it extensively to share files with a partner and at about 1 gig of data bad things start to happen. When I moved all the files out of the shares, deleted them and since have had no problems. The 1 gig could be a coincidence but my partner pointed it out on his end of the share. It is a really cool feature of Windows Live IM but we stretched it way beyond what it was meant for, now we are running our shared content on a server. This is lengthy response to your question, but wanted to point it out to help others.

Windows Live Messenger screw up the memory and caused windows crash with different bugcheck code and the symptom look like it is memory corrupton or ram problem.. Bugcheck code 19 is only one of them.  A similair problem was also reported at EE. Refer the following problem it crasheswith bugcheck code 19, 05, BE and C5.
http://www.experts-exchange.com/Microsoft/Applications/Q_22668861.html