ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Proliant 380e G8 BSOD

 
karolOSW
Visitor

Proliant 380e G8 BSOD

PLz Help me  I am getting a constantly occurring BSOD  "BAD_POOL_HEADER " on a Windows 2012R2 server

I upgrade all drivers from  

Service Pack for ProLiant (SPP) Version 2016.10.0 and one day was OK

this is my dmp file


Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\\122116-44718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 9200.17581.amd64fre.win8_gdr.151112-0600
Machine Name:
Kernel base = 0xfffff800`98801000 PsLoadedModuleList = 0xfffff800`98acdae0
Debug session time: Wed Dec 21 11:16:06.128 2016 (UTC + 1:00)
System Uptime: 0 days 0:01:42.887
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {21, fffff8a004de7000, 13b0, 40000000500}

*** WARNING: Unable to verify timestamp for MxG2hDO64.sys
*** ERROR: Module load completed but symbols could not be loaded for MxG2hDO64.sys
Probably caused by : MxG2hDO64.sys ( MxG2hDO64+51676 )

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

1: kd> 
1: kd> 
1: kd> 
1: kd> 
1: kd> 
1: 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: 0000000000000021, the data following the pool block being freed is corrupt.  Typically this means the consumer (call stack ) has overrun the block.
Arg2: fffff8a004de7000, The pool pointer being freed.
Arg3: 00000000000013b0, The number of bytes allocated for the pool block.
Arg4: 0000040000000500, The corrupted value found following the pool block.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  6.2.9200.17581 (win8_gdr.151112-0600)

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  ProLiant DL380e Gen8

SYSTEM_SKU:  669253-B21      

BIOS_VENDOR:  HP

BIOS_VERSION:  P73

BIOS_DATE:  08/02/2014

DUMP_TYPE:  2

BUGCHECK_P1: 21

BUGCHECK_P2: fffff8a004de7000

BUGCHECK_P3: 13b0

BUGCHECK_P4: 40000000500

BUGCHECK_STR:  0x19_21

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80098b59170
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80098b59370
GetUlongPtrFromAddress: unable to read from fffff80098b59488
GetPointerFromAddress: unable to read from fffff80098b59078
 fffff8a004de7000 Paged pool

CPU_COUNT: 4

CPU_MHZ: 704

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2d

CPU_STEPPING: 7

CPU_MICROCODE: 6,2d,7,0 (F,M,S,R)  SIG: 710'00000000 (cache) 710'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  TDT-KAROL

ANALYSIS_SESSION_TIME:  12-21-2016 12:43:11.0938

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80098a738a4 to fffff8009885b240

STACK_TEXT:  
fffff880`0f63cbf8 fffff800`98a738a4 : 00000000`00000019 00000000`00000021 fffff8a0`04de7000 00000000`000013b0 : nt!KeBugCheckEx
fffff880`0f63cc00 fffff880`0c251676 : fffff8a0`04de7000 fffff8a0`04de7000 00000000`00000001 00000000`58544d44 : nt!ExDeferredFreePool+0xc9c
fffff880`0f63cce0 fffff8a0`04de7000 : fffff8a0`04de7000 00000000`00000001 00000000`58544d44 00000000`00000001 : MxG2hDO64+0x51676
fffff880`0f63cce8 fffff8a0`04de7000 : 00000000`00000001 00000000`58544d44 00000000`00000001 fffff880`0c23b8a9 : 0xfffff8a0`04de7000
fffff880`0f63ccf0 00000000`00000001 : 00000000`58544d44 00000000`00000001 fffff880`0c23b8a9 fffff8a0`feed8801 : 0xfffff8a0`04de7000
fffff880`0f63ccf8 00000000`58544d44 : 00000000`00000001 fffff880`0c23b8a9 fffff8a0`feed8801 00000000`00000000 : 0x1
fffff880`0f63cd00 00000000`00000001 : fffff880`0c23b8a9 fffff8a0`feed8801 00000000`00000000 00000000`00000000 : 0x58544d44
fffff880`0f63cd08 fffff880`0c23b8a9 : fffff8a0`feed8801 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff880`0f63cd10 fffff8a0`feed8801 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : MxG2hDO64+0x3b8a9
fffff880`0f63cd18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0c23ddff : 0xfffff8a0`feed8801


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  d93e7e508606190ce593763d0543e5735e964a33

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  1174279a56edc2ba24456bf43235758fb265eb00

THREAD_SHA1_HASH_MOD:  4232a9146b1c73ed2b8af3fca159239e0edb31a6

FOLLOWUP_IP: 
MxG2hDO64+51676
fffff880`0c251676 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  MxG2hDO64+51676

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MxG2hDO64

IMAGE_NAME:  MxG2hDO64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4fedf361

BUCKET_ID_FUNC_OFFSET:  51676

FAILURE_BUCKET_ID:  0x19_21_MxG2hDO64!unknown_function

BUCKET_ID:  0x19_21_MxG2hDO64!unknown_function

PRIMARY_PROBLEM_CLASS:  0x19_21_MxG2hDO64!unknown_function

TARGET_TIME:  2016-12-21T10:16:06.000Z

OSBUILD:  9200

OSSERVICEPACK:  17581

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  2

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8

OSEDITION:  Windows 8 LanManNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-11-12 21:06:25

BUILDDATESTAMP_STR:  151112-0600

BUILDLAB_STR:  win8_gdr

BUILDOSVER_STR:  6.2.9200.17581

ANALYSIS_SESSION_ELAPSED_TIME: 50f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x19_21_mxg2hdo64!unknown_function

FAILURE_ID_HASH:  {cb0b6dab-9351-2c20-ff5c-fc21bcade3d9}

Followup:     MachineOwner