Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD Unexpected Store Exception


  • Please log in to reply
5 replies to this topic

#1 Snom

Snom

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 22 September 2017 - 01:47 PM

Recently started getting it. Happens at least once or twice a day. I updated drivers recently but only after I started getting a different BSOD. Now I get this one, but I don't really know why. The minidump is saying hardware disk but ive done all the scans and memory diagnostics. Nothing wrong. I also have done the file scanner and nothing shows up. WhoCrashed is telling me it could be a driver. Maybe it could be my BIOS? I'm not sure. I'm not really a computer expert but I've been trying to fix this the last two weeks. I used driver booster to update the drivers though, so maybe I should update them manually myself? 

 

 

 

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

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.10586.1106 (th2_release.170904-1742)

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F3

BIOS_DATE: 11/02/2015

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: B150M-DS3H-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

BUGCHECK_P1: ffffe0018996c000

BUGCHECK_P2: ffffd00024a86f80

BUGCHECK_P3: 0

BUGCHECK_P4: 0

EXCEPTION_RECORD: ffffd00024a87f08 -- (.exr 0xffffd00024a87f08)
ExceptionAddress: fffff801a198ba60 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 000001e2812f5570
Parameter[2]: 00000000c00000c0
Inpage operation failed at 000001e2812f5570, due to I/O error 00000000c00000c0

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
fffff801`a198ba60 418b00 mov eax,dword ptr [r8]

FOLLOWUP_IP: 
+0
000001e2`812f5570 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000001e2812f5570

CONTEXT: ffffd00024a87720 -- (.cxr 0xffffd00024a87720)
rax=ffffd00024a8820c rbx=ffffd00021d3a000 rcx=ffffd00021d3a000
rdx=ffffd00021d3a000 rsi=fffff801a1aba2e8 rdi=ffffd00021d3a000
rip=fffff801a198ba60 rsp=ffffd00024a88140 rbp=000001e2812f574a
r8=000001e2812f5570 r9=00000000000001da r10=ffffd00021d3aea0
r11=0000000000000000 r12=ffffe00187b5d000 r13=ffffd00024a883e8
r14=000001e2812f56f4 r15=ffffd00021d3b000
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+0x50:
fffff801`a198ba60 418b00 mov eax,dword ptr [r8] ds:002b:000001e2`812f5570=????????
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: c78

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

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

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

EXCEPTION_STR: 0xc0000006_c00000c0

BUGCHECK_STR: 0x154_c0000006_c00000c0

ANALYSIS_SESSION_HOST: DESKTOP-DK3LCJV

ANALYSIS_SESSION_TIME: 09-22-2017 11:50:26.0208

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

STACK_TEXT: 
ffffd000`24a86ed8 fffff801`a1a7acf2 : 00000000`00000154 ffffe001`8996c000 ffffd000`24a86f80 00000000`00000000 : nt!KeBugCheckEx
ffffd000`24a86ee0 fffff801`a19d11e4 : c61ace7b`d6bddefe b598b597`b598b598 ce5bbdd9`bdd8b5b8 e71edf1e`e71ed6bd : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x22
ffffd000`24a86f20 fffff801`a19af2ff : 4aae39eb`62eead57 4ad13aaf`42d03a8e 8d5a63f5`42b042b0 93ec6b0b`52ef84f8 : nt! ?? ::FNODOBFM::`string'+0x2de4
ffffd000`24a86f50 fffff801`a19c5aad : 00000000`00000000 ffffd000`24a870f0 00000000`00000052 4a4b2969`10e710a5 : nt!_C_specific_handler+0x9f
ffffd000`24a86fc0 fffff801`a1886a69 : 00000000`00000000 00000000`000000c1 ffffd000`24a875c0 6aa86287`62a762a7 : nt!RtlpExecuteHandlerForException+0xd
ffffd000`24a86ff0 fffff801`a1884e99 : 00000000`00000000 ffffd000`24a87c20 00000000`00000000 ffffd000`00000001 : nt!RtlDispatchException+0x429
ffffd000`24a876f0 fffff801`a19ca6ce : ffffe001`8860e010 00010000`000012d0 00000000`00000000 fffff801`a1895b89 : nt!KiDispatchException+0x195
ffffd000`24a87dd0 fffff801`a19c8da1 : 00000000`00000000 00000000`00000000 ffffe001`8a83d330 00000000`00000000 : nt!KiExceptionDispatch+0xce
ffffd000`24a87fb0 fffff801`a198ba60 : ffffd000`21d3a000 ffffd000`21d3a000 00000000`00001000 fffff801`a1934480 : nt!KiPageFault+0x221
ffffd000`24a88140 fffff801`a1934480 : ffffe001`8996c050 fffff801`a1aba2e8 ffffd000`21d3a000 fffff801`a193528b : nt!RtlDecompressBufferXpressLz+0x50
ffffd000`24a88160 fffff801`a197d164 : 00000000`00000002 000001e2`812f5570 ffffe001`8996c050 00000000`00000000 : nt!RtlDecompressBufferEx+0x64
ffffd000`24a881b0 fffff801`a197cfce : ffffe001`894ce450 ffff8c9e`842146ba ffffe001`87b5d040 fffff801`a197bbf4 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x15c
ffffd000`24a88280 fffff801`a197d449 : 00000000`00000002 ffffe001`87ad12a0 ffffe001`8996c050 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xb6
ffffd000`24a882e0 fffff801`a197d64d : 00000000`ffffffff ffffe001`00001557 00000000`00000086 ffffe001`894ce450 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1e1
ffffd000`24a88380 fffff801`a197e0f6 : fffff801`a1b78670 ffffe001`894ce450 00000000`00000040 ffffe001`894ce450 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1
ffffd000`24a88440 fffff801`a197e1a1 : ffffe001`8996c000 ffffd000`24a88550 fffff801`a197e180 fffff801`a197e180 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x52
ffffd000`24a88490 fffff801`a19257e5 : ffffe001`8c12c080 ffffd000`24a88550 ffffe001`83154820 fffff801`a19315d0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffd000`24a884c0 fffff801`a1977c28 : 00000000`00000003 ffffe001`894ce450 ffffe001`87b5d000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd000`24a88510 fffff801`a1979bbc : ffffd000`24a88610 fffff801`a197de28 ffffe001`8996c000 ffffd000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xac
ffffd000`24a885e0 fffff801`a19798cf : ffffe001`8996c000 ffffe001`894ce450 fffff801`a1b7b680 fffff801`a1b7b680 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x180
ffffd000`24a88630 fffff801`a1977ab9 : 00000000`0000000c ffffe001`831548d0 ffffe001`894ce450 00000000`00000001 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbb
ffffd000`24a886b0 fffff801`a197794d : ffffe001`831548d0 ffffd000`24a88760 ffffd000`00000001 fffff680`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x165
ffffd000`24a88730 fffff801`a1914a89 : 000001d1`9fa3c000 fffff580`10804000 00000000`0000162a fffff801`a18bc0bd : nt!SmPageRead+0x51
ffffd000`24a88780 fffff801`a1913de2 : 00000000`00000002 00000000`00000000 ffffe001`831547d0 00000000`00000000 : nt!MiIssueHardFaultIo+0x129
ffffd000`24a88800 fffff801`a18b1593 : 00000000`c0033333 000001d1`9fa00010 ffffd000`24a88a00 fffff680`00000000 : nt!MiIssueHardFault+0x162
ffffd000`24a888a0 fffff801`a19c8cbc : ffffe001`8c12c080 000001d1`00000000 ffffe001`8c12c080 ffffd000`24a88a80 : nt!MmAccessFault+0x7f3
ffffd000`24a88a00 00007ff9`30aeb71f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000070`e0afe1d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`30aeb71f


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 7363b625dc50677ef4907ffa1524181659350335

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 265387c02dcdacf13a7c8ac1ed9c591c4d8fddb3

THREAD_SHA1_HASH_MOD: 901685eb5ed44e617e07e22622321d209483595d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME: hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x154_c0000006_c00000c0_IMAGE_hardware_disk

BUCKET_ID: 0x154_c0000006_c00000c0_IMAGE_hardware_disk

PRIMARY_PROBLEM_CLASS: 0x154_c0000006_c00000c0_IMAGE_hardware_disk

TARGET_TIME: 2017-09-22T15:53:29.000Z

OSBUILD: 10586

OSSERVICEPACK: 1106

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: 2017-09-04 23:57:56

BUILDDATESTAMP_STR: 170904-1742

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.1106

ANALYSIS_SESSION_ELAPSED_TIME: 17e2

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x154_c0000006_c00000c0_image_hardware_disk

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

Followup: MachineOwner

I have no idea what is causing this. I ran WhoCrashed as well and got this


On Fri 9/22/2017 10:53:29 AM your computer crashed
crash dump file: C:\Windows\Minidump\092217-19000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142A00) 
Bugcheck code: 0x154 (0xFFFFE0018996C000, 0xFFFFD00024A86F80, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Fri 9/22/2017 10:53:29 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x154 (0xFFFFE0018996C000, 0xFFFFD00024A86F80, 0x0, 0x0)
Error: CUSTOM_ERROR
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


I guess the confusion is that the memory dump file says probably caused by hardware_disk and the WhoCrashed says it might be a driver that cannot be identifed.



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:11 AM

Posted 22 September 2017 - 08:22 PM

The memory dump that you posted shows an I/O error - which typically is hardware in nature.

That, along with the hardware_disk error makes it pretty sure that the problem is with your hard drive.
Please start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please start with the Hard Drive diagnostics, but be sure to finish ALL of the tests - and let us know the results.

I suggest using the Seagate Seatools long/extended test to test your hard drive.  If this is an SSD, then please post back for further instructions.

 

The WhoCrashed info is just a standard response, as drivers are most often the most common problem causing BSOD's
You'll note that it also tries to blame the Windows kernel (core of the operating system) - which won't be the case if there's a hardware problem (and it's very unlikely to be to blame even if there is a software problem).

 

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Snom

Snom
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 24 September 2017 - 09:54 PM

Major Update. I was meaning to wait to do this to make sure I had completely solved the issue. I had used the driver verifier to try and weed out a faulty driver because I had read about it somewhere else. My computer began crashing on a loop and said DRIVER_VERIFIER_DETECTED_VIOLATION. I disabled the settings and read the mini dumps and it turned out that it was LGBusEnum.sys that was causing the crashes. I proceeded to update the Logictech drivers from their website and I have not crashed since! It is strange because I never got a notification or notice of an upgrade for it from other software. My driver was pretty outdated compared to the most recent one but I have not crashed at all since I installed the latest version. Thank you for responding!



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:11 AM

Posted 25 September 2017 - 06:47 AM

Very interesting and great troubleshooting!

I have been watching the Logitech drivers (as I use them and know that they are very old when compared with Windows10) and have found those from 2012 to be remarkably stable in Windows 10.

What was the date of the LBBusEnum.sys that was causing the crashes?  Could it have been that the driver was corrupted (rather than outdated) and replacing it was what fixed the BSOD?


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 Snom

Snom
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  

Posted 25 September 2017 - 07:23 PM

Yeah, the driver was probably corrupted.The date on the driver was 6/13/2016 and 8.85.75.0

WhoCrashed said it was a software bug that was causing the system error, so you are probably right. 



#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:11 AM

Posted 26 September 2017 - 06:34 AM

Thanks!


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users