Windows 10 BSOD ntkrnlmp.exe

[HappyPetal]

[COLOR=rgba(17, 17, 17, 1)]Computer name: ADMINRG-6U7652G

Windows version: Windows 10, 10.0, version 2004, build: 19041
Windows dir: C:\WINDOWS
Hardware: Gigabyte Technology Co., Ltd., Z77X-D3H
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz 8664, level: 6
4 logical processors, active mask: 15
RAM: 8474140672 bytes (7.9GB)[/COLOR]


Hi,

I never had BSOD or any problems until I updated my Windows 10.

Here is the latest minidump

https://drive.google.com/file/d/17m0psc-th3n_3u9Hc0YCiG5aObfiM-EE/view?usp=sharing

I find if very hard to believe it is hardware when it has been fine for years then crashes immediately after Windows update.

What have I done?


- sfc/scannow

- disabled all non microsoft services in msconfig

- Windows Memory Diagnostics


Any help appreciated.

Josh.



[COLOR=rgba(30, 30, 30, 1)]Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Joshua\Desktop\minidump\041921-6765-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`56200000 PsLoadedModuleList = 0xfffff803`56e2a3d0
Debug session time: Mon Apr 19 10:54:12.018 2021 (UTC + 10:00)
System Uptime: 0 days 21:30:26.686
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run [/COLOR][COLOR=rgba(0, 0, 255, 1)]!analyze -v
[/COLOR][COLOR=rgba(30, 30, 30, 1)]nt!KeBugCheckEx:
fffff803`565f5e40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe40e`fbc27700=0000000000000154
0: kd> !analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_STORE_EXCEPTION (154)
The store component caught an unexpected exception.
Arguments:
Arg1: ffffac8dc8fa8000, Pointer to the store context or data manager
Arg2: ffffe40efbc277b0, Exception information
Arg3: 0000000000000002, Reserved
Arg4: 0000000000000000, Reserved

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


BUGCHECK_CODE: 154

BUGCHECK_P1: ffffac8dc8fa8000

BUGCHECK_P2: ffffe40efbc277b0

BUGCHECK_P3: 2

BUGCHECK_P4: 0

PROCESS_NAME: MemCompression

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

SYMBOL_NAME: nt!RtlDecompressBufferXpressLz+50

MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt

[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: 0x154_c0000006_c0000483_nt!RtlDecompressBufferXpressLz

FAILURE_ID_HASH: {b1364ad4-c79e-08f8-b13a-5597db174610}

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



FROM APP WHO CRASHED[/COLOR]


[COLOR=rgba(17, 17, 17, 1)]On Mon 19/04/2021 10:54:12
AM your computer crashed or a problem was reported
crash dump file:
C:\WINDOWS\Minidump\041921-6765-01.dmp
This was probably caused by the
following module: [COLOR=rgba(17, 17, 17, 1)]ntoskrnl.exe[/COLOR] (nt+0x3F5E40)
Bugcheck code: 0x154
(0xFFFFAC8DC8FA8000, 0xFFFFE40EFBC277B0, 0x2, 0x0)
Error: [COLOR=rgba(17, 17, 17, 1)]UNEXPECTED_STORE_EXCEPTION[/COLOR]
file path:
C:\WINDOWS\system32\ntoskrnl.exe
product: [COLOR=rgba(17, 17, 17, 1)]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=rgba(17, 17, 17, 1)]Microsoft Corporation[/COLOR]
description: NT Kernel &
System
Bug check description: This indicates that the store component caught
an unexpected exception.
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. [/COLOR]

Continue reading...