PC constantly crashes and freezes, resulting in BSOD, CRITICAL_PROCESS_DIED, error 0x000000EF, UNEXPECTED_STORE_EXCEPTION, ntoskrnl.exe

  • Thread starter ColoringPlane17
  • Start date
C

ColoringPlane17

For the longest time my PC's been randomly freezing, which results typically in almost a dozen BSOD a day, sometimes it takes 4 hours, sometimes 4 minutes. The most common error I get is CRITICAL_PROCESS_DIED, although sometimes I also get UNEXPECTED_STORE_EXCEPTION, but that one is rarer.

Here are my PC specs:

Windows version: Windows 10 , 10.0, build: 18363
Motherboard: ASRock, Z370 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel8664, level: 6
12 logical processors, active mask: 4095
GPU: Nvidia GeForce GTX 1080
RAM: 68651618304 bytes (63,9GB)


These BSODs have been occurring for quite some time now, I've taken my desktop to two different service stations, but ultimately it still keeps dying. So far I have tried:
- sfc /scannow, which comes up clean
- chkdsk, comes up clean
- dism /online /checkhealth, comes up clean
- Windows memory diagnostic comes up clean
- updated drivers for the motherboard from the website, couldn't install 2.
- updating my graphics drivers and Windows OC.


I also ran WhoCrashed and this is what came up:


Crash Dump Analysis


Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Mon 03.02.2020 0:22:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020320-63812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xEF (0xFFFFC90B9F9A9140, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 03.02.2020 14:31:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020320-72750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xEF (0xFFFFE30E5D2DD280, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 03.02.2020 12:01:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020320-55078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x154 (0xFFFFD58EDC3DB000, 0xFFFF9F80B3C63F00, 0x2, 0x0)
Error: UNEXPECTED_STORE_EXCEPTION
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 the store component caught an unexpected exception.
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 Mon 03.02.2020 1:44:58 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020320-93578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xEF (0xFFFFCF0BB0065240, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 01.02.2020 21:45:23 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020120-59875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xEF (0xFFFFAB8AF9BAA280, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




Conclusion
5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



I also ran BlueScreenViewer and it pointed out that it's caused by 'Driver ntoskrnl.exe', which doesn't tell me much, since it's apparently not a real driver.
3bf300a6-10fe-4944-b363-34586613b6d2?upload=true.jpg

Honestly, I'm not tech-savvy at all, and don't understand most of this, so if anybody could help me out and explain it in basic terms, I'd greatly appreciate it.

Continue reading...
 

Similar threads

P
Replies
0
Views
19
P'AuanAraijawaipannan
P
O
Replies
0
Views
47
Oskar Podkaura
O
N
Replies
0
Views
33
nathan delsol
N
O
Replies
0
Views
52
Oskar Podkaura
O
Back
Top Bottom