New
#1
Win 7 pro BSOD Pool_corruption
Hi There
I have a pc newly built that has been crashing . I tested the memory using memtest and it found that one of the memory chips was faulty so i swapped for working memory which tested fine but now im getting pool corruption bsod. see below . Is it possible that the system is corrupt as i installed the os with the faulty memory already in the machine.
Any help or guidance would be greatly appreciated
regards
G
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Oliver\Desktop\050410-16785-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50
Debug session time: Tue May 4 14:50:53.985 2010 (GMT+1)
System Uptime: 0 days 6:08:18.421
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffffa80025a0cd0, 0, fffffa80025a0cd0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+75b )
Followup: Pool_corruption
---------
2: 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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa80025a0cd0, the pool entry being checked.
Arg3: 0000000000000000, the read back flink freelist value (should be the same as 2).
Arg4: fffffa80025a0cd0, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002c0a10b to fffff80002ad7600
STACK_TEXT:
fffff880`0315d798 fffff800`02c0a10b : 00000000`00000019 00000000`00000003 fffffa80`025a0cd0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0315d7a0 fffff800`02c0c4c1 : fffff800`00000003 fffffa80`034b5d30 00000000`00000000 fffff880`0100e66e : nt!ExFreePool+0x75b
fffff880`0315d830 fffff880`01007633 : 00000000`00000705 fffff8a0`0a9d9ed8 fffffa80`6c734d46 fffff800`000003ed : nt!ExFreePoolWithTag+0x411
fffff880`0315d8e0 fffff800`02dc7746 : 00000000`00000001 fffff880`0129b0b8 fffff880`0315d9b0 00000000`00000000 : fltmgr! ?? ::FNODOBFM::`string'+0x429
fffff880`0315d910 fffff880`0129abcc : fffff8a0`0a9d9c70 fffffa80`018c31a0 fffff880`0315d9e8 00000000`00000706 : nt!FsRtlTeardownPerStreamContexts+0xe2
fffff880`0315d960 fffff880`0129a8d5 : 00000000`01010000 00000000`00000000 fffff800`02c7c500 00000000`00000001 : Ntfs!NtfsDeleteScb+0x108
fffff880`0315d9a0 fffff880`0120dcb4 : fffff8a0`0a9d9b70 fffff8a0`0a9d9c70 fffff800`02c7c500 fffff880`0315db12 : Ntfs!NtfsRemoveScb+0x61
fffff880`0315d9e0 fffff880`012982dc : fffff8a0`0a9d9b40 fffff800`02c7c5a0 fffff880`0315db12 fffffa80`05a5de40 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`0315da10 fffff880`01216882 : fffffa80`05a5de40 fffffa80`05a5de40 fffff8a0`0a9d9b40 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xdc
fffff880`0315da90 fffff880`012af813 : fffffa80`05a5de40 fffff800`02c7c5a0 fffff8a0`0a9d9b40 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`0315dad0 fffff880`0128938f : fffffa80`05a5de40 fffff8a0`0a9d9c70 fffff8a0`0a9d9b40 fffffa80`03481180 : Ntfs!NtfsCommonClose+0x353
fffff880`0315dba0 fffff800`02ae4861 : 00000000`00000000 fffff800`02dd4800 fffffa80`018c3101 fffffa80`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`0315dc70 fffff800`02d7ca86 : 00000000`00000000 fffffa80`018c31a0 00000000`00000080 fffffa80`018a9040 : nt!ExpWorkerThread+0x111
fffff880`0315dd00 fffff800`02ab5b06 : fffff880`02f63180 fffffa80`018c31a0 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0315dd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExFreePool+75b
fffff800`02c0a10b cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExFreePool+75b
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExFreePool+75b
BUCKET_ID: X64_0x19_3_nt!ExFreePool+75b
Followup: Pool_corruption
---------
Last edited by gavinlynch; 04 May 2010 at 18:37.