Computer repeatedly blue screening from UNEXPECTED_STORE_EXCEPTION (Bugcheck: 0x00000154)

Question

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000154 (0xffff83021a1f0000, 0xffffa902f37e1020, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b522c3fd-e1eb-43e0-9504-3751c8af5313.

For some reason my computer has suddenly started freezing about a week ago and in general is running really slow after it blue screened once. Since then, it also keeps randomly blue screening. It seems like whenever I increase usage of the RAM or something along those lines it freezes. For example for some reason when I'm typing it will randomly start lagging and the characters will stop showing up, then after a few seconds they'll appear on the screen.

Any advice or assistance is extremely appreciated. I've looked at the hard drives and they seem to be fine. I'm not really sure what it could be.

Here's the Memory.Dmp File Log:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3374

    Key  : Analysis.Elapsed.mSec
    Value: 3840

    Key  : Analysis.IO.Other.Mb
    Value: 1

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 25

    Key  : Analysis.Init.CPU.mSec
    Value: 483

    Key  : Analysis.Init.Elapsed.mSec
    Value: 42514

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 97

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x154

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x154

    Key  : Failure.Bucket
    Value: 0x154_c0000006_c000009c_IMAGE_storahci.sys

    Key  : Failure.Hash
    Value: {8e9c4ea8-d07a-904f-1aae-b3525bc0be92}

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 16777216

    Key  : Hypervisor.Flags.ValueHex
    Value: 1000000

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.DumpDriver
    Value: DUMP_STORAHCI

    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3

    Key  : WER.OS.Version
    Value: 10.0.22621.2506

BUGCHECK_CODE:  154

BUGCHECK_P1: ffff83021a1f0000

BUGCHECK_P2: ffffa902f37e1020

BUGCHECK_P3: 2

BUGCHECK_P4: 0

FILE_IN_CAB:  MEMORY.DMP

EXCEPTION_RECORD:  ffffa902f37e2018 -- (.exr 0xffffa902f37e2018)
ExceptionAddress: fffff8076c7b1972 (nt!RtlDecompressBufferXpressLz+0x0000000000000042)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 000002444ed3be80
   Parameter[2]: 00000000c000009c
Inpage operation failed at 000002444ed3be80, due to I/O error 00000000c000009c

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000002444ed3be80

IMAGE_NAME:  storahci.sys

MODULE_NAME: storahci

FAULTING_MODULE: fffff8076e070000 storahci

CONTEXT:  ffffa902f37e1830 -- (.cxr 0xffffa902f37e1830)
rax=fffff8076c7b1930 rbx=0000000000000000 rcx=ffffbc81cff68000
rdx=ffffbc81cff68000 rsi=000002444ed3be80 rdi=ffffbc81cff68000
rip=fffff8076c7b1972 rsp=ffffa902f37e2250 rbp=ffffbc81cff69000
 r8=000002444ed3be80  r9=00000000000000e9 r10=0000fffff8076c7b
r11=000002444ed3bf69 r12=ffffbc81cff68000 r13=ffffa902f37e24d8
r14=000002444ed3bf13 r15=ffffbc81cff68ea0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!RtlDecompressBufferXpressLz+0x42:
fffff807`6c7b1972 418b00          mov     eax,dword ptr [r8] ds:002b:00000244`4ed3be80=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

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:  00000000c000009c

EXCEPTION_STR:  0xc0000006

STACK_TEXT:  
ffffa902`f37e2250 fffff807`6c4f1950     : ffffbc81`cff68000 ffff8302`1a1f0050 00000244`4ed3be80 ffffbc81`cff68000 : nt!RtlDecompressBufferXpressLz+0x42
ffffa902`f37e2270 fffff807`6c65dd01     : ffff8302`1a1f1788 ffff8302`1a1f0050 00000244`4ed3be80 00000244`4ed3be80 : nt!RtlDecompressBufferEx+0x60
ffffa902`f37e22c0 fffff807`6c7c5558     : 00000000`00000004 fffff807`6c7bece2 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x22b
ffffa902`f37e2390 fffff807`6c7c61b8     : 00000000`00000001 00000000`00007c55 ffff8302`1a1f0050 ffff8302`00003000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
ffffa902`f37e23e0 fffff807`6c7c4d45     : ffffffff`ffffffff ffff8302`2da92000 ffffa902`f37e24c0 ffff8302`2a080cd0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1c4
ffffa902`f37e2480 fffff807`6c7be7db     : ffffa902`f37e26b9 00000000`00000001 fffff807`6ce69600 ffff8302`31f8a880 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc9
ffffa902`f37e2530 fffff807`6c7be6b1     : ffff8302`1a1f0000 ffff8302`2a080cd0 ffff8302`2da92000 ffff8302`1a1f19c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x93
ffffa902`f37e25b0 fffff807`6c4eb6fa     : ffff8302`1a8060f4 ffff8302`1a1f0000 00000000`00000000 ffff8302`2da92000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffa902`f37e25e0 fffff807`6c65d81e     : fffff807`6c7be690 ffffa902`f37e2680 00000000`00000002 ffff8302`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x7a
ffffa902`f37e2650 fffff807`6c7c05b8     : ffffa902`00000000 ffff8302`0c4dd1c8 00000000`000003ff ffff8302`2a080cd0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xd6
ffffa902`f37e2720 fffff807`6c7bdec3     : 00000000`000003ff 00000000`000003ff ffffa902`f37e27d0 ffff8302`2a080cd0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x48
ffffa902`f37e2770 fffff807`6c65d2b2     : 00000000`0000000c ffff8302`2a080cd0 00000000`00000003 00000000`00000003 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0x1d7
ffffa902`f37e2800 fffff807`6c7c7832     : ffff8302`31f8a940 ffffa902`f37e28c0 00000000`00000003 ffffa902`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x1cc
ffffa902`f37e2880 fffff807`6c648c62     : ffff8302`20927a42 00000000`00000001 ffff8302`1aef1700 fffff807`6c469099 : nt!SmPageRead+0x42
ffffa902`f37e28c0 fffff807`6c4b6ba7     : 00000000`00000002 ffffa902`f37e2a00 ffff8302`31f8a830 ffff8302`31f8a830 : nt!MiIssueHardFaultIo+0x191792
ffffa902`f37e2910 fffff807`6c4621b1     : 00000000`c0033333 00000000`00000001 0000027b`37c45d40 0000008e`00000000 : nt!MiIssueHardFault+0x207
ffffa902`f37e29c0 fffff807`6c627929     : ffffa902`f37e2b60 0000027b`37402070 0000027b`374f9370 0000027b`3748d850 : nt!MmAccessFault+0x331
ffffa902`f37e2ae0 00007ff8`f7489bd2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x369
0000008e`ce17eba8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`f7489bd2

STACK_COMMAND:  .cxr 0xffffa902f37e1830 ; kb

FAILURE_BUCKET_ID:  0x154_c0000006_c000009c_IMAGE_storahci.sys

OS_VERSION:  10.0.22621.2506

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8e9c4ea8-d07a-904f-1aae-b3525bc0be92}

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

Answer 1

Hi Jeffrey,

Welcome to Microsoft Community.

I'm Hahn and I'm here to help you with your concern.

The Bugcheck Analysis indicates an UNEXPECTED_STORE_EXCEPTION (154) with the following details:

• Arg1: ffff83021a1f0000, Pointer to the store context or data manager
• Arg2: ffffa902f37e1020, Exception information
• Arg3: 0000000000000002, Reserved
• Arg4: 0000000000000000, Reserved

Bug Check 0x154 UNEXPECTED_STORE_EXCEPTION - Windows drivers | Microsoft Learn

The bugcheck code (BUGCHECK_CODE) is 154, and the failure appears to be related to the storahci.sys driver, with the error code c0000006 (In-page I/O error). The exception occurred during a memory decompression operation, specifically in the function nt!RtlDecompressBufferXpressLz.

Storahci.sys is a system driver file associated with the Windows operating system. It is responsible for managing storage devices, such as hard drives and solid-state drives, connected to your computer. This driver allows your operating system to communicate with the storage devices and ensures their proper functioning.

The relevant part of the stack trace indicates that the process involved is "MemCompression," and the error occurred while trying to access memory due to an I/O error. MemCompression is a feature in Windows that compresses some data in RAM to save space and improve performance.

Possible causes and steps to resolve the issue:

• Update Drivers: Ensure that your storage controller drivers, especially storahci.sys, are up to date. You can check for driver updates on your device manufacturer's website or through Windows Update.
• System File Checker (SFC) and DISM: Run the System File Checker (SFC) and Deployment Image Service and Management Tool (DISM) to check and repair system files. Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support
• Verify RAM: Memory-related issues can sometimes lead to system crashes. Run a memory diagnostic test to check for any potential problems with your RAM. You can use the built-in Windows Memory Diagnostic tool. To run Windows Memory Diagnostic:
  • Press Windows key + S, type "Windows Memory Diagnostic," and select the app.
  • Choose to restart and check for problems.
• Check Disk Integrity: Run a disk check to ensure the integrity of your system's disk. You can use the chkdsk command in the Command Prompt with administrative privileges. chkdsk /f

Disclaimer: Running chkdsk can check the file system and file system metadata of a volume for logical and physical errors. To avoid any trouble for you, do not cancel or interrupt chkdsk, and back up important data.

• Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default settings and basic device drivers aren't causing the issue. Observing Windows in safe mode enables you to narrow down the source of a problem, and can help you troubleshoot problems on your PC. Start your PC in safe mode in Windows - Microsoft Support

I hope this helps.  If there is anything not clear, please do not hesitate to let me know.

Your Sincerely

Hahn - MSFT | Microsoft Community Support Specialist