Need help BSOD problems

Question

I've been having BSOD for months now and even when upgrdaing and replacing parts in my pc the craches continue. I've done all the tests possible. chkdsk in the command prompt, repairing my local disk, updating drivers but the issue still persists. I was able to access the minidump file from one of the crashes and I've put it into Windows debugger but I dont know how to interpret the analysis. If someone could help me interpret the results I would be so grateful. I've pasted it here:

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

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

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1437

    Key  : Analysis.Elapsed.mSec
    Value: 3195

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x154

    Key  : Bugcheck.Code.TargetModel
    Value: 0x154

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x154_c0000005_nt!MiStoreModifiedWriteComplete

    Key  : Failure.Exception.Code
    Value: 0xc0000005

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff803d245f711

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x45f711

    Key  : Failure.Exception.Record
    Value: 0xffffef031f9ef798

    Key  : Failure.Hash
    Value: {cdd5420b-7f50-747d-a366-958ddc4171cd}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0


BUGCHECK_CODE:  154

BUGCHECK_P1: ffffa40a0943e000

BUGCHECK_P2: ffffef031f9ee7a0

BUGCHECK_P3: 1

BUGCHECK_P4: 0

FILE_IN_CAB:  012126-15531-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa40a0945c3c0

EXCEPTION_RECORD:  ffffef031f9ef798 -- (.exr 0xffffef031f9ef798)
ExceptionAddress: fffff803d245f711 (nt!MiStoreModifiedWriteComplete+0x0000000000000019)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

CONTEXT:  ffffef031f9eefa0 -- (.cxr 0xffffef031f9eefa0)
rax=ffffef031f9ef9f8 rbx=ffffa40a261f7610 rcx=8000000000000042
rdx=0000000000727000 rsi=ffffef031f9efa80 rdi=ffffa40a033fdcf0
rip=fffff803d245f711 rsp=ffffef031f9ef9d0 rbp=0000000000000042
 r8=0000000000000002  r9=00000000000003ff r10=ffffa40a0945c3c0
r11=ffffa409f28ea1c8 r12=0000000000000000 r13=ffffa409f28ea010
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nt!MiStoreModifiedWriteComplete+0x19:
fffff803`d245f711 488b29          mov     rbp,qword ptr [rcx] ds:002b:80000000`00000042=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

READ_ADDRESS: fffff803d2fc44c0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_STR:  0xc0000005

IP_IN_PAGED_CODE: 
nt!MiStoreModifiedWriteComplete+19
fffff803`d245f711 488b29          mov     rbp,qword ptr [rcx]

STACK_TEXT:  
ffffef03`1f9ef9d0 fffff803`d222dd90     : ffffa40a`261f7610 00000000`00000042 ffffef03`1f9efa80 ffffa40a`033fdcf0 : nt!MiStoreModifiedWriteComplete+0x19
ffffef03`1f9efa00 fffff803`d222da93     : ffffa40a`261f7610 ffffa40a`0943e000 00000000`00000001 fffff803`d2e259d0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxWorkItemComplete+0x110
ffffef03`1f9efa60 fffff803`d222cdda     : ffffa40a`261f7610 fffff803`d20376d8 ffffa40a`033fdcf0 ffffa40a`0943e000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmWorkItemFree+0xf3
ffffef03`1f9efae0 fffff803`d24a3d6f     : ffff2e72`00000000 00000000`00000001 ffffffff`fffdb610 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStWorker+0x43a
ffffef03`1f9efb80 fffff803`d248c4da     : ffffa40a`0943e000 fffff803`d24a3d40 ffffc301`1d6ef180 024fe07f`bcbbbdff : nt!SMKM_STORE<SM_TRAITS>::SmStWorkerThread+0x2f
ffffef03`1f9efbb0 fffff803`d26a32d4     : ffffc301`1d6ef180 ffffa40a`0945c3c0 fffff803`d248c480 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffffef03`1f9efc00 00000000`00000000     : ffffef03`1f9f0000 ffffef03`1f9e9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!MiStoreModifiedWriteComplete+19

MODULE_NAME: nt

IMAGE_VERSION:  10.0.26100.7623

STACK_COMMAND: .cxr 0xffffef031f9eefa0 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  19

FAILURE_BUCKET_ID:  0x154_c0000005_nt!MiStoreModifiedWriteComplete

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {cdd5420b-7f50-747d-a366-958ddc4171cd}

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

Moved from: Windows for business | Windows Server | Performance | System performance

Answer 1

Hi Noémi Kouassi,

Thank you for posting on Microsoft Q&A forum and providing the crash dump details. I understand how disruptive and frustrating it is to experience repeated blue screen crashes, especially after upgrading hardware and running multiple diagnostic tests.

After reviewing the dump, the system is hitting an UNEXPECTED_STORE_EXCEPTION (0x154). In simple terms, Windows is crashing while handling memory that’s being written back to the drive. This usually points to a low‑level stability issue rather than a normal software or application problem.

To help narrow down the root cause, I recommend the following steps, in order:

Step 1: Temporarily run the system at default BIOS settings

Even when memory passes diagnostic tools, marginal instability can show up under real Windows workloads (memory compression and paging in particular). Please temporarily:

• Disable XMP/EXPO memory profiles and run the RAM at default speeds
• Disable any CPU undervolting, curve optimizer or overclocking features

This is only for testing and helps confirm whether memory timing or the CPU’s memory controller is contributing to the crashes.

Step 2: Test the system in Safe Mode

Safe Mode starts Windows with only basic Microsoft drivers and disables most third‑party software and background services.

1. Hold Shift on your keyboard and click Restart from the Windows Start menu
2. When the recovery screen appears, select: Troubleshoot > Advanced options > Startup Settings > Restart
3. After the system restarts, you’ll see a list of options
4. Press 4 (or F4) for Safe Mode, or 5 (or F5) for Safe Mode with Networking

If the system is stable in Safe Mode, it strongly suggests a third‑party driver or background tool (for example, antivirus, disk utilities, or encryption software) is involved.

If the system still crashes in Safe Mode, that points more toward a hardware‑level or firmware issue (memory, SSD firmware, or system stability).

Step 3: Check and update SSD firmware

The crash occurred during a disk write operation, so storage firmware is important to rule out. Please identify the model of your system SSD and check for firmware updates using the manufacturer’s official tool. These updates don’t usually come through Windows Update, but outdated firmware can cause crashes under heavy or sustained disk activity.

Step 4: Temporarily disable or remove third‑party disk or security software

If you’re running any third‑party antivirus, disk encryption, or storage optimization tools, please temporarily disable or uninstall them for testing. These types of tools operate very close to Windows’ storage and memory subsystems and can cause crashes without obvious error messages.

*Disclaimer: Temporarily turn off antivirus protection. However, keep in mind that if you do so, your device may be vulnerable to threats. So please turn it on immediately once issue fixed. 

After completing these steps, please let me know:

• Whether the system becomes more stable
• If crashes seem to happen during idle time, heavy disk usage or after sleep/wake

Based on the results, we can safely narrow this down and decide the best next steps.

---

If you have additional questions about this answer, please click "Comment".

Note: If you want to receive email notifications about this thread, follow the steps in our documentation to enable email notifications.