ntkrnlmp.exe bsod's

bascotie · Apr 13, 2021

Hi guys,

Got another one for ya. This dell laptop seems to crash often times after just a couple minutes of being logged in. Other times, like recently, I was able to use it for an hour no problem, download updates, test youtube, etc.

Attached are the logs and most are pointing to ntkrnlmnp.exe. This is on Win 10 20H2. Built in dell quick diag passed. I'm running the full diag now as well. Thank you!

bascotie · Apr 13, 2021

May have found the solution (just like my previous post too) where the LONG DST is failing but SMART/Shortdst pass. This is quite unusual but looks like I'll have to start doing long tests more often. Thanks guys!

zbook · Apr 13, 2021

See posting instructions:
Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista
SysnativeBSODCollectionApp
Sysnative BSOD Dump + File Collection App [Detailed] Output Explained

x BlueRobot · Apr 14, 2021

bascotie said:
May have found the solution (just like my previous post too) where the LONG DST is failing but SMART/Shortdst pass. This is quite unusual but looks like I'll have to start doing long tests more often. Thanks guys!

Looked like a failing hard-disk, all of the dumps are generic Stop 0x7Es but the last two were Stop 0x124s. S.M.A.R.T. status isn't always the most reliable to be honest, hence why we usually recommend a long test if you're going to run HDD/SSD diagnostics.

Rich (BB code):

BugCheck 1000007E, {ffffffff80000003, fffff8044c9038c3, ffff83045ae8be88, ffff83045ae8b6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff80227b038c3, ffffba0d2bc6ee88, ffffba0d2bc6e6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff80624b038c3, ffff840e8fbcfe88, ffff840e8fbcf6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff802725038c3, fffff4088a728e88, fffff4088a7286c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff801585038c3, ffffb60ba26bde88, ffffb60ba26bd6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff800061038c3, ffffd7832d643e88, ffffd7832d6436c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff8044bd038c3, ffffbf8059656e88, ffffbf80596566c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff806849038c3, ffffaf8f7a66ee88, ffffaf8f7a66e6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff8026e1038c3, ffff9d8d9e253e88, ffff9d8d9e2536c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff80582b038c3, fffffe8eb2e56e88, fffffe8eb2e566c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff807343038c3, ffffdd0932d75e88, ffffdd0932d756c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff803457038c3, fffff6847701de88, fffff6847701d6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff8025d5038c3, fffff900c006de88, fffff900c006d6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff802767038c3, ffff8384cf843e88, ffff8384cf8436c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff80761f038c3, fffffc07db8dde88, fffffc07db8dd6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff8047fd038c3, fffff6815683be88, fffff6815683b6c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff8075e1038c3, ffffe402a1ec0e88, ffffe402a1ec06c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff80531b038c3, ffff8b0be1676e88, ffff8b0be16766c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffff80000003, fffff8043ad038c3, ffff890c405b5e88, ffff890c405b56c0}
Probably caused by : ntkrnlmp.exe ( nt!KeCheckStackAndTargetAddress+53 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, ffffc28f296a1028, fe000000, 801136}
Probably caused by : GenuineIntel
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 124, {0, ffffd40483b2a028, fe000000, 801136}
Probably caused by : GenuineIntel
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

jcgriff2 · Apr 22, 2021

Check out the exception code and memory addresses in that CODE BOX report. Most are identical - or very close to it (mem addresses).

x BlueRobot said:
Looked like a failing hard-disk, all of the dumps are generic Stop 0x7Es but the last two were Stop 0x124s. S.M.A.R.T. status isn't always the most reliable to be honest, hence why we usually recommend a long test if you're going to run HDD/SSD diagnostics.

Agree.

John

Search

Search

ntkrnlmp.exe bsod's

bascotie

Well-known member

Attachments

bascotie

Well-known member

zbook

Member

x BlueRobot

Administrator

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

ntkrnlmp.exe bsod's

bascotie

Well-known member

Attachments

bascotie

Well-known member

zbook

Member

x BlueRobot

Administrator

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)