bad.pool.header error

  • Thread starter Thread starter Amore3
  • Start date Start date
A

Amore3

I just re-installed vista and the first night I left the computer running. I
the morning while trying to log in (from hybernation), I got the dreaded blue
screen error bad.pool.header. It has happened the 2 nights I left the
computer on. Since I do most of the scanning (defender, virus, etc) at night
while I sleep, I prefer not to shut down before going to sleep,

When the computer re-boots after the error, it works fine

Anyone else with a similar problem?

Al
 
I also have same issue.
I dont know is this reason,yet. But it seem happening with automatic
defregment.
I have 32 vista home premium, with custom language and I dont have SP1 yet
AMD prosessor and Nvidia gfx card.
Only mouse is same than yours.
 
Hi,

BAD_POOL_HEADER is usually driver related and unlikely to be related to the
defrag utility unless perhaps it's the drive controllers. An error code,
modules involved, some history on the issue, and a dump file may help
decipher the cause.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Jake_Fin said:
I also have same issue.
I dont know is this reason,yet. But it seem happening with automatic
defregment.
I have 32 vista home premium, with custom language and I dont have SP1 yet
AMD prosessor and Nvidia gfx card.
Only mouse is same than yours.
Click to expand...
 
0x00000019 (0x00000020, 0xfd765910, 0xfd765990)

Somehow I cannot connect this information to anywhere at my PC.
Hard drives are SATA 160 GB Maxtor 6Y160M0 SCSI Disk Device --> driver
6.0.6000.16386 microsoft.
Thanks for info.

Rick Rogers said:
Hi,

BAD_POOL_HEADER is usually driver related and unlikely to be related to
the defrag utility unless perhaps it's the drive controllers. An error
code, modules involved, some history on the issue, and a dump file may
help decipher the cause.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
Click to expand...
 
kd> !analyze -v
*******************************************************************************
*
*
* 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: 00000020, a pool block header size is corrupt.
Arg2: fe22f4f0, The pool entry we were looking for within the page.
Arg3: fe22f4f0, The next pool entry.
Arg4: 4a000008, (reserved)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************



MODULE_NAME: win32k

FAULTING_MODULE: 81800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fe22f4f0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
a332bbc4 818e7ce8 00000019 00000020 fe22f4f0 nt+0xd8681
a332bc38 818e86f6 fe22f4f8 00000000 a332bc54 nt+0xe7ce8
a332bc48 902d8847 fe22f4f8 a332bc64 902d92d0 nt+0xe86f6
a332bc54 902d92d0 84ce9b58 fe22f4f8 a332bc80 win32k+0xd8847
a332bc64 902dd82b fe7a1924 fe22f4f8 00000308 win32k+0xd92d0
a332bc80 902d974b fe22f4f8 a332bd14 00000000 win32k+0xdd82b
a332bce4 902de450 a332bd14 000025ff 00000000 win32k+0xd974b
a332bd48 8188caaa 01c6fa14 00000000 00000000 win32k+0xde450
a332bd64 77560f34 badb0d00 01c6f9a0 00000000 nt+0x8caaa
a332bd68 badb0d00 01c6f9a0 00000000 00000000 0x77560f34
a332bd6c 01c6f9a0 00000000 00000000 00000000 0xbadb0d00
a332bd70 00000000 00000000 00000000 00000000 0x1c6f9a0


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k+d8847
902d8847 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k+d8847

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
 
Now full dump info

*******************************************************************************
*
*
* 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: 00000020, a pool block header size is corrupt.
Arg2: fdf74d10, The pool entry we were looking for within the page.
Arg3: fdf74d10, The next pool entry.
Arg4: 4a000008, (reserved)

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fdf74d10 Paged session pool

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
9cc75c6c 818e7ce8 00000019 00000020 fdf74d10 nt!KeBugCheckEx+0x1e
9cc75ce0 910cab23 fdf74d18 00000000 ff005128 nt!ExFreePoolWithTag+0x17f
9cc75cfc 910cea16 fdf74d18 fdf74d18 9cc75d24 win32k!HMFreeObject+0xa6
9cc75d0c 910cdec0 fdf74d18 00010062 0135f890 win32k!FreeTimer+0x51
9cc75d24 910cea73 ff005128 00000005 00000000 win32k!FindTimer+0x65
9cc75d40 910cea4a ff005128 00000005 0135f890 win32k!_KillTimer+0x16
9cc75d54 8188caaa 00010062 00000005 0135f904 win32k!NtUserKillTimer+0x2a
9cc75d54 77310f34 00010062 00000005 0135f904 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0135f904 00000000 00000000 00000000 00000000 0x77310f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMFreeObject+a6
910cab23 668b460a mov ax,word ptr [esi+0Ah]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!HMFreeObject+a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

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

kd> !analyze -v
*******************************************************************************
*
*
* 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: 00000020, a pool block header size is corrupt.
Arg2: fdf74d10, The pool entry we were looking for within the page.
Arg3: fdf74d10, The next pool entry.
Arg4: 4a000008, (reserved)

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fdf74d10 Paged session pool

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
9cc75c6c 818e7ce8 00000019 00000020 fdf74d10 nt!KeBugCheckEx+0x1e
9cc75ce0 910cab23 fdf74d18 00000000 ff005128 nt!ExFreePoolWithTag+0x17f
9cc75cfc 910cea16 fdf74d18 fdf74d18 9cc75d24 win32k!HMFreeObject+0xa6
9cc75d0c 910cdec0 fdf74d18 00010062 0135f890 win32k!FreeTimer+0x51
9cc75d24 910cea73 ff005128 00000005 00000000 win32k!FindTimer+0x65
9cc75d40 910cea4a ff005128 00000005 0135f890 win32k!_KillTimer+0x16
9cc75d54 8188caaa 00010062 00000005 0135f904 win32k!NtUserKillTimer+0x2a
9cc75d54 77310f34 00010062 00000005 0135f904 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0135f904 00000000 00000000 00000000 00000000 0x77310f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMFreeObject+a6
910cab23 668b460a mov ax,word ptr [esi+0Ah]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!HMFreeObject+a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

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

kd> lmvm win32k
start end module name
91000000 911ff000 win32k (pdb symbols)
c:\symbols\win32k.pdb\A6364233910549F3A054E0BD5869F65F2\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file:
c:\symbols\win32k.sys\47C787181ff000\win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Fri Feb 29 06:16:24 2008 (47C78718)
CheckSum: 001F0A91
ImageSize: 001FF000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
 
Also had same error, but different process
kd> !analyze -v
*******************************************************************************
*
*
* 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: 00000020, a pool block header size is corrupt.
Arg2: fe22f4f0, The pool entry we were looking for within the page.
Arg3: fe22f4f0, The next pool entry.
Arg4: 4a000008, (reserved)

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




BUGCHECK_STR: 0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
Unable to read MiSystemVaType memory at 819117e0
fe22f4f0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: sidebar.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
a332bbc4 818e7ce8 00000019 00000020 fe22f4f0 nt!KeBugCheckEx+0x1e
a332bc38 818e86f6 fe22f4f8 00000000 a332bc54 nt!ExFreePoolWithTag+0x17f
a332bc48 902d8847 fe22f4f8 a332bc64 902d92d0 nt!ExFreePool+0xf
a332bc54 902d92d0 84ce9b58 fe22f4f8 a332bc80
win32k!ExFreeToPagedLookasideList+0x1e
a332bc64 902dd82b fe7a1924 fe22f4f8 00000308 win32k!DelQEntry+0x44
a332bc80 902d974b fe22f4f8 a332bd14 00000000 win32k!xxxReadPostMessage+0x10a
a332bce4 902de450 a332bd14 000025ff 00000000
win32k!xxxRealInternalGetMessage+0x2b9
a332bd48 8188caaa 01c6fa14 00000000 00000000 win32k!NtUserPeekMessage+0x3f
a332bd48 77560f34 01c6fa14 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01c6f9c0 00000000 00000000 00000000 00000000 0x77560f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!ExFreeToPagedLookasideList+1e
902d8847 eb09 jmp win32k!ExFreeToPagedLookasideList+0x29
(902d8852)

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!ExFreeToPagedLookasideList+1e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x19_20_win32k!ExFreeToPagedLookasideList+1e

BUCKET_ID: 0x19_20_win32k!ExFreeToPagedLookasideList+1e

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


Jake_Fin said:
Now full dump info

*******************************************************************************
* *
* 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: 00000020, a pool block header size is corrupt.
Arg2: fdf74d10, The pool entry we were looking for within the page.
Arg3: fdf74d10, The next pool entry.
Arg4: 4a000008, (reserved)

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fdf74d10 Paged session pool

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
9cc75c6c 818e7ce8 00000019 00000020 fdf74d10 nt!KeBugCheckEx+0x1e
9cc75ce0 910cab23 fdf74d18 00000000 ff005128 nt!ExFreePoolWithTag+0x17f
9cc75cfc 910cea16 fdf74d18 fdf74d18 9cc75d24 win32k!HMFreeObject+0xa6
9cc75d0c 910cdec0 fdf74d18 00010062 0135f890 win32k!FreeTimer+0x51
9cc75d24 910cea73 ff005128 00000005 00000000 win32k!FindTimer+0x65
9cc75d40 910cea4a ff005128 00000005 0135f890 win32k!_KillTimer+0x16
9cc75d54 8188caaa 00010062 00000005 0135f904 win32k!NtUserKillTimer+0x2a
9cc75d54 77310f34 00010062 00000005 0135f904 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0135f904 00000000 00000000 00000000 00000000 0x77310f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMFreeObject+a6
910cab23 668b460a mov ax,word ptr [esi+0Ah]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!HMFreeObject+a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

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

kd> !analyze -v
*******************************************************************************
* *
* 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: 00000020, a pool block header size is corrupt.
Arg2: fdf74d10, The pool entry we were looking for within the page.
Arg3: fdf74d10, The next pool entry.
Arg4: 4a000008, (reserved)

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fdf74d10 Paged session pool

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
9cc75c6c 818e7ce8 00000019 00000020 fdf74d10 nt!KeBugCheckEx+0x1e
9cc75ce0 910cab23 fdf74d18 00000000 ff005128 nt!ExFreePoolWithTag+0x17f
9cc75cfc 910cea16 fdf74d18 fdf74d18 9cc75d24 win32k!HMFreeObject+0xa6
9cc75d0c 910cdec0 fdf74d18 00010062 0135f890 win32k!FreeTimer+0x51
9cc75d24 910cea73 ff005128 00000005 00000000 win32k!FindTimer+0x65
9cc75d40 910cea4a ff005128 00000005 0135f890 win32k!_KillTimer+0x16
9cc75d54 8188caaa 00010062 00000005 0135f904 win32k!NtUserKillTimer+0x2a
9cc75d54 77310f34 00010062 00000005 0135f904 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0135f904 00000000 00000000 00000000 00000000 0x77310f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMFreeObject+a6
910cab23 668b460a mov ax,word ptr [esi+0Ah]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!HMFreeObject+a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

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

kd> lmvm win32k
start end module name
91000000 911ff000 win32k (pdb symbols)
c:\symbols\win32k.pdb\A6364233910549F3A054E0BD5869F65F2\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file:
c:\symbols\win32k.sys\47C787181ff000\win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Fri Feb 29 06:16:24 2008 (47C78718)
CheckSum: 001F0A91
ImageSize: 001FF000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0


Rick Rogers said:
Got a dump file?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
Click to expand...
Click to expand...
 
I have the same problem on a new Dell Latitude D830 running Vista Ultimate.
The following is the detail given by Vista:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 19
BCP1: 00000020
BCP2: 84B96000
BCP3: 84B96A00
BCP4: 09400000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini052208-03.dmp
C:\Users\Fred\AppData\Local\Temp\WER-58500-0.sysdata.xml
C:\Users\Fred\AppData\Local\Temp\WER59E2.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

The problem seemed to have started when I tried to share a folder by either
right-clicking and selecting sharing from the menu or by selecting share from
the properties dialog block for a directory. The BSOD would appear
immediately. I removed the sharing but now am getting BSOD on a regular basis
BAD_POOL_HEADER.

On restart, Vista asks me to "Check for a Solution". I say OK but the box
just goes away with no answer after a few seconds. I checked the Vista
website, but Microsoft does not acknowledge the problem.

Any ideas out there?

Jake_Fin said:
Also had same error, but different process
kd> !analyze -v
*******************************************************************************
*
*
* 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: 00000020, a pool block header size is corrupt.
Arg2: fe22f4f0, The pool entry we were looking for within the page.
Arg3: fe22f4f0, The next pool entry.
Arg4: 4a000008, (reserved)

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




BUGCHECK_STR: 0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
Unable to read MiSystemVaType memory at 819117e0
fe22f4f0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: sidebar.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
a332bbc4 818e7ce8 00000019 00000020 fe22f4f0 nt!KeBugCheckEx+0x1e
a332bc38 818e86f6 fe22f4f8 00000000 a332bc54 nt!ExFreePoolWithTag+0x17f
a332bc48 902d8847 fe22f4f8 a332bc64 902d92d0 nt!ExFreePool+0xf
a332bc54 902d92d0 84ce9b58 fe22f4f8 a332bc80
win32k!ExFreeToPagedLookasideList+0x1e
a332bc64 902dd82b fe7a1924 fe22f4f8 00000308 win32k!DelQEntry+0x44
a332bc80 902d974b fe22f4f8 a332bd14 00000000 win32k!xxxReadPostMessage+0x10a
a332bce4 902de450 a332bd14 000025ff 00000000
win32k!xxxRealInternalGetMessage+0x2b9
a332bd48 8188caaa 01c6fa14 00000000 00000000 win32k!NtUserPeekMessage+0x3f
a332bd48 77560f34 01c6fa14 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01c6f9c0 00000000 00000000 00000000 00000000 0x77560f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!ExFreeToPagedLookasideList+1e
902d8847 eb09 jmp win32k!ExFreeToPagedLookasideList+0x29
(902d8852)

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!ExFreeToPagedLookasideList+1e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x19_20_win32k!ExFreeToPagedLookasideList+1e

BUCKET_ID: 0x19_20_win32k!ExFreeToPagedLookasideList+1e

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


Jake_Fin said:
Now full dump info

*******************************************************************************
* *
* 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: 00000020, a pool block header size is corrupt.
Arg2: fdf74d10, The pool entry we were looking for within the page.
Arg3: fdf74d10, The next pool entry.
Arg4: 4a000008, (reserved)

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fdf74d10 Paged session pool

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
9cc75c6c 818e7ce8 00000019 00000020 fdf74d10 nt!KeBugCheckEx+0x1e
9cc75ce0 910cab23 fdf74d18 00000000 ff005128 nt!ExFreePoolWithTag+0x17f
9cc75cfc 910cea16 fdf74d18 fdf74d18 9cc75d24 win32k!HMFreeObject+0xa6
9cc75d0c 910cdec0 fdf74d18 00010062 0135f890 win32k!FreeTimer+0x51
9cc75d24 910cea73 ff005128 00000005 00000000 win32k!FindTimer+0x65
9cc75d40 910cea4a ff005128 00000005 0135f890 win32k!_KillTimer+0x16
9cc75d54 8188caaa 00010062 00000005 0135f904 win32k!NtUserKillTimer+0x2a
9cc75d54 77310f34 00010062 00000005 0135f904 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0135f904 00000000 00000000 00000000 00000000 0x77310f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMFreeObject+a6
910cab23 668b460a mov ax,word ptr [esi+0Ah]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!HMFreeObject+a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

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

kd> !analyze -v
*******************************************************************************
* *
* 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: 00000020, a pool block header size is corrupt.
Arg2: fdf74d10, The pool entry we were looking for within the page.
Arg3: fdf74d10, The next pool entry.
Arg4: 4a000008, (reserved)

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fdf74d10 Paged session pool

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 818e7ce8 to 818d8681

STACK_TEXT:
9cc75c6c 818e7ce8 00000019 00000020 fdf74d10 nt!KeBugCheckEx+0x1e
9cc75ce0 910cab23 fdf74d18 00000000 ff005128 nt!ExFreePoolWithTag+0x17f
9cc75cfc 910cea16 fdf74d18 fdf74d18 9cc75d24 win32k!HMFreeObject+0xa6
9cc75d0c 910cdec0 fdf74d18 00010062 0135f890 win32k!FreeTimer+0x51
9cc75d24 910cea73 ff005128 00000005 00000000 win32k!FindTimer+0x65
9cc75d40 910cea4a ff005128 00000005 0135f890 win32k!_KillTimer+0x16
9cc75d54 8188caaa 00010062 00000005 0135f904 win32k!NtUserKillTimer+0x2a
9cc75d54 77310f34 00010062 00000005 0135f904 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0135f904 00000000 00000000 00000000 00000000 0x77310f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMFreeObject+a6
910cab23 668b460a mov ax,word ptr [esi+0Ah]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!HMFreeObject+a6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47c78718

FAILURE_BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

BUCKET_ID: 0x19_20_win32k!HMFreeObject+a6

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

kd> lmvm win32k
start end module name
91000000 911ff000 win32k (pdb symbols)
c:\symbols\win32k.pdb\A6364233910549F3A054E0BD5869F65F2\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file:
c:\symbols\win32k.sys\47C787181ff000\win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Fri Feb 29 06:16:24 2008 (47C78718)
CheckSum: 001F0A91
ImageSize: 001FF000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0


Rick Rogers said:
Got a dump file?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

0x00000019 (0x00000020, 0xfd765910, 0xfd765990)

Somehow I cannot connect this information to anywhere at my PC.
Hard drives are SATA 160 GB Maxtor 6Y160M0 SCSI Disk Device --> driver
6.0.6000.16386 microsoft.
Thanks for info.

"Rick Rogers" <[email protected]> kirjoitti viestiss
Hi,

BAD_POOL_HEADER is usually driver related and unlikely to be related to
the defrag utility unless perhaps it's the drive controllers. An error
code, modules involved, some history on the issue, and a dump file may
help decipher the cause.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
Click to expand...
Click to expand...
Click to expand...
 
Back
Top