Share via

Bluescreen on Windows 10 - hardware_disk

Anonymous
2019-08-07T08:09:26+00:00

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,

Microsoft (R) Windows Debugger Version 10.0.18362.1 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\080719-7125-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

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

Response                         Time (ms)     Location

Deferred                                       cache*c:\myCache

Deferred                                       SRV*https://msdl.microsoft.com/download/symbols

Symbol search path is: cache*c:\myCache;SRV*https://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 18362 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff80207000000 PsLoadedModuleList = 0xfffff80207446450

Debug session time: Wed Aug  7 10:37:33.718 2019 (UTC + 4:00)

System Uptime: 0 days 11:53:44.303

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 !analyze -v

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

Response                         Time (ms)     Location

Deferred                                       cache*c:\myCache

Deferred                                       SRV*https://msdl.microsoft.com/download/symbols

3: kd> .reload

Loading Kernel Symbols

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

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

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

.....

Loading User Symbols

Loading unloaded module list

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

3: kd> !analyze -v

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

UNEXPECTED_STORE_EXCEPTION (154)

The store component caught an unexpected exception.

Arguments:

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

Arg2: fffff18fed2b5f00, Exception information

Arg3: 0000000000000002, Reserved

Arg4: 0000000000000000, Reserved

Debugging Details:

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  20FCS0E80L

SYSTEM_SKU:  LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th

SYSTEM_VERSION:  ThinkPad X1 Carbon 4th

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  N1FET69W (1.43 )

BIOS_DATE:  05/22/2019

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  20FCS0E80L

BASEBOARD_VERSION:  Not Defined

DUMP_TYPE:  2

BUGCHECK_P1: ffff8d0c77bf2000

BUGCHECK_P2: fffff18fed2b5f00

BUGCHECK_P3: 2

BUGCHECK_P4: 0

EXCEPTION_RECORD:  fffff18fed2b6ea8 -- (.exr 0xfffff18fed2b6ea8)

ExceptionAddress: fffff8020715d6e0 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)

ExceptionCode: c0000006 (In-page I/O error)

ExceptionFlags: 00000000

NumberParameters: 3

Parameter[0]: 0000000000000000

Parameter[1]: 0000021ec631bd10

Parameter[2]: 00000000c00000a3

Inpage operation failed at 0000021ec631bd10, due to I/O error 00000000c00000a3

EXCEPTION_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.

FAULTING_IP:

nt!RtlDecompressBufferXpressLz+50

fffff802`0715d6e0 418b08          mov     ecx,dword ptr [r8]

FOLLOWUP_IP:

+0

0000021e`c631bd10 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000021ec631bd10

CONTEXT:  fffff18fed2b66f0 -- (.cxr 0xfffff18fed2b66f0)

rax=fffff8020715d690 rbx=0000000000000000 rcx=ffffde8192b7e000

rdx=ffffde8192b7e000 rsi=0000000000000002 rdi=0000021ec631bd10

rip=fffff8020715d6e0 rsp=fffff18fed2b70e8 rbp=ffffde8192b7e000

r8=0000021ec631bd10  r9=0000000000000175 r10=ffffde8192b7eea0

r11=0000021ec631be85 r12=fffff18fed2b7378 r13=ffff8d0c7a9cb000

r14=0000021ec631be2f r15=ffffde8192b7f000

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+0x50:

fffff8020715d6e0 418b08          mov     ecx,dword ptr [r8] ds:002b:0000021ec631bd10=????????

Resetting default scope

CPU_COUNT: 4

CPU_MHZ: af8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4e

CPU_STEPPING: 3

CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: CC'00000000 (cache) CC'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MemCompression

CURRENT_IRQL:  0

IO_ERROR: (NTSTATUS) 0xc00000a3 - {Drive Not Ready}  The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed.

EXCEPTION_STR:  0xc0000006_c00000a3

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

BUGCHECK_STR:  0x154_c0000006_c00000a3

ANALYSIS_SESSION_HOST:  LAPTOP-UM0QM7BJ

ANALYSIS_SESSION_TIME:  08-07-2019 11:47:16.0408

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_TEXT:

fffff18fed2b5e48 fffff8020732074a : 0000000000000154 ffff8d0c77bf2000 fffff18fed2b5f00 0000000000000002 : nt!KeBugCheckEx

fffff18fed2b5e50 fffff802071d9bde : ffff8d0c77bf2000 fffff18fed2b5f00 ffffb7e600000002 0000000000000000 : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x7e

fffff18fed2b5ea0 fffff8020719b439 : fffff18f00000002 fffff18fed2b73d0 fffff18fed2b1000 fffff18fed2b8000 : nt!SMKM_STORE&lt;SM_TRAITS&gt;::SmStDirectReadIssue'::1'::filt$0+0x22

fffff18fed2b5ed0 fffff802071c8aef : fffff18fed2b73d0 fffff18fed2b64b0 0000000000000000 000000000010001f : nt!_C_specific_handler+0xa9

fffff18fed2b5f40 fffff802070c2df5 : 0000000000000000 0000000000000000 fffff18fed2b64b0 00007fffffff0000 : nt!RtlpExecuteHandlerForException+0xf

fffff18fed2b5f70 fffff802070c738e : fffff18fed2b6ea8 fffff18fed2b6bf0 fffff18fed2b6ea8 0000021ec631bd10 : nt!RtlDispatchException+0x4a5

fffff18fed2b66c0 fffff802071d1c1d : ffff8d0c77bf4600 fffff8020708678d 0000000000002000 fffff18fed2b6f50 : nt!KiDispatchException+0x16e

fffff18fed2b6d70 fffff802071cde05 : 0000000000000000 0000000000000000 fffff18fed2b7378 0000000000000000 : nt!KiExceptionDispatch+0x11d

fffff18fed2b6f50 fffff8020715d6e0 : ffffde8192b7e000 ffff8d0c77bf2050 fffff8020705caf0 ffffde8192b7e000 : nt!KiPageFault+0x445

fffff18fed2b70e8 fffff8020705caf0 : ffffde8192b7e000 ffffde8192b7e000 0000000000000002 0000021ec631bd10 : nt!RtlDecompressBufferXpressLz+0x50

fffff18fed2b7100 fffff8020715f469 : 0000000000000000 fffff80200000001 0000000000000000 ffff8d0c77bf3788 : nt!RtlDecompressBufferEx+0x60

fffff18fed2b7150 fffff8020715f2f4 : 0000000000000004 fffff18fed2b7360 0000000000000000 00000000000000af : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x155

fffff18fed2b7230 fffff8020715f172 : 0000000000000001 000000000000bd10 ffff8d0c0000bd10 ffff8d0c00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0

fffff18fed2b7280 fffff8020715ef9b : 00000000ffffffff ffff8d0c7a9cb000 fffff18fed2b7360 ffff8d0c804e67d0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186

fffff18fed2b7320 fffff8020715ede1 : ffff8d0c7a9cb000 0000000000000000 0000000000000001 ffff8d0c77bf3788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xcb

fffff18fed2b73d0 fffff8020715ecf1 : ffff8d0c77bf2000 ffff8d0c804e67d0 ffff8d0c7a9cb000 ffff8d0c77bf39b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85

fffff18fed2b7450 fffff80207069918 : ffff8d0c798c4080 ffff8d0c77bf2000 0000000000000000 0000000000000000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21

fffff18fed2b7480 fffff80207162251 : fffff8020715ecd0 fffff18fed2b7530 0000000000000003 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78

fffff18fed2b74f0 fffff8020714aee1 : fffff18fed2b75f0 fffff8020758bb78 ffff8d0c77bf2000 fffff18fed2b7740 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcd

fffff18fed2b75c0 fffff8020714aac7 : 000000000000000c ffff8d0c77bf2000 fffff18fed2b7670 ffff8d0c804e67d0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a5

fffff18fed2b7610 fffff80207161563 : 000000000000000c ffff8d0c804e67d0 0000000000000001 0000000000000001 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbf

fffff18fed2b76a0 fffff80207162c3f : ffff8d0c00000001 ffff8d0c7e8cfc00 0000000000000000 ffff8d0c77bf2000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167

fffff18fed2b7710 fffff8020708db5b : ffff8d0c7817d580 0000000000000001 ffff8d0c7817d640 fffff802070749e6 : nt!SmPageRead+0x33

fffff18fed2b7760 fffff8020708d259 : 0000000000000002 fffff18fed2b77f0 fffff18fed2b7958 ffffb7dbdffef7a8 : nt!MiIssueHardFaultIo+0x117

fffff18fed2b77b0 fffff80207072a9b : 00000000c0033333 0000000000000001 00007ffbdeb17d30 000000334a3ff260 : nt!MiIssueHardFault+0x489

fffff18fed2b7860 fffff802071cdd20 : ffff8d0c00000000 fffff18f00000001 0000000000000001 fffff18fed2b7a80 : nt!MmAccessFault+0x40b

fffff18fed2b7a00 00007ffbdea94366 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x360

000000334a3ff030 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`dea94366

THREAD_SHA1_HASH_MOD_FUNC:  be91335f728989fad5a9a5641f89ffee7fe3c14c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  284d6f66330e36aa06844fea7f04f02730e9e11d

THREAD_SHA1_HASH_MOD:  901685eb5ed44e617e07e22622321d209483595d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x154_c0000006_c00000a3_IMAGE_hardware_disk

BUCKET_ID:  0x154_c0000006_c00000a3_IMAGE_hardware_disk

PRIMARY_PROBLEM_CLASS:  0x154_c0000006_c00000a3_IMAGE_hardware_disk

TARGET_TIME:  2019-08-07T06:37:33.000Z

OSBUILD:  18362

OSSERVICEPACK:  267

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  2032-02-15 13:16:10

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  3acb8

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x154_c0000006_c00000a3_image_hardware_disk

FAILURE_ID_HASH:  {0eae7fa6-c488-d80f-fffd-8617d2ef2750}

Followup:     MachineOwner

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Vijay A. Verma 104.9K Reputation points Volunteer Moderator
2019-08-07T10:31:07+00:00

A. Analysis Results

080519-6906-01.dmp

CRITICAL_PROCESS_DIED (ef)

IMAGE_NAME: ntkrnlmp.exe

*** WARNING: Unable to verify timestamp for dump_iaStorAC.sys

080719-6890-01.dmp

CRITICAL_PROCESS_DIED (ef)

IMAGE_NAME: ntkrnlmp.exe

*** WARNING: Unable to verify timestamp for dump_iaStorAC.sys

080719-7125-01.dmp

UNEXPECTED_STORE_EXCEPTION (154)

IMAGE_NAME: hardware_disk

*** WARNING: Unable to verify timestamp for dump_iaStorAC.sys

B. Third Party Drivers

dump_iaStorAC.sys - Intel RST Driver

Driver date - Tue Mar 20 03:03:43 2018

C. Recommendations

A. Create a system restore point so that if something wrong happens you can revert.

Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

B. Download latest driver Intel RST driver from and install https://downloadcenter.intel.com/download/27984...

Download SetupRST.exe

Disclaimer - This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Was this answer helpful?

1 person found this answer helpful.
0 comments

9 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-08-07T08:22:38+00:00

    Thanks a lot

    Dump files are uploaded 

    https://1drv.ms/u/s!Ai8K67U8Pf8JgsEV1-iE7g4SmMIMjQ?e=yCZX5F

    regards,

    Mohammad Al-Masri

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-07T08:18:04+00:00

    Hello Vijay,

    Thanks a lot,

    here you go

    https://1drv.ms/u/s!Ai8K67U8Pf8JgsEV1-iE7g4SmMIMjQ?e=yCZX5F

    Thanks,

    Mohammad Al-Masri

    Was this answer helpful?

    0 comments
  3. Sumit D - IA 170.7K Reputation points Independent Advisor
    2019-08-07T08:15:21+00:00

    Hi,

    I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.

    We need log files(called dump files) that tell us what lead to crash.

    Please share them with us for a better analysis of the problem. Instructions can be found here:

    https://answers.microsoft.com/en-us/windows/for...

    Please let us know if you need any assistance about posting dump files.

    Was this answer helpful?

    0 comments
  4. Vijay A. Verma 104.9K Reputation points Volunteer Moderator
    2019-08-07T08:11:00+00:00

    Hi Al-Masri

    I am Vijay, an Independent Advisor. I am here to work with you on this problem.

    To know what exactly is causing the crashes, I need to analyze minidumps generated by crashes with WinDBG. WinDBG is the only tool which can do end to end complete analysis of ..dmp files generated by BSOD (Blue screen of death).

    Go to C:\Windows\Minidump

    Zip the contents of the folder corresponding to date and time of your crashes.

    Upload the content to Onedrive or any other file sharing site for me to locate the problem.

    If you are uploading Memory.dmp also, please upload it separately as the size of memory dump is very large.

    Do let me know if you have any more question or require further help.

    Was this answer helpful?

    0 comments