windows 10 Bad Pool Header

Forums › Microsoft Windows › windows 10 Bad Pool Header

jackyleunght2002

392 posts

Ultimate Geek

#204495 4-Oct-2016 14:07

Hi there Computer Helpers

Recently brought it back to the computer shop for a range of this BSOD issues. They have replaced the motherboard for me which I hope it was fixed. So I have download all the relevant drivers
* Nividia graphics card drivers
* Microsoft office 2010 Inc all the relevant updates
* all the windows 10 updates
* then the anniversary updates as well

This morning I just want to have a look and have a tested on it, then here we go it reset 3 times with the Blue Screen with Bad Pool Request.

Now I just dong know what is causing it....

I have follow some advise on the forum and copy the files inside the c:\windows\minidump folder. Will someone know by analysis those command?

Thanks
Jacky

Brumfondl

1186 posts

Uber Geek

Trusted

#1645248 4-Oct-2016 14:26

Is this a fresh Windows install after the motherboard replacement? I also note no mention of the relevant manufacturer's drivers for the board itself.

Tradepub

Free professional, reference and technical white papers (affiliate link).

gzt

16994 posts

Uber Geek

Lifetime subscriber

#1645256 4-Oct-2016 14:48

Short answer return it to the repair shop. They will want to sort that out for you.

Kaitiaki

2 posts

Wannabe Geek

#1645282 4-Oct-2016 15:56

I agree with gzt. If it's freshly back from the shop, they should have a look at it.

However, if you're keen to do some more sleuthing yourself, you could look at the logs/event viewer. It might give you some clues as to what exactly it's being asked to do when it BSOD's on you.

I did this a couple of years ago, helped me find a faulty memory controller on a new motherboard.

xpd

Geek @ Coastguard NZ
13720 posts

Uber Geek

Retired Mod

ID Verified

Trusted

Lifetime subscriber

#1645283 4-Oct-2016 16:03

Run MemTest for starters yourself - might find its just a dodgy stick of RAM.

Gavin / xpd / FastRaccoon / Geek of Coastguard New Zealand

LinkTree - kiwiblast.co.nz - Lego and more

Support Kiwi music! The People Black Smoke Trigger Like A Storm Devilskin

NZ GEEKS Discord______________________________

Lias

5579 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#1645306 4-Oct-2016 16:58

BSOD's like that are usually caused by bad drivers, with bad hardware following up as the minority option.

I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup.

gzt

16994 posts

Uber Geek

Lifetime subscriber

#1645335 4-Oct-2016 17:20

Yep. I'd be guessing a driver incompatibility. If your dump is set up correctly and the right dump etc and that is a big if to get right, you can try the online dump analyser and post the output to the forum:

http://www.osronline.com/page.cfm?name=Analyze

The thing is, if that repair shop intended to fix this for you with a motherboard replacement then they are probably best placed to resolve the issue. There may be a good reason why they chose to look at the hardware.

jackyleunght2002

392 posts

Ultimate Geek

#1645474 4-Oct-2016 21:45

Primary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)

Online Crash Dump Analysis Service

See http://www.osronline.com for more information

Windows 8 Kernel Version 14393 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 14393.206.amd64fre.rs1_release.160915-0644

Machine Name:

Kernel base = 0xfffff801`e147b000 PsLoadedModuleList = 0xfffff801`e177f080

Debug session time: Mon Oct 3 14:34:09.321 2016 (UTC - 4:00)

System Uptime: 0 days 0:00:19.958

*******************************************************************************

* *

* 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: ffffd485390eb770, the pool entry being checked.

Arg3: ffffd485384f0072, the read back flink freelist value (should be the same as 2).

Arg4: ffffd485390eb770, the read back blink freelist value (should be the same as 2).

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x19_3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from fffff801e16c86dc to fffff801e15c52b0

STACK_TEXT:

ffffc401`f9dbbea8 fffff801`e16c86dc : 00000000`00000019 00000000`00000003 ffffd485`390eb770 ffffd485`384f0072 : nt!KeBugCheckEx

ffffc401`f9dbbeb0 fffff801`e1879727 : ffffd485`00000001 00000000`00001000 00000000`00000001 ffffe502`fd000400 : nt!ExDeferredFreePool+0xf3c

ffffc401`f9dbbfa0 fffff801`e1876d31 : 00000000`00000001 ffffc401`f9dbc048 ffffd485`391519ac ffffc401`00000001 : nt!CmpAddSecurityCellToCache+0x8f

ffffc401`f9dbbff0 fffff801`e188bef5 : ffffd485`0001a020 ffffd485`01010001 ffffc401`f9dbc170 ffffc401`f9dbc0d0 : nt!CmpValidateHiveSecurityDescriptors+0x129

ffffc401`f9dbc090 fffff801`e188b355 : 00000000`00020000 00000000`01010001 00000000`000db7b4 00000000`00000001 : nt!CmCheckRegistry+0x111

ffffc401`f9dbc170 fffff801`e1877b80 : ffffc401`f9dbc328 ffffc401`00000000 ffffc401`00020000 ffffffff`80000e4c : nt!CmpInitializeHive+0x4f5

ffffc401`f9dbc250 fffff801`e187d04a : ffffc401`f9dbc505 00000202`276c9601 ffffc401`6e664d43 ffffc401`00000000 : nt!CmpInitHiveFromFile+0x3d0

ffffc401`f9dbc460 fffff801`e1880cc8 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff801`00000000 : nt!CmpCmdHiveOpen+0xbe

ffffc401`f9dbc670 fffff801`e187da35 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmLoadKey+0x190

ffffc401`f9dbc740 fffff801`e187d170 : 00000000`00000000 000000c3`d357edb8 00000000`00000800 00000000`00000000 : nt!CmLoadDifferencingKey+0x8bd

ffffc401`f9dbc9b0 fffff801`e15cff93 : 00000000`00001510 fffff801`e18ea03b 00000202`276c96d0 00000202`28f8b2e0 : nt!NtLoadKeyEx+0x48

ffffc401`f9dbca10 00007ffa`15106de4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

000000c3`d357ed28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffa`15106de4

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!ExDeferredFreePool+f3c

fffff801`e16c86dc cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExDeferredFreePool+f3c

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+f3c

BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+f3c

Followup: Pool_corruption

---------

jackyleunght2002

392 posts

Ultimate Geek

#1645476 4-Oct-2016 21:50

jackyleunght2002: Hi there Computer Helpers

Recently brought it back to the computer shop for a range of this BSOD issues. They have replaced the motherboard for me which I hope it was fixed. So I have download all the relevant drivers
* Nividia graphics card drivers
* Microsoft office 2010 Inc all the relevant updates
* all the windows 10 updates
* then the anniversary updates as well

This morning I just want to have a look and have a tested on it, then here we go it reset 3 times with the Blue Screen with Bad Pool Request.

Now I just dong know what is causing it....

I have follow some advise on the forum and copy the files inside the c:\windows\minidump folder. Will someone know by analysis those command?

Thanks
Jacky

My motherboard is Gigybyte Z170-HD3

gzt

16994 posts

Uber Geek

Lifetime subscriber

#1645485 4-Oct-2016 22:18

Ok, post the next few that occur and we see if it is the same or different each time.

Are you starting this machine with windows 8 and then upgrading to 10?

If that is the case - it would be better to start fresh with 10 and eliminate any potential driver configuration problems that may be arising from the upgrade scenario.

jackyleunght2002

392 posts

Ultimate Geek

#1645488 4-Oct-2016 22:25

it is a new windows 10 setup

i only have 2 dump files

Primary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)

Online Crash Dump Analysis Service

See http://www.osronline.com for more information

Windows 8 Kernel Version 14393 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 14393.206.amd64fre.rs1_release.160915-0644

Machine Name:

Kernel base = 0xfffff801`7247a000 PsLoadedModuleList = 0xfffff801`7277e080

Debug session time: Mon Oct 3 14:33:21.561 2016 (UTC - 4:00)

System Uptime: 0 days 10:25:55.198

*******************************************************************************

* *

* 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: ffff9386d5c2d4f0, The pool entry we were looking for within the page.

Arg3: ffff9386d5c2d5a0, The next pool entry.

Arg4: 00000000040b002c, (reserved)

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

OVERLAPPED_MODULE: Address regions for 'dump_iaStorA' and 'dump_storpor' overlap

BUGCHECK_STR: 0x19_20

POOL_ADDRESS: ffff9386d5c2d4f0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff801726c6de0 to fffff801725c42b0

STACK_TEXT:

ffffe081`429d03a8 fffff801`726c6de0 : 00000000`00000019 00000000`00000020 ffff9386`d5c2d4f0 ffff9386`d5c2d5a0 : nt!KeBugCheckEx

ffffe081`429d03b0 fffff800`1e2d2212 : ffff9386`d5c2d500 ffff9386`d5ce6290 00000000`00000000 fffff800`0000000b : nt!ExDeferredFreePool+0x640

ffffe081`429d0490 fffff800`1e2d8200 : ffff9386`d5c2d500 00000000`00000000 ffff9386`d81fa278 ffff9386`00000009 : FLTMGR!ExFreeToNPagedLookasideList+0x46

ffffe081`429d04c0 fffff800`1e3044bf : ffff9386`d81fa288 00000000`00000000 00000000`00000000 ffff9386`d335f950 : FLTMGR!DoReleaseContext+0x80

ffffe081`429d0500 fffff800`1e2d4b95 : ffff9386`d81fed50 ffffe081`429d05d9 ffff9386`d335f950 ffff9386`d0cd57e0 : FLTMGR!FltpDeleteContextList+0xaf

ffffe081`429d0530 fffff800`1e2d4278 : ffffe081`429d0710 fffff801`7279d400 00000000`00000002 ffff9386`d6607900 : FLTMGR!FltpPerformPreCallbacks+0x7b5

ffffe081`429d0640 fffff800`1e2d3386 : ffff9386`d6607920 ffffe081`429d0710 ffff9386`d6607920 ffffe081`429d0720 : FLTMGR!FltpPassThroughInternal+0x88

ffffe081`429d0670 fffff800`1e2d312e : ffffffff`fffe7960 ffff9386`d0c73df0 00000000`00000001 fffff801`724b62ae : FLTMGR!FltpPassThrough+0x1a6

ffffe081`429d06f0 fffff801`728dbfcd : ffff9386`d81fed50 ffff9386`d81fed50 ffff9386`d6607920 ffff9386`00000021 : FLTMGR!FltpDispatch+0x9e

ffffe081`429d0750 fffff801`728d7448 : ffffb780`bc68d080 00000000`00000000 ffff9386`c8b7af20 00000000`0000009f : nt!IopDeleteFile+0x12d

ffffe081`429d07d0 fffff801`72529671 : 00000000`00000000 00000000`00000000 ffffb780`bc68d080 ffff9386`d81fed50 : nt!ObpRemoveObjectRoutine+0x78

ffffe081`429d0830 fffff801`728f5765 : 00000000`00000000 ffff9386`d81f8cd0 ffffb780`bc68d080 ffff9386`d81f8cd0 : nt!ObfDereferenceObject+0xa1

ffffe081`429d0870 fffff801`72589713 : ffff9386`d81f8cd0 ffffe081`429d0930 fffff801`7279da00 fffff801`727bb180 : nt!MiSegmentDelete+0x171

ffffe081`429d08b0 fffff801`725a7b08 : 00000000`00000002 fffff801`7279d8c0 fffff801`7279d400 fffff801`7279d400 : nt!MiProcessDereferenceList+0xab

ffffe081`429d0960 fffff801`7254c3f5 : f7864886`2a0b063c ffff9386`c8b72040 00000000`00000080 fffff801`725a79ec : nt!MiDereferenceSegmentThread+0x11c

ffffe081`429d0b90 fffff801`725c9776 : fffff801`727bb180 ffff9386`c8b72040 fffff801`7254c3b4 35303131`39303631 : nt!PspSystemThreadStartup+0x41

ffffe081`429d0be0 00000000`00000000 : ffffe081`429d1000 ffffe081`429ca000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

FLTMGR!ExFreeToNPagedLookasideList+46

fffff800`1e2d2212 ebe3 jmp FLTMGR!ExFreeToNPagedLookasideList+0x2b (fffff800`1e2d21f7)

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: FLTMGR!ExFreeToNPagedLookasideList+46

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: FLTMGR

IMAGE_NAME: FLTMGR.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 578997a5

FAILURE_BUCKET_ID: X64_0x19_20_FLTMGR!ExFreeToNPagedLookasideList+46

BUCKET_ID: X64_0x19_20_FLTMGR!ExFreeToNPagedLookasideList+46

Followup: MachineOwner

gzt

16994 posts

Uber Geek

Lifetime subscriber

#1645489 4-Oct-2016 22:28

If you go that way then avoid adding any other drivers, just let windows 10 take care of it.

jackyleunght2002

392 posts

Ultimate Geek

#1645492 4-Oct-2016 22:31

i don't have anything to add anymore...

i just hope this BSOD non-sense to be stop each morning i turn on the machine..

Thanks anyways

Jacky

gzt

16994 posts

Uber Geek

Lifetime subscriber

#1645497 4-Oct-2016 22:44

That seems unlikely. You could try again without Anniversary. Obviously that requires yet another system refresh/rebuild. (then don't forget to set 'defer upgrades' on the first start)