I don't know whats going on but i had this problem for about 2 months and still haven't found a fix. The computer would crash and boot me into the BIOS and the HDD would not appear. I got a new SSD and i still have the same problem. If you need more information just comment what you need and i can reply. (Computer 6 months old)
EDIT: when it crashes i hear a zap sound
- 8 GB RAM
- Intel Core i7-6500U
-Windows 10
-Samsung 850 Evo 250 GB SSD (new)
I used WhoCrashed and this is what it displayed
On Wed 2/22/2017 5:42:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\022217-3656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xEF (0xFFFFCE01EE0BF780, 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 Wed 2/22/2017 5:42:12 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!RtlLookupFunctionEntry+0x11A)
Bugcheck code: 0xEF (0xFFFFCE01EE0BF780, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED
On Wed 2/22/2017 5:40:31 PM your computer crashed
crash dump file: C:\Windows\Minidump\022217-3640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xEF (0xFFFFCF01AD16F780, 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 Wed 2/22/2017 5:37:55 PM your computer crashed
crash dump file: C:\Windows\Minidump\022217-3687-01.dmp
This was probably caused by the following module: filecrypt.sys (filecrypt+0xF9A0)
Bugcheck code: 0x7A (0xFFFF9006B1E31F88, 0xFFFFFFFFC000000E, 0x25CBEC860, 0xFFFFF8028FFAF9A0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\filecrypt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows sandboxing and encryption filter
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 2/22/2017 11:37:45 AM your computer crashed
crash dump file: C:\Windows\Minidump\022217-3593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xEF (0xFFFFCA028326F780, 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.
EDIT: when it crashes i hear a zap sound
- 8 GB RAM
- Intel Core i7-6500U
-Windows 10
-Samsung 850 Evo 250 GB SSD (new)
I used WhoCrashed and this is what it displayed
On Wed 2/22/2017 5:42:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\022217-3656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xEF (0xFFFFCE01EE0BF780, 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 Wed 2/22/2017 5:42:12 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!RtlLookupFunctionEntry+0x11A)
Bugcheck code: 0xEF (0xFFFFCE01EE0BF780, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .
Google query: ntdll.sys CRITICAL_PROCESS_DIED
On Wed 2/22/2017 5:40:31 PM your computer crashed
crash dump file: C:\Windows\Minidump\022217-3640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xEF (0xFFFFCF01AD16F780, 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 Wed 2/22/2017 5:37:55 PM your computer crashed
crash dump file: C:\Windows\Minidump\022217-3687-01.dmp
This was probably caused by the following module: filecrypt.sys (filecrypt+0xF9A0)
Bugcheck code: 0x7A (0xFFFF9006B1E31F88, 0xFFFFFFFFC000000E, 0x25CBEC860, 0xFFFFF8028FFAF9A0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\filecrypt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows sandboxing and encryption filter
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 2/22/2017 11:37:45 AM your computer crashed
crash dump file: C:\Windows\Minidump\022217-3593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xEF (0xFFFFCA028326F780, 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.
Facebook
Twitter
Instagram