BSOD error 0x000000ef and ntoskrnl.exe

[KyleWard38]

Like the title says, I am getting a BSOD CRITICAL_PROCESS_DIED error that has something to do with the ntoskrnl.exe driver. This has happened twice, last week and today, and just before the most recent time the Windows explorer process froze up for 10-20 seconds and I couldn't really do anything. It unfroze on it's own, and I was able to continue using the computer for a minute or two normally before the BSOD occured. I believe this happened before the first error as well but I am not sure if I remember correctly. System and crash info is below, if any other information I can provide might help please let me know. Any and all help is appreciated and thanks in advance!

--------------------
SYSTEM INFO
--------------------
OS: Windows 10 Home 64-bit 10.0.14393.0
Processor: Intel i7 965 @ 3.20ghz
Display info: Nvidia GeForce GTX 780
RAM: 24GB
Motherboard: Gigabyte EX58-UD4P
Bios version: 2.4

--------------------------
LAST CRASH INFO
--------------------------
Dump file: 111116-37593-01.dmp
Bug check string: CRITICAL_PROCESS_DIED
Bug check code: 0x000000ef
Parameter 1: ffffd105`a7a5a080
Parameter 2: 00000000`00000000
Parameter 3: 00000000`00000000
Parameter 4: 00000000`00000000
Caused by driver: ntoskrnl.exe
Caused by address: ntoskrnl.exe+14a510
File description: NT Kernel & System
File version: 10.0.14393.447 (rs1_release_inmarket.161102-0100)
Processor: x64
Crash address: ntoskrnl.exe+14a510
Processors count: 8
Major version: 15
Minor version: 14393
Dump file size: 537,156

 

[Colif]

NTOSKRNL = NewTechnology Operating System Kernel, windows won't work without it. It often gets the blame for driver actions.

suggestions from MS

If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.

If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.

Check with the manufacturer to see if an updated system BIOS or firmware is available.

You can try running the hardware diagnostics supplied by the system manufacturer.

Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 Specifications.

Run a virus detection program. Viruses can infect all types of hard disks formatted for Windows, and resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.

Use the System File Checker tool to repair missing or corrupted system files. The System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. Use the following command to run the System File Checker tool (SFC.exe) in a command prompt with admin rights.

SFC /scannow

For more information, see Use the System File Checker tool to repair missing or corrupted system files.
Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.

Microsoft link