New
#1
Constant ntkrnlmp.exe BSOD
I have had my PC since November of 14 and had no problems with it until I upgraded to Windows 10. I then began to get a string of BSOD such as these (from the WhoCrashed software):
On Thu 2/25/2016 10:10:01
PM your computer crashed
crash dump file:
C:\Windows\memory.dmp
uptime: 01:11:15
This was probably caused by the
following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code:
0x1E (0xFFFFFFFFC0000005, 0xFFFFF8015B7182A0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
KMODE_EXCEPTION_NOT_HANDLED
Bug check description:
This indicates that a kernel-mode program generated an exception which the error
handler did not catch.
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 Thu 2/25/2016 7:22:46 PM your computer
crashed
crash dump file:
C:\Windows\Minidump\022516-20000-01.dmp
uptime: 00:34:35
This was probably
caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code:
0x3D (0xFFFFF8034ABD4D38, 0xFFFFF8034ABD4550, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
Bug check
description: This bug check appears very infrequently.
The crash took place
in the Windows kernel. Possibly this problem is caused by another driver that
cannot be identified at this time.
On Thu 2/25/2016 6:46:38 PM your computer
crashed
crash dump file:
C:\Windows\Minidump\022516-25781-01.dmp
uptime: 21:47:18
This was probably
caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code:
0x1E (0xFFFFFFFFC0000005, 0xFFFFF802C509E4E6, 0x0, 0xFFFFFFFFFFFFFFFF)
Error:
KMODE_EXCEPTION_NOT_HANDLED
Bug check description:
This indicates that a kernel-mode program generated an exception which the error
handler did not catch.
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.
I have done everything that I can think of - I have run memtest86 to check the RAM (all sticks have passed at least 8 passes), updated every driver, used driver verifier, and done two completely clean Windows 10 installs. Any help at all would be sincerely appreciated.
Attachment 66394