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, I've recently been getting multiple BSOD errors cause by the following modules ntoskrnl.exe and ntkrnlmp.exe Here is a WhoChrased report: On... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by hawk424, Aug 2, 2017.

  1. hawk424 Win User

    BSOD - ntoskrnl.exe & ntkrnlmp.exe


    Hi, I've recently been getting multiple BSOD errors cause by the following modules ntoskrnl.exe and ntkrnlmp.exe

    Here is a WhoChrased report:

    On Thu 2017-08-03 1:33:12 PM your computer crashed
    crash dump file: C:\Windows\Minidump\080317-6578-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
    Bugcheck code: 0x139 (0x3, 0xFFFFB00124994DB0, 0xFFFFB00124994D08, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The kernel has detected the corruption of a critical data structure.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 2017-08-03 1:33:12 PM 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: 0x139 (0x3, 0xFFFFB00124994DB0, 0xFFFFB00124994D08, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    Bug check description: The kernel has detected the corruption of a critical data structure.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 2017-08-03 1:22:34 PM your computer crashed
    crash dump file: C:\Windows\Minidump\080317-9203-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xF3F7F)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802DD579F7F, 0xFFFFD4806A368698, 0xFFFFD4806A367ED0)
    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 Thu 2017-08-03 1:16:46 PM your computer crashed
    crash dump file: C:\Windows\Minidump\080317-6843-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
    Bugcheck code: 0x50 (0xFFFFCC019AA9D068, 0x0, 0xFFFFF802EED3CBF3, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    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 Thu 2017-08-03 1:06:29 PM your computer crashed
    crash dump file: C:\Windows\Minidump\080317-12078-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801A3B08D00, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    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 kernel-mode program 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.

    :)
     
    hawk424, Aug 2, 2017
    #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, Aug 2, 2017
    #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, Aug 2, 2017
    #3
  4. philc43 Win User

    BSOD - ntoskrnl.exe & ntkrnlmp.exe

    One of your mini-dumps showed the graphics driver might be need updating:

    Code: fffff801`a585a688 fffff801`a9d80bf4*** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys atikmdag+0xb0bf4[/quote] The driver is atikmdag.sys Tue Apr 25 02:11:16 2017
    Please update the AMD drivers. The best way to do this is to uninstall everything of AMD using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the AMD website. When you do this be sure the "clean install" box is checked and only install the Graphics driver.
     
    philc43, Aug 2, 2017
    #4
  5. hawk424 Win User
    The driver is atikmdag.sys Tue Apr 25 02:11:16 2017
    Please update the AMD drivers. The best way to do this is to uninstall everything of AMD using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the AMD website. When you do this be sure the "clean install" box is checked and only install the Graphics driver.[/quote] I tried doing this yesterday and installed new drivers but the problem seems to still be happening
     
    hawk424, Aug 2, 2017
    #5
  6. hawk424 Win User
    I'm currently running memtest and i'm receiving some errors , could this be causing the issue?
     
    hawk424, Aug 2, 2017
    #6
  7. philc43 Win User
    Yes, if you are getting any errors in Memtest86 then your RAM is faulty and you can stop the current test. In some cases it can be the motherboard slot so to confirm you can repeat the testing with just one memory stick at a time in different slots to find out which stick or which slot is faulty. In most cases it is a faulty stick.
     
    philc43, Aug 2, 2017
    #7
  8. hawk424 Win User

    BSOD - ntoskrnl.exe & ntkrnlmp.exe

    Okay i'll go ahead and try this out, thanks!
     
    hawk424, Aug 2, 2017
    #8
  9. hawk424 Win User
    Yup one of my sticks were faulty, thanks for the help!
     
    hawk424, Apr 5, 2018
    #9
Thema:

BSOD - ntoskrnl.exe & ntkrnlmp.exe

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

  2. 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...
  3. 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...
  4. 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...
  5. .exe

    in Windows 10 Network and Sharing
    .exe: So i was not able to run Amd.exe . To do so i went to regedit and under Hkey class root .exe i changed the value .exe to “%1” %* but the mistake i made was i did not gave a space after “%1”. So after i restarted my pc i am anot able to open any .exe files i tried...
  6. 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...
  7. 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...
  8. Random BSODs on Dell XPS 13 9350 (ntoskrnl, ntkrnlmp, ndis)

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs on Dell XPS 13 9350 (ntoskrnl, ntkrnlmp, ndis): Hello All, My XPS 13 9350 has been BSODing again after a few months of relative stability. I've ran memtest86, 20 runs without errors, chkdsk, sfc/scannow, and DISM scanhealth all returning without errors or integrity violations. I've also used Whocrashed to analyze...
  9. 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...
  10. Random BSOD's [ntkrnlmp, ntoskrnl, rt640x64] + PC Freezes while Gaming

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD's [ntkrnlmp, ntoskrnl, rt640x64] + PC Freezes while Gaming: Hello all! I have previously posted in this specific forum due to random BSOD's which had mostly taken the error of IRQL_NOT_LESS_OR_EQUAL but it has been quite a while since that post [I'll link it here] and I have lacked the time. Nevertheless, since lowering the...

Users found this page by searching for:

  1. This was probably caused by the following module ntklmp.exe