I have received a BSDO just now.
Using the WhoCrashed software, I believe the error is caused by either ntoskrnl.exe or ntkrnlmp.exe
These two .exe has bugged my pc a lot, giving some BSOD like, System Thread Exception Not Handled. etc. I have tried to solve it like running sfc/scannow , run windows defender offline, perform Windows Update, even disable fast startup, yet this problem happens
occasionally.
This is the minidump file:
https://1drv.ms/u/s!AuDdpDNqFagDlyzAHi2jEk1o3w_5
From WhoCrashed:
System Information (local)
Computer name: DESKTOP-B9K34PR
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\Windows
Hardware: Aspire A515-51G, Acer, KBL, Charmander_KL
CPU: GenuineIntel Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8459489280 bytes total
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sat 10/2/2018 7:20:08 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021018-9000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175880)
Bugcheck code: 0x1C7 (0x0, 0xFFFFDB8E42641000, 0x650C5740, 0x1F370)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 10/2/2018 7:20:08 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!SeConvertSidToStringSid+0x11BA6)
Bugcheck code: 0x1C7 (0x0, 0xFFFFDB8E42641000, 0x650C5740, 0x1F370)
Error: CUSTOM_ERROR
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
2 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.
