📎 AI Summary:
The forum thread discusses a Windows 10 laptop experiencing crashes with the "unexpected store exception" error, likely related to hardware or drive issues. The original poster provides diagnostic results, and responders suggest potential causes such as a failing hard drive or outdated drivers, recommending scans like sfc, chkdsk, and hardware tests. Overall, the contributors offer technical advice aimed at diagnosing and resolving system stability problems linked to hardware or storage components.
The forum thread discusses a Windows 10 laptop experiencing crashes with the "unexpected store exception" error, likely related to hardware or drive issues. The original poster provides diagnostic results, and responders suggest potential causes such as a failing hard drive or outdated drivers, recommending scans like sfc, chkdsk, and hardware tests. Overall, the contributors offer technical advice aimed at diagnosing and resolving system stability problems linked to hardware or storage components.
Solution
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 154, {ffff94867f6e5000, fffffc0993b85f90, 2, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_disk
Followup: MachineOwneryou normally see this bugcheck after a driver update or similar. If it's something like your audio driver then usually entering Device manager and rolling back the driver can help.
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
Code:
PRIMARY_PROBLEM_CLASS: 0x154_c0000006_c000000e_IMAGE_hardware_diskVSTwindrvr6.sys Fri Jul 4 08:28:01 2008: Jungo Win Driver Device Driver. Check for updates:
Jungo Connectivity | WinDriver Support
I also checked your support page for updated drivers over at Samsung and for some reason I can't find them at all.
Notebook 9 Spin | Official Samsung Support
Try checking the drive by running a chkdsk
Link Removed
This could indicate there is an issue with your hard drive or your page file being corrupt below. I would recommend running a fitness test on your hard drive. Seagate SeaTools work pretty well for this.
You may also want to test your memory with Mem86+
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_STORE_EXCEPTION (154)
The store component caught an unexpected exception.
Arguments:
Arg1: ffff94867f6e5000, Pointer to the store context or data manager
Arg2: fffffc0993b85f90, Exception information
Arg3: 0000000000000002, Reserved
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.16299.248 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
SYSTEM_PRODUCT_NAME: 940X3L
SYSTEM_SKU: ATIV A5A5-A5A5-A5A5-A5A5-A5A5-A5A5
SYSTEM_VERSION: P08AFD
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P08AFD.053.160311.PS
BIOS_DATE: 03/11/2016
BASEBOARD_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
BASEBOARD_PRODUCT: NP940X3L-K01US
BASEBOARD_VERSION: SGL8658A07-C01-G001-S0001+10.0.10586
DUMP_TYPE: 2
BUGCHECK_P1: ffff94867f6e5000
BUGCHECK_P2: fffffc0993b85f90
BUGCHECK_P3: 2
BUGCHECK_P4: 0
EXCEPTION_RECORD: fffffc0993b86ed8 -- (.exr 0xfffffc0993b86ed8)
ExceptionAddress: fffff8014bee4ef3 (nt!RtlDecompressBufferXpressLz+0x0000000000000043)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 00000000116be810
Parameter[2]: 00000000c000000e
Inpage operation failed at 00000000116be810, due to I/O error 00000000c000000e
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+43
fffff801`4bee4ef3 458b08 mov r9d,dword ptr [r8]
FOLLOWUP_IP:
+0
00000000`116be810 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000116be810
CONTEXT: fffffc0993b86720 -- (.cxr 0xfffffc0993b86720)
rax=fffffc0993b87128 rbx=ffff80003d981ea0 rcx=ffff80003d981000
rdx=0000000000001000 rsi=00000000116be810 rdi=ffff80003d981000
rip=fffff8014bee4ef3 rsp=fffffc0993b87118 rbp=0000000000000000
r8=00000000116be810 r9=00000000000001e2 r10=00000000116be9f2
r11=00000000116be99c r12=00000000116be810 r13=ffff948683022000
r14=ffff80003d982000 r15=ffff80003d981000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!RtlDecompressBufferXpressLz+0x43:
fffff801`4bee4ef3 458b08 mov r9d,dword ptr [r8] ds:002b:00000000`116be810=????????
Resetting default scope
CPU_COUNT: 4
CPU_MHZ: a20
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 4e
CPU_STEPPING: 3
CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: BA'00000000 (cache) BA'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MemCompression
CURRENT_IRQL: 0
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
IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
EXCEPTION_STR: 0xc0000006_c000000e
BUGCHECK_STR: 0x154_c0000006_c000000e
ANALYSIS_SESSION_HOST: PMILJUDAVISX2
ANALYSIS_SESSION_TIME: 03-09-2018 14:12:53.0747
ANALYSIS_VERSION: 10.0.16299.91 amd64fre
STACK_TEXT:
fffffc09`93b85ed8 fffff801`4bef4992 : 00000000`00000154 ffff9486`7f6e5000 fffffc09`93b85f90 00000000`00000002 : nt!KeBugCheckEx
fffffc09`93b85ee0 fffff801`4bef3781 : ffff9486`7f6e5000 fffffc09`93b85f90 fffff801`00000002 fffffc09`93b860a0 : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x7e
fffffc09`93b85f30 fffff801`4bde208f : fffff801`00000002 00000000`00000000 fffffc09`93b81000 fffffc09`93b88000 : nt!`SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue'::`1'::filt$0+0x1f
fffffc09`93b85f60 fffff801`4be0d13d : 00000000`00000000 fffffc09`93b86100 fffffc09`93b86ed8 fffff801`0acc2968 : nt!_C_specific_handler+0x9f
fffffc09`93b85fd0 fffff801`4bd32a50 : 00000000`00000000 fffffc09`93b86ed8 ff001dec`00000002 1d8d4c00`0e95c315 :
...
...
...
THREAD_SHA1_HASH_MOD_FUNC: be91335f728989fad5a9a5641f89ffee7fe3c14c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1e8b5dbdbeb5ae6b90df170fda79a54fb9f91b21
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_c000000e_IMAGE_hardware_disk
...
...
...
FAILURE_ID_HASH_STRING: km:0x154_c0000006_c000000e_image_hardware_disk
FAILURE_ID_HASH: {6ef1f8aa-ba96-513b-39a6-be53976d18b0}
3: kd> .exr fffffc0993b85f90
ExceptionAddress: fffffc0993b865c0
ExceptionCode: 93b86ed8
ExceptionFlags: fffffc09
NumberParameters: 0
3: kd> .exr fffffc0993b865c0
ExceptionAddress: fffff8014befb2cc (nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x0000000000000270)
ExceptionCode: 00000007
ExceptionFlags: 00000000
NumberParameters: 1271459840
Parameter[0]: fffff8014c056f48
....
You may also want to test your memory with Mem86+
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_STORE_EXCEPTION (154)
The store component caught an unexpected exception.
Arguments:
Arg1: ffff94867f6e5000, Pointer to the store context or data manager
Arg2: fffffc0993b85f90, Exception information
Arg3: 0000000000000002, Reserved
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.16299.248 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
SYSTEM_PRODUCT_NAME: 940X3L
SYSTEM_SKU: ATIV A5A5-A5A5-A5A5-A5A5-A5A5-A5A5
SYSTEM_VERSION: P08AFD
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P08AFD.053.160311.PS
BIOS_DATE: 03/11/2016
BASEBOARD_MANUFACTURER: SAMSUNG ELECTRONICS CO., LTD.
BASEBOARD_PRODUCT: NP940X3L-K01US
BASEBOARD_VERSION: SGL8658A07-C01-G001-S0001+10.0.10586
DUMP_TYPE: 2
BUGCHECK_P1: ffff94867f6e5000
BUGCHECK_P2: fffffc0993b85f90
BUGCHECK_P3: 2
BUGCHECK_P4: 0
EXCEPTION_RECORD: fffffc0993b86ed8 -- (.exr 0xfffffc0993b86ed8)
ExceptionAddress: fffff8014bee4ef3 (nt!RtlDecompressBufferXpressLz+0x0000000000000043)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 00000000116be810
Parameter[2]: 00000000c000000e
Inpage operation failed at 00000000116be810, due to I/O error 00000000c000000e
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+43
fffff801`4bee4ef3 458b08 mov r9d,dword ptr [r8]
FOLLOWUP_IP:
+0
00000000`116be810 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000116be810
CONTEXT: fffffc0993b86720 -- (.cxr 0xfffffc0993b86720)
rax=fffffc0993b87128 rbx=ffff80003d981ea0 rcx=ffff80003d981000
rdx=0000000000001000 rsi=00000000116be810 rdi=ffff80003d981000
rip=fffff8014bee4ef3 rsp=fffffc0993b87118 rbp=0000000000000000
r8=00000000116be810 r9=00000000000001e2 r10=00000000116be9f2
r11=00000000116be99c r12=00000000116be810 r13=ffff948683022000
r14=ffff80003d982000 r15=ffff80003d981000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!RtlDecompressBufferXpressLz+0x43:
fffff801`4bee4ef3 458b08 mov r9d,dword ptr [r8] ds:002b:00000000`116be810=????????
Resetting default scope
CPU_COUNT: 4
CPU_MHZ: a20
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 4e
CPU_STEPPING: 3
CPU_MICROCODE: 6,4e,3,0 (F,M,S,R) SIG: BA'00000000 (cache) BA'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MemCompression
CURRENT_IRQL: 0
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
IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
EXCEPTION_STR: 0xc0000006_c000000e
BUGCHECK_STR: 0x154_c0000006_c000000e
ANALYSIS_SESSION_HOST: PMILJUDAVISX2
ANALYSIS_SESSION_TIME: 03-09-2018 14:12:53.0747
ANALYSIS_VERSION: 10.0.16299.91 amd64fre
STACK_TEXT:
fffffc09`93b85ed8 fffff801`4bef4992 : 00000000`00000154 ffff9486`7f6e5000 fffffc09`93b85f90 00000000`00000002 : nt!KeBugCheckEx
fffffc09`93b85ee0 fffff801`4bef3781 : ffff9486`7f6e5000 fffffc09`93b85f90 fffff801`00000002 fffffc09`93b860a0 : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x7e
fffffc09`93b85f30 fffff801`4bde208f : fffff801`00000002 00000000`00000000 fffffc09`93b81000 fffffc09`93b88000 : nt!`SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue'::`1'::filt$0+0x1f
fffffc09`93b85f60 fffff801`4be0d13d : 00000000`00000000 fffffc09`93b86100 fffffc09`93b86ed8 fffff801`0acc2968 : nt!_C_specific_handler+0x9f
fffffc09`93b85fd0 fffff801`4bd32a50 : 00000000`00000000 fffffc09`93b86ed8 ff001dec`00000002 1d8d4c00`0e95c315 :
...
...
...
THREAD_SHA1_HASH_MOD_FUNC: be91335f728989fad5a9a5641f89ffee7fe3c14c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1e8b5dbdbeb5ae6b90df170fda79a54fb9f91b21
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_c000000e_IMAGE_hardware_disk
...
...
...
FAILURE_ID_HASH_STRING: km:0x154_c0000006_c000000e_image_hardware_disk
FAILURE_ID_HASH: {6ef1f8aa-ba96-513b-39a6-be53976d18b0}
3: kd> .exr fffffc0993b85f90
ExceptionAddress: fffffc0993b865c0
ExceptionCode: 93b86ed8
ExceptionFlags: fffffc09
NumberParameters: 0
3: kd> .exr fffffc0993b865c0
ExceptionAddress: fffff8014befb2cc (nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x0000000000000270)
ExceptionCode: 00000007
ExceptionFlags: 00000000
NumberParameters: 1271459840
Parameter[0]: fffff8014c056f48
....
