BSOD - ntoskrnl.exe & ntkrnlmp.exe

Hi, I've recently been getting multiple BSOD errors cause by the following modules ntoskrnl.exe and ntkrnlmp.exe

Here is a WhoChrased report:

On Thu 2017-08-03 1:33:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\080317-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x139 (0x3, 0xFFFFB00124994DB0, 0xFFFFB00124994D08, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2017-08-03 1:33:12 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFB00124994DB0, 0xFFFFB00124994D08, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2017-08-03 1:22:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\080317-9203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF3F7F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802DD579F7F, 0xFFFFD4806A368698, 0xFFFFD4806A367ED0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2017-08-03 1:16:46 PM your computer crashed
crash dump file: C:\Windows\Minidump\080317-6843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x50 (0xFFFFCC019AA9D068, 0x0, 0xFFFFF802EED3CBF3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2017-08-03 1:06:29 PM your computer crashed
crash dump file: C:\Windows\Minidump\080317-12078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801A3B08D00, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

One of your mini-dumps showed the graphics driver might be need updating:

Code:

fffff801`a585a688  fffff801`a9d80bf4*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0xb0bf4

The driver is atikmdag.sys Tue Apr 25 02:11:16 2017
Please update the AMD drivers. The best way to do this is to uninstall everything of AMD using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the AMD website. When you do this be sure the "clean install" box is checked and only install the Graphics driver.

philc43 said:

One of your mini-dumps showed the graphics driver might be need updating:

Code:

fffff801`a585a688  fffff801`a9d80bf4*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0xb0bf4

The driver is atikmdag.sys Tue Apr 25 02:11:16 2017
Please update the AMD drivers. The best way to do this is to uninstall everything of AMD using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the AMD website. When you do this be sure the "clean install" box is checked and only install the Graphics driver.

I tried doing this yesterday and installed new drivers but the problem seems to still be happening

I'm currently running memtest and i'm receiving some errors , could this be causing the issue?

Yes, if you are getting any errors in Memtest86 then your RAM is faulty and you can stop the current test. In some cases it can be the motherboard slot so to confirm you can repeat the testing with just one memory stick at a time in different slots to find out which stick or which slot is faulty. In most cases it is a faulty stick.

Okay i'll go ahead and try this out, thanks!

Yup one of my sticks were faulty, thanks for the help!