Share via

How to fix BSOD caused by ntoskrnl.exe and ntkrnlmp.exe

Anonymous
2018-02-13T03:12:16+00:00

PLEASE HELP !!!!

System Information (local)


Computer name: MYAKOOB-US

Windows version: Windows 10 , 10.0, build: 15063

Windows dir: C:\WINDOWS

Hardware: 20BUS1KJ00, LENOVO

CPU: GenuineIntel Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz Intel586, level: 6

4 logical processors, active mask: 15

RAM: 17052958720 bytes total

*** * Crash Dump Analysis*


Crash dumps are enabled on your computer.

Crash dump directories:

C:\WINDOWS

C:\WINDOWS\Minidump

On Mon 2/12/2018 7:35:39 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!setjmpex+0x8FC9)

Bugcheck code: 0x7F (0x8, 0xFFFFDA011E050F50, 0x1E26BB58, 0xFFFFF80071F5FA4D)

Error: UNEXPECTED_KERNEL_MODE_TRAP

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Sun 2/11/2018 11:24:25 AM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\021118-13578-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7FA82)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018709AA82, 0xFFFFAA80C1293B68, 0xFFFFAA80C12933B0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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 system thread 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 Fri 2/2/2018 11:43:30 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\020318-14125-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x17DC50)

Bugcheck code: 0x7F (0x8, 0xFFFFD7812FF10F50, 0x318D6B58, 0xFFFFF803CB8EAA4D)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 1/29/2018 2:44:49 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\012918-22578-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x17DC50)

Bugcheck code: 0x7F (0x8, 0xFFFFBB80AD409F50, 0xAEF19B58, 0xFFFFF802782DAA4D)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 1/29/2018 12:57:44 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\012918-22984-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x17DC50)

Bugcheck code: 0x7F (0x8, 0xFFFF97003CA51F50, 0x3E8A6B58, 0xFFFFF8018995CA4D)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Sat 1/27/2018 11:59:05 AM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\012718-14031-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x17DC50)

Bugcheck code: 0x7F (0x8, 0xFFFFF8013BDDAE50, 0xFFFFC68185126DE4, 0x0)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 1/25/2018 9:49:04 AM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\012518-13843-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x17DC50)

Bugcheck code: 0x7F (0x8, 0xFFFFDF0081E09F50, 0x83879B58, 0xFFFFF8022ACD8A4D)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Tue 1/23/2018 3:19:41 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\012318-21953-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x17DC50)

Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800FDB0CE82)

Error: IRQL_NOT_LESS_OR_EQUAL

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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.

This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.

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 1/20/2018 1:55:32 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\012018-12265-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x17DC50)

Bugcheck code: 0x7F (0x8, 0xFFFFF803A6DDAE50, 0xA78DAB58, 0xFFFFF803A44EDA4D)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Sat 1/20/2018 12:44:23 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\012018-12734-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x17DC50)

Bugcheck code: 0x7F (0x8, 0xFFFFAC809B3EDF50, 0x9BDFEB58, 0xFFFFF8023C4E4A4D)

Error: UNEXPECTED_KERNEL_MODE_TRAP

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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.

*** * Conclusion*


On your computer a total of 14 crash dumps have been found. Only 10 have been 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.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Sumit 43,801 Reputation points Volunteer Moderator
2018-02-13T06:03:38+00:00

*** WARNING: Unable to verify timestamp for LEMo6022.sys

*** ERROR: Module load completed but symbols could not be loaded for LEMo6022.sys

*** WARNING: Unable to verify timestamp for pelmouse.sys

*** ERROR: Module load completed but symbols could not be loaded for pelmouse.sys

Related to Primax Electronics Mouse Suite Driver

Dates to 2015:

Timestamp:        Thu Dec 17 11:18:34 2015 (56724CB2)

*** WARNING: Unable to verify timestamp for mfencbdc.sys

*** ERROR: Module load completed but symbols could not be loaded for mfencbdc.sys

mfencbdc+0x2bc74

Related to Mcafee.

For Mouse driver,

Remove the Driver and install the newest copy.

Remove the driver completely:

https://answers.microsoft.com/en-us/windows/for...

You can find the newest driver links on the manufacturer's website or here:

http://www.carrona.org/dvrref.php

For McAfee:

https://answers.microsoft.com/en-us/protect/for...

Remove it using removal tool and use Windows Defender in its place.

Let us know if you require any assistance.

Was this answer helpful?

0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-03-06T13:12:34+00:00

    Hello :

    Any help ?

    Thank you !

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-03-03T16:28:43+00:00

    I did a Complete Re-install of the Windows 10 and it worked for a week and i now have a new Exception for BSOD Errors..

    SYSTEM_SERVICE_EXCEPTION

    I have uploaded a new set of Dump files. Here is the link 

    https://1drv.ms/f/s!AgOKLiZDL-l\_gwZFyTeV0raBvYGg

    Please help !

    Thank you !

    Mohammed Yakoob

    Oracle USA

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-13T03:41:14+00:00

    there you go..Link on OneDrive

    https://1drv.ms/f/s!AgOKLiZDL-l\_gn4okbLymWZ0mJHD

    this has all the last ONLY 6 Dump Files as Requested with System Information file as well. Please let me know ASAP.

    I get this BSOD every 2 hrs on Windows 10. It's been real bad at work. 

    Thank you So much !

    Mohammed Yakoob

    Oracle USA

    Was this answer helpful?

    0 comments No comments
  4. Sumit 43,801 Reputation points Volunteer Moderator
    2018-02-13T03:19:08+00:00

    Hello,

    We need log files(called dump files) that tell us what lead to crash.

    Please share them with us for a better analysis of the problem. Instructions can be found here:

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    0 comments No comments