Keepers
Threadstarter
- Dabei seit
- 10.06.2004
- Beiträge
- 104
- Alter
- 34
Ich erhalte in unregelmäßigen Abständen regelmäßig den Bluescreen "Bad Pool Header".
Ich kann jedoch nicht identifizieren welches Problem vorliegt. Der Ram ist in Ordnung, die Festplatten auch.
Die Online Suche hat mir noch nie etwas gebracht, Berichte sende ich automatisch immer ein.
Folgendes sagt mir das Problemcenter noch dazu:
Und das steht in der dmp File:
Hardware:
Q9550, Asus P5Q SE2, OCZ 2x2GB, WD Caviar Blue 640GB, Samsung F1 640GB
Ich kann jedoch nicht identifizieren welches Problem vorliegt. Der Ram ist in Ordnung, die Festplatten auch.
Die Online Suche hat mir noch nie etwas gebracht, Berichte sende ich automatisch immer ein.
Folgendes sagt mir das Problemcenter noch dazu:
Code:
Weitere Informationen über das Problem
BCCode: 19
BCP1: 00000022
BCP2: 8860E000
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Serverinformationen: 313f3ff5-059f-4f30-9df8-fec432fc9d6cUnd das steht in der dmp File:
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Stefan\Documents\Mini081209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x81e0c000 PsLoadedModuleList = 0x81f23c70
Debug session time: Wed Aug 12 22:13:24.812 2009 (GMT+2)
System Uptime: 0 days 0:24:23.004
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {22, 8860e000, 0, 0}
*** WARNING: Unable to verify timestamp for PCTAppEvent.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTAppEvent.sys
*** WARNING: Unable to verify timestamp for TfSysMon.sys
*** ERROR: Module load completed but symbols could not be loaded for TfSysMon.sys
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
Probably caused by : PCTAppEvent.sys ( PCTAppEvent+dc58 )
Followup: MachineOwner
---------
0: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
0: 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: 00000022,
Arg2: 8860e000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for PCTAppEvent.sys
*** ERROR: Module load completed but symbols could not be loaded for PCTAppEvent.sys
*** WARNING: Unable to verify timestamp for TfSysMon.sys
*** ERROR: Module load completed but symbols could not be loaded for TfSysMon.sys
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
BUGCHECK_STR: 0x19_22
POOL_ADDRESS: GetPointerFromAddress: unable to read from 81f43868
Unable to read MiSystemVaType memory at 81f23420
8860e000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: TFNotice.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 81ec1c3c to 81ed9b0d
STACK_TEXT:
9ac58a14 81ec1c3c 00000019 00000022 8860e000 nt!KeBugCheckEx+0x1e
9ac58a50 81ef914a 8860e000 9ac58a9c 9ac58a80 nt!ExpFindAndRemoveTagBigPages+0x1d5
9ac58ac0 9d326c58 8860e000 00000000 9ac58ae0 nt!ExFreePoolWithTag+0x145
WARNING: Stack unwind information not available. Following frames may be wrong.
9ac58ad0 9d31ad03 8860e000 8860e000 9ac58b0c PCTAppEvent+0xdc58
9ac58ae0 9d31bb64 00000001 87f83e00 885cb160 PCTAppEvent+0x1d03
9ac58b0c 9d31e194 9a049b08 885cb160 00008000 PCTAppEvent+0x2b64
9ac58b48 9d31e493 000004a0 864d1020 00000080 PCTAppEvent+0x5194
9ac58b80 9d323244 0000163c 000004a0 00000000 PCTAppEvent+0x5493
9ac58bbc 81ffd1e8 0000163c 000004a0 00000000 PCTAppEvent+0xa244
9ac58bec 820245c1 00000001 4d608af4 866254a8 nt!PspExitProcess+0x99
9ac58c54 82024b32 800c00cc 00000000 86625248 nt!PspExitThread+0x574
9ac58c74 81ffcf3d 86625248 800c00cc 00000001 nt!PspTerminateThreadByPointer+0x5b
9ac58ca4 8ab96b32 ffffffff 800c00cc 0012fe98 nt!NtTerminateProcess+0x1e0
9ac58cdc 90750c67 ffffffff 800c00cc ffffffff TfSysMon+0x6b32
9ac58d40 9d322ea8 ffffffff 800c00cc ffffffff avipbb+0x8c67
9ac58d54 81e56c7a ffffffff 800c00cc 0012fe98 PCTAppEvent+0x9ea8
9ac58d54 77a25e74 ffffffff 800c00cc 0012fe98 nt!KiFastCallEntry+0x12a
0012fe98 00000000 00000000 00000000 00000000 0x77a25e74
STACK_COMMAND: kb
FOLLOWUP_IP:
PCTAppEvent+dc58
9d326c58 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: PCTAppEvent+dc58
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: PCTAppEvent
IMAGE_NAME: PCTAppEvent.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4949a302
FAILURE_BUCKET_ID: 0x19_22_PCTAppEvent+dc58
BUCKET_ID: 0x19_22_PCTAppEvent+dc58
Followup: MachineOwner
---------
0: kd>
0: kd>Hardware:
Q9550, Asus P5Q SE2, OCZ 2x2GB, WD Caviar Blue 640GB, Samsung F1 640GB
