Solved BSOD BAD_POOL_HEADER - Crashes after new mb, cpu and ram and Windows

[CrispyTheGoat]

Hi All,

This is my first post so sorry for any mistakes.

So the background information is this. I have installed a new motherboard, RAM and CPU (See PC specs below) and the reinstall of Windows 7 64-bit on my SSD went rather well. However I then started getting BSODs after installing most of my drivers and software. I get the error message BAD_POOL_HEADER. I have attached a .txt document with the BlueScreen Viewer which I believe shows dump files? I have also attached the DM Log Collector .zip file. I cannot find anything obvious in event viewer around the time these crashes happen. There is no particular pattern as to when these happen, however the one thing I am sure of is that I do not get them when in safe mode. I have run Windows Memory Diagnostic and the sfc /scannow command which brought back no issues or missing files.

Case: Zalman Z11 Plus Mid Tower
Motherboard: Asus P8P67-PRO Rev 3.1 (New Board) / Asus P6T Deluxe V2 (Old Board)
CPU: i7-3770k 3.5GHz (New) / I7-920 2.67GHz (Old)
RAM: Kingston HyperX Genesis DDR3 1600MHz 16GB (New) / Integral DDR3 1060MHz 8GB (Old)
Graphics Card: EVGA 750Ti FTW 2GB with ACX 2.0 Cooling
Power Supply: Corsair 750 Non-modular 750W

Any suggestions or help in resolving this issue is greatly appreciated. Thanks in advance for taking your time to read this.
Attached Files

 

[Arc]

Dumps are not showing anything precisely, but as all of them are showing MBAM running in the background, I would suggest you to uninstall MBAM and then reinstall a fresh copy.

https://support.malwarebytes.org/customer/portal/articles/1835311?b_id=6438

See how it goes. Let us know.
_________________________________________________

BugCheck 19, {20, fffffa8011044280, fffffa80110442e0, 4060009}

GetPointerFromAddress: unable to read from fffff800032c90e8
GetUlongFromAddress: unable to read from fffff800032c9198
GetUlongFromAddress: unable to read from fffff80003236210
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

6: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8011044280, The pool entry we were looking for within the page.
Arg3: fffffa80110442e0, The next pool entry.
Arg4: 0000000004060009, (reserved)

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

GetUlongFromAddress: unable to read from fffff80003236210

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  fffffa8011044280 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  mbamservice.ex

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

BUCKET_ID:  INVALID_KERNEL_CONTEXT

FAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXT

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:invalid_kernel_context

FAILURE_ID_HASH:  {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}

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

 

[CrispyTheGoat]

Hiya, Apologies for not replying or letting you all know sooner. I have since resolved the issue. I believe the issue was the pool header was corrupt which was caused by using the drivers from the disk as opposed to using the latest ones from the Asus website. I re-installed Windows using the most up to date drivers and I have not had a problem since.

Thank you all for your time.