BSOD - ntkrnlmp.exe

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 14,901
    Windows 10 Pro
       #11

    You might want to update your system specs then :)
    It says 2x4GB.
      My Computers


  2. Posts : 17
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       #12

    I screwed up the product link - it is 2x4GB and NOT 4x2GB.

    XMS3 — 8GB (2x4GB) DDR3 1333MHz C9 Memory Kit (CMX8GX3M2B1333C9

      My Computer


  3. Posts : 14,901
    Windows 10 Pro
       #13

    Try to increase the voltage with 0.012 and see how it goes
      My Computers


  4. Posts : 17
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       #14

    The target voltage is already set at 1.500v but it's achieving 1.488v when I check in status monitoring. So, to clarify, should I set target voltage to 1.512v?
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #15

    Is XMP enabled?
      My Computers


  6. Posts : 17
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       #16

    Don't think my BIOS has XMP (I haven't seen it). I'm able to change RAM frequency and voltage manually though, so same difference?
      My Computer


  7. Posts : 14,901
    Windows 10 Pro
       #17

    Just Watching said:
    The target voltage is already set at 1.500v but it's achieving 1.488v when I check in status monitoring. So, to clarify, should I set target voltage to 1.512v?
    I hope you are right about this :)
    Because that would mean a driver is causing issues, to catch this driver, driver verifier is needed.



    Diagnostic Test

     DRIVER VERIFIER


    warning   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   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.
      My Computers


  8. Posts : 17
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       #18

    See attached file
      My Computer


  9. Posts : 14,901
    Windows 10 Pro
       #19

    None are caused by driver verifier.
    Keep verifier running for about 35h more.
      My Computers


  10. Posts : 17
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       #20

    Well things have gone from bad to FUBAR. The system is now completely unusable. I can't even get the dump files off it to post here - it crashes too quickly. I eventually managed to turn driver verifier off, but it's still crashing like crazy. Most of time not even bluescreening - just freezing or restarting itself without warning.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:02.
Find Us




Windows 10 Forums