Random BSOD when gaming "BAD POOL HEADER"

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

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.

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.

I looked at them and this is what I found

Code:

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
atikmdag+0x2988b[

Graphics driver/CODE]

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

Code:

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

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
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.
 
USTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  aces.exe
CURRENT_IRQL:  0

War Thunder

Code:

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}

Code:

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
Followup: MachineOwner

Remove Norton then use the Norton Removal Utility https://support.norton.com/sp/en/us/...rProfile_en_us Replace it with
Microsoft Security Essentials (http://windows.microsoft.com/en-US/w...tials-download)

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 http://www.sevenforums.com/graphic-c...ndows-7-a.html . Once you have them downloaded, uninstall you current driver from control panel. next clean up any left over drivers from following this tutorial http://www.sevenforums.com/tutorials...nstalling.html 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.