Hi,
I turned on my PC this morning and got a BSOD with the message Critical Process Died. Naturally I ran BlueScreenView which generated a handy text file that showed me what driver was causing the problem. However, I can't quite understand what it says. It seems to be related to a certain nt kernel file but I am not too sure. The dump file contents are as below, and it would be lovely if anyone could help with decoding the contents.
I ran sfc/scannow but there were no integrity violations.
I also ran my Norton 360 AV but it detected no severe viruses.
==================================================
Dump File : 072716-19375-01.dmp
Crash Time : 7/27/2016 9:09:23 AM
Bug Check String : CRITICAL_PROCESS_DIED
Bug Check Code : 0x000000ef
Parameter 1 : ffffe000`c4b5b840
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+142940
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10586.494 (th2_release_sec.160630-1736)
Processor : x64
Crash Address : ntoskrnl.exe+142940
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\072716-19375-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 10586
Dump File Size : 304,964
Dump File Time : 7/27/2016 9:10:19 AM
==================================================
As well as running BlueScreenView, I decided to run WinDbg in order to get more details. This was what it generated. Hopefully it will be helpful.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe000c4b5b840, 0, 0, 0}
ETW minidump data unavailable
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+a4 )
********************************************************************************
I also ran the !analyze -v to get more details. Should you require them, do tell me. It seems a bit of an eye sore to post it in a single post that's already long enough.
Thanks!
My PC Specs:
PSU: Corsair 750W
MB: ASUS Z97-Pro
CPU: Intel i5-4690K @ 3.50Ghz (no overclock)
GPU: Palit GTX 1080
Memory: 2x Kingston HyperX DDR3 1600Mhz 4GB (Total of 8GB)
Windows 10 x64
Hard Drives: SSD - Samsung EVO 850, 250GB
HDD - Western Digital 1TB
I turned on my PC this morning and got a BSOD with the message Critical Process Died. Naturally I ran BlueScreenView which generated a handy text file that showed me what driver was causing the problem. However, I can't quite understand what it says. It seems to be related to a certain nt kernel file but I am not too sure. The dump file contents are as below, and it would be lovely if anyone could help with decoding the contents.
I ran sfc/scannow but there were no integrity violations.
I also ran my Norton 360 AV but it detected no severe viruses.
==================================================
Dump File : 072716-19375-01.dmp
Crash Time : 7/27/2016 9:09:23 AM
Bug Check String : CRITICAL_PROCESS_DIED
Bug Check Code : 0x000000ef
Parameter 1 : ffffe000`c4b5b840
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+142940
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10586.494 (th2_release_sec.160630-1736)
Processor : x64
Crash Address : ntoskrnl.exe+142940
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\072716-19375-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 10586
Dump File Size : 304,964
Dump File Time : 7/27/2016 9:10:19 AM
==================================================
As well as running BlueScreenView, I decided to run WinDbg in order to get more details. This was what it generated. Hopefully it will be helpful.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe000c4b5b840, 0, 0, 0}
ETW minidump data unavailable
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+a4 )
********************************************************************************
I also ran the !analyze -v to get more details. Should you require them, do tell me. It seems a bit of an eye sore to post it in a single post that's already long enough.
Thanks!
My PC Specs:
PSU: Corsair 750W
MB: ASUS Z97-Pro
CPU: Intel i5-4690K @ 3.50Ghz (no overclock)
GPU: Palit GTX 1080
Memory: 2x Kingston HyperX DDR3 1600Mhz 4GB (Total of 8GB)
Windows 10 x64
Hard Drives: SSD - Samsung EVO 850, 250GB
HDD - Western Digital 1TB
Facebook
Twitter
Instagram