I got the bad pool caller a few days ago so I'm thinking it may just be the printer drivers that I've installed so i uninstalled it and it goes away for 2-3 days. It came today again when i switch on my monitor.
I have remove all installation of the Hp printer but can it be caused by traces of the printer driver lying around?, if so how do i remove the traces?
i just got this rig so i don't know which parts it causing it.
I've updated every driver of every hardware.
I downloaded memtest and tested my rams and no errors showed up.
this is one of the minidump that another guy on another forum managed to read for me.
it happened again just now. problem is it doesnt come everytime its just once in 2-5 days. so its impossible for me to remove the card and know when it will happen and replace it again.
I've attached another minidump.
Thanks.
I have remove all installation of the Hp printer but can it be caused by traces of the printer driver lying around?, if so how do i remove the traces?
i just got this rig so i don't know which parts it causing it.
I've updated every driver of every hardware.
I downloaded memtest and tested my rams and no errors showed up.
this is one of the minidump that another guy on another forum managed to read for me.
Code:
Loading Dump File [C:\Documents and Settings\edit\Desktop\Mini101307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Windows\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Oct 12 17:41:43.921 2007 (GMT-4)
System Uptime: 0 days 14:50:24.892
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................................
........
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, cd4, 2130006, 888d7c50}
Probably caused by : hardware ( nt!KeForceResumeThread+1 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 02130006, Memory contents of the pool block
Arg4: 888d7c50, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: 888d7c50
FREED_POOL_TAG: File
BUGCHECK_STR: 0xc2_7_File
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LOCK_ADDRESS: 80558b60 -- (!locks 80558b60)
Resource @ nt!PiEngineLock (0x80558b60) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0x80558b60
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
MISALIGNED_IP:
nt!KeForceResumeThread+1
804f9deb 5d pop ebp
LAST_CONTROL_TRANSFER: from 8054a583 to 804f9deb
STACK_TEXT:
bacf3cd4 8054a583 000000c2 00000007 00000cd4 nt!KeForceResumeThread+0x1
bacf3d24 805bf940 888d7c50 00000000 88c6aa40 nt!MiFreePoolPages+0x2a1
bacf3d4c 805b9ee5 00000000 88c6aa58 00000001 nt!PipForAllDeviceNodesCallback+0x29
bacf3d64 805ba330 88c6aa58 00000001 80561e80 nt!VdmSwapContexts+0x199
bacf3dac 805ce84c 00000000 00000000 00000000 nt!CcPfParametersRead+0x21
bacf3ddc 8054532e 805378ce 00000000 00000000 nt!`string'+0x14
bacf3e64 00000000 00000000 00000000 00000000 nt!WmiTraceMessageVa+0x290
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeForceResumeThread+1
804f9deb 5d pop ebp
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
SYMBOL_NAME: nt!KeForceResumeThread+1
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
it happened again just now. problem is it doesnt come everytime its just once in 2-5 days. so its impossible for me to remove the card and know when it will happen and replace it again.
I've attached another minidump.
Thanks.