Windows 10: BSOD - ntoskrnl.exe & ntkrnlmp.exe

Discus and support BSOD - ntoskrnl.exe & ntkrnlmp.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi all! I've just encountered this BSOD and I tried to analyze it myself using WhoCrashed. It tells me that it was probably caused by ntoskrnl.exe &... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by acfourleaf, Sep 4, 2015.

  1. BSOD - ntoskrnl.exe & ntkrnlmp.exe


    Hi all! I've just encountered this BSOD and I tried to analyze it myself using WhoCrashed. It tells me that it was probably caused by ntoskrnl.exe & ntkrnlmp.exe. I've looked into it but I haven't been able to find a fix to this and I was wondering If anyone could give me a hand.

    This BSOD occurred right after start up. I turned on driver verifier to see what was wrong with my drivers. As a side note, I've ran memtest for 8+ passes, have benchmarked my CPU with IntelBurnTest while monitoring temperatures and have ran Furmark for my GPU while monitoring that as well. At this point I'm not sure if it is because of faulty drivers or because of bad hardware.

    Any help is appreciated, thanks!

    :)
     
    acfourleaf, Sep 4, 2015
    #1
  2. dktaege Win User

    Windows 10: BSOD - ntoskrnl.exe & ntkrnlmp.exe

    Here are the specs

    Operating System

    Windows 10 Enterprise 64-bit

    CPU

    Intel Core i7 4790K @ 4.00GHz 55 °C

    Haswell 22nm Technology

    RAM

    16,0GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)

    Motherboard

    Gigabyte Technology Co. Ltd. Z97MX-Gaming 5 (SOCKET 0) 28 °C

    Graphics

    EV2436W (1920x1200@59Hz)

    EA241WM (1920x1200@59Hz)

    Intel HD Graphics 4600 (Gigabyte)

    4095MB NVIDIA GeForce GTX 960 (MSI) 35 °C

    ForceWare version: 385.28

    SLI Disabled

    Storage

    232GB Samsung SSD 850 EVO 250GB (SSD) 35 °C

    931GB SAMSUNG HD103SJ (SATA) 32 °C

    698GB Crucial_CT750MX300SSD1 (SSD) 34 °C

    232GB Generic External USB Device (SSD) 35 °C

    I clean installed the graphics driver just recently, didnt help

    WhoCrashed gives me this:

    On Sat 26.08.2017 19:07:32 your computer crashed

    crash dump file: C:\WINDOWS\Minidump\082617-8796-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x183B0C)

    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8030F410B0C, 0xFFFFAC8182B06528, 0xFFFFAC8182B05D70)

    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

    file path: C:\WINDOWS\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: This indicates that a system thread 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 Sat 26.08.2017 19:07:32 your computer crashed

    crash dump file: C:\WINDOWS\memory.dmp

    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

    Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8030F410B0C, 0xFFFFAC8182B06528, 0xFFFFAC8182B05D70)

    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Any help? thanks in advance!
     
    dktaege, Sep 4, 2015
    #2
  3. dktaege Win User
    Windows 10: BSOD - ntoskrnl.exe & ntkrnlmp.exe

    1. it was preinstalled when i got the computer

    2. i didnt

    3. Version 1703 Build 15063.540
     
    dktaege, Sep 4, 2015
    #3
  4. essenbe Win User

    BSOD - ntoskrnl.exe & ntkrnlmp.exe

    Hello, acfourleaf and welcome to the forums.

    Code: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status Arg2: 0000000000000103, the status Arg3: ffffe0010349f110, the IRP Arg4: 0000000000000000[/quote] You had a hard drive I/O problem according supposedly caused by

    Use !analyze -v to get detailed debugging information.
    BugCheck C9, {6, 103, ffffe0010349f110, 0}
    Code: Unable to load image \SystemRoot\System32\drivers\ISCTD64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ISCTD64.sys *** ERROR: Module load completed but symbols could not be loaded for ISCTD64.sys Probably caused by : ntkrnlmp.exe ( nt!IovCompleteRequest+c3 ) Followup: MachineOwner[/quote] That is the driver for the Intel Smart Connect technology. That seems to cause some people a lot of problems. I would suggest disabling it, if you can. If you continue to have problems, Check the hard drives with the manufacturer's diagnostic program. If you need to know what Smart connect does, I will try to explain it for you, but I suspect you know. If your System Specs had listed your hard drives, I could tell you the which test to run probably. If you need to know, just tell me what hard drives you have and I may be able to give you a link.
     
    essenbe, Sep 4, 2015
    #4
  5. Very weird, I thought I removed that already. I didnt see it in programs under control panel so I had to go into Device Manager to remove it and now that I'm back in device manager, Intel Smart Connect seems to be back. Guess I'll try again and report back with any new updates.

    Thanks for the help!

    Quick update: So it turns out for my motherboard [MSI Z97G45 GAMING], there's a setting in BIOS to turn on Intel Smart Connect Technology and had to disable that to completely remove it from my system. Hopefully this fixes my BSODs! I'm going to give it a few days and if there isn't any BSODs then I will marked this as solved *Smile
     
    acfourleaf, Sep 4, 2015
    #5
  6. essenbe Win User
    Good investigation on your part. I hope it solves your problem. Thank you for marking it solved, if that is the case. If it is not, please post back here and let us know. If you haven't already, please turn off driver Verifier.
     
    essenbe, Apr 5, 2018
    #6
Thema:

BSOD - ntoskrnl.exe & ntkrnlmp.exe

Loading...
  1. BSOD - ntoskrnl.exe & ntkrnlmp.exe - Similar Threads - BSOD ntoskrnl exe

  2. BSOD on Computer Startup- ntoskrnl exe stop code irql_not_less_or_equal Nothing is working

    in Windows 10 Gaming
    BSOD on Computer Startup- ntoskrnl exe stop code irql_not_less_or_equal Nothing is working: Background: I have to have this done before school starts in June for me. and I have important images of my toddler nephew on there and i am very low on funds and dont have money to fix it and am in transitional housing so i can get housing and im applying for SSI so I cant...
  3. BSOD on Computer Startup- ntoskrnl exe stop code irql_not_less_or_equal Nothing is working

    in Windows 10 Software and Apps
    BSOD on Computer Startup- ntoskrnl exe stop code irql_not_less_or_equal Nothing is working: Background: I have to have this done before school starts in June for me. and I have important images of my toddler nephew on there and i am very low on funds and dont have money to fix it and am in transitional housing so i can get housing and im applying for SSI so I cant...
  4. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...
  5. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...
  6. Random BSOD ntoskrnl, ntkrnlmp executables

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD ntoskrnl, ntkrnlmp executables: I have a Lenovo laptop with the following specs: Intel Core i7-8550U 4C / 8T, 1.8 / 4.0GHz, 8MB Integrated Intel UHD Graphics 620 Intel SoC Platform 16GB Soldered DDR4-2400 512GB SSD M.2 2280 PCIe NVMe 13.9" UHD 3840x2160 IPS 300nits Glossy I started getting random...
  7. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  8. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  9. BSOD (system service exception) on new computer: ntoskrnl, ntkrnlmp

    in Windows 10 BSOD Crashes and Debugging
    BSOD (system service exception) on new computer: ntoskrnl, ntkrnlmp: Last week, I assembled a new desktop computer (with all new components) and installed windows 10 Educational. (See my 2nd PC details.) I updated and installed all the latest drivers. (I think at least.) But, since installation, I am having BSOD on various moments with the...
  10. BSOD's have returned! [ntkrnlmp, ntoskrnl] HYPERVISOR error

    in Windows 10 BSOD Crashes and Debugging
    BSOD's have returned! [ntkrnlmp, ntoskrnl] HYPERVISOR error: Hello all, its nice to be back! I've had a couple threads in the forum which regard my issues with BSODs the last being around 5 months ago from now and the other a bit longer. Though generally the errors have been consistent but has dipped in frequency with the help I...