2 Recurring BSODs on new computer: Kernal Security Check Failure and Bad Pool Header RRS feed

  • Question

  • Hi there,

    Based on the following thread, I've uploaded my minidumps to onedrive.

    Can you please look at the dumps in this folder and help me figure out how to stop the random BSODs?!337&authkey=!AM7PYjAOTtVb2Yw&ithint=folder%2cdmp

    I'm running a 1-week old HP Spectre x360 with what seems to be McAffee LiveSafe pre-loaded. Windows Defender seems to be disabled.

    Below is a copy paste of my system info:

    OS Name Microsoft Windows 10 Home
    Version 10.0.10240 Build 10240
    Other OS Description Not Available
    OS Manufacturer Microsoft Corporation
    System Name ENOCH
    System Manufacturer HP
    System Model HP Spectre x360 Convertible
    System Type x64-based PC
    System SKU K3D89EA#ABU
    Processor Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400 Mhz, 2 Core(s), 4 Logical Processor(s)
    BIOS Version/Date American Megatrends Inc. F.2A, 18/09/2015
    SMBIOS Version 2.8
    Embedded Controller Version 33.16
    BIOS Mode UEFI
    BaseBoard Manufacturer HP
    BaseBoard Model Not Available
    BaseBoard Name Base Board
    Platform Role Mobile
    Secure Boot State On
    PCR7 Configuration Elevation Required to View
    Windows Directory C:\windows
    System Directory C:\windows\system32
    Boot Device \Device\HarddiskVolume1
    Locale United Kingdom
    Hardware Abstraction Layer Version = "10.0.10240.16392"
    Username ENOCH\Jan
    Time Zone GMT Standard Time
    Installed Physical Memory (RAM) 8.00 GB
    Total Physical Memory 7.91 GB
    Available Physical Memory 4.82 GB
    Total Virtual Memory 9.16 GB
    Available Virtual Memory 5.69 GB
    Page File Space 1.25 GB
    Page File C:\pagefile.sys
    Hyper-V - VM Monitor Mode Extensions Yes
    Hyper-V - Second Level Address Translation Extensions Yes
    Hyper-V - Virtualisation Enabled in Firmware No
    Hyper-V - Data Execution Protection Yes

    Thursday, November 12, 2015 9:21 AM


  • These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.

    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!!  If you do not know what this means you probably are not

    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)

    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Thursday, November 12, 2015 11:03 AM