Windows 10: Ongoing BSOD Issues - BAD POOL HEADER Solved

Page 1 of 2 12 LastLast
  1.    07 Sep 2016 #1

    Ongoing BSOD Issues - BAD POOL HEADER


    Hi.

    I have been experiencing BSOD on a fairly regular basis. They seem to occur randomly, usually at least once a week.

    I am running Windows 10 on a HP Spectre X360.

    The DM log collector file is attached.

    Any help on how to solve it would be much appreciated.

    Thanks
    Dominic
      My ComputerSystem Spec


  2. Posts : 5,007
    Windows 10 Pro X64 15063.138
       08 Sep 2016 #2

    Looks like you are over clicking your PC a bit:

    Code:
    3: kd> !sysinfo cpuspeed
    CPUID:        "Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz"
    MaxSpeed:     2300
    CurrentSpeed: 2400
    Please set all clocks and voltages to normal, see if that makes any difference.

    Also noticed you have some very old (2011) drivers from SuperAntiSpyware. Plese uninstall it, see if that helps.
      My ComputersSystem Spec

  3.    08 Sep 2016 #3

    Thanks for the response.

    I havent done any overclocking myself, if it is high it has automatically done that. I had a quick look and couldn't find anywhere to change it in the bios.
    I uninstalled superantispyware, but an hour or so later I got another BSOD (same bad pool header code). The latest dm log is attached.
    Attachment 100510
      My ComputerSystem Spec


  4. Posts : 11,525
    Windows 10 Pro
       09 Sep 2016 #4

    Hi dominics.

    My apologies for bumping in, but I'm posting to clarify the 'overclock' a bit.

    Per the information provided by Intel it isn' an overclock, the CPU has a max frequency range of 2.8GHz.
    This means that the CPU will perform with a frequency between 2.3GHz and 2.8GHz without any change in the BIOS or software, to add any overclock method is usually not possible with laptops.
      My ComputersSystem Spec


  5. Posts : 5,007
    Windows 10 Pro X64 15063.138
       10 Sep 2016 #5

    Thanks for the info @axe0.
      My ComputersSystem Spec


  6. Posts : 5,007
    Windows 10 Pro X64 15063.138
       10 Sep 2016 #6

    The latest dump indicates a problem with tdx.sys which is a Microsoft driver.
    Code:
    BugCheck 19, {3, ffffc2870d6c9750, 0, ffffc2870d6c9750}
    
    *** WARNING: Unable to verify timestamp for tdx.sys
    *** ERROR: Module load completed but symbols could not be loaded for tdx.sys
    Probably caused by : tdx.sys ( tdx+6dbd )
    Try updating the driver for your Intel® Dual Band Wireless-AC 7265 device. There is a 8/3/2016 update available. The one you have now is dated 2/26/16: Drivers & Software
      My ComputersSystem Spec

  7.    11 Sep 2016 #7

    I've installed the update and I'll let you know how it goes over the next couple of days.

    Thanks
      My ComputerSystem Spec

  8.    12 Sep 2016 #8

    Had another BSOD just now, log file attached.
    Attachment 101022
      My ComputerSystem Spec


  9. Posts : 5,007
    Windows 10 Pro X64 15063.138
       12 Sep 2016 #9

    Something is going on but I don't know what the cause is. Got the following errors in windbg:

    Code:
    ffffcc00`88a9b040  fffff802`d468e8a0Unable to load image \??\C:\WINDOWS\system32\drivers\mwac.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mwac.sys
    *** ERROR: Module load completed but symbols could not be loaded for mwac.sys
    This belongs to MBAMWebAccessControl. Uninstall it and see if that helps.

    Code:
    ffffcc00`88a9c908  fffff802`d4b09c4cUnable to load image \SystemRoot\System32\drivers\Netwtw04.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Netwtw04.sys
    *** ERROR: Module load completed but symbols could not be loaded for Netwtw04.sys
     Netwtw04+0x109c4c
    This belongs to Intel(R) Wireless Adapter. Not sure what to do here as you have the latest driver available.

    Code:
    ffffcc00`88a9dbf8  fffff802`ce2bf9a0Unable to load image \SystemRoot\system32\drivers\networx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for networx.sys
    *** ERROR: Module load completed but symbols could not be loaded for networx.sys
     networx+0xf9a0
    Description: Networx.sys is not essential for Windows and will often cause problems. Networx.sys is located in the C:\Windows\System32\drivers folder.
    The driver can be started or stopped from Services in the Control Panel or by other programs. The program is not visible. The file is certified by a trustworthy company. The service has no detailed description. The networx.sys file is not a Windows core file. networx.sys appears to be a compressed file.

    You can try stopping it in Services, see if that helps. I just checked and I don't have it on my computer.
      My ComputersSystem Spec

  10.    12 Sep 2016 #10

    Hi have uninstalled Networx, if I get another BSOD i'll uninstall malwarebytes.
    I'll let you know how it goes.
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
BSOD, Bad Pool Header in BSOD Crashes and Debugging
Acer Aspire ES1-711-P14W with Windows 10. I had Windows 10 since Insiders builds and a few weeks ago it started BSODing frequently, mainly DPC_WATCHDOG_VIOLATION and BAD_POOL_HEADER, I thought a reinstall would fix the issue but it didn't, I still...
4th BSOD Bad Pool Header in the last hour in BSOD Crashes and Debugging
I am fairly new at this troubleshooting but I did follow all the steps you provided. Attached is the requested file. Thank you in advance for all your help.
Solved BSOD - Bad Pool Header in BSOD Crashes and Debugging
I've tested the memory with memtest86, uninstalled recently installed software and updated my drivers with driver reviver. these were the recommendations on other forums and i'm unsure what else i can do to try and fix this. i tried to upload my...
BSOD Bad pool header in BSOD Crashes and Debugging
I Received the error, A problem has been detected and Windows has been shut down to prevent damage to your computer. BAD_POOL_HEADER Technical Information: *** STOP: 0x00000019
BSOD Bad Pool Header in BSOD Crashes and Debugging
Since upgrading to Windows 10 from Windows 7, my computer would crash once a day with a bad pool header notification. I have tried everything I can think of to resolve this issue, and am coming here as a last resort. Below is my DM Log Collector zip.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:00.
Find Us