• 所有社区 - 中文
    • 所有社区 - 中文
    • 论坛
    • 创意
    • 博客
高级

不是您要找的? 咨询专家!

此论坛帖文需要解决方案。
好评0

BAD_POOL_CALLER BSOD caused by nis.exe on Windows 10

Hi

I recently "upgraded" my desktop machine to Windows 10 and having been getting BSOD BAD_POOL_CALLER crashes intermittently since.   It was stable with Windows 7.

When I load the dump file from the crash in Windbg, the process is always nis.exe.   The bugcheck analysis is below,

The NIS version installed is 22.6.0.142.   Live Update says it's up to date.

Thanks

*******************************************************************************
*                                                                             *
*                        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: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000126c, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff800e5a92628, Address of the block of pool being deallocated

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

fffff803a880c520: Unable to get MiVisibleState

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER:  Hewlett-Packard

SYSTEM_PRODUCT_NAME:  p6677c

SYSTEM_SKU:  BT432AA#ABC

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  6.02

BIOS_DATE:  07/21/2010

BASEBOARD_MANUFACTURER:  FOXCONN

BASEBOARD_PRODUCT:  2AB1

BASEBOARD_VERSION:  DVT

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: 7

BUGCHECK_P2: 126c

BUGCHECK_P3: 0

BUGCHECK_P4: fffff800e5a92628

POOL_ADDRESS: fffff803a880c520: Unable to get MiVisibleState
 fffff800e5a92628

BUGCHECK_STR:  0xc2_7

CPU_COUNT: 4

CPU_MHZ: b54

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 10

CPU_MODEL: 5

CPU_STEPPING: 3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  nis.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  ASGARD

ANALYSIS_SESSION_TIME:  06-13-2016 18:26:13.0608

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff803a86bfcf7 to fffff803a85d0780

STACK_TEXT:  
ffffd001`36c8a808 fffff803`a86bfcf7 : 00000000`000000c2 00000000`00000007 00000000`0000126c 00000000`00000000 : nt!KeBugCheckEx
ffffd001`36c8a810 fffff800`e4e69aef : ffffe000`5287c7e0 fffff800`e54a8994 ffffe000`5287c7e0 ffffe000`40e97130 : nt!ExDeferredFreePool+0x547
ffffd001`36c8a8f0 ffffe000`5287c7e0 : fffff800`e54a8994 ffffe000`5287c7e0 ffffe000`40e97130 ffffe000`561c3e00 : SYMEVENT64x86+0x9aef
ffffd001`36c8a8f8 fffff800`e54a8994 : ffffe000`5287c7e0 ffffe000`40e97130 ffffe000`561c3e00 fffff800`e4e63d67 : 0xffffe000`5287c7e0
ffffd001`36c8a900 ffffe000`5287c7e0 : ffffe000`40e97130 ffffe000`561c3e00 fffff800`e4e63d67 ffffe000`561c3dd0 : BHDrvx64+0xa8994
ffffd001`36c8a908 ffffe000`40e97130 : ffffe000`561c3e00 fffff800`e4e63d67 ffffe000`561c3dd0 fffff800`e4e63ea4 : 0xffffe000`5287c7e0
ffffd001`36c8a910 ffffe000`561c3e00 : fffff800`e4e63d67 ffffe000`561c3dd0 fffff800`e4e63ea4 00000000`00000000 : 0xffffe000`40e97130
ffffd001`36c8a918 fffff800`e4e63d67 : ffffe000`561c3dd0 fffff800`e4e63ea4 00000000`00000000 00000000`00000b64 : 0xffffe000`561c3e00
ffffd001`36c8a920 ffffe000`561c3dd0 : fffff800`e4e63ea4 00000000`00000000 00000000`00000b64 ffffe000`561c3dc0 : SYMEVENT64x86+0x3d67
ffffd001`36c8a928 fffff800`e4e63ea4 : 00000000`00000000 00000000`00000b64 ffffe000`561c3dc0 fffff800`e4e63827 : 0xffffe000`561c3dd0
ffffd001`36c8a930 00000000`00000000 : 00000000`00000b64 ffffe000`561c3dc0 fffff800`e4e63827 fffff800`e4e7d9d8 : SYMEVENT64x86+0x3ea4


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  d43954b4fe0cc280da9252bebcc65f7811ea5388

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  73aa2ab71b107c86fd24f24bb33c47dfce3eec75

THREAD_SHA1_HASH_MOD:  87e6d8e07dcbef41d62e94700c2dd5861bc96d11

FOLLOWUP_IP:
SYMEVENT64x86+9aef
fffff800`e4e69aef ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  SYMEVENT64x86+9aef

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SYMEVENT64x86

IMAGE_NAME:  SYMEVENT64x86.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  54bd88ac

BUCKET_ID_FUNC_OFFSET:  9aef

FAILURE_BUCKET_ID:  0xc2_7_SYMEVENT64x86!Unknown_Function

BUCKET_ID:  0xc2_7_SYMEVENT64x86!Unknown_Function

PRIMARY_PROBLEM_CLASS:  0xc2_7_SYMEVENT64x86!Unknown_Function

TARGET_TIME:  2016-06-13T00:48:56.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-04-23 00:04:21

BUILDDATESTAMP_STR:  160422-1850

BUILDLAB_STR:  th2_release_sec

BUILDOSVER_STR:  10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: 4ada

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc2_7_symevent64x86!unknown_function

FAILURE_ID_HASH:  {cc36a976-f8a4-3bf5-436f-04424a53de13}

回复

好评0

Re: BAD_POOL_CALLER BSOD caused by nis.exe on Windows 10

Have you considered reinstalling Norton?  Upgrading the OS has been known to corrupt Norton so I suggest you download and run the Norton Remove and Reinstall Tool.  This will uninstall your copy saving your settings and reinstall a fresh new activated copy of NIS.  Be sure you read the Before you begin section.  Once your new copy is installed, remember to run Live Update, restarting where required, until no more updates are available.

Please let us know how you get on.

Thanks.

Windows 10 x64 1903
好评0

Re: BAD_POOL_CALLER BSOD caused by nis.exe on Windows 10

Hello

I just want to ask 1 question. When you upgraded to Windows 19. did you reinstall NIS?

Success always occurs in private and failure in full view. Windows 10 Pro 64 bit Norton Core Security Plus 22.19.8.65 Core Firmware 282 Chrome latest version.

This thread is closed from further comment. Please visit the forum to start a new thread.