Windows 7 ntoskrnl.exe BSOD windows 7 x64

[fnukyguy]

had a BSOD recently...whocrashed said ntoskrnl.exe is to blame...
it happened while testing out a flash webcam-instant messager website for the first time : Link Removed due to 404 Error

if its because of webcam-drivers or graphic drivers, wouldnt the dumpfile tell me so?

my guess it has something to do with all the windows updates that was released 14th of june this month

here is the minidump-file

any ideas?

 

[Trouble]

Bad Pool Header

............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff80003063e50, fba9d2fba9d2fba9, d2fba9d2fba9d2fb}
[COLOR=#b22222]Probably caused by : Pool_Corruption[/COLOR] ( nt!ExDeferredFreePool+a53 )
Followup: Pool_corruption
---------
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=#b22222]BAD_POOL_HEADER [/COLOR](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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff80003063e50, the pool entry being checked.
Arg3: fba9d2fba9d2fba9, the read back flink freelist value (should be the same as 2).
Arg4: d2fba9d2fba9d2fb, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------

BUGCHECK_STR:  0x19_3
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff800030064b3 to fffff80002edbd00
STACK_TEXT:  
fffff880`037e7858 fffff800`030064b3 : 00000000`00000019 00000000`00000003 fffff800`03063e50 fba9d2fb`a9d2fba9 : nt!KeBugCheckEx
fffff880`037e7860 fffff800`02ec6732 : 00000000`00000000 00000000`00000130 fffff880`00001f80 00000000`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`037e7950 fffff800`02f554f5 : fffffa80`09664ec8 fffff880`00000001 00000000`00000001 fffff880`037e7bb0 : nt!MiAgeWorkingSet+0x5e8
fffff880`037e7b00 fffff800`02ec68c6 : 00000000`000072a2 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4d886
fffff880`037e7b80 fffff800`02ec6d67 : 00000000`00000008 fffff880`037e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`037e7bd0 fffff800`0317832e : fffffa80`0550d9e0 00000000`00000080 fffffa80`0548e890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`037e7d40 fffff800`02ecd666 : fffff880`009b2180 fffffa80`0550d9e0 fffff880`009bd0c0 3d743d74`e338e338 : nt!PspSystemThreadStartup+0x5a
fffff880`037e7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!ExDeferredFreePool+a53
fffff800`030064b3 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!ExDeferredFreePool+a53
FOLLOWUP_NAME:  Pool_corruption
IMAGE_NAME:  Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

You have several bad (in the sense that they are very old) drivers that you need to address first and then a few others which we may need to revisit that are somewhat old and marginal.
pcouffin.sys 12/5/2006 (DVDFab , VSO, Blindwrite, etc.,) update, or uninstall or rename (as a last resort)
LVUSBS64.sys 2/3/2007 (Logitech Machine Vision Engine Loader belongs to the software Logitech QuickCam by Logitech Inc) update, or uninstall or rename (as last resort)
CamDrL64.sys 2/3/2007 (another logitech driver) action = same as above
LVMVDrv.sys 2/6/2007 (another logitech driver) action = same as above
ManyCam_x64.sys 3/13/2008 (ManyCam Virtual Webcam, WDM Video Capture Driver) update, or uninstall or rename (as a last resort)
anodlwfx.sys 3/6/2009 (ANOD Network Security Filter driver Alpha Networks Inc) action = same as above
Additonally you have sptd.sys 10/11/2009 a well known villian when it comes to BSODs, usually a product of a driver emulator type software like Daemon Tools use Link Removed for your appropriate version of Win7 and click the uninstall button.
Take care of the above items and read these
Link Removed follow the instructions and make sure you right click it and choose run as administrator.
and
Link Removed follow the instructions to provide memory tab and all slots (SPD tab) as well as zipping up and including the exported html report from RAMMon.
Check with ASUS regarding AsIO.sys 8/3/2009 (ASUS Probe) see if they have anything more current or consider uninstalling.
Last you might want to possibly consider removing Avast and replacing with Link Removed due to 404 Error
Good luck and keep us posted
Regards
Randy

 

[fnukyguy]

thanks! this was very helpfull!

come to think of it, I got the bsod while I was selecting which webcamera to use in the settings at Link Removed due to 404 Error

I was switching quickly between the "manycam"-virtual-webcam, the logitech 4000 and microsoft livecam and suddenly I got a bsod..

im pretty sure I got the bsod because of the manycam-program , or the logitech 4000 (it was using old vista 64 drivers, there are no win7 64bit drivers for it)...
ive gotten rid of manycam and logitech 4000, hopefully I wont see a bsod again...

 

[Trouble]

Thanks for the follow-up. If any new BSODs should happen, include them with your next post in this thread along with the additional information requested above.
Welcome to the forums and thanks for joining our community.
Regards
Randy

 

[fnukyguy]

by the way, does this sound likely to you?
that the bsod is caused by webcam drivers even though minidump debuggers say ntoskrnl.exe is probably the cause?

 

[Trouble]

Very likely.... read the paragraph from windbg that I posted above.

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.

No absolute guarantee, but yes likely.