Windows 10: BSOD caused by ntoskrnl.exe and ntkrnlmp.exe on startup

This happened after Dell came out and installed a new monitor in the machine.

I am posting this from Safe Mode as we speak from the computer with the issue. I have tried running a chkdsk on the computer and it fixed some errors. I tried finding the logfile, but maybe I had to have a special argument telling it to log. Sfc /scannow came back with nothing, but the machine will not boot into windows normally.

I am pretty certain that what is going on here is driver related, because of the hardware switch, but I do not know how to narrow it down to figure out what driver is causing the issue. I have attempted to reinstall the video drivers and uninstall the PnP monitor drivers for this machine. I have included the BSOD files. If you need any more information about this machine let me know. The machine itself is new and was 100% working before the monitor replacement.


Thanks,

G

:)

 

Random BSoD on Win10 caused by ntoskrnl.exe or ntkrnlmp.exe

Happy to help

Driver verified and related to your ATI video driver

Completely remove the current driver (or software) and install the newest driver available. For instructions on how to do that Read all about updating drivers here Updating a driver.

 

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

*** 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:

Driver Reference Table (DRT)

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.

 

Hi ghutchison,

Welcome to the 10forums *Smile

Please try again to upload the chkdsk log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums






Diagnostics Test

Clean boot
Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.

 

Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
I attempted to run the chkdsk from cmd prompt in safemode. Was then prompted to restart the computer to run the check. I restart the computer and then it blue screened same stop code error. I load back into safe mode, clean boot the thing, doesn't work. I go into the system recovery tools bootrec /fixmbr /fixboot run okay but /rebuildbcd displayed there being zero windows installations. Weird thing I noticed too in Diskpart...the drive is set gpt so i cannot set it as active.

Do all of these things correlate? I am pretty lost how it would go from working > broken screen> working with broken screen>replaced screen> won't boot. I've spent a lot of time trying ot get this thing to work. If I can't get it up by tomorrow I'm wiping it.

 

You can't use mbr commands on a GPT disk, that just won't work.


What command did you try to run for chkdsk?

 

Isn't uefi a hybrid of the two?

Chkdsk /r /f

 

UEFI is the interface communication between the hardware and OS where GPT and MBR are partitioning schemes for a disk.