Windows 10: BSOD Bad Pool Header (19) Windows 10 Home 64 Bit

Discus and support BSOD Bad Pool Header (19) Windows 10 Home 64 Bit in Windows 10 BSOD Crashes and Debugging to solve the problem; I'm having a lot of trouble at the moment today switching from windows 7 to windows 10. More crashes has happened in the last 4 hours than the first... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Hayateazekura, Sep 10, 2016.

  1. HAYATEAZEKURA
    Hayateazekura Win User

    BSOD Bad Pool Header (19) Windows 10 Home 64 Bit


    I'm having a lot of trouble at the moment today switching from windows 7 to windows 10. More crashes has happened in the last 4 hours than the first time I used windows 95 through windows 7.
    Here is my minidump file information. I'm not sure what to do. Any help I will greatly be appreciated

    Code: Windows 8 Kernel Version 14393 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 14393.0.amd64fre.rs1_release.160715-1616 Machine Name: Kernel base = 0xfffff800`0a288000 PsLoadedModuleList = 0xfffff800`0a58d060 Debug session time: Sat Sep 10 18:03:33.541 2016 (UTC - 4:00) System Uptime: 0 days 1:15:30.158 ******************************************************************************* * * * 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: 0000000000000025, Arg2: 000000000000000c Arg3: 0000000000000005 Arg4: ffffcd024a747710 Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 BUGCHECK_STR: 0x19_25 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: MicrosoftEdgeC CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000a4d4dfb to fffff8000a3d1f90 STACK_TEXT: ffffa681`190bf598 fffff800`0a4d4dfb : 00000000`00000019 00000000`00000025 00000000`0000000c 00000000`00000005 : nt!KeBugCheckEx ffffa681`190bf5a0 fffff800`548999a1 : ffffcd02`4a747720 ffffe087`cdf83700 ffffcd02`49e3aa90 fffff800`00000003 : nt!ExAllocatePoolWithTag+0x102b ffffa681`190bf680 fffff800`5482b087 : 00000000`00000000 00000000`00000001 0000037e`a774d000 00000000`00000000 : dxgkrnl!operator delete+0x11 ffffa681`190bf6b0 fffff800`548cd387 : ffffcd02`4a747720 ffffcd02`4bfd31e0 ffffe087`cd1a2010 00000000`00000000 : dxgkrnl!DXGPROCESS_ADAPTER_INFO::`scalar deleting destructor'+0x1f ffffa681`190bf6e0 fffff800`548c30c3 : ffffe087`cde2d7d0 ffffa681`190bf830 ffffe087`d1861ee0 ffffcd02`4ec47010 : dxgkrnl!DXGPROCESS::CloseAdapter+0x83 ffffa681`190bf710 fffff800`548c8b93 : ffffcd02`4bfd31e0 ffffcd02`4ec47010 ffffe087`cd1a2010 ffffcd02`4ec47101 : dxgkrnl!DXGDEVICE:BSOD Bad Pool Header (19) Windows 10 Home 64 Bit :DestroyDevice+0x177 ffffa681`190bf770 fffff800`548cc141 : ffffcd02`4ec47010 ffffa681`190bf830 00000000`00000001 ffffcd02`4ec47010 : dxgkrnl!DXGDEVICE:BSOD Bad Pool Header (19) Windows 10 Home 64 Bit :DestroyAllDeviceState+0x15f ffffa681`190bf7b0 fffff800`548cc230 : ffffcd02`4ec47010 ffffcd02`4ec47010 ffffcd02`4ec47010 ffffe087`c93d63f0 : dxgkrnl!ADAPTER_RENDER:BSOD Bad Pool Header (19) Windows 10 Home 64 Bit :DestroyDevice+0xb1 ffffa681`190bf7e0 fffff800`548cc2d6 : ffffcd02`4ec47010 ffffe087`00000001 ffffcd02`4ec47010 ffffa681`190bf948 : dxgkrnl!ADAPTER_RENDER:BSOD Bad Pool Header (19) Windows 10 Home 64 Bit :DestroyDeviceNoLocksInternal+0x70 ffffa681`190bf8a0 fffff800`5482b060 : ffffcd02`4ec47010 ffffa681`190bf940 00000000`00000000 00000128`9ce05501 : dxgkrnl!ADAPTER_RENDER:BSOD Bad Pool Header (19) Windows 10 Home 64 Bit :DestroyDeviceNoLocks+0x7a ffffa681`190bf8d0 fffff800`548c0e8d : ffffcd02`4ec47010 ffffcd02`4ec47010 00000000`00000000 ffffcd02`4bfd31e0 : dxgkrnl!ENSURE_DEVICE_DEREFERENCE_NOLOCKS::~ENSURE_DEVICE_DEREFERENCE_NOLOCKS+0x28 ffffa681`190bf900 fffff800`0a3dcc93 : ffffe087`c93d6080 ffffe087`c93d6080 00000000`00000020 00000128`9ce08380 : dxgkrnl!DxgkDestroyDevice+0x2ad ffffa681`190bfa80 00007ff9`3c134604 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000020`530fe768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff9`3c134604 STACK_COMMAND: kb FOLLOWUP_IP: dxgkrnl!operator delete+11 fffff800`548999a1 4883c428 add rsp,28h SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgkrnl!operator delete+11 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 57899857 FAILURE_BUCKET_ID: X64_0x19_25_dxgkrnl!operator_delete+11 BUCKET_ID: X64_0x19_25_dxgkrnl!operator_delete+11 Followup: MachineOwner ---------[/quote]

    :)
     
    Hayateazekura, Sep 10, 2016
    #1
  2. ZIGZAG3143 (MS -MVP)
    ZigZag3143 (MS -MVP) Win User

    Windows 10 64 bit BSoD - Bad Pool Header

    Related to the mwac.sys Malwarebytes Web Access Control from Malwarebytes Corporation

    Completely remove the current driver (or software) and install the newest driver available. For instructions on how to do that Read all about updating drivers by my partner JMH3143 here Updating a driver.
     
    ZigZag3143 (MS -MVP), Sep 10, 2016
    #2
  3. EDISNORI
    Edisnori Win User
    Windows 10 64 bit BSoD - Bad Pool Header

    As the title says I had a Blue screen with the error Bad_Pool_header, I looked it up and causes were defective Ram and drivers from my understanding. I tested my ram and have a all clear so I would like some help narrowing down the search to which driver
    is defective.

    I uploaded the minidump file to onedrive here is the link:


    https://onedrive.live.com/redir?resid=F4F2B9A2B57AF836!922&authkey=!AMTmO0WtPuI6pGo&ithint=file,zip

    I hope I'm going in the right direction to fixing these crashes my computer has. Thanks for the time and assistance.
     
    Edisnori, Sep 10, 2016
    #3
  4. AXE0
    axe0 New Member

    BSOD Bad Pool Header (19) Windows 10 Home 64 Bit

    axe0, Sep 10, 2016
    #4
Thema:

BSOD Bad Pool Header (19) Windows 10 Home 64 Bit

Loading...

  1. BSOD Bad Pool Header (19) Windows 10 Home 64 Bit - Similar Threads - BSOD Bad Pool

  2. BSOD - Bad Pool Header

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Bad Pool Header: In the past few weeks I have been getting BSOD's rather frequently, specifically everytime I am playing a game. But this one caught my attention as the second error hinted at a malfunctioning disk. I have already tried looking for out of date drivers but have not succeeded...

  3. Bad Pool Header BSOD

    in Windows 10 Installation and Upgrade
    Bad Pool Header BSOD: I installed the Linux Bash Shell on my laptop last year. It went fine, and I was able to use it. After getting the Windows 10 April 2018 Update, I get a Bad Pool Header BSOD whenever I try to open the shell. I already tried updating my drivers (using Driver Booster 5.2),...

  4. BSOD Bad Pool Header

    in Windows 10 BSOD Crashes and Debugging
    BSOD Bad Pool Header: 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. 32179

  5. BSOD, Bad Pool Header

    in Windows 10 BSOD Crashes and Debugging
    BSOD, Bad Pool Header: 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 had 2 BSODs with the...

  6. BSOD - Bad Pool Header

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Bad Pool Header: 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 minidump folder aswell as a...

  7. BSOD Bad pool header

    in Windows 10 BSOD Crashes and Debugging
    BSOD Bad pool header: 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 Beginning dump of physical memory Physical memory dump complete. I try many...

  8. BSOD Bad Pool Header

    in Windows 10 BSOD Crashes and Debugging
    BSOD Bad Pool Header: Hello I have a Laptone Wifi Dongle and a wireless mouse dongle in my USB ports on my Dell Inspiron 1750 laptop. I have uploaded the file dumps for you. I get the BDOS screen occasionally when I am browsing on my computer. Thanks 70566

  9. Bad Pool Header

    in Windows 10 Support
    Bad Pool Header: Need to know why this error code appears and then how to fix 28108

  10. Bad Pool Header

    in Windows 10 Support
    Bad Pool Header: What is a "bad pool header". When it comes up it demands to reboot. Things will be just fine and then occasionally it will come up again and demands a reboot. Is there any "fix". What is going on, any way to fix it, to stop the process. What and why is it occurring? 21313