Windows 10: BSOD Bugcheck 154

About every two weeks I get the BSOD Bugcheck 154. I am not actively using the computer at the time the error occurs.

I have run DISM and SFC numerous times and the error continues to happen.

I ran windbg and got this output: Any suggetions on what to do?



Microsoft R Windows Debugger Version 10.0.20153.1000 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.


************* Path validation summary **************

Response Time ms Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 18362 MP 4 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff806`35000000 PsLoadedModuleList = 0xfffff806`35448190

Debug session time: Sun Jul 12 00:19:23.207 2020 UTC - 7:00

System Uptime: 10 days 7:25:58.029

Loading Kernel Symbols

...............................................................

................................................................

................................................................

............................

Loading User Symbols

PEB address is NULL !

Loading unloaded module list

..................................................

For analysis of this file, run <link alt="!analyze -v" cmd="!analyze -v"><u>!analyze -v</u></link>

nt!KeBugCheckEx:

fffff806`351c23a0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8482`0a265730=0000000000000154

2: kd&gt; !analyze -v

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

* *

* Bugcheck Analysis *

* *

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



UNEXPECTED_STORE_EXCEPTION 154

The store component caught an unexpected exception.

Arguments:

Arg1: ffffc60ff908d000, Pointer to the store context or data manager

Arg2: ffff84820a2657e0, Exception information

Arg3: 0000000000000002, Reserved

Arg4: 0000000000000000, Reserved



Debugging Details:

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


KEY_VALUES_STRING: 1


Key : Analysis.CPU.mSec

Value: 8155


Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on RAWIDEAPAD


Key : Analysis.DebugData

Value: CreateObject


Key : Analysis.DebugModel

Value: CreateObject


Key : Analysis.Elapsed.mSec

Value: 11179


Key : Analysis.Memory.CommitPeak.Mb

Value: 84


Key : Analysis.System

Value: CreateObject


Key : WER.OS.Branch

Value: 19h1_release


Key : WER.OS.Timestamp

Value: 2019-03-18T12:02:00Z


Key : WER.OS.Version

Value: 10.0.18362.1


ADDITIONAL_XML: 1


OS_BUILD_LAYERS: 1


BUGCHECK_CODE: 154


BUGCHECK_P1: ffffc60ff908d000


BUGCHECK_P2: ffff84820a2657e0


BUGCHECK_P3: 2


BUGCHECK_P4: 0


EXCEPTION_RECORD: ffff84820a266788 -- <link alt=".exr 0xffff84820a266788" cmd=".exr 0xffff84820a266788"><u>.exr 0xffff84820a266788</u></link>

ExceptionAddress: fffff8063515e360 nt!RtlDecompressBufferXpressLz+0x0000000000000050

ExceptionCode: c0000006 In-page I/O error

ExceptionFlags: 00000000

NumberParameters: 3

Parameter[0]: 0000000000000000

Parameter[1]: 000001b4878feaa0

Parameter[2]: 00000000c000000e

Inpage operation failed at 000001b4878feaa0, due to I/O error 00000000c000000e


EXCEPTION_PARAMETER1: 0000000000000000


EXCEPTION_PARAMETER2: 000001b4878feaa0


CONTEXT: ffff84820a265fd0 -- <link alt=".cxr 0xffff84820a265fd0" cmd=".cxr 0xffff84820a265fd0"><u>.cxr 0xffff84820a265fd0</u></link>

rax=fffff8063515e310 rbx=0000000000000000 rcx=ffff920014d2a000

rdx=ffff920014d2a000 rsi=0000000000000002 rdi=000001b4878feaa0

rip=fffff8063515e360 rsp=ffff84820a2669c8 rbp=ffff920014d2a000

r8=000001b4878feaa0 r9=0000000000000824 r10=ffff920014d2aea0

r11=000001b4878ff2c4 r12=ffff84820a266c58 r13=ffffc60010e41000

r14=000001b4878ff26e r15=ffff920014d2b000

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246

nt!RtlDecompressBufferXpressLz+0x50:

fffff806`3515e360 418b08 mov ecx,dword ptr [r8] ds:002b:000001b4`878feaa0=????????

Resetting default scope


BLACKBOXBSD: 1 <link alt="!blackboxbsd" cmd="!blackboxbsd"><u>!blackboxbsd</u></link>


BLACKBOXNTFS: 1 <link alt="!blackboxntfs" cmd="!blackboxntfs"><u>!blackboxntfs</u></link>


BLACKBOXPNP: 1 <link alt="!blackboxpnp" cmd="!blackboxpnp"><u>!blackboxpnp</u></link>


BLACKBOXWINLOGON: 1


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.


EXCEPTION_CODE_STR: c0000006


EXCEPTION_PARAMETER3: 00000000c000000e


EXCEPTION_STR: 0xc0000006


TRAP_FRAME: ffff84820a2672e0 -- <link alt=".trap 0xffff84820a2672e0" cmd=".trap 0xffff84820a2672e0"><u>.trap 0xffff84820a2672e0</u></link>

NOTE: The trap frame does not contain all registers.

<col fg="emphfg">Some register values may be zeroed or incorrect.</col>

rax=ffffd60107e03418 rbx=0000000000000000 rcx=ffffd60107d5f558

rdx=ffffd60107e04138 rsi=0000000000000000 rdi=0000000000000000

rip=fffff806355db38e rsp=ffff84820a267470 rbp=ffffc60015bdc080

r8=ffffd60107e033f0 r9=0000000000000000 r10=0000000000000000

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nt!MiRemoveSharedCommitNode+0x1ce:

fffff806`355db38e 483901 cmp qword ptr [rcx],rax ds:ffffd601`07d5f558=0000000000000000

Resetting default scope



STACK_TEXT:

ffff8482`0a267470 fffff806`355db17d : 00000000`00000000 ffffd601`1de694f8 ffffd600`fc8a45b0 00000000`00000000 : nt!MiRemoveSharedCommitNode+0x1ce

ffff8482`0a2674e0 fffff806`3560ad08 : ffffd601`00000000 ffffd601`00000002 ffffd601`09221390 ffffd601`0380fa40 : nt!MiSectionClose+0x1d

ffff8482`0a267510 fffff806`356283c1 : 00000000`00000000 00000000`00000000 ffff8482`0a2676a0 00000000`00000001 : nt!ObCloseHandleTableEntry+0x278

ffff8482`0a267650 fffff806`3562832b : 00000000`00000d6c 00000000`00000001 ffffd601`189cc2d0 fffff806`3536f0a9 : nt!ObpCloseHandle+0x85

ffff8482`0a2676c0 fffff806`4c57fbac : ffffd601`09220e70 01000000`00100000 ffffd601`189cc2d0 fffff806`4c501767 : nt!ObCloseHandle+0x2b

ffff8482`0a2676f0 fffff806`4c51454a : 00000000`00834000 ffffd601`09220e70 ffffc600`0c9385a0 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_BLOCK::~VIDMM_RECYCLE_BLOCK+0x8c

ffff8482`0a267740 fffff806`4c57fae5 : ffffc600`011efb30 fffff806`4c568c7b 00000000`00000001 00000000`00000002 : dxgmms2!VIDMM_RECYCLE_BLOCK::`scalar deleting destructor'+0xe

ffff8482`0a267770 fffff806`4c569d10 : ffffd601`0ae725e0 ffffc600`0c9385a0 ffffc600`0c9385a0 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR:estroyRange+0x5d

ffff8482`0a2677b0 fffff806`4c566566 : ffffd601`0ae725e0 00000000`00000001 00000000`00000001 00000000`00000020 : dxgmms2!VIDMM_RECYCLE_BLOCK::CleanupFreeBlock+0x68

ffff8482`0a2677e0 fffff806`4c568f07 : ffffd601`0ae725e0 ffffd601`0ae72648 ffffd601`1a5045c8 fffff806`4c913a25 : dxgmms2!VIDMM_RECYCLE_RANGE:ebouncedUnlock+0x18a

ffff8482`0a267840 fffff806`4c5810c1 : ffffc600`0c938500 ffffc600`0c9385a0 ffffd601`04c0b800 0000000b`00000001 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR:rocessDebounceList+0xdf

ffff8482`0a2678b0 fffff806`4c580ed1 : ffffd601`185385c8 fffff806`350a24e7 ffffc60f`00000000 ffffd601`00000000 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::FlushTransitions+0x31

ffff8482`0a2678f0 fffff806`4c514ca9 : ffffc60f`f6780000 00000000`00000000 00000000`00000000 0000016c`76673500 : dxgmms2!VIDMM_GLOBAL::FlushHeapTransitions+0x59

ffff8482`0a267960 fffff806`4c95e113 : 00000000`80000300 0000016c`76673500 01d65002`00000000 ffffd601`04c0b8a0 : dxgmms2!VidMmFlushHeapTransitions+0x9

ffff8482`0a267990 fffff806`351d3c15 : ffffc60f`f938f0c0 ffffc60f`f6780000 0000000b`3fa7f0a0 00000000`00000000 : dxgkrnl!DxgkFlushHeapTransitions+0xe3

ffff8482`0a267a00 00007fff`05aa4ba4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

0000000b`3fa7f378 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`05aa4ba4


STACK_COMMAND: .trap 0xffff84820a2672e0 ; kb

SYMBOL_NAME: dxgmms2!VIDMM_RECYCLE_BLOCK::~VIDMM_RECYCLE_BLOCK+8c

MODULE_NAME: <link alt="lmvm dxgmms2" cmd="lmvm dxgmms2"><u>dxgmms2</u></link>

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.18362.900

BUCKET_ID_FUNC_OFFSET: 8c

FAILURE_BUCKET_ID: 0x154_c0000006_c000000e_dxgmms2!VIDMM_RECYCLE_BLOCK::_VIDMM_RECYCLE_BLOCK

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {56c7901d-bfa4-a62f-d029-a6b31ff55750}

Followup: MachineOwner

---------

:)

 

(BSOD) bugcheck was: 0x000000a0 INTERNAL_POWER_ERROR

Has any one got this BSOD when stress testing a overclock before? i can get the minidump if some one can read it for me i was trying for 4.5Ghz @ 1.31v and after around 20min of stressing i would get this BSOD and it would shut my system down not even sure i saw a BSOD just a shutdown?

 

"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 " BSOD on Windows 10.

Hi Jayan,



Please reply to a few questions asked below:

• Since when are you facing the above issue? Did you make any recent changes to the computer?
• Did you try booting the computer in Safe mode and check if the issue persists?

We are not able to access the link shared in the above post. If haven’t tried, please follow the steps suggested above and check if similar issue occurs on the computer.



Write to us with the answers to the above questions and the status of bugcheck error code received on the computer for further assistance.
Your reply is most important for us to ensure we assist you accordingly.



Thank you.

 

This is causing 90% of my Win7 64bit BSOD's...

WTF is this?

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff9e0084e02c0, 0x0000000000000000, 0xfffff88003c7b293, 0x0000000000000005

any suggestions thnx a bunch!