BSOD: "Bad Pool Header" when log on Win7 + others BSOD problem

[tijang]

BSOD: "Bad Pool Header" when log on Win7 + others BSOD problem

I have some problem on my Toshiba M645 Laptop.
The blue screen came out when I try to log on,
BSOD "Bad Pool Header" appears in front of the log on screen. (already started-up before)
This is the first time of BSOD by newly OS, all drivers installed and it happens one time.
Before this happens, I turned on my external LCD monitor that included 4 USB Hub connector.
[4 USB Devices: Keyboard, Mouse, DAC, UPS Data Link turned on when switched on the monitor]

Previously, I've seen BSOD "Page Fault in Nonpaged Area" when softwares, devices are
starting up (appears one time), then I formatted OS & claimed a new mainboard already.
Can anyone tell me the system data written failed can caused this problem or the hardware issue?

Maybe it's caused by driver problem, please check my dump files & help.
Thanks in advance.

My Laptop: Toshiba Satellite M645-1014X

OS: Windows 7 Ultimate x64 OEM Toshiba
CPU: Intel Core i5 M560 2.67GHz
RAM: Samsung 4GB 2x2 Dual Channel
HDD: Hitachi 500GB
VGA: Intel HD Graphics, NVIDIA Geforce GT330M 1GB
SOUND: Realtek High Definition Audio

 

[tijang]

May I bump once.
Hope someone can find out what caused my two blue screens, also the solutions.
Thanks a lot.

 

[wish]

Hi,
Your single dump have 0x19_20 bugcheck (BAD_POOL_HEADER) -> usual cause by 3rd party driver.

Start with diagnose your hardrive since the perform report indicates hardisk error.
1] Right click Command prompt -> run as admin -> chkdsk /f /r
2] Try manufacture Hardrive Diagnostic tools --> Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Then enable driver verifier to stress out your drivers.
If there is any driver violation your windows will crash, then attach the new files here.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Log

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8008c529c0, fffffa8008c52a20, 4060002}

GetPointerFromAddress: unable to read from fffff800030f30e0
Probably caused by : ntkrnlmp.exe ( nt!IopFreeMiniCompletionPacket+87 )

Followup: MachineOwner
---------

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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8008c529c0, The pool entry we were looking for within the page.
Arg3: fffffa8008c52a20, The next pool entry.
Arg4: 0000000004060002, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffffa8008c529c0 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fee6d3 to fffff80002ebb740

STACK_TEXT:  
fffff880`1c145958 fffff800`02fee6d3 : 00000000`00000019 00000000`00000020 fffffa80`08c529c0 fffffa80`08c52a20 : nt!KeBugCheckEx
fffff880`1c145960 fffff800`0317396b : fffff880`00baa000 fffff800`031a5748 fffffa80`20706349 00000000`6e496c41 : nt!ExDeferredFreePool+0x12c4
fffff880`1c145a10 fffff800`02e720ca : fffffa80`099d7000 0000002a`08ada060 fffff880`00baa000 00000000`00000000 : nt!IopFreeMiniCompletionPacket+0x87
fffff880`1c145a40 fffff800`02e71f00 : fffffa80`099d7000 fffffa80`08b02090 fffffa80`099d7000 fffffa80`08b02090 : nt!AlpcpDeferredFreeCompletionPacketLookaside+0x2a
fffff880`1c145a70 fffff800`031102fe : fffff8a0`09a6d840 fffff880`1c145ca0 fffffa80`08b02090 00000000`00000000 : nt!AlpcpFreeCompletionPacketLookaside+0x38
fffff880`1c145ac0 fffff800`031a8764 : 00000000`00000000 fffffa80`00000001 00000000`0063f000 fffff880`00000002 : nt!AlpcpInitializeCompletionList+0x21e
fffff880`1c145b40 fffff800`02eba993 : fffffa80`08b02090 fffffa80`08d38600 00000000`001c7380 00000000`00000000 : nt!NtAlpcSetInformation+0x32f
fffff880`1c145c20 00000000`770805ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0063efd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770805ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!IopFreeMiniCompletionPacket+87
fffff800`0317396b eba1            jmp     nt!IopFreeMiniCompletionPacket+0x26 (fffff800`0317390e)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!IopFreeMiniCompletionPacket+87

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x19_20_nt!IopFreeMiniCompletionPacket+87

BUCKET_ID:  X64_0x19_20_nt!IopFreeMiniCompletionPacket+87

Followup: MachineOwner
---------