Windows 10: Random BSOD when gaming "BAD POOL HEADER" Solved

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 10,695
    Windows 10 Pro and Windows 10 Pro Insider
       31 Jul 2015 #11

    OK, but you didn't use the link I posted in my instructions. It does make a big difference in which test, but we'll just wait. Was it still running when you took that screenshot? It says pass 1/4. I see the wall time is 12 hours though. If you will, the next BSOD you have, please run the BSOD Posting Instructiona again and I'll see what it says. BSOD - Posting Instructions

    Also, please fill out your system specs in as much detail as possible. Please give manufacturer and Model for every component you have and the version of Windows 10 you are running. If you would like to know what we would like, at the bottom left of this post, click 'My System Specs' and see mine. Please include your PSU and CPU Cooler. This may help. System Specs - Fill in at Ten Forums
      My ComputersSystem Spec

  2.    31 Jul 2015 #12

    Yes, it was still running. I guess it only stops once I press esc like you said, and will do regarding the next bsod
      My ComputerSystem Spec

  3.    31 Jul 2015 #13

    I'll run the one that you suggested earlier, and post the results
      My ComputerSystem Spec

  4. Posts : 10,695
    Windows 10 Pro and Windows 10 Pro Insider
       31 Jul 2015 #14

    You may want to wait. You only had 1 dump file. So, it could have just been a one time thing that will not happen again. Plus it is easier to get a picture of what is happening with several dump files. So, it's up to you, but the dump file clearly states it was memory corruption. Then again, it wouldn't be the first time a dump file blamed the wrong thing.
      My ComputersSystem Spec

  5.    31 Jul 2015 #15

    Would it be helpful if I linked you to my post from sevenforum regarding my previous BSODs on it?

    If so, then here you go

    Constant BSOD's on my desktop after getting a new gpu - Windows 7 Help Forums
      My ComputerSystem Spec

  6. Posts : 10,695
    Windows 10 Pro and Windows 10 Pro Insider
       31 Jul 2015 #16

    Thanks for the link. Sorry you didn't get any help. The info you posted does not help much. We get most of our information from the info in the BSOD Posting Instructions. What it did tell me was that you had a whole lot different of error codes blaming several different things. That usually means something else is wrong. Typically errors should be the same with the same cause. It is unusual for there to be numerous problems all at once. It is usually 1 error and 1 problem. The 2 most prevalent things that will do that, it looks like to me, is that can be caused by bad Ram or a bad hard drive. That is the typical results. When Ram throws an error, whatever driver is most in use crashes and that is what the error reporting picks up. Basically the same with a Hard Drive. When the hard drive is called upon to provide drivers or data but doesn't respond, the driver called for gets the blame. I hope that is understandable. It is also the reason that several dump files together gives us a better understanding on what the problem is. It is also, from a Debugging perspective, why bad ram is the worst problem you can have. It causes all of the dump files to be unreliable.

    No test is 100% accurate. But in ram testing, the link I gave is the best one. It is what I use if I think I have ram errors. It is pretty much the 'Gold Standard' for memory tests. There is a big difference between memtest86 and memtest86+. I believe for most hardware people, memtest86+ is the only test they trust. But, even that is not 100% accurate. I hope that explains it a little. There is a lot of 'intuition' that happens when analyzing dump files.
      My ComputersSystem Spec

  7.    31 Jul 2015 #17

    Yeah, that explains it thanks. I'll run the one that you linked me too earlier, and hopefully it has something to do with the ram otherwise it's going to be a pain in the ass to continue digging to try and find the culprit. I'll update you on the results, for now I'll try to see if I can get the old minidump files
      My ComputerSystem Spec

  •    31 Jul 2015 #18

    It seems like the old windows files didn't get deleted in case you want to roll back using the windows 10 feature. Here's the old dumps
      My ComputerSystem Spec

  • Posts : 10,695
    Windows 10 Pro and Windows 10 Pro Insider
       31 Jul 2015 #19

    I looked at them and this is what I found

    Use !analyze -v to get detailed debugging information.
    BugCheck 1E, {ffffffffc0000005, fffff880010fb039, 0, ffffffffffffffff}
    *** WARNING: Unable to verify timestamp for BHDrvx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
    Probably caused by : BHDrvx64.sys ( BHDrvx64+a8aa0 )
    Followup: MachineOwner

    Norton, a known cause of BSODs

    [CODE]fffff880`033d3018 fffff880`112a288bUnable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

    Graphics driver/CODE]

    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, fffff880045df418, fffff8800317f588, fffff8800317ede0}
    Probably caused by : Ironx64.SYS ( Ironx64+32418 )
    Followup: MachineOwner
    Norton/symantec. again

    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff8801120196c, fffff8800aaf4bd0, 0}
    Probably caused by : dxgmms1.sys ( dxgmms1!VidMmDestroyAllocation+2c )
    Followup: MachineOwner
    DirectX but usually caused by Graphics

    An exception happened while executing a system service routine.
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff800032477bf, Address of the instruction which caused the bugcheck
    Arg3: fffff88008d66bb0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    PROCESS_NAME:  aces.exe
    War Thunder

    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
    Followup: MachineOwnerUse !analyze -v to get detailed debugging information.
    BugCheck 50, {fffff707ece7f048, 0, fffff80003288233, 5}

    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
    Followup: MachineOwner
    Remove Norton then use the Norton Removal Utility Replace it with
    Microsoft Security Essentials (

    Reinstall your graphics drivers. I will give you some information to try to give you a good clean install. Only install the Graphics driver and nothing else.

    I am going to give you some links that will help you get a good clean install and not have any drivers you don't need that will conflict with other drivers. Download a WHQL driver from . Once you have them downloaded, uninstall you current driver from control panel. next clean up any left over drivers from following this tutorial and select only ATI Display Drivers. After you have done that and rebooted, install the new driver, only select custom install and install only what you have to. Very few people need most of what they include. You do not need the audio/HDMI drivers as you already have that in your Motherboard drivers. Unless there is some reason you need them, the only thing you really need is the Display Driver.
      My ComputersSystem Spec

  •    31 Jul 2015 #20

    Alright, will do that in a bit but do you want me to stop using Norton completely?

    Edit: It's just extremely weird that I haven't had any BSOD's since I've changed my gpu back in May
      My ComputerSystem Spec

    Page 2 of 4 FirstFirst 1234 LastLast

    Related Threads
    Is there any way to delete these system folders. I don't use them, and I never will. If I delete them though, they are simply re-created. Thanks
    Hi In Windows 10, how I do not display the "Life at a glance" and "Play and explore" columns of the Start menu? Thanks Bye
    Hi, as with many I have upgraded to Windows 10 today and it is going well except for the fact I am unable to save any files or create new ones in the Documents and Pictures folders or any sub-folders within these folders, and I have no idea why it...
    I've installed Build 10041 and upgrade to 10049 three times now, each time I was able to do a search for Windows Update or Sound which would show me the correct results but this time, I'm not getting the right results. In the past I would do a Reset...
    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 19:45.
    Find Us