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\A6364233910549F3A054E0BD5869 F65F2\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" <rick@mvps.org> kirjoitti viestissä
news:uTW5kadmIHA.2396@TK2MSFTNGP02.phx.gbl...
> Got a dump file?
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org
> My thoughts http://rick-mvp.blogspot.com
>
> "Jake_Fin" <jarkko.ruottinen@mail.suomi.net> wrote in message
> news:3E6C0799-B019-4F20-A4FE-A1714EC639A9@microsoft.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" <rick@mvps.org> kirjoitti viestissä
>> news:ODvoQGSmIHA.3636@TK2MSFTNGP02.phx.gbl...
>>> 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
>>> http://mvp.support.microsoft.com/
>>> Windows help - www.rickrogers.org
>>> My thoughts http://rick-mvp.blogspot.com
>>>
>>> "Jake_Fin" <jarkko.ruottinen@mail.suomi.net> wrote in message
>>> news:499FDB04-8241-4486-962D-77DCD44E49FA@microsoft.com...
>>>>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.
>>>>
>>>> "nexisroath" <nexisroath.35mtsk@no-mx.forums.vistaheads.com> kirjoitti
>>>> viestissä news:nexisroath.35mtsk@no-mx.forums.vistaheads.com...
>>>>>
>>>>> I have been having the same problems. Being more intuitive with
>>>>> hardware
>>>>> than software, i have encountered this problem aswell.
>>>>>
>>>>> these are my hardware specs. do you have the same or similar issues
>>>>> with hardware or are we a very few in a specific statistic?
>>>>>
>>>>>
>>>>> Manufacturer: CUSTOM
>>>>> Motherboard: MSI IP35 Platnium Edition
>>>>> Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2 CPUs), ~2.4GHz
>>>>> Memory: 8191GB RAM
>>>>> Hard Drive: 81 GB, 1001 GB
>>>>> Video Card: Radeon X1950 Pro Radeon X1950 Pro Crossfire
>>>>> Monitor: 24" HDLCD Wide screen flat panel
>>>>> Sound Card: Razer Barracuda AC-1
>>>>> Speakers/Headphones: Razer Barracuda HP-1
>>>>> Keyboard: Razer Tarantula
>>>>> Mouse: Logitec MX518
>>>>> Mouse Surface: Table
>>>>> Operating System: Windows Vista 64bit
>>>>>
>>>>>
>>>>> --
>>>>> nexisroath
>>>>> Posted via http://www.vistaheads.com
>>>>>
>>>>
>>>
>>
>
Linear Mode
