Windows 10: BSOD ntkrnlmp.exe

I have nodebook computer MSI GE72VR 7RF with windows 10 PRO. I have a BUgcheck Analysis can you help me. Think.

Microsoft (R) Windows Debugger Version 10.0.15063.468 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 Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\SymbolsSrvCache*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\SymbolsSrvCache*https://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
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 = 0xfffff803`9cc99000 PsLoadedModuleList = 0xfffff803`9d047290
Debug session time: Sun Oct 21 21:51:42.157 2018 (UTC + 2:00)
System Uptime: 2 days 4:28:37.891
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 12B, {ffffffffc00002c4, a32, 34ad090, ffff9d00d6773000}

Probably caused by : ntkrnlmp.exe ( nt!ST_STORE<SM_TRAITS>::StDmPageError+f0 )

Followup: MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 0000000000000a32, physical page number
Arg3: 00000000034ad090, zero
Arg4: ffff9d00d6773000, zero

Debugging Details:
------------------


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: GE72VR 7RF

SYSTEM_SKU: 179B.3

SYSTEM_VERSION: REV:1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: E179BIMS.30C

BIOS_DATE: 10/27/2017

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: MS-179B

BASEBOARD_VERSION: REV:1.0

DUMP_TYPE: 1

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: a32

BUGCHECK_P3: 34ad090

BUGCHECK_P4: ffff9d00d6773000

SM_COMPRESSION_FORMAT: 3

SM_SOURCE_PFN1: 3fd96

SM_SOURCE_PFN2: ffffffffffffffff

SM_SOURCE_OFFSET: 1d090

SM_SOURCE_SIZE: a32

SM_TARGET_PFN: 2b3ab

SM_BUFFER_HASH: d60ac8c3

SM_ONEBIT_SOLUTION_COUNT: 0

BUGCHECK_STR: 0x12B_c00002c4_StCtDecompressFailed

CPU_COUNT: 8

CPU_MHZ: af8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: MemCompression

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-13NGUO4

ANALYSIS_SESSION_TIME: 10-22-2018 02:29:26.0197

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

LAST_CONTROL_TRANSFER: from fffff8039cf3ea1c to fffff8039ce42490

STACK_TEXT:
ffffd888`3a82f1c8 fffff803`9cf3ea1c : 00000000`0000012b ffffffff`c00002c4 00000000`00000a32 00000000`034ad090 : nt!KeBugCheckEx
ffffd888`3a82f1d0 fffff803`9cea4b76 : 00000000`00000200 00000000`00000003 ffffb40b`2f9d9050 00000000`034ad090 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xf0
ffffd888`3a82f220 fffff803`9cde797d : 00000000`00000004 ffffd888`3a82f430 00000000`00000000 00000000`00000097 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0xbd1d2
ffffd888`3a82f300 fffff803`9cde7842 : 00000000`00000001 00000000`0001d090 00000000`0001d090 00000000`00010000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x95
ffffd888`3a82f350 fffff803`9cde766d : ffffb40b`ffffffff ffffb40b`67bbc000 ffffd888`3a82f430 ffffb40b`653d0ad0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
ffffd888`3a82f3f0 fffff803`9cde74c1 : ffffb40b`67bbc000 fffff803`00000000 ffffc407`00000001 ffffb40b`2f9da788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1
ffffd888`3a82f4a0 fffff803`9cde73d1 : ffffb40b`2f9d9000 ffffb40b`653d0ad0 ffffb40b`67bbc000 ffffb40b`2f9da9b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffffd888`3a82f520 fffff803`9ccf94aa : ffffb40b`645fc700 ffffd888`3a82f5f0 00000000`00000000 00000000`00000001 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffd888`3a82f550 fffff803`9cdea00d : fffff803`9cde73b0 ffffd888`3a82f5f0 00000000`00000003 ffffb40b`67bbc000 : nt!KeExpandKernelStackAndCalloutInternal+0x8a
ffffd888`3a82f5b0 fffff803`9cd04959 : ffffd888`3a82f6b0 fffff803`9cd044fd 00000000`00000000 fffff803`9cde95bc : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad
ffffd888`3a82f680 fffff803`9cd0439a : 00000000`00000000 00000000`00000000 ffffd888`3a82f730 ffffb40b`653d0ad0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1b1
ffffd888`3a82f6d0 fffff803`9cde9320 : 00000000`0000000c 00000000`00000010 ffffb40b`653d0ad0 ffffb40b`6489e450 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xce
ffffd888`3a82f750 fffff803`9cdea9c6 : 00000000`00000010 ffffb40b`6489e508 00000000`00000000 ffffb40b`2f9d9000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x168
ffffd888`3a82f7c0 fffff803`9cd650f6 : 00000000`00000000 ffffb40b`26133a80 ffffd888`3a82f8a0 fffff803`9cd92c36 : nt!SmPageRead+0x2e
ffffd888`3a82f810 fffff803`9cd65ba4 : 00000000`00000002 ffffd888`3a82f8a0 00000000`00000001 ffffd888`3a82f978 : nt!MiIssueHardFaultIo+0x122
ffffd888`3a82f860 fffff803`9cd91374 : 00000000`c0033333 00000000`00000001 000001c6`30a0f000 ffffb40b`00000000 : nt!MiIssueHardFault+0x234
ffffd888`3a82f910 fffff803`9ce4fbda : 00000000`00000000 000001c6`30a0ef60 000001c6`30a0e020 00000000`00004a00 : nt!MmAccessFault+0x384
ffffd888`3a82fa80 00007ffe`855fc387 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x31a
0000001f`f9ebe4e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`855fc387


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 0e25f7e1a5e1caae3d28e6a7023983c4503045c5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f0137c00d149edcbd1f4230e2aa81143d0998a6f

THREAD_SHA1_HASH_MOD: 82d14546c43bd06881f781d6d197c4c7f7ceb9cb

FOLLOWUP_IP:
nt!ST_STORE<SM_TRAITS>::StDmPageError+f0
fffff803`9cf3ea1c cc int 3

FAULT_INSTR_CODE: 48c033cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+f0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5ba316ae

BUCKET_ID_FUNC_OFFSET: f0

FAILURE_BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

PRIMARY_PROBLEM_CLASS: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

TARGET_TIME: 2018-10-21T19:51:42.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: 2018-09-20 05:40:30

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: d77

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x12b_c00002c4_stctdecompressfailed_nt!st_store_sm_traits_::stdmpageerror

FAILURE_ID_HASH: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

Followup: MachineOwner
---------

:)

 

Multiple BSODs caused by ntkrnlmp.exe in Windows 10

Also, i not that to geeky to comprehend what was written in the .DMP file, you can also check this:

https://www.tenforums.com/bsod-crashes-debugging/21169-bsod-ntoskrnl-exe-ntkrnlmp-exe.html

it says that it regards the BIOS. . . . ?

 

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.

 

Event 10016 error

Hi seahenting, generally BSOD's are caused by a corrupt / incompatible device driver, when ntkrnlmp is listed alone as the cause, it is very had to diagnose the underlying issue . . .