BSOD at startup: Bad Pool Header 0x19

[collven]

Windows 7 Enterprise x64
Not original OS, retail version
System is 6 months old, as is the OS install.

Sorry, my perfmon wouldn't run. This is my work laptop, and I'm going home now, so if any more info is needed, I will update tonight.

Thanks

 

[yowanvista]

Remove/upgrade Symantec pcAnywhere, your current version is obsolete.

awechomd.sys        fffff880`06df6000    fffff880`06dfd000    0x00007000    0x45d97d5e    19/02/2007 14:35:10                
aw_host5.sys        fffff880`04199000    5974efbb`041a2000    0x5974f73b00009000    0x45d97d75    19/02/2007 14:35:33                
agrsm64.sys        fffff880`0ac7d000    fffff880`0ad9f000    0x00122000    0x49184ccf    10/11/2008 19:01:35

Update your Norton security product, use the latest versions.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8007dc6b20, The pool entry we were looking for within the page.
Arg3: fffffa8007dc6be0, The next pool entry.
Arg4: 00000000040c0002, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800042b7100
 fffffa8007dc6b20 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  smss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800041b2cae to fffff80004084c40

STACK_TEXT:  
fffff880`06bd57c8 fffff800`041b2cae : 00000000`00000019 00000000`00000020 fffffa80`07dc6b20 fffffa80`07dc6be0 : nt!KeBugCheckEx
fffff880`06bd57d0 fffff880`01bd8c27 : 00000000`0055f318 fffffa80`07d70e00 00000000`706d4443 00000000`0055f318 : nt!ExDeferredFreePool+0x12da
fffff880`06bd5880 fffff880`01bd87f3 : fffffa80`05ec66b0 00000000`00000001 00000000`00000000 00000000`00000001 : crashdmp!FreePortResources+0x7f
fffff880`06bd58b0 fffff880`01bd8889 : 00000000`00000000 00000000`00000000 fffff880`706d4443 00000000`00000000 : crashdmp!CrashdmpFreeDumpStack+0x6b
fffff880`06bd58e0 fffff800`0417f9ae : fffffa80`08970b60 00000000`00000004 00000000`0055f318 00000000`00000000 : crashdmp!CrashdmpDisable+0x69
fffff880`06bd5910 fffff800`044e14ea : 00000000`00000001 fffffa80`08970b60 00000000`00000001 00000000`00000000 : nt!IopDisableCrashDump+0x1e
fffff880`06bd5940 fffff800`044fb3dc : 00000000`00000000 fffff880`06bd5b60 00000000`00000000 fffffa80`08964b30 : nt!IoConfigureCrashDump+0xaa
fffff880`06bd5970 fffff800`04083ed3 : fffffa80`08970b60 00000000`00135000 00000000`00135000 00000000`00130000 : nt!NtSetSystemInformation+0x65f
fffff880`06bd5ae0 00000000`77262a0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0055f2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77262a0a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
crashdmp!FreePortResources+7f
fffff880`01bd8c27 48391b          cmp     qword ptr [rbx],rbx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  crashdmp!FreePortResources+7f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: crashdmp

IMAGE_NAME:  crashdmp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcabd

FAILURE_BUCKET_ID:  X64_0x19_20_crashdmp!FreePortResources+7f

BUCKET_ID:  X64_0x19_20_crashdmp!FreePortResources+7f

Followup: MachineOwner
---------

 

[collven]

OK, I'll try that tonight. Is there anything else you can see in there?

 

[yowanvista]

OK, I'll try that tonight. Is there anything else you can see in there?

Your Symantec products appear to be the cause.