Windows 10: help with NTDLL and Hardware_Disk BSOD

Discus and support help with NTDLL and Hardware_Disk BSOD in Windows 10 Drivers and Hardware to solve the problem; I'm currently having an issue with my PC. regardless of what program is running or not. I keep receiving a NDTLL or Hardware_disk error. I have tried... Discussion in 'Windows 10 Drivers and Hardware' started by ChristopherScroggins1, Jan 30, 2021.

  1. CHRISTOPHERSCROGGINS1
    ChristopherScroggins1 Win User

    help with NTDLL and Hardware_Disk BSOD


    I'm currently having an issue with my PC. regardless of what program is running or not. I keep receiving a NDTLL or Hardware_disk error. I have tried the DSMI and the SFC commands. I have updated all drivers and reverted my update and reupdated. still will get the error. I have ran a check on the hard drive and the memory both came up good. the error wont happen immediately it will some times take 15 to 30 min before BSOD.


    under is my crash dump. if you need more information please let me know.



    ymbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 12 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff805`0a200000 PsLoadedModuleList = 0xfffff805`0ae2a2f0

    Debug session time: Sat Jan 30 17:21:23.879 2021 UTC - 8:00

    System Uptime: 0 days 0:37:28.508

    Loading Kernel Symbols

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

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

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

    Loading User Symbols

    PEB address is NULL !

    Loading unloaded module list

    .......

    For analysis of this file, run !analyze -v

    4: kd> !analyze -v

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

    * *

    * Bugcheck Analysis *

    * *

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



    UNEXPECTED_STORE_EXCEPTION 154

    The store component caught an unexpected exception.

    Arguments:

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

    Arg2: fffff483573b6d50, Exception information

    Arg3: 0000000000000002, Reserved

    Arg4: 0000000000000000, Reserved



    Debugging Details:

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





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 2



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-ECC9K94



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 2



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 69



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 154



    BUGCHECK_P1: ffffc481110f8000



    BUGCHECK_P2: fffff483573b6d50



    BUGCHECK_P3: 2



    BUGCHECK_P4: 0



    EXCEPTION_RECORD: fffff483573b7cd8 -- .exr 0xfffff483573b7cd8

    ExceptionAddress: fffff8050a4f49e0 nt!RtlDecompressBufferXpressLz+0x0000000000000050

    ExceptionCode: c0000006 In-page I/O error

    ExceptionFlags: 00000000

    NumberParameters: 3

    Parameter[0]: 0000000000000000

    Parameter[1]: 00000267ae4a8ac0

    Parameter[2]: 00000000c00000c0

    Inpage operation failed at 00000267ae4a8ac0, due to I/O error 00000000c00000c0



    EXCEPTION_PARAMETER1: 0000000000000000



    EXCEPTION_PARAMETER2: 00000267ae4a8ac0



    CONTEXT: fffff483573b7510 -- .cxr 0xfffff483573b7510

    rax=fffff8050a4f4990 rbx=ffffaa0191d77000 rcx=ffffaa0191d77000

    rdx=ffffaa0191d77000 rsi=0000000000000002 rdi=00000267ae4a8ac0

    rip=fffff8050a4f49e0 rsp=fffff483573b7f18 rbp=00000267ae4a911d

    r8=00000267ae4a8ac0 r9=00000000000006b3 r10=ffffaa0191d77ea0

    r11=00000267ae4a9173 r12=fffff483573b8188 r13=ffffc48102f31000

    r14=ffffaa0191d78000 r15=0000000000000000

    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:

    fffff805`0a4f49e0 418b08 mov ecx,dword ptr [r8] ds:002b:00000267`ae4a8ac0=????????

    Resetting default scope



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    PROCESS_NAME: MemCompression



    IO_ERROR: NTSTATUS 0xc00000c0 - This device does not exist.



    EXCEPTION_STR: 0xc0000006_c00000c0



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



    STACK_TEXT:

    fffff483`573b6c98 fffff805`0a793f5e : 00000000`00000154 ffffc481`110f8000 fffff483`573b6d50 00000000`00000002 : nt!KeBugCheckEx

    fffff483`573b6ca0 fffff805`0a60ee36 : ffffc481`110f8000 fffff483`573b6d50 fffff483`00000002 fffff483`573b6e00 : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x7e

    fffff483`573b6cf0 fffff805`0a5cbf32 : fffff805`00000002 fffff805`0a2d1244 fffff483`573b3000 fffff483`573b9000 : nt!`SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue'::`1'::filt$0+0x22

    fffff483`573b6d20 fffff805`0a5fe642 : fffff805`0a2d1244 fffff483`573b7300 fffff805`0a5cbe90 00000000`00000000 : nt!_C_specific_handler+0xa2

    fffff483`573b6d90 fffff805`0a52bf97 : fffff483`573b7300 00000000`00000000 fffff483`573b81e0 fffff805`0a4c3359 : nt!RtlpExecuteHandlerForException+0x12

    fffff483`573b6dc0 fffff805`0a52ab86 : fffff483`573b7cd8 fffff483`573b7a10 fffff483`573b7cd8 00000267`ae4a8ac0 : nt!RtlDispatchException+0x297

    fffff483`573b74e0 fffff805`0a6078ac : ffffc481`0f29e7c0 fffff805`0a5540e6 00000000`00010000 fffff483`573b7d80 : nt!KiDispatchException+0x186

    fffff483`573b7ba0 fffff805`0a603a43 : fffff483`573b8ad8 fffff483`573b8ae0 fffff483`573b8ae8 fffff483`573b8af0 : nt!KiExceptionDispatch+0x12c

    fffff483`573b7d80 fffff805`0a4f49e0 : ffffaa01`91d77000 ffffc481`110f8050 fffff805`0a4c42d0 ffffaa01`91d77000 : nt!KiPageFault+0x443

    fffff483`573b7f18 fffff805`0a4c42d0 : ffffaa01`91d77000 ffffaa01`91d77000 00000000`00000002 00000267`ae4a8ac0 : nt!RtlDecompressBufferXpressLz+0x50

    fffff483`573b7f30 fffff805`0a4c4018 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlDecompressBufferEx+0x60

    fffff483`573b7f80 fffff805`0a4c3ea5 : 00000000`00000004 fffff805`0a4c3a0e 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x150

    fffff483`573b8040 fffff805`0a4c36dc : 00000000`00000001 00000000`00008ac0 ffffc481`110f8000 ffffc481`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5

    fffff483`573b8090 fffff805`0a4c350c : 00000000`ffffffff ffffc481`02f31000 fffff483`573b8170 ffffc481`15ef4e90 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180

    fffff483`573b8130 fffff805`0a4c3359 : ffffaa01`8f2ed730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8

    fffff483`573b81e0 fffff805`0a4c3211 : ffffc481`110f8000 ffffc481`15ef4e90 ffffc481`02f31000 ffffc481`110f99c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85

    fffff483`573b8260 fffff805`0a554488 : ffffc481`133ad040 ffffc481`110f8000 00000000`00000000 ffffc481`131f9a70 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21

    fffff483`573b8290 fffff805`0a50a337 : fffff805`0a4c31f0 fffff483`573b8330 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78

    fffff483`573b8300 fffff805`0a43e0b4 : fffff483`573b8400 00000000`31526d73 00000000`000003ff fffff805`0af229c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7

    fffff483`573b83d0 fffff805`0a43dae8 : 00000000`0000000c 00000000`000003ff fffff483`573b8480 fffff805`0af229c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac

    fffff483`573b8420 fffff805`0a509597 : 00000000`0000000c 00000000`00000001 ffffc481`15ef4e90 ffffc481`131f9a70 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0

    fffff483`573b84b0 fffff805`0a51d34b : ffffc481`00000001 ffffc481`131f9b30 00000000`00000000 ffffc481`110f8000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167

    fffff483`573b8520 fffff805`0a4b6f60 : fffff483`00000100 00000000`00000000 fffff483`573b8778 fffff805`0a4b4eb0 : nt!SmPageRead+0x33

    fffff483`573b8570 fffff805`0a4b4a0d : 00000000`00000002 fffff483`573b8600 fffff483`573b8778 ffffc481`131f9a20 : nt!MiIssueHardFaultIo+0x10c

    fffff483`573b85c0 fffff805`0a40c9c8 : 00000000`c0033333 00000000`00000000 ffff950e`87d300e0 00000000`00000000 : nt!MiIssueHardFault+0x29d

    fffff483`573b8680 fffff805`0a60395e : 00000000`c0000016 00000000`00000002 00000000`00000000 00000000`00000002 : nt!MmAccessFault+0x468

    fffff483`573b8820 fffff805`0a82ae4e : fffff483`573b8b80 fffff805`0a5fc744 00000000`ffffffff 00000001`00000000 : nt!KiPageFault+0x35e

    fffff483`573b89b0 fffff805`0a82ad3e : ffffc481`134e3080 00000000`00000002 ffffc481`006c2a60 00000000`00000001 : nt!ObpReferenceObjectByHandleWithTag+0xfe

    fffff483`573b8a40 fffff805`0a7fadf0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x2e

    fffff483`573b8a90 fffff805`0a6071b8 : ffffc481`133ad040 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtSetEvent+0x90

    fffff483`573b8b00 00007ff9`1820c174 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

    00000075`02f8f188 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`1820c174





    MODULE_NAME: hardware_disk



    IMAGE_NAME: hardware_disk



    STACK_COMMAND: .thread ; .cxr ; kb



    FAILURE_BUCKET_ID: 0x154_c0000006_c00000c0_IMAGE_hardware_disk



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {0cc645b8-fadc-9b56-35ff-9f2a52cbe856}



    Followup: MachineOwner

    ---------

    :)
     
    ChristopherScroggins1, Jan 30, 2021
    #1
  2. LUDDE_PUDDE
    Ludde_Pudde Win User

    hardware_disk bsod

    Hi I just reset my computer because i was having bsods. After i had reset my pc the errors that i had stopped. But now i am getting a new bsod screen but not as often it is just when i play a certain game. In the minidump it says hardware_disk. So I was
    wondering if anyone could help me with that. My specs are:

    CPU:Intel Core i5 7400

    Motherboard: AsusTek Computer INC. Model: G11CD-K

    RAM: DDR4 two sticks with 8GB

    GPU: NVIDIA GeForce GTX 1060 3GB

    Minidump: https://we.tl/t-DTg8DLbhNo
     
    Ludde_Pudde, Jan 30, 2021
    #2
  3. KERNEL-PANIC
    Kernel-Panic Win User
    hardware_disk bsod

    The minidump points to ntoskrnl.exe which is the Windows NT OS kernel. This can be a hardware or software issue, but it is best to rule out the drivers first, then look at hardware related errors.

    This guide has a comprehensive list of tests to do to isolate the issue and if followed should figure out whether it is a an issue with faulty ram or hard drive, or if it is as simple as updating the drivers. Unfortunately you could be looking at a faulty ram
    stick or a failing hard drive, and very rarely a bad capacitor on the motherboard, but take it all one step at a time and see if the issue is easily fixable

    https://www.auslogics.com/en/articles/fix-ntosk...
     
    Kernel-Panic, Jan 30, 2021
    #3
  4. ZKITZO
    Zkitzo Win User

    help with NTDLL and Hardware_Disk BSOD

    BSOD - UNEXPECTED_STORE_EXCEPTION - 0x154 - MODULE_NAME hardware_disk

    My PC crashed twice today, both times about 5 minutes after playing The Division 2.

    First dump: 052319-61843-01.dmp

    Second dump: 052419-59812-01.dmp

    I did a `!analyze -v` on the dumps and both show `MODULE_NAME hardware_disk`

    Could someone please give me some more insight on the BSOD's?
     
    Zkitzo, Jan 30, 2021
    #4
Thema:

help with NTDLL and Hardware_Disk BSOD

Loading...

  1. help with NTDLL and Hardware_Disk BSOD - Similar Threads - help NTDLL Hardware_Disk

  2. Kernel32DLL and ntdll crashing games

    in Windows 10 BSOD Crashes and Debugging
    Kernel32DLL and ntdll crashing games: hello,recently most of my games kept crashing and these 2 errors kept popping upthis happens few weeks ago but the problem just suddenly gone and now its back and what started this issue is battlefield 2042i uninstalled battlefield 2042 and deleted everything related to it...

  3. Kernel32DLL and ntdll crashing games

    in Windows 10 Gaming
    Kernel32DLL and ntdll crashing games: hello,recently most of my games kept crashing and these 2 errors kept popping upthis happens few weeks ago but the problem just suddenly gone and now its back and what started this issue is battlefield 2042i uninstalled battlefield 2042 and deleted everything related to it...

  4. Kernel32DLL and ntdll crashing games

    in Windows 10 Software and Apps
    Kernel32DLL and ntdll crashing games: hello,recently most of my games kept crashing and these 2 errors kept popping upthis happens few weeks ago but the problem just suddenly gone and now its back and what started this issue is battlefield 2042i uninstalled battlefield 2042 and deleted everything related to it...

  5. hardware_disk bsod unexpected store exception

    in Windows 10 BSOD Crashes and Debugging
    hardware_disk bsod unexpected store exception: Hi I used to experience bsod a lot unexpected store exception or critical process died and i did a lot of things to stop the bsod. I have reinstalled windows like 6 times because after a lot of bsods I encounter automatic repair loop. I also did different fixes that I saw...

  6. hardware_disk bsod

    in Windows 10 BSOD Crashes and Debugging
    hardware_disk bsod: Hi I just reset my computer because i was having bsods. After i had reset my pc the errors that i had stopped. But now i am getting a new bsod screen but not as often it is just when i play a certain game. In the minidump it says hardware_disk. So I was wondering if anyone...

  7. ntdll crash

    in Windows 10 BSOD Crashes and Debugging
    ntdll crash: hi, ntdll.dll crash with this:' Felet uppstod i programmet med namn: SilverFast 8.exe, version 8.8.0.18, tidsstämpel 0x5dfa0415 , felet uppstod i modulen med namn: ntdll.dll, version 10.0.18362.418, tidsstämpel 0x99ca0526 Undantagskod: 0xc0000374 Felförskjutning:...

  8. Bluescreen on Windows 10 - hardware_disk

    in Windows 10 BSOD Crashes and Debugging
    Bluescreen on Windows 10 - hardware_disk: Hello forum, i'm facing a bluescreen issue very often, i did re install the windows with the latest windows update, still getting the issue, i have analyzed the blue screen dump, i'm not able to read it, whether it is related to HW failure or drivers Thanks,...

  9. BSOD - UNEXPECTED_STORE_EXCEPTION - 0x154 - MODULE_NAME hardware_disk

    in Windows 10 BSOD Crashes and Debugging
    BSOD - UNEXPECTED_STORE_EXCEPTION - 0x154 - MODULE_NAME hardware_disk: My PC crashed twice today, both times about 5 minutes after playing The Division 2. First dump: https://1drv.ms/u/s!AsyoGgY7l748mWMqQUWXkQDUBRG- Second dump: https://1drv.ms/u/s!AsyoGgY7l748mWTj5c1u-mXxCfDE I did a `!analyze -v` on the dumps and both show `MODULE_NAME...

  10. NTDLL crash

    in Windows 10 Customization
    NTDLL crash: Hey, Since a few weeks I experience crash-to-desktops for different software. The relevant program starts up and closes after about 2-10 seconds after which I see the desktop. No error message appears. When I look at "Windows Logs" the crash would have to do with the...