BSOD while playing games please help!!!!

[Darthlightning]

So I built my PC last year and it was fine for the first 6 months then I started crashing/BSOD for ages but then I upgraded my cooling and it worked fine, however then it started crashing?BSOD again 6 months ago, but then fixed it 3 months ago by updating a motherboard BIOS. A few days ago the same problem has started again however they are more frequent when playing games but this time all BSOD's are casued by the same driver:

Driver caused by: ntoskrnl.exe
Casued by address: ntoskrnl.exe+72a40
Bug check String varies - Most common - IRQL_NOT_LESS_OR_EQUAL or BAD_POOL_HEADER

These will happen very frequently when playing games and are very annoying, my temps are okay as I monitor them.

Specs:
AMD FX-6300
MSI 7950 3GB OC
500GB WD HDD
8gb 1600mhz Corsair Vengeance
Hyper cooler 212 EVO
MSI 970A-G43
3 fans
600W corsair PSU

Edit:
CMD scan - No problems detected
CMD verifier - No changes/problems detected

 

[Quixit]

Try running Memtest86 to make sure it's not a problem with your RAM (which is common for random crashes)

http://www.memtest86.com/

 

[johnbl]

ntoskrnl.exe is the key core of the windows, problems in this file will be caused by hardware problems or bugs in device drivers that are making calls to ntoskrnl.exe incorrectly. IE not useful in helping to figure out your problem.

IRQL_NOT_LESS_OR_EQUAL is a common device driver problem, often because of memory corruption.
BAD_POOL_HEADER means that something has corrupted shared kernel memory.

I would start by running memtest86 to check that your physical machine works as expected.
if it works then boot windows, make sure your core windows files are not corrupted: run cmd.exe as an admin, then
run
sfc.exe /scannow

and make sure all corruptions are fixed (or none found)

if no cause of the failure is found then you have to update device drivers from your motherboard vendor, or have someone look at the memory .dmp files and see if they can see the cause of the corruption. ( or give you a list of likely drivers that cause corruption)
if you still can not find the problem you have to run cmd.exe as an admin, run
verifier.exe /standard /all

reboot and wait for the next bugcheck, verifier will force windows to check the drivers for programming errors and will bugcheck the system when it finds the first mistake. (info saved in the memory dump file)

use
verifier.exe /reset
to turn off the extra driver checking after the bugcheck or your system will run slowly until you do.

 

[Darthlightning]

ntoskrnl.exe is the key core of the windows, problems in this file will be caused by hardware problems or bugs in device drivers that are making calls to ntoskrnl.exe incorrectly. IE not useful in helping to figure out your problem.

IRQL_NOT_LESS_OR_EQUAL is a common device driver problem, often because of memory corruption.
BAD_POOL_HEADER means that something has corrupted shared kernel memory.

I would start by running memtest86 to check that your physical machine works as expected.
if it works then boot windows, make sure your core windows files are not corrupted: run cmd.exe as an admin, then
run
sfc.exe /scannow

and make sure all corruptions are fixed (or none found)

if no cause of the failure is found then you have to update device drivers from your motherboard vendor, or have someone look at the memory .dmp files and see if they can see the cause of the corruption. ( or give you a list of likely drivers that cause corruption)
if you still can not find the problem you have to run cmd.exe as an admin, run
verifier.exe /standard /all

reboot and wait for the next bugcheck, verifier will force windows to check the drivers for programming errors and will bugcheck the system when it finds the first mistake. (info saved in the memory dump file)

use
verifier.exe /reset
to turn off the extra driver checking after the bugcheck or your system will run slowly until you do.

None of its worked
Its crashed again and Ive set up crash dump files but dont know where to find them. Also the crashes are less frequent and sometimes dont even BSOD

 

[johnbl]

crash dump files have a file extension of .dmp you can search your hard drive for them.

by default mini memory dumps are stored in c:\windows\minidump directory (in a file name based on the date)
kernel memory dumps are stored in c:\windows\memory.dmp file

ntoskrnl.exe is the key core of the windows, problems in this file will be caused by hardware problems or bugs in device drivers that are making calls to ntoskrnl.exe incorrectly. IE not useful in helping to figure out your problem.

IRQL_NOT_LESS_OR_EQUAL is a common device driver problem, often because of memory corruption.
BAD_POOL_HEADER means that something has corrupted shared kernel memory.

I would start by running memtest86 to check that your physical machine works as expected.
if it works then boot windows, make sure your core windows files are not corrupted: run cmd.exe as an admin, then
run
sfc.exe /scannow

and make sure all corruptions are fixed (or none found)

if no cause of the failure is found then you have to update device drivers from your motherboard vendor, or have someone look at the memory .dmp files and see if they can see the cause of the corruption. ( or give you a list of likely drivers that cause corruption)
if you still can not find the problem you have to run cmd.exe as an admin, run
verifier.exe /standard /all

reboot and wait for the next bugcheck, verifier will force windows to check the drivers for programming errors and will bugcheck the system when it finds the first mistake. (info saved in the memory dump file)

use
verifier.exe /reset
to turn off the extra driver checking after the bugcheck or your system will run slowly until you do.

None of its worked
Its crashed again and Ive set up crash dump files but dont know where to find them. Also the crashes are less frequent and sometimes dont even BSOD