Page 1 of 2 12 LastLast

  1. Joined : Jun 2016
    Posts : 6
    windows 10
       05 Jun 2016 #1

    BSOD (IRQL_NOT_LESS_OR_EQUAL) probably caused by ntkrnlmp.exe


    Hi

    I am having multiple BSODs with the IRQL_NOT_LESS_OR_EQUAL message.
    I believe the dump files are pointing towards ntkrnlmp.exe but I don't have a lot of experience with dump files.
    I was wondering if anyone would take a look at the files? (the ones from the 4th of june, the others are way older and I believe unrelated)

    thanks!

    (if I am in the wrong place for asking or have created a duplicate thread I apologize, this is my first time posting here)

    EDIT : Just Bluescreened again, not sure if it is related since its another message but i have updated the dump files
      My System SpecsSystem Spec


  2. Joined : Jun 2015
    Posts : 10,897
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       05 Jun 2016 #2

    Hi sylren,

    Welcome to the 10forums

    Please follow below suggestions and report back how it goes or if any BSOD occurs.

    - Please remove Daemon tools, a well known cause for BSODs.
    - Please check your Samsung SSD for firmware updates with Samsung Magician.
    - Please free up space on your D partition to at least 15% free space. Windows needs at least 10-15% free space on each partition to not annoy the user with background stuff Windows performs, preferred at least 15% to be sure no issue occurs.
    - Please remove VirtualBox while troubleshooting.
    Code:
    ffffd000`65b3d998  fffff800`393aced0Unable to load image \SystemRoot\system32\DRIVERS\VBoxDrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for VBoxDrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for VBoxDrv.sys
     VBoxDrv+0x1ced0
    Is TunnelBear a requirement for your daily use?
    The tcpip.sys and netio.sys are Windows network drivers, this gives a possible indication of the network drivers where in most cases the cause is with either VPNs, protection software or USB network adapters.
    Code:
    ffffd000`2c4ef330  fffff801`27d89320 tcpip!TcpNsiInterfaceDispatch
    ffffd000`2c4ef338  fffff801`27b3a6e8 NETIO!NsiEnumerateObjectsAllParametersEx+0x1f8
    ffffd000`2c4ef340  fffff801`27d881c8 tcpip!TcpInformationObject+0x138
      My System SpecsSystem Spec


  3. Joined : Jun 2016
    Posts : 6
    windows 10
       05 Jun 2016 #3

    thanks for the quick reply!

    I have removed Daemon tools and TunnelBear and I cleared some stuff from the D partition, it should have enough space now.
    Unfortunately I do absolutely need Virtualbox for today (finishing up a final project) but I will remove it as soon as I am done.
    Next I will be checking the SSD with the Samsung Magician.
    Do you also advice I do something about the windows network drivers?
      My System SpecsSystem Spec


  4. Joined : Jun 2015
    Posts : 10,897
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       05 Jun 2016 #4

    It is a good thing to check for driver updates, but for now it would be better to first see how your system behaves after all suggestions have been applied
      My System SpecsSystem Spec


  5. Joined : Jun 2016
    Posts : 6
    windows 10
       05 Jun 2016 #5

    ok, I will update again when I know more
      My System SpecsSystem Spec


  6. Joined : Jun 2016
    Posts : 6
    windows 10
       05 Jun 2016 #6

    I was not yet able to check the SSD yet, but I Bluescreened again and after starting up it bluescreened with a memory at the login screen.
    It then bluescreened again with a memory error before the login screen so I decided to open up the case and take out 1 stick of RAM (im running 2 sticks of 8, so it should be fine with just the one).
    It now booted up normally.
    Do you think the problem could be hardware related? (these last situations seem to suggest so)
    I have also included the new mini dumps
      My System SpecsSystem Spec


  7. Joined : Jun 2015
    Posts : 10,897
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       05 Jun 2016 #7

    That certainly looks like it yes, though a reseat may also help

    I would suggest that you run MemTest86+ on this single stick to see if errors pop up.
    Please note, if MemTest86+ doesn't find errors does NOT mean the stick is not faulty.



    BSOD (IRQL_NOT_LESS_OR_EQUAL)  probably caused by ntkrnlmp.exe Diagnostic Test BSOD (IRQL_NOT_LESS_OR_EQUAL)  probably caused by ntkrnlmp.exe
     RAM TEST

    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   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.


    Make a photo of the result and post it.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.
      My System SpecsSystem Spec


  8. Joined : Jun 2016
    Posts : 6
    windows 10
       05 Jun 2016 #8

    I will run the memtest on the single stick I have removed now (I think that if one is faulty its that one, since it seems to be working for now) overnight, and report back tomorrow. Should it be ok to run the pc on the single stick for now so I can finish the project or do you advice against it?
      My System SpecsSystem Spec


  9. Joined : May 2016
    Posts : 534
    Windows 10
       05 Jun 2016 #9

    You may want to try the Windows Memory Test - Search > MDSCHED.EXE

    EDIT: Some months ago I was experiencing something similar with my other Windows 8.1 PC.
    It was even corrupting all my HDD.
    The solution I found was not use my new Wriless Mouse (5GHz) and also I had to uninstall all the updates back to 21.09.2015. I stoped to Update PC, and since 3 Month no more BSOD.
      My System SpecsSystem Spec


  10. Joined : Jun 2015
    Posts : 10,897
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       05 Jun 2016 #10

    Hi Adalwar,

    Thanks for your suggestion, but MemTest86+ is proven better.
    MemTest86+ has found many times errors where the built-in feature was unable to find them.
      My System SpecsSystem Spec


 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
IRQL_NOT_LESS_OR_EQUAL possibly ntkrnlmp.exe ( nt!KiRetireDpcList+4bb
I've had BSOD problems on two separate laptops of the same model and make, I shipped and returned the first one and got a replacement. The BSODs still kept happening even on a newly shipped laptop. Please help. :/
BSOD Crashes and Debugging
ntkrnlmp.exe caused BSOD
Hi there, I started to get BSOD yesterday. They all happening whild I playing online game, yester day i got 2, both shows ATTEMPTED_WRITE_TO_READONLY_MEMORY And today I got one with DRIVER_OVERRAN_STACK_BUFFER and another one with...
BSOD Crashes and Debugging
Solved Repeated BSOD irql_not_less_or_equal- Pfn list corrupt - ntkrnlmp.exe
Over the last week or so I've been having BSOD crashes at random intervals. Sometimes they seem to occur when my laptop has been asleep, or when it wakes up, but other times when I'm using it. When it crashes, I haven't been doing anything more...
BSOD Crashes and Debugging
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+225b0
Hi Guys, When booting Windows 10 I am presented with a BSOD, when using the debugging tools to look at the dump files this error is coming out all the time. Any ideas? - Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+225b0 )...
BSOD Crashes and Debugging
BSOD caused by ntoskrnl.exe (nt+0x14E240) IRQL_NOT_LESS_OR_EQUAL
Hi! I installed Windows 10 multiple times and every time i get this error. Please help me!36488
BSOD Crashes and Debugging
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 12:31.
Find Us
Twitter Facebook Google+



Windows 10 Forums