Windows 10: 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

:)

 

BSOD cause by ntkrnlmp.exe

Hi Sumit,

here the minidumps file.

BSOD by ntkrnlmp.exe

122117-13890-01.dmp

122117-14796-01.dmp

many thanks for replying

 

Frequently BSOD KMODE_EXCEPTION_NOT_HANDLED 0x0000001e

Hi, I've already used winDbg to debug the dmp file. And I get the information that "

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f8e )

"

And i searched about the ntkrnlmp.exe but didn't find any useful information.

I don't know what should I do next... Check the hardware or check the drivers ?

I really need help. The BSOD is so frequently. I could get a BSOD even if I start the OS no more than ten minutes.

Here is the dmp files: Minidump.zip

 

Please remove Norton and use Windows Defender as alternative, there are some event logs that show conflicts/problems with Windows Defender and Windows built-in network drivers, I believe Norton has something to do with that. Although I find it a bit odd that there are Windows Defender event logs present.






Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

 

Thank you so much for the quick reply - I really appreciate it. I used the Norton Removal Tool to remove Norton and have started using Windows Defender. Both sfc/scannow runs found no integrity violations. I will monitor over the next week to see if removing Norton did the trick, and, if so, mark this as solved. Many thanks again!

 

Nope - it just happened again. Here is what Whocrashed shows:

On Fri 2/26/2016 10:10:10
AM your computer crashed
crash dump file:
C:\Windows\Minidump\022616-15015-01.dmp
uptime: 00:47:05
This was probably
caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code:
0x1A (0x5002, 0xFFFFF58010804000, 0x923E, 0x55000923FFFFFFFE)
Error: MEMORY_MANAGEMENT
Bug check description: This
indicates that a severe memory management error occurred.
This might be a
case of memory corruption. More often memory corruption happens because of
software errors in buggy drivers, not because of faulty RAM modules.
The
crash took place in the Windows kernel. Possibly this problem is caused by
another driver that cannot be identified at this time.

Here is a link to the dump files if it is useful:

https://onedrive.live.com/?id=6D0233...0233C5DF0C4847

 

This time I don't need much more *Smile
It is a few basic things with the 0x1A,

• something wants to access data on the disk which is invalid,
• the memory management attempts to recover this problem,
• the accessed address is changed to 0's,
• another attempt to access this address occured what caused the BSOD.

That is what happened basically, the suggestion is to run MemTest86+ per the instructions.

• If MemTest86+ doesn't show any errors enable driver verifier to catch any driver violations.
• If MemTest86+ does show 1 or more errors,
  • stop the test
  • remove all sticks but 1 and run the test again
  • switch the stick to another slot, run the test and switch to another slot everytime the test finished
  • switch the stick with another stick and do step 3 again.
  • Meanwhile note the results to find out if a slot or stick is causing the error(s)

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Last, please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabs

• CPU
• Mainboard
• Memory
• SPD*
• Graphics

*SPD shows the details of each module, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each module.

Please post each screenshot in your next reply/replies.