ntoskrnl.exe BSOD with clean memtest

chuckado

Distinguished
Mar 7, 2011
41
0
18,530
Hello, I have started receiving different blue screens over the past week that seem to be caused by ntoskrnl.exe. Everything I have read points to a memory issue, so I let a memtest run over night with no errors. I have removed my overclock and the issue continues. Temperature on my machine is fine as well. Any advice would be appreciated. My part list is as follows:
Gigabyte Z170 Gaming 7
Core i5-6600k
Samsung Evo 850 500gb
EVGA 650W PSU
EVGA GTX 1080 SC
Corsair Vengeance LPX 16GB (4 x 4GB) DDR4 2800MHz
Scythe Cooling Motherboard SCKTT-1000 CPU fan
 
Solution
sometime these issues maybe harddrive ? I fought things like this and found the hard drive was corrupting things cant hurt to test it

heres a list of what can be

http://www.computerhope.com/issues/ch000646.htm

http://www.tenforums.com/bsod-crashes-debugging/20414-having-randons-bsod-caused-ntoskrnl-exe.html

could be anything bad driver or any hardware one time for it was the motherboards ''gimmicware'' like asus suite or some fast boot or utility thing , malware program .

may look and act as a memory issue, but it can be far from it

''In most cases ntoskrnl.exe was blamed because a driver (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own. When this...
sometime these issues maybe harddrive ? I fought things like this and found the hard drive was corrupting things cant hurt to test it

heres a list of what can be

http://www.computerhope.com/issues/ch000646.htm

http://www.tenforums.com/bsod-crashes-debugging/20414-having-randons-bsod-caused-ntoskrnl-exe.html

could be anything bad driver or any hardware one time for it was the motherboards ''gimmicware'' like asus suite or some fast boot or utility thing , malware program .

may look and act as a memory issue, but it can be far from it

''In most cases ntoskrnl.exe was blamed because a driver (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own. When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space. At this point the OS panics and throws a BSOD to prevent damage to the system.''

http://www.bleepingcomputer.com/forums/t/621544/multiple-bsod-errors-mostly-related-to-ntoskrnlexe-error/

anything that calls on the memory can do the same you memory maybe great but something could be utilizing it incorrect

http://www.tenforums.com/bsod-crashes-debugging/64748-random-bsods-ntoskrnl-exe-driver-related-2.html
 
Solution