This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)īugcheck code: 0x154 (0xFFFFA803765C9000, 0xFFFFA70ED9FC50F0, 0x2, 0x0)īug check description: This indicates that the store component caught an unexpected exception. On Mon 16:56:42 your computer crashed or a problem was reportedĬrash dump file: C:\WINDOWS\Minidump\041320-6359-01.dmp Google query: ntdll.sys CRITICAL_PROCESS_DIED It is suggested you look for an update for the following driver: ntdll.sys. This was probably caused by the following module: ntdll.sys (ntdll!RtlLookupFunctionEntry+0x82)Ī third party driver was identified as the probable root cause of this system error.
Possibly this problem is caused by another driver that cannot be identified at this time. The crash took place in the Windows kernel. There is a possibility this problem was caused by a virus or other malware. Product: Microsoft® Windows® Operating Systemīug check description: This indicates that a critical system process died. This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)īugcheck code: 0圎F (0xFFFF968870E59380, 0x0, 0x0, 0x0)įile path: C:\WINDOWS\system32\ntoskrnl.exe On Sun 12:15:07 your computer crashed or a problem was reportedĬrash dump file: C:\WINDOWS\Minidump\041920-6843-01.dmp Windows version: Windows 10, 10.0, build: 18363ĬPU: GenuineIntel Intel(R) Core(TM) i9-7940X CPU 3.10GHz Intel8664, level: 6Ģ8 logical processors, active mask: 268435455Ĭrash dumps are enabled on your computer. It has only crashed once, less than a minute after starting a very high intensity test of everything, including the C drive (this was the April 13 crash shown in the WhoCrashed report below.) It subsequently ran the same battery of tests but targeting the D drive without any issue. I have run various load tests on the PC fairly using BurnInTest V9.1 Pro, including some which push it much harder than normal use. The calculator at suggested I need about 550W.
0 kommentar(er)
