Windows 10: Random BSOD: Probably caused by : ntkrnlmp.exe

Discus and support Random BSOD: Probably caused by : ntkrnlmp.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; I was playing a game when my computer suddenly crashed with the BSOD : IRQL_NOT_LESS_OR_EQUAL Below is my crash dump file, if anyone could please... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by YDelm, Jan 11, 2019.

  1. YDelm Win User

    Random BSOD: Probably caused by : ntkrnlmp.exe

    I was playing a game when my computer suddenly crashed with the BSOD : IRQL_NOT_LESS_OR_EQUAL

    Below is my crash dump file, if anyone could please help me identify the issue, I would really appreciate it.

    Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 17134 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 17134.1.amd64fre.rs4_release.180410-1804

    Machine Name:

    Kernel base = 0xfffff801`1cc99000 PsLoadedModuleList = 0xfffff801`1d047150

    Debug session time: Fri Jan 11 11:04:22.939 2019 (UTC - 5:00)

    System Uptime: 0 days 16:55:30.642

    Loading Kernel Symbols





    Loading User Symbols

    PEB is paged out (Peb.Ldr = 00000046`ad557018). Type ".hh dbgerr001" for details

    Loading unloaded module list



    * *

    * Bugcheck Analysis *

    * *


    Use !analyze -v to get detailed debugging information.

    BugCheck A, {ffff85c0000b0040, 2, 0, fffff8011ccece90}

    Probably caused by : ntkrnlmp.exe ( nt!MI_READ_PTE_LOCK_FREE+0 )

    Followup: MachineOwner


    7: kd> !analyze -v


    * *

    * Bugcheck Analysis *

    * *



    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high. This is usually

    caused by drivers using improper addresses.

    If a kernel debugger is available get the stack backtrace.


    Arg1: ffff85c0000b0040, memory referenced

    Arg2: 0000000000000002, IRQL

    Arg3: 0000000000000000, bitfield :

    bit 0 : value 0 = read operation, 1 = write operation

    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

    Arg4: fffff8011ccece90, address which referenced memory

    Debugging Details:







    BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

    SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.


    SYSTEM_SKU: To be filled by O.E.M.


    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 1.10

    BIOS_DATE: 08/06/2018

    BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.



    DUMP_TYPE: 1

    BUGCHECK_P1: ffff85c0000b0040

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff8011ccece90

    READ_ADDRESS: ffff85c0000b0040




    fffff801`1ccece90 488b01 mov rax,qword ptr [rcx]

    CPU_COUNT: 8

    CPU_MHZ: e10

    CPU_VENDOR: AuthenticAMD

    CPU_FAMILY: 17

    CPU_MODEL: 11


    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXPNP: 1 (!blackboxpnp)



    PROCESS_NAME: AMD Ryzen Master.exe


    ANALYSIS_SESSION_TIME: 01-11-2019 12:16:46.0016

    ANALYSIS_VERSION: 10.0.17763.132 amd64fre

    TRAP_FRAME: ffff910b88b806a0 -- (.trap 0xffff910b88b806a0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=ffff858000000000 rbx=0000000000000000 rcx=ffff85c0000b0040

    rdx=ffff910b88b80a40 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8011ccece90 rsp=ffff910b88b80838 rbp=ffff910b88b80940

    r8=0000000000000000 r9=ffff85c2e170b000 r10=fffffa0000000028

    r11=0020000000000000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei ng nz na pe nc


    fffff801`1ccece90 488b01 mov rax,qword ptr [rcx] ds:ffff85c0`000b0040=????????????????

    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff8011ce53c69 to fffff8011ce430a0


    ffff910b`88b80558 fffff801`1ce53c69 : 00000000`0000000a ffff85c0`000b0040 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

    ffff910b`88b80560 fffff801`1ce508e5 : ffffbb04`8d128ede 00000159`c4672458 ffffa407`7f9e5080 fffff801`1ce4a175 : nt!KiBugCheckDispatch+0x69

    ffff910b`88b806a0 fffff801`1ccece90 : fffff801`1ccf539d ffff910b`88b80b80 ffffa407`7f9e5080 fffff797`79517350 : nt!KiPageFault+0x425

    ffff910b`88b80838 fffff801`1ccf539d : ffff910b`88b80b80 ffffa407`7f9e5080 fffff797`79517350 fffff801`1ccf4a9e : nt!MI_READ_PTE_LOCK_FREE

    ffff910b`88b80840 fffff801`1ccf324e : ffff910b`88b809c0 ffff910b`88b80a31 00000000`c0000016 fffff801`00000000 : nt!MiDispatchFault+0x3ed

    ffff910b`88b80990 fffff801`1ce507da : 00000000`00000000 00000159`c4670150 00000159`da4f1050 00000159`c4677770 : nt!MmAccessFault+0x21e

    ffff910b`88b80b00 00007ff9`e417c1aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x31a

    00000046`ad6f9c70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`e417c1aa

    THREAD_SHA1_HASH_MOD_FUNC: a9648449c83af6cbf8bc3f23e2a73652458e4656

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: fbd4f631d61d3e0ee749caceeecf850ae39805b9

    THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6



    fffff801`1ccece90 488b01 mov rax,qword ptr [rcx]

    FAULT_INSTR_CODE: 48018b48



    FOLLOWUP_NAME: MachineOwner


    IMAGE_NAME: ntkrnlmp.exe


    STACK_COMMAND: .thread ; .cxr ; kb





    TARGET_TIME: 2019-01-11T16:04:22.000Z

    OSBUILD: 17134




    SUITE_MASK: 272



    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS


    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2019-01-01 01:44:13

    BUILDDATESTAMP_STR: 180410-1804

    BUILDLAB_STR: rs4_release

    BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804



    FAILURE_ID_HASH_STRING: km:av_nt!mi_read_pte_lock_free

    FAILURE_ID_HASH: {46795dd4-7dde-8cf0-b2ba-3f69fbe2847b}

    Followup: MachineOwner


    YDelm, Jan 11, 2019
  2. ARC
    Arc Win User

    Random BSOD while browsing internet

    BitDefender is nothing special. mwac.sys causes BSODs anywhere.
    A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
    In that very thread, the suggested action apparently worked.

    The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
    As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
    That is why I posted that my suggestion may work, or may not. Let us see where it goes.
  3. retr0 Win User
    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 received (thanks!) Since my last post, I have had near to no blue screens but am getting the odd few this past month, and judging by WhoCrashed, the modules which seem to cause it have been the same ever since.
    In summary, here's what has been done:
    I have my doubts on what may have caused the current one and here is what WhoCrashed states:

    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)  Bugcheck code: 0x20001 (0x11, 0x210CC1, 0x1003, 0xFFFFE80000231DF0) Error: HYPERVISOR_ERROR file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The hypervisor has encountered a fatal error. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    retr0, Jan 11, 2019
  4. Random BSOD: Probably caused by : ntkrnlmp.exe

    Random BSOD

    Appear to be getting random BSOD from time to time. Ran the debug with result being:

    Probably caused by : memory_corruption ( nt!MiDeleteVa+15d6 )
    samantha101(1), Jan 11, 2019

Random BSOD: Probably caused by : ntkrnlmp.exe

  1. Random BSOD: Probably caused by : ntkrnlmp.exe - Similar Threads - Random BSOD Probably

  2. Random BSODs with unknown cause

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs with unknown cause: Hey guys! Got a problem with my new system. I get different bluescreens from time to time. Here is a link to an example dump file: - 121818-9968-01.dmp My system: I9-9900k RTX 2080ti 32GB Corsair RGB Pro DDR4 3600 DIMM Samsung 970 Pro 1TB DarkPower...
  3. Multiple BSOD - "Probably Caused by:" memory_corruption / Unknown_Image / ntkrnlmp.exe -...

    in Windows 10 BSOD Crashes and Debugging
    Multiple BSOD - "Probably Caused by:" memory_corruption / Unknown_Image / ntkrnlmp.exe -...: Hello, I've recently started getting random BSOD on my Windows 10 machine. Only one has happened while light web browsing and the others have happened while the computer is idle and/or locked. The "Probably cause by" reason has been memory_corruption a couple times,...
  4. BSOD Probably caused by : memory_corruption

    in Windows 10 BSOD Crashes and Debugging
    BSOD Probably caused by : memory_corruption: Hi, My computer frequently has BSOD. I have used windbg to analyze 800mb dump file as attached bellow: please help , thank you! Microsoft (R) Windows Debugger Version 10.0.17763.1 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File...
  5. BSOD, Bugcheck Analysis : "probably caused by : GenuineIntel"

    in Windows 10 BSOD Crashes and Debugging
    BSOD, Bugcheck Analysis : "probably caused by : GenuineIntel": My 4-year-old custom build started having Bluescreens a month ago, it's rather random and sometimes I don't have crashes for days but it's very unpredictable. I wasn't able to trigger the crash with various test programs so I'm a little lost how I find a solution to my...
  6. BSOD (IRQL_NOT_LESS_OR_EQUAL) probably caused by ntkrnlmp.exe

    in Windows 10 BSOD Crashes and Debugging
    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...
  7. 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...
  8. Asus laptop - Bsod - Probably caused by - ntoskrnlmp.exe

    in Windows 10 BSOD Crashes and Debugging
    Asus laptop - Bsod - Probably caused by - ntoskrnlmp.exe: I have an Asus laptop and since I upgraded to windows 10, I've been getting periodical shutdowns. I've received two Bsod's but most of the time, my laptop would fall asleep while I was using it. I ran chkdsk and everything checked out ok so I decided to run verifier to see if...
  9. BSOD for 3 years ago "Probably caused by : GenuineIntel"

    in Windows 10 BSOD Crashes and Debugging
    BSOD for 3 years ago "Probably caused by : GenuineIntel": Hi I've made up my computer something like 3 years ago with windows 8 I encounter sporadic BSOD and always though it was windows issue. Always hopping that a windows update will fix it someday. I recently updated my PC to windows 10 - same behavior. I've updated the...
  10. Random BSODs caused by ntoskrnl.exe

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs caused by ntoskrnl.exe: Hi all, 3 weeks ago I did a fresh install of Windows 10 and since then I'm getting BSODs at least once every 1-2 hours. These BSODs vary from SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED to KMODE_EXCEPTION_NOT_HANDLED. Also these...