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

  1. Posts : 1
    WIndows 10 Home 64 bit
       10 Sep 2016 #1

    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

    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                                    *
    *                                                                             *
    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.
    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
    PROCESS_NAME:  MicrosoftEdgeC
    LAST_CONTROL_TRANSFER:  from fffff8000a4d4dfb to fffff8000a3d1f90
    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::DestroyDevice+0x177
    ffffa681`190bf770 fffff800`548cc141 : ffffcd02`4ec47010 ffffa681`190bf830 00000000`00000001 ffffcd02`4ec47010 : dxgkrnl!DXGDEVICE::DestroyAllDeviceState+0x15f
    ffffa681`190bf7b0 fffff800`548cc230 : ffffcd02`4ec47010 ffffcd02`4ec47010 ffffcd02`4ec47010 ffffe087`c93d63f0 : dxgkrnl!ADAPTER_RENDER::DestroyDevice+0xb1
    ffffa681`190bf7e0 fffff800`548cc2d6 : ffffcd02`4ec47010 ffffe087`00000001 ffffcd02`4ec47010 ffffa681`190bf948 : dxgkrnl!ADAPTER_RENDER::DestroyDeviceNoLocksInternal+0x70
    ffffa681`190bf8a0 fffff800`5482b060 : ffffcd02`4ec47010 ffffa681`190bf940 00000000`00000000 00000128`9ce05501 : dxgkrnl!ADAPTER_RENDER::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
    dxgkrnl!operator delete+11
    fffff800`548999a1 4883c428        add     rsp,28h
    SYMBOL_NAME:  dxgkrnl!operator delete+11
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dxgkrnl
    IMAGE_NAME:  dxgkrnl.sys
    FAILURE_BUCKET_ID:  X64_0x19_25_dxgkrnl!operator_delete+11
    BUCKET_ID:  X64_0x19_25_dxgkrnl!operator_delete+11
    Followup: MachineOwner
    Last edited by Brink; 10 Sep 2016 at 17:51. Reason: code box
      My ComputerSystem Spec

  2.   My ComputersSystem Spec


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...
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.
Hi, After upgrading to windows 10 pro from windows 7 pro I randomly get BSOD bad pool header. I've attached the zip file. Any help would be appreciated. Thanks!
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:32.
Find Us