New
#1
BSOD BAD POOL CALLER since Win10 laptop build 17035
Please help - attaching the relevant zip file with the mini dumps and info...thanks
---
Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\temp\dumps\111417-5718-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 17035 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 17035.1000.amd64fre.rs_prerelease.171103-1616Machine Name:Kernel base = 0xfffff802`6d4a6000 PsLoadedModuleList = 0xfffff802`6d81c890Debug session time: Tue Nov 14 18:56:23.587 2017 (UTC - 5:00)System Uptime: 0 days 0:03:39.443Loading Kernel Symbols............................................................................................. .................................................................................................... ...................Loading User SymbolsLoading unloaded module list..........******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck C2, {4, 0, 0, ffffa4890fbc9638}Probably caused by : memory_corruption ( nt!MiBuildImageControlArea+15565b )Followup: MachineOwner---------3: 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 corruptedArg2: 0000000000000000, Pointer to pool headerArg3: 0000000000000000, First part of pool header contentsArg4: ffffa4890fbc9638, 0Debugging Details:------------------DUMP_CLASS: 1DUMP_QUALIFIER: 400BUILD_VERSION_STRING: 10.0.17035.1000 (WinBuild.160101.0800)DUMP_TYPE: 2BUGCHECK_P1: 4BUGCHECK_P2: 0BUGCHECK_P3: 0BUGCHECK_P4: ffffa4890fbc9638FAULTING_IP: nt!MiBuildImageControlArea+15565bfffff802`6dafe213 4d85e4 test r12,r12BUGCHECK_STR: 0xc2_4CPU_COUNT: 4CPU_MHZ: 855CPU_VENDOR: GenuineIntelCPU_FAMILY: 6CPU_MODEL: 25CPU_STEPPING: 2CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTPROCESS_NAME: psia.exeCURRENT_IRQL: 0ANALYSIS_SESSION_HOST: DESKTOP-O79GJVTANALYSIS_SESSION_TIME: 11-15-2017 13:03:09.0721ANALYSIS_VERSION: 10.0.16299.15 amd64freLAST_CONTROL_TRANSFER: from fffff8026d75ed7e to fffff8026d62ca50STACK_TEXT: ffff978b`11e5a3b8 fffff802`6d75ed7e : 00000000`000000c2 00000000`00000004 00000000`00000000 00000000`00000000 : nt!KeBugCheckExffff978b`11e5a3c0 fffff802`6dafe213 : ffffa488`fe1abc20 00000000`00000000 00000000`00000000 fffff802`00000002 : nt!ExFreePoolWithTag+0x1d4effff978b`11e5a4a0 fffff802`6d9a88cd : 00000000`00000002 ffffb580`f5503178 ffff978b`00000012 ffff978b`00001000 : nt!MiBuildImageControlArea+0x15565bffff978b`11e5a530 fffff802`6d9a6d78 : ffff978b`11e5a9d0 00000004`00000002 00000000`00000000 00000000`00000000 : nt!MiCreateImageFileMap+0x3d5ffff978b`11e5a700 fffff802`6d9d382e : ffff978b`11e5a9d0 ffff978b`11e5a8a0 ffff978b`11e5a9d0 ffffa488`f00165e0 : nt!MiCreateNewSection+0x228ffff978b`11e5a870 fffff802`6d9d2eed : ffff978b`11e5a8a0 00000000`00000000 ffffde02`0a5b3580 00000000`00000000 : nt!MiCreateImageOrDataSection+0x2ceffff978b`11e5a960 fffff802`6d9d2dc4 : ffffa488`faf95060 00000000`00000000 ffff978b`11e5ab90 ffff978b`11e5aaf8 : nt!MiCreateSection+0xddffff978b`11e5aac0 fffff802`6d9d2be5 : 00000000`00000000 ffff978b`11e5acc0 00000000`00000002 00000000`11000000 : nt!MmCreateSection+0xe4ffff978b`11e5ab40 fffff802`6d638253 : ffffde02`04b8e080 00000000`058be458 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x155ffff978b`11e5abd0 00007ff9`89bdc704 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`058be438 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`89bdc704THREAD_SHA1_HASH_MOD_FUNC: 864c9d806dc19b406e6784edc65992eda813e8d4THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 009287d2cf7a849af82c822028624e8d8f363fa8THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406FOLLOWUP_IP: nt!MiBuildImageControlArea+15565bfffff802`6dafe213 4d85e4 test r12,r12FAULT_INSTR_CODE: 74e4854dSYMBOL_STACK_INDEX: 2SYMBOL_NAME: nt!MiBuildImageControlArea+15565bFOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntDEBUG_FLR_IMAGE_TIMESTAMP: 59fd1ebeIMAGE_VERSION: 10.0.17035.1000STACK_COMMAND: .thread ; .cxr ; kbIMAGE_NAME: memory_corruptionBUCKET_ID_FUNC_OFFSET: 15565bFAILURE_BUCKET_ID: 0xc2_4_nt!MiBuildImageControlAreaBUCKET_ID: 0xc2_4_nt!MiBuildImageControlAreaPRIMARY_PROBLEM_CLASS: 0xc2_4_nt!MiBuildImageControlAreaTARGET_TIME: 2017-11-14T23:56:23.000ZOSBUILD: 17035OSSERVICEPACK: 1000SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK: 272PRODUCT_TYPE: 1OSPLATFORM_TYPE: x64OSNAME: Windows 10OSEDITION: Windows 10 WinNt TerminalServer SingleUserTSOS_LOCALE: USER_LCID: 0OSBUILD_TIMESTAMP: 2017-11-03 21:58:22BUILDDATESTAMP_STR: 160101.0800BUILDLAB_STR: WinBuildBUILDOSVER_STR: 10.0.17035.1000ANALYSIS_SESSION_ELAPSED_TIME: 791ANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:0xc2_4_nt!mibuildimagecontrolareaFAILURE_ID_HASH: {82ab6b21-ce14-759e-ffbb-30e614bdbe30}Followup: MachineOwner---------