BSOD BAD POOL CALLER - reboot loop after Win10 laptop build 17035

Hi - ever since I went to the latest fast ring build the laptop keeps crashing (blue screen of death) with bad pool caller ... memory dumps and system info can be viewed here:

https://1drv.ms/u/s!AovDqjsnYlriiPYMSrmM81OqnKKSCQ

Would appreciate your help

---

Loading Dump File [C:\temp\dumps\111417-7546-01.dmp]

Loading Dump File [C:\temp\dumps\111417-7546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

************* Path validation summary **************
Response Time (ms) Location
Response Time (ms) Location
Deferred Deferred srv*srv*

Symbol search path is: Symbol search path is: srv*
srv*
Executable search path is:
Executable search path is:
Windows 10 Kernel Windows 10 Kernel Version 17035Version 17035 MP MP (4 procs) (4 procs) Free x64
Free x64
Product: Product: WinNtWinNt, suite:, suite: TerminalServer TerminalServer SingleUserTS SingleUserTS

Built by: 17035.1000.amd64fre.rs_prerelease.171103-1616
Built by: 17035.1000.amd64fre.rs_prerelease.171103-1616
Machine Name:Machine Name:

Kernel base = 0xfffff802`e6290000 PsLoadedModuleList = 0xfffff802`e6606890
Kernel base = 0xfffff802`e6290000 PsLoadedModuleList = 0xfffff802`e6606890
Debug session time: Tue Nov 14 18:43:27.459 2017 (UTC - 5:00)
Debug session time: Tue Nov 14 18:43:27.459 2017 (UTC - 5:00)
System Uptime: 0 days 0:04:21.324System Uptime: 0 days 0:04:21.324

Loading Kernel Symbols
Loading Kernel Symbols
..............................................................................................................................

................................................................................................................................

................................................................................................................................

............................................

Loading User Symbols
Loading User Symbols
Loading unloaded module list
.Loading unloaded module list
...................

Unable to deliver callback, Unable to deliver callback, 3131

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

Use Use !analyze -v !analyze -v to get detailed debugging information.

to get detailed debugging information.

BugCheck BugCheck C2C2, {, {44, , 00, , 00, , ffffde0072797888ffffde0072797888}

}

Probably caused by : Probably caused by : memory_corruptionmemory_corruption ( ( nt!MiBuildImageControlArea+15565bnt!MiBuildImageControlArea+15565b )
)

Followup:
Followup: MachineOwnerMachineOwner
---------

---------

1: kd> !analyze -v
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: 0000000000000004, Pool header has been corrupted
Arg2: 0000000000000000, Pointer to pool header
Arg3: 0000000000000000, First part of pool header contents
Arg4: ffffde0072797888, 0

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

*******************************************************************************
* *
* 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: 0000000000000004, Pool header has been corrupted
Arg2: 0000000000000000, Pointer to pool header
Arg3: 0000000000000000, First part of pool header contents
Arg4: ffffde0072797888, 0

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

DUMP_CLASS:
DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17035.1000 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 4

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: ffffde0072797888

FAULTING_IP:
nt!MiBuildImageControlArea+15565b1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.17035.1000 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 4

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: ffffde0072797888

FAULTING_IP:
nt!MiBuildImageControlArea+15565b

fffff802`e68e8213 4d85e4 test r12,r12
fffff802`e68e8213 4d85e4 test r12,r12

BUGCHECK_STR: 0xc2_4

CPU_COUNT: 4

CPU_MHZ: 855

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 25

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: psia.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-O79GJVT

ANALYSIS_SESSION_TIME: 11-15-2017 14:35:04.0377

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

LAST_CONTROL_TRANSFER: from fffff802e6548d7e to fffff802e6416a50

STACK_TEXT:
BUGCHECK_STR: 0xc2_4

CPU_COUNT: 4

CPU_MHZ: 855

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 25

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: psia.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-O79GJVT

ANALYSIS_SESSION_TIME: 11-15-2017 14:35:04.0377

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

LAST_CONTROL_TRANSFER: from fffff802e6548d7e to fffff802e6416a50

STACK_TEXT:
ffff9d8a`232ae3b8 fffff802`e6548d7e : 00000000`000000c2 00000000`00000004 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9d8a`232ae3c0 fffff802`e68e8213 : ffffde00`83d86af0 00000000`00000000 00000000`00000000 fffff802`00000002 : nt!ExFreePoolWithTag+0x1d4e
ffff9d8a`232ae4a0 fffff802`e67928cd : 00000000`00000002 ffffca01`6f638178 ffff9d8a`00000012 ffff9d8a`00001000 : nt!MiBuildImageControlArea+0x15565b
ffff9d8a`232ae530 fffff802`e6790d78 : ffff9d8a`232ae9d0 00000004`00000002 00000000`00000000 00000000`00000000 : nt!MiCreateImageFileMap+0x3d5
ffff9d8a`232ae700 fffff802`e67bd82e : ffff9d8a`232ae9d0 ffff9d8a`232ae8a0 ffff9d8a`232ae9d0 ffffde00`628165e0 : nt!MiCreateNewSection+0x228
ffff9d8a`232ae870 fffff802`e67bceed : ffff9d8a`232ae8a0 00000000`00000000 ffff880d`5ecfaef0 00000000`00000000 : nt!MiCreateImageOrDataSection+0x2ce
ffff9d8a`232ae960 fffff802`e67bcdc4 : ffffde00`6d6d9ac0 00000000`00000000 ffff9d8a`232aeb90 ffff9d8a`232aeaf8 : nt!MiCreateSection+0xdd
ffff9d8a`232aeac0 fffff802`e67bcbe5 : 00000000`00000000 ffff9d8a`232aecc0 00000000`00000002 00000000`11000000 : nt!MmCreateSection+0xe4
ffff9d8a`232aeb40 fffff802`e6422253 : ffff880d`5969b080 00000000`059be6a8 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x155
ffff9d8a`232aebd0 00007ffe`241ac704 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`059be688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`241ac704

ffff9d8a`232ae3b8 fffff802`e6548d7e : 00000000`000000c2 00000000`00000004 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9d8a`232ae3c0 fffff802`e68e8213 : ffffde00`83d86af0 00000000`00000000 00000000`00000000 fffff802`00000002 : nt!ExFreePoolWithTag+0x1d4e
ffff9d8a`232ae4a0 fffff802`e67928cd : 00000000`00000002 ffffca01`6f638178 ffff9d8a`00000012 ffff9d8a`00001000 : nt!MiBuildImageControlArea+0x15565b
ffff9d8a`232ae530 fffff802`e6790d78 : ffff9d8a`232ae9d0 00000004`00000002 00000000`00000000 00000000`00000000 : nt!MiCreateImageFileMap+0x3d5
ffff9d8a`232ae700 fffff802`e67bd82e : ffff9d8a`232ae9d0 ffff9d8a`232ae8a0 ffff9d8a`232ae9d0 ffffde00`628165e0 : nt!MiCreateNewSection+0x228
ffff9d8a`232ae870 fffff802`e67bceed : ffff9d8a`232ae8a0 00000000`00000000 ffff880d`5ecfaef0 00000000`00000000 : nt!MiCreateImageOrDataSection+0x2ce
ffff9d8a`232ae960 fffff802`e67bcdc4 : ffffde00`6d6d9ac0 00000000`00000000 ffff9d8a`232aeb90 ffff9d8a`232aeaf8 : nt!MiCreateSection+0xdd
ffff9d8a`232aeac0 fffff802`e67bcbe5 : 00000000`00000000 ffff9d8a`232aecc0 00000000`00000002 00000000`11000000 : nt!MmCreateSection+0xe4
ffff9d8a`232aeb40 fffff802`e6422253 : ffff880d`5969b080 00000000`059be6a8 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x155
ffff9d8a`232aebd0 00007ffe`241ac704 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`059be688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`241ac704

THREAD_SHA1_HASH_MOD_FUNC: 864c9d806dc19b406e6784edc65992eda813e8d4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 009287d2cf7a849af82c822028624e8d8f363fa8

THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP:
nt!MiBuildImageControlArea+15565b

THREAD_SHA1_HASH_MOD_FUNC: 864c9d806dc19b406e6784edc65992eda813e8d4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 009287d2cf7a849af82c822028624e8d8f363fa8

THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP:
nt!MiBuildImageControlArea+15565b

fffff802`e68e8213 4d85e4 test r12,r12
fffff802`e68e8213 4d85e4 test r12,r12

FAULT_INSTR_CODE: 74e4854d

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiBuildImageControlArea+15565b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME:
FAULT_INSTR_CODE: 74e4854d

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!MiBuildImageControlArea+15565b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt
nt

DEBUG_FLR_IMAGE_TIMESTAMP: 59fd1ebe

IMAGE_VERSION: 10.0.17035.1000

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 15565b

FAILURE_BUCKET_ID: 0xc2_4_nt!MiBuildImageControlArea

BUCKET_ID: 0xc2_4_nt!MiBuildImageControlArea

PRIMARY_PROBLEM_CLASS: 0xc2_4_nt!MiBuildImageControlArea

TARGET_TIME: 2017-11-14T23:43:27.000Z

OSBUILD: 17035

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-11-03 21:58:22

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17035.1000

ANALYSIS_SESSION_ELAPSED_TIME: a1e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc2_4_nt!mibuildimagecontrolarea

FAILURE_ID_HASH: {82ab6b21-ce14-759e-ffbb-30e614bdbe30}

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

DEBUG_FLR_IMAGE_TIMESTAMP: 59fd1ebe

IMAGE_VERSION: 10.0.17035.1000

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 15565b

FAILURE_BUCKET_ID: 0xc2_4_nt!MiBuildImageControlArea

BUCKET_ID: 0xc2_4_nt!MiBuildImageControlArea

PRIMARY_PROBLEM_CLASS: 0xc2_4_nt!MiBuildImageControlArea

TARGET_TIME: 2017-11-14T23:43:27.000Z

OSBUILD: 17035

OSSERVICEPACK: 1000

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-11-03 21:58:22

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17035.1000

ANALYSIS_SESSION_ELAPSED_TIME: a1e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc2_4_nt!mibuildimagecontrolarea

FAILURE_ID_HASH: {82ab6b21-ce14-759e-ffbb-30e614bdbe30}

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

This thread is locked. You can vote as helpful, but you cannot reply or subscribe to this thread.

Answer

Erika Aro

Hi,

The BSOD BAD POOL CALLER error can be due to drivers since drivers do not update automatically when an update/upgrade takes place. Run the driver verifier to troubleshoot the concern. If the issue persists, perform a clean install.

As a workaround, rollback from 17035 to the previous build (17025). To do so, go to Settings > Update & Security > Recovery > Go back to the previous version of Windows 10. After that, restart your device and reinstall any missing drivers. Verify if it will prompt you to update to a new version.

Additionally, we encourage you to post this as a feedback in the Feedback Hub. We'll gather additional details and information about your concern that will help determine the cause and address it. The feedback items regularly receive Microsoft responses to see what we're doing about your submission.

For more information on Feedback Hub, see our support article and YouTube video

. In order to submit a new feedback, please follow the steps below:

Type Feedback Hub in the Cortana search and press Enter.
Navigate to Feedback in the left menu, click + Add new feedback tab.
Select the Problem, and share the details you want to us to know, and choose the appropriate category and subcategory.

Note: Reproduce your concern if possible while is monitoring is enabled. To do this, click Begin monitoring or Start Capture to start recording and Stop monitoring when you’re done.
Once you've completed the form and monitoring, click Submit.
Click My feedback at the top, then find the item you submitted.
Open the item you submitted, then click Share.
Click Copy link, then paste the link here in your response (It will look like https://aka.ms/<unique link>).

Revisit frequently for status updates. If you have further queries, don't hesitate to post back.

Contribute to the Windows forum!

Windows 10 Forum Top Contributors:

BSOD BAD POOL CALLER - reboot loop after Win10 laptop build 17035

Replies (3)

Question Info

BSOD BAD POOL CALLER - reboot loop after Win10 laptop build 17035

Replies (3) 

Question Info

Replies (3)