Question BSOD help please...

[croat25]

Hello, my rig is pretty new, and I started to experience BSOD lately with 154 UNEXPECTED STORE EXCEPTION error.

Here is my dump file :

Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Korisnik\Desktop\072419-17171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff803732b9000 PsLoadedModuleList = 0xfffff803736d4670
Debug session time: Wed Jul 24 15:58:55.320 2019 (UTC + 2:00)
System Uptime: 10 days 17:28:28.000
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
11: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

UNEXPECTED_STORE_EXCEPTION (154)
The store component caught an unexpected exception.
Arguments:
Arg1: ffff810bb8b85000, Pointer to the store context or data manager
Arg2: fffff20bccb1c420, 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: 17763.1.amd64fre.rs5_release.180914-1434

DUMP_TYPE: 2

BUGCHECK_P1: ffff810bb8b85000

BUGCHECK_P2: fffff20bccb1c420

BUGCHECK_P3: 2

BUGCHECK_P4: 0

EXCEPTION_RECORD: fffff20bccb1d3c8 -- (.exr 0xfffff20bccb1d3c8)
ExceptionAddress: fffff80373407660 (nt!RtlDecompressBufferXpressLz+0x0000000000000040)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 000001ea002a02f0
Parameter[2]: 00000000c000000e
Inpage operation failed at 000001ea002a02f0, 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+40
fffff80373407660 418b00 mov eax,dword ptr [r8] FOLLOWUP_IP: +0 000001ea002a02f0 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000001ea002a02f0

CONTEXT: fffff20bccb1cc10 -- (.cxr 0xfffff20bccb1cc10)
rax=fffff20bccb1d618 rbx=ffffaf81da352ea0 rcx=ffffaf81da352000
rdx=ffffaf81da352000 rsi=0000000000000002 rdi=000001ea002a02f0
rip=fffff80373407660 rsp=fffff20bccb1d608 rbp=0000000000000000
r8=000001ea002a02f0 r9=000000000000007c r10=000001ea002a036c
r11=000001ea002a0316 r12=fffff20bccb1d898 r13=ffff810bc08c0000
r14=ffffaf81da353000 r15=ffffaf81da352000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!RtlDecompressBufferXpressLz+0x40:
fffff80373407660 418b00 mov eax,dword ptr [r8] ds:002b:000001ea002a02f0=????????
Resetting default scope

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: MemCompression

CURRENT_IRQL: 0

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR: 0xc0000006_c000000e

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

BUGCHECK_STR: 0x154_c0000006_c000000e

ANALYSIS_SESSION_HOST: BOB

ANALYSIS_SESSION_TIME: 07-24-2019 17:54:28.0693

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_TEXT:
fffff20bccb1c368 fffff803735bb02e : 0000000000000154 ffff810bb8b85000 fffff20bccb1c420 0000000000000002 : nt!KeBugCheckEx
fffff20bccb1c370 fffff803734861b8 : ffff810bb8b85000 fffff20bccb1c420 0000000000000002 0000000000000000 : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x7e
fffff20bccb1c3c0 fffff80373447492 : 0000000000000002 fffff20bccb1d8f0 fffff20bccb18000 fffff20bccb1e000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue'::1'::filt$0+0x22
fffff20bccb1c3f0 fffff80373475a62 : fffff20bccb1d8f0 fffff20bccb1c9d0 fffff20bccb1cab0 000000000010001f : nt!_C_specific_handler+0xa2
fffff20bccb1c460 fffff803733ce3a0 : fffff20bccb1cab0 0000000000000000 fffff20bccb1c9d0 0000000000000000 : nt!RtlpExecuteHandlerForException+0x12
fffff20bccb1c490 fffff803732dbbb4 : fffff20bccb1d3c8 fffff20bccb1d110 fffff20bccb1d3c8 000001ea002a02f0 : nt!RtlDispatchException+0x430
fffff20bccb1cbe0 fffff8037347e8c2 : ffff810bb71ef640 fffff80373322a19 0000000000002000 fffff20bccb1d470 : nt!KiDispatchException+0x144
fffff20bccb1d290 fffff8037347abae : ffffaf81d93f4ea0 fffff20bccb1d4f0 fffff20bccb1d898 0000000000000000 : nt!KiExceptionDispatch+0xc2
fffff20bccb1d470 fffff80373407660 : ffffaf81da352000 ffff810bb8b85050 fffff803733afc20 ffffaf81da352000 : nt!KiPageFault+0x42e
fffff20bccb1d608 fffff803733afc20 : ffffaf81da352000 ffffaf81da352000 0000000000000002 000001ea002a02f0 : nt!RtlDecompressBufferXpressLz+0x40
fffff20bccb1d620 fffff803733fc84a : fffff80300000000 fffff80300000000 0000000000000000 000001ea002a0000 : nt!RtlDecompressBufferEx+0x60
fffff20bccb1d670 fffff803733fc6e4 : 0000000000000004 fffff20bccb1d880 0000000000000000 0000000000000000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x146
fffff20bccb1d750 fffff803733fc492 : 0000000000000001 00000000000002f0 ffff810b000002f0 000000000000a000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
fffff20bccb1d7a0 fffff803733fc2bd : 00000000ffffffff ffff810bc08c0000 fffff20bccb1d880 ffff810bc300ade0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
fffff20bccb1d840 fffff803733fb3d5 : ffff810bc08c0000 0000000000000000 ffff810b00000000 ffff810bb8b86788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1
fffff20bccb1d8f0 fffff803733fab11 : ffff810bb8b85000 ffff810bc300ade0 ffff810bc08c0000 ffff810bb8b869b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
fffff20bccb1d970 fffff803733999c8 : ffff810bc5062040 ffff810bb8b85000 ffff810bc5062040 0000000000000000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
fffff20bccb1d9a0 fffff803734046e5 : fffff803733faaf0 fffff20bccb1da50 0000000000000003 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffff20bccb1da10 fffff80373403d34 : fffff20bccb1da00 0000000000000000 0000086e18de8d58 fffff8037321d7ae : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad
fffff20bccb1dae0 fffff80373406074 : 0000000000000000 0000086e18de8d58 fffff80373815e90 fffff80373815c68 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1b4
fffff20bccb1db30 fffff8037332dbfa : 0000000000989680 ffff810bc5062040 fffff80373405fd0 ffff810bbdf39a78 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmAsyncReadQueueWorker+0xa4
fffff20bccb1db70 fffff803732f6b35 : ffff810bc5062040 ffff810baf264180 ffff810bc5062040 0000000000000200 : nt!ExpWorkerThread+0x16a
fffff20bccb1dc10 fffff803734743cc : ffffaf81d8f14180 ffff810bc5062040 fffff803732f6ae0 ffff810bb64ab3f0 : nt!PspSystemThreadStartup+0x55
fffff20bccb1dc60 0000000000000000 : fffff20bccb1e000 fffff20bccb18000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x1c


THREAD_SHA1_HASH_MOD_FUNC: dd050bed2957fa0b3bc048a63ed636a396f33291

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9bad96c08e3db1118bebcfad95b35cdf0fcf08f4

THREAD_SHA1_HASH_MOD: ef0b9811d1c3c2b0b400d0c8a17067df59efd56d

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

BUCKET_ID: 0x154_c0000006_c000000e_IMAGE_hardware_disk

PRIMARY_PROBLEM_CLASS: 0x154_c0000006_c000000e_IMAGE_hardware_disk

TARGET_TIME: 2019-07-24T13:58:55.000Z

OSBUILD: 17763

OSSERVICEPACK: 615

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2020-05-15 18:13:35

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 9f44

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x154_c0000006_c000000e_image_hardware_disk

FAILURE_ID_HASH: {6ef1f8aa-ba96-513b-39a6-be53976d18b0}

Followup: MachineOwner


Also I did sfc /scannow and results said that Windows Resource Protection found corrupt files and successfully repaired them. I am not sure if that will fix my problem, if someone more experienced can tell me whats wrong from dump file.

Thank you.

 

[Satan-IR]

Welcome to the forums!

Can you upload the actual dump file/s somewhere like Google Drive or Dropbox and post a link here so we can have a look?

 

[croat25]

Sure, here it is.

https://ufile.io/xx0iluw2

 

[Satan-IR]

What are you full system specs including make and model of PSU?

What Windows is this, 10? Is it a new clean installation of Windows? Is it a genuine Windows?

When does this BSOD happen?

It is a bugcheck 154 and the driver named is win32kbase.sys. It could be still because of data corruption.

I'd suggest you also run chkdsk C: /F and you can use DISM tools.

I'd also suggest you run memtest to check if your RAM sticks are faulty and have errors or not. If you have more than one RAM stick run memtest with one module at a time and 8 passes at least.

 

[croat25]

What are you full system specs including make and model of PSU?

What Windows is this, 10? Is it a new clean installation of Windows? Is it a genuine Windows?

When does this BSOD happen?

It is a bugcheck 154 and the driver named is win32kbase.sys. It could be still because of data corruption.

I'd suggest you also run chkdsk C: /F and you can use DISM tools.

I'd also suggest you run memtest to check if your RAM sticks are faulty and have errors or not. If you have more than one RAM stick run memtest with one module at a time and 8 passes at least.

Thank you, I will monitor to see if problem occurs. Its genuine Windows 10 Home, I paid for it, and activated them by phone with Microsoft agent when bought PC 6 months ago all newly build with all new components. AMD Ryzen 5 2600, Nvidia RTX 2060, 2x8mb crosair 3000mhz, Toshiba HD 1tb + SSD Kingston 240 checked with their manager for firmware. My initial thought was it might be a problem with SSD but I dont know anything about hardware.

 

[Satan-IR]

Thank you, I will monitor to see if problem occurs. Its genuine Windows 10 Home, I paid for it, and activated them by phone with Microsoft agent when bought PC 6 months ago all newly build with all new components. AMD Ryzen 5 2600, Nvidia RTX 2060, 2x8mb crosair 3000mhz, Toshiba HD 1tb + SSD Kingston 240 checked with their manager for firmware. My initial thought was it might be a problem with SSD but I dont know anything about hardware.

Is the Windows installed on the SSD? You can download HD Sentinel from here to check the SMART health status of the drives (HDD and SSD).

As far as firmware goes SSD makers usually have a management utility/application through which you can check if you have the latest firmware or not and update it if applicable and also monitor their health status. You can find the SSD manager for Kingston here.

As I suggested earlier, I think it's a good idea to run the memtest with each of the 8GB RAM modules are a time to check if RAM has errors or not.

If you have any other BSODs and a dump file is dropper upload them and link here so we can check them too.

 

[croat25]

Thank you for now, I did lots of cleaning, updating, checking things, so now I will monitor if its fixed. I noticed in event manager that aprox 2 a day I got warning ESENT on performance where problem is that writing takes to long probably due to a freezing of a system which last for like 20 seconds. I will try memtest as soon as I learn how to use it, I read somewhere I should copy it on usb and boot it from it.

 

[Satan-IR]

That ESENT error might be related to storage. As said I'd check the health of the SSD if that's where Windows is installed?

Yes you can make a bootable USB flash drive or DVD and change boot priority in BIOS and boot from it to use memtest.

Run each 8GB RAM stick on its own so that you can make sure which one is bad if memtest finds errors. There should be no errors when memtest finishes its passes; so even a single error means RAM is faulty.

 

[croat25]

That ESENT error might be related to storage. As said I'd check the health of the SSD if that's where Windows is installed?

Yes you can make a bootable USB flash drive or DVD and change boot priority in BIOS and boot from it to use memtest.

Run each 8GB RAM stick on its own so that you can make sure which one is bad if memtest finds errors. There should be no errors when memtest finishes its passes; so even a single error means RAM is faulty.

Will do memtest soon, did windows memory scan but thats not sufficient I suppose, no errors. SSD manager says drive is ok, but there isnt any diagnostics only readings of drive are all 100 health. Anyways I will provide a pic where some bad block count could be worrying, not sure..

https://imgur.com/a/zZ0knCp

View: https://imgur.com/a/zZ0knCp

 

[Satan-IR]

Will do memtest soon, did windows memory scan but thats not sufficient I suppose, no errors. SSD manager says drive is ok, but there isnt any diagnostics only readings of drive are all 100 health. Anyways I will provide a pic where some bad block count could be worrying, not sure..

https://imgur.com/a/zZ0knCp

View: https://imgur.com/a/zZ0knCp

You can check with HD Sentinel and see what the program says about drive health. In the SMART tab for the drive you can right-click in right pane and choose 'Decimal data fields'

Bad blocks can exist on new drives, no big deal. also your 'Reallocated events' count is zero and 'SSD spare blocks' are still all there (100%) so no bad blocks have actually been remapped I think. That means the drive is OK, no worries.

Anyway I guess you can always check with Kingston support or customer service to see what they say and whether that warrants a return and replacement

Is Windows up to date with latest updates? Also motherboard BIOS and drivers are all up to date?