Windows 10: 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 *

* *

*******************************************************************************



IRQL_NOT_LESS_OR_EQUAL (a)

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.

Arguments:

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:

------------------





KEY_VALUES_STRING: 1





STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 401



BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804



SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.



SYSTEM_PRODUCT_NAME: MS-7B85



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



SYSTEM_VERSION: 1.0



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: 1.10



BIOS_DATE: 08/06/2018



BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.



BASEBOARD_PRODUCT: B450 GAMING PRO CARBON AC (MS-7B85)



BASEBOARD_VERSION: 1.0



DUMP_TYPE: 1



BUGCHECK_P1: ffff85c0000b0040



BUGCHECK_P2: 2



BUGCHECK_P3: 0



BUGCHECK_P4: fffff8011ccece90



READ_ADDRESS: ffff85c0000b0040



CURRENT_IRQL: 2



FAULTING_IP:

nt!MI_READ_PTE_LOCK_FREE+0

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



CPU_COUNT: 8



CPU_MHZ: e10



CPU_VENDOR: AuthenticAMD



CPU_FAMILY: 17



CPU_MODEL: 11



CPU_STEPPING: 0



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXPNP: 1 (!blackboxpnp)





DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



BUGCHECK_STR: AV



PROCESS_NAME: AMD Ryzen Master.exe



ANALYSIS_SESSION_HOST: DESKTOP-J7D0H84



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

nt!MI_READ_PTE_LOCK_FREE:

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

Resetting default scope



LAST_CONTROL_TRANSFER: from fffff8011ce53c69 to fffff8011ce430a0



STACK_TEXT:

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



FOLLOWUP_IP:

nt!MI_READ_PTE_LOCK_FREE+0

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



FAULT_INSTR_CODE: 48018b48



SYMBOL_STACK_INDEX: 3



SYMBOL_NAME: nt!MI_READ_PTE_LOCK_FREE+0



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: nt



IMAGE_NAME: ntkrnlmp.exe



DEBUG_FLR_IMAGE_TIMESTAMP: 5c2b0c3d



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 0



FAILURE_BUCKET_ID: AV_nt!MI_READ_PTE_LOCK_FREE



BUCKET_ID: AV_nt!MI_READ_PTE_LOCK_FREE



PRIMARY_PROBLEM_CLASS: AV_nt!MI_READ_PTE_LOCK_FREE



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



OSBUILD: 17134



OSSERVICEPACK: 0



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 272



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



OS_LOCALE:



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



ANALYSIS_SESSION_ELAPSED_TIME: bc7



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:av_nt!mi_read_pte_lock_free



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



Followup: MachineOwner

---------

:)

 

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.

 

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:

Code:

Code:

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.

 

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 )