Çözüldü UNEXPECTED_STORE_EXCEPTION mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10

igzacier

Kilopat
Katılım
13 Mart 2015
Mesajlar
8
Daha fazla  
Cinsiyet
Erkek
Bu hatayı çok uzun süredir alıyordum ve bir ay önce kadar bilgisayarım çöktü. Mecburen format attım ve format atarken şu an hatırlayamadığım disk sorunlarından iki bölüme ayırmış olduğum diski tamamen birleştirip her şeyi silerek kurtulabilmiştim. İki gün önce maalesef yine bu hatayla karşılaştım. Minidump dosyasının orijinalini sıkıştırırken erişim yok hatası aldığı için paylaşamıyorum fakat içeriğini WinDbg ile yönetici olarak açabildiğim için gösterebilirim.

Kod:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
 ExtensionRepository : Implicit.
 UseExperimentalFeatureForNugetShare : true.
 AllowNugetExeUpdate : true.
 NonInteractiveNuget : true.
 AllowNugetMSCredentialProviderInstall : true.
 AllowParallelInitializationOfLocalRepositories : true.

 EnableRedirectToV8JsProvider : false.

 -- Configuring repositories.
 ----> Repository : LocalInstalled, Enabled: true.
 ----> Repository : UserExtensions, Enabled: true.

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.031 seconds.

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.563 seconds.
 ----> Repository : UserExtensions, Enabled: true, Packages count: 0
 ----> Repository : LocalInstalled, Enabled: true, Packages count: 41.

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64.
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************
Response Time (ms) Location.
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff801`76c00000 PsLoadedModuleList = 0xfffff801`7782a730
Debug session time: Thu Apr 4 09:34:39.124 2024 (UTC + 3:00)
System Uptime: 14 days 20:41:42.001
Loading Kernel Symbols.
...............................................................
................................................................
................................................................

Loading User Symbols.
PEB address is NULL !
Loading unloaded module list.
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`76ffd890 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa20c`caf31f80=0000000000000154
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 9843.

 Key : Analysis.Elapsed.mSec
 Value: 11576.

 Key : Analysis.IO.Other.Mb
 Value: 0

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 0

 Key : Analysis.Init.CPU.mSec
 Value: 1499.

 Key : Analysis.Init.Elapsed.mSec
 Value: 22705.

 Key : Analysis.Memory.CommitPeak.Mb
 Value: 92.

 Key : Bugcheck.Code.KiBugCheckData
 Value: 0x154.

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x154.

 Key : Bugcheck.Code.TargetModel
 Value: 0x154.

 Key : Failure.Bucket
 Value: 0x154_c0000006_c000009c_IMAGE_storahci.sys

 Key : Failure.Hash
 Value: {8e9c4ea8-d07a-904f-1aae-b3525bc0be92}

 Key : Hypervisor.Enlightenments.Value
 Value: 0

 Key : Hypervisor.Enlightenments.ValueHex
 Value: 0

 Key : Hypervisor.Flags.AnyHypervisorPresent
 Value: 0

 Key : Hypervisor.Flags.ApicEnlightened
 Value: 0

 Key : Hypervisor.Flags.ApicVirtualizationAvailable
 Value: 0

 Key : Hypervisor.Flags.AsyncMemoryHint
 Value: 0

 Key : Hypervisor.Flags.CoreSchedulerRequested
 Value: 0

 Key : Hypervisor.Flags.CpuManager
 Value: 0

 Key : Hypervisor.Flags.DeprecateAutoEoi
 Value: 0

 Key : Hypervisor.Flags.DynamicCpuDisabled
 Value: 0

 Key : Hypervisor.Flags.Epf
 Value: 0

 Key : Hypervisor.Flags.ExtendedProcessorMasks
 Value: 0

 Key : Hypervisor.Flags.HardwareMbecAvailable
 Value: 0

 Key : Hypervisor.Flags.MaxBankNumber
 Value: 0

 Key : Hypervisor.Flags.MemoryZeroingControl
 Value: 0

 Key : Hypervisor.Flags.NoExtendedRangeFlush
 Value: 0

 Key : Hypervisor.Flags.NoNonArchCoreSharing
 Value: 0

 Key : Hypervisor.Flags.Phase0InitDone
 Value: 0

 Key : Hypervisor.Flags.PowerSchedulerQos
 Value: 0

 Key : Hypervisor.Flags.RootScheduler
 Value: 0

 Key : Hypervisor.Flags.SynicAvailable
 Value: 0

 Key : Hypervisor.Flags.UseQpcBias
 Value: 0

 Key : Hypervisor.Flags.Value
 Value: 0

 Key : Hypervisor.Flags.ValueHex
 Value: 0

 Key : Hypervisor.Flags.VpAssistPage
 Value: 0

 Key : Hypervisor.Flags.VsmAvailable
 Value: 0

 Key : Hypervisor.RootFlags.AccessStats
 Value: 0

 Key : Hypervisor.RootFlags.CrashdumpEnlightened
 Value: 0

 Key : Hypervisor.RootFlags.CreateVirtualProcessor
 Value: 0

 Key : Hypervisor.RootFlags.DisableHyperthreading
 Value: 0

 Key : Hypervisor.RootFlags.HostTimelineSync
 Value: 0

 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
 Value: 0

 Key : Hypervisor.RootFlags.IsHyperV
 Value: 0

 Key : Hypervisor.RootFlags.LivedumpEnlightened
 Value: 0

 Key : Hypervisor.RootFlags.MapDeviceInterrupt
 Value: 0

 Key : Hypervisor.RootFlags.MceEnlightened
 Value: 0

 Key : Hypervisor.RootFlags.Nested
 Value: 0

 Key : Hypervisor.RootFlags.StartLogicalProcessor
 Value: 0

 Key : Hypervisor.RootFlags.Value
 Value: 0

 Key : Hypervisor.RootFlags.ValueHex
 Value: 0

 Key : SecureKernel.HalpHvciEnabled
 Value: 0

 Key : WER.DumpDriver
 Value: DUMP_STORAHCI.

 Key : WER.OS.Branch
 Value: vb_release.

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 154.

BUGCHECK_P1: ffffa80d6ce8c000.

BUGCHECK_P2: ffffa20ccaf32030.

BUGCHECK_P3: 2

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

EXCEPTION_RECORD: ffffa20ccaf32fb8 -- (.exr 0xffffa20ccaf32fb8)
ExceptionAddress: fffff80176f30470 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
 ExceptionCode: c0000006 (In-page I/O error)
 ExceptionFlags: 00000000.
NumberParameters: 3
 Parameter[0]: 0000000000000000.
 Parameter[1]: 00000240a7670fd0.
 Parameter[2]: 00000000c000009c.
Inpage operation failed at 00000240a7670fd0, due to I/O error 00000000c000009c.

EXCEPTION_PARAMETER1: 0000000000000000.

EXCEPTION_PARAMETER2: 00000240a7670fd0.

IMAGE_NAME: storahci.sys

MODULE_NAME: storahci.

FAULTING_MODULE: fffff8017ba70000 storahci.

CONTEXT: ffffa20ccaf327f0 -- (.cxr 0xffffa20ccaf327f0)
rax=fffff80176f30420 rbx=ffff9080c049f000 rcx=ffff9080c049f000
rdx=ffff9080c049f000 rsi=0000000000000002 rdi=00000240a7670fd0
rip=fffff80176f30470 rsp=ffffa20ccaf331f8 rbp=00000240a7671246
 r8=00000240a7670fd0 r9=00000000000002cc r10=ffff9080c049fea0
r11=00000240a767129c r12=ffffa20ccaf33468 r13=ffffa80d89585000
r14=ffff9080c04a0000 r15=0000000000000000
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`76f30470 418b08 mov ecx,dword ptr [r8] ds:002b:00000240`a7670fd0=????????
Resetting default scope.

PROCESS_NAME: MemCompression.

ERROR_CODE: (NTSTATUS) 0xc0000006 - 0x%p adresindeki y nerge, 0x%p bellek adresine ba vurdu. Gerekli veriler, 0x%x G/ hata durumu y z nden belle e yerle tirilmedi.

EXCEPTION_CODE_STR: c0000006.

EXCEPTION_PARAMETER3: 00000000c000009c.

EXCEPTION_STR: 0xc0000006.

STACK_TEXT:
ffffa20c`caf331f8 fffff801`76eef7b0 : ffff9080`c049f000 ffff9080`c049f000 00000000`00000002 00000240`a7670fd0 : nt!RtlDecompressBufferXpressLz+0x50
ffffa20c`caf33210 fffff801`76eef4c0 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00040000 : nt!RtlDecompressBufferEx+0x60
ffffa20c`caf33260 fffff801`76eef34d : 00000000`00000004 fffff801`76eeeeb6 00000000`00000000 00000000`00000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x150
ffffa20c`caf33320 fffff801`76eee5fc : 00000000`00000001 00000000`00010fd0 ffffa80d`6ce8c000 ffffa80d`00010000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5
ffffa20c`caf33370 fffff801`76eee42c : 00000000`ffffffff ffffa80d`89585000 ffffa20c`caf33450 ffffa80d`6b7e7050 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180
ffffa20c`caf33410 fffff801`76eee279 : fffff801`7486e730 00000000`00000001 00000000`00000000 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8
ffffa20c`caf334c0 fffff801`76eee131 : ffffa80d`6ce8c000 ffffa80d`6b7e7050 ffffa80d`89585000 ffffa80d`6ce8d9c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffffa20c`caf33540 fffff801`76e7c6b8 : ffffa80d`75d9e080 ffffa80d`6ce8c000 00000000`00000000 ffffa80d`75644a80 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffa20c`caf33570 fffff801`76eec8cb : fffff801`76eee110 ffffa20c`caf33610 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffa20c`caf335e0 fffff801`76e0f69c : ffffa20c`caf336e0 00000000`31526d73 00000000`000003ff fffff801`779239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
ffffa20c`caf336b0 fffff801`76e0f0d0 : 00000000`0000000c 00000000`000003ff ffffa20c`caf33760 fffff801`779239c0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
ffffa20c`caf33700 fffff801`76eece47 : 00000000`0000000c 00000000`00000010 ffffa80d`6b7e7050 ffffa80d`75644a80 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
ffffa20c`caf33790 fffff801`76f5ecaf : ffffa80d`00000010 ffffa80d`75644b40 00000000`00000000 ffffa80d`6ce8c000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
ffffa20c`caf33800 fffff801`76e6dde4 : 0000007f`00000100 00000000`00000000 ffffa20c`caf33a58 fffff801`76e6ed60 : nt!SmPageRead+0x33
ffffa20c`caf33850 fffff801`76e6e8bd : 00000000`00000002 ffffa20c`caf338e0 ffffa20c`caf33a58 ffffa80d`75644a30 : nt!MiIssueHardFaultIo+0x10c
ffffa20c`caf338a0 fffff801`76e246c8 : 00000000`c0033333 00000000`00000001 000063c9`06850edc 00000000`00000000 : nt!MiIssueHardFault+0x29d
ffffa20c`caf33960 fffff801`7700d798 : 000049f8`00000000 00000000`00000001 000063c9`05d1ec28 ffffa20c`caf33b80 : nt!MmAccessFault+0x468
ffffa20c`caf33b00 00007ffd`cfd360a5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
000000b3`49ffee10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`cfd360a5

STACK_COMMAND: .cxr 0xffffa20ccaf327f0 ; kb.

FAILURE_BUCKET_ID: 0x154_c0000006_c000009c_IMAGE_storahci.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {8e9c4ea8-d07a-904f-1aae-b3525bc0be92}

Followup: MachineOwner.
---------
 
Çözüm
Evet, diskinle ilgili raporlamalar da var sistem raporunda "bile". Diski sistemden çıkar ve yeni bir disk takıp mavi ekran sorununu hallet.
Minidump dosyasının orijinalini sıkıştırırken erişim yok hatası aldığı için paylaşamıyorum

Paylaşın.
 
Merhaba,

İstisna kaydı olayla ilgili tüm bilgiyi vermiş zaten.
Rich (BB code):
EXCEPTION_RECORD:  ffffa20ccaf32fb8 -- (.exr 0xffffa20ccaf32fb8)
ExceptionAddress: fffff80176f30470 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000240a7670fd0
   Parameter[2]: 00000000c000009c
Inpage operation failed at 00000240a7670fd0, due to I/O error 00000000c000009c

Sistem nt!RtlDecompressBufferXpressLz çağrısında istisna kaydı almış olarak görünüyor. Bir bakıma bu fonksiyon ya da çağrı aslında Microsoft tarafından geliştirilen ve iyi sıkıştırma oranlarıyla hızlı sıkıştırma ve açma için tasarlanmış bir sıkıştırma algoritmasından başka bir şey değildir. Amacı da bu algoritma ile sıkıştırılmış bir veri arabelleğini belirtilen bir diğer arabelleğe açar.

Rich (BB code):
08 ffffa20c`caf33060 fffff801`76f30470     nt!KiPageFault+0x43d
09 ffffa20c`caf331f8 fffff801`76eef7b0     nt!RtlDecompressBufferXpressLz+0x50
0a ffffa20c`caf33210 fffff801`76eef4c0     nt!RtlDecompressBufferEx+0x60

Rich (BB code):
CONTEXT:  ffffa20ccaf327f0 -- (.cxr 0xffffa20ccaf327f0)
rax=fffff80176f30420 rbx=ffff9080c049f000 rcx=ffff9080c049f000
rdx=ffff9080c049f000 rsi=0000000000000002 rdi=00000240a7670fd0
rip=fffff80176f30470 rsp=ffffa20ccaf331f8 rbp=00000240a7671246
 r8=00000240a7670fd0  r9=00000000000002cc r10=ffff9080c049fea0
r11=00000240a767129c r12=ffffa20ccaf33468 r13=ffffa80d89585000
r14=ffff9080c04a0000 r15=0000000000000000
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`76f30470 418b08          mov     ecx,dword ptr [r8] ds:002b:00000240`a7670fd0=????????
Resetting default scope

Yukarıdaki istisna kaydının devamında da Sayfa içi bir G/Ç hatasında sistem çöküyor. Yani bu olay şöyle tabir edilebilir ki; genellikle diskteki sayfa dosyasına veya sanal belleğe veri okuma/ yazma sırasında sorun yaşandığı bir durumu ifade ediyor. Bu hatadan anladığımız şey bir veri yazımı sırasında yazılan adres erişim hatasına düşmüş, peki neden? Aşağıda yazmış sebebini:

Rich (BB code):
Inpage operation failed at 00000240a7670fd0, due to I/O error 00000000c000009c

00000240a7670fd0 adresiyle ilgili bir G/Ç işlemi sırasında sistem c000009c hatasıyla durmuş. c000009c nedir diye bakarsak:

Rich (BB code):
0: kd> !error c000009c
Error code: (NTSTATUS) 0xc000009c (3221225628) - STATUS_DEVICE_DATA_ERROR

STATUS_DEVICE_DATA_ERRORThere are bad blocks (sectors) on the hard disk.

Disteki bozuk sektörler, bloklar bu hataya sebep olmuş ve bu yüzden sistemin mavi ekrana düşmüş. Kısaca, diskinde bir problem tespiti var sistem tarafından.
Rich (BB code):
IOCTL  : 0x18814

Device Type    : Disk << Hata.
Method         : ff000000
Access         : fffffffffffffffff
Function       : 0
 
Son düzenleme:
Olay görüntüleyicisi raporları burada.
Sanırım disk ölmüş.
 

Dosya Ekleri

  • HDTune_Error_Scan_TOSHIBA_MQ01ABD050.png
    HDTune_Error_Scan_TOSHIBA_MQ01ABD050.png
    17 KB · Görüntüleme: 19
  • HDTune_Health_TOSHIBA_MQ01ABD050.png
    HDTune_Health_TOSHIBA_MQ01ABD050.png
    31,8 KB · Görüntüleme: 21

Yeni konular

Geri
Yukarı