Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Win 7 pro BSOD Pool_corruption

04 May 2010   #1
gavinlynch

Windows 7 Professional 64bit
 
 
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
---------


My System SpecsSystem Spec
.
05 May 2010   #2
usasma
Microsoft MVP

 
 

Due to the presence of ntfs.sys in the stack text, I'd suggest these things:
Quote:
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
and

Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
My primary suspicion is a hardware error (which the above tests should help isolate). This is because you've got 8 memory dumps, with 7 different error messages and 7 different causes (which is usually indicative of a hardware problems).

Please replace this older driver: ewusbmdm.sys Sun Mar 16 23:06:13 2008 - EWUSBMDM.SYS is related to USB Modem/Serial Device Driver - "Huawei Mobile Connect" package. More info on it here: Driver Reference

But, because of the Pool_Corruption error, I'd suggest running Driver Verifier according to these directions:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Summary of the BSOD's:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May  4 09:50:53.985 2010 (GMT-4)
System Uptime: 0 days 6:08:18.421
BugCheck 19, {3, fffffa80025a0cd0, 0, fffffa80025a0cd0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+75b )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May  1 07:36:18.482 2010 (GMT-4)
System Uptime: 0 days 0:31:02.355
BugCheck A, {fffffa0003ac0178, 2, 1, fffff80002b85a5f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 29 19:26:39.127 2010 (GMT-4)
System Uptime: 0 days 15:24:35.984
BugCheck 3B, {c0000005, fffff960000d8054, fffff88007dd0f90, 0}
Probably caused by : win32k.sys ( win32k+c8054 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  O2 Broadband.e
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 29 04:01:24.232 2010 (GMT-4)
System Uptime: 0 days 0:05:13.089
BugCheck 4A, {76e2021a, 2, 0, fffff8800935fc60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
PROCESS_NAME:  OUTLOOK.EXE
BUGCHECK_STR:  RAISED_IRQL_FAULT
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Apr 28 13:26:33.077 2010 (GMT-4)
System Uptime: 0 days 9:46:46.934
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : tcpip.sys ( tcpip!IppRouteSetTimeout+14 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Apr 26 07:09:50.152 2010 (GMT-4)
System Uptime: 0 days 2:36:20.010
BugCheck D1, {fffff8a00c0d3000, 2, 0, fffff8800150fa84}
Probably caused by : cng.sys ( cng!SHA256Transform+65 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Apr 26 04:32:31.582 2010 (GMT-4)
System Uptime: 0 days 0:01:10.439
BugCheck 1A, {41790, fffffa8001e026d0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a08 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  wmi64.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Apr 19 04:50:18.453 2010 (GMT-4)
System Uptime: 0 days 0:06:43.920
BugCheck 3B, {c0000096, fffff80002ada966, fffff88006ef2dc0, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
My System SpecsSystem Spec
06 May 2010   #3
gavinlynch

Windows 7 Professional 64bit
 
 

Thanks USASMA it turns out my crappy psu screwed up my motherboard so replaced both and now everything peachy well at least for the time being <

cheers

Gavin
My System SpecsSystem Spec
.

Reply

 Win 7 pro BSOD Pool_corruption




Thread Tools




Similar help and support threads
Thread Forum
BSOD - Pool_Corruption etc...
Hello, Im quite new to debug NT dumps so I'm looking for little help with BSOD on w7 ent. x64 edition. In short, problem is recurring when i try to sleep notebook or eventually when its restoring from sleep mode. Ive checked some debug tutorials but got little problem with loading...
BSOD Help and Support
Windows 7 x64 Pro BSOD on Pool_Corruption
Hi, Can someone take a look at the Minidumps and see if you can find out the cause, the laptop is a brand new (2 days old) Dell Lat. E6510 and the Mem test and HDD Long test come out clean. Thanks, Abdul Moid
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 06:15.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App