Çözüldü KERNEL_DATA_INPAGE_ERROR mavi ekran hatası

aaltan21 · 21 Eylül 2020

Son zamanlarda yaşadığım mavi ekran sorununun sebebini merak ediyorum. Buyurun dump dosyaları: dumps - Google Drive

Trieetz · 21 Eylül 2020

Sistem açılıyorken mavi ekran alıyorsanız güvenli modda bu işlemleri yapın. Güvenli moda girmeden de yapabilirsiniz.

Eksik dosyalarınızı onarın.
Windows Update çalıştırın.
Bu işlemler işe yaramaz ise tavsiyem en yakın zamanda temiz kurulum ile Windows 10 geçmeniz.

ViooYa · 21 Eylül 2020

HD Tune programıyla diskinizi tarayın ve işlem sonucunu bildirin bize. Diskinizden kaynaklandığını görüyorum.

SMB Server ile alakalı da bir şeyler var ancak ben tam anlayamadım. Murat Hoca'yı etiketliyorum konuya o daha doğru bilgi verecektir.
@Murat5038

Bu işlemden sonra komut istemi CMD'yi yönetici olarak çalıştırın ardından

Kod:

DISM /Online /Cleanup-Image /RestoreHealth

komutunu girin. İşlemin tamamlanmasını bekleyin.

aaltan21 · 21 Eylül 2020

ViooYa dedi:
HD Tune programıyla diskinizi tarayın ve işlem sonucunu bildirin bize. Diskinizden kaynaklandığını görüyorum.

SMB server ile alakalı da bir şeyler var ancak ben tam anlayamadım. Murat Hoca'yı etiketliyorum konuya o daha doğru bilgi verecektir.
@Murat5038

Bu işlemden sonra komut istemi CMD'yi yönetici olarak çalıştırın ardından.

Kod:

DISM /Online /Cleanup-Image /RestoreHealth

komutunu girin. İşlemin tamamlanmasını bekleyin.

Bundan önceki hatalar diskten kaynaklanıyordu ancak HD Tune ile taratıp başka bir program ile bad sectorleri temizlememe rağmen bilgisayardaki donma ve mavi ekran sorununu çözemedim.

Recep Baltaş · 21 Eylül 2020

aaltan21 dedi:
Bundan önceki hatalar diskten kaynaklanıyordu ancak HD Tune ile taratıp başka bir program ile bad sectorleri temizlememe rağmen bilgisayardaki donma ve mavi ekran sorununu çözemedim.

Bad sector temizleme diye bir şey yok. Ancak görmezden gelebilir sistem. Bad sector veren bir diskten bir daha hayır gelmez...

Sorun disk kaynaklı:

Kod:

ERROR_CODE: (NTSTATUS) 0xc00000c0 - Bu ayg t, yok.

BLACKBOXDISK: 1

DISKSEC_ORG_ID:  WDC

DISKSEC_MODEL:  WDC WD3200AVVS-63L2B0

Kod:

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc0081cca8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc00000c0, error status (normally i/o status code)
Arg3: 000020001edc3860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80103995b0d, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

fffff8004da9de58: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff8004db5a308

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2155

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 16343

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_ltsb

    Key  : WER.OS.Timestamp
    Value: 2020-07-11T06:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.19780


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7a

BUGCHECK_P1: fffff6fc0081cca8

BUGCHECK_P2: ffffffffc00000c0

BUGCHECK_P3: 20001edc3860

BUGCHECK_P4: fffff80103995b0d

ERROR_CODE: (NTSTATUS) 0xc00000c0 - Bu ayg t, yok.

BLACKBOXDISK: 1

DISKSEC_ORG_ID:  WDC

DISKSEC_MODEL:  WDC WD3200AVVS-63L2B0         

DISKSEC_MANUFACTURING_ID:       WD-WCAV1858930

DISKSEC_ISSUE_DESC_STR: 

DISKSEC_TOTAL_SIZE: 188

DISKSEC_REASON: 1

DISKSEC_PUBLIC_TOTAL_SECTION_SIZE: 54

DISKSEC_PUBLIC_OFFSET: 12c

DISKSEC_PUBLIC_DATA_SIZE: 0

DISKSEC_PRIVATE_TOTAL_SECTION_SIZE: 8

DISKSEC_PRIVATE_OFFSET: 180

DISKSEC_PRIVATE_DATA_SIZE: 0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  ffffd000609a6420 -- (.trap 0xffffd000609a6420)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe001c0441c90 rbx=0000000000000000 rcx=fffff8010396b840
rdx=ffffe001c0165c10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80103995b0d rsp=ffffd000609a65b0 rbp=ffffe001bffe18c0
 r8=ffffe001c031b3c0  r9=0000000000000012 r10=0000000000000000
r11=fffff8004d95c8d3 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
srv2!SrvCleanup+0xd8cd:
fffff801`03995b0d ff1565b6fcff    call    qword ptr [srv2!_imp_IoGetCurrentProcess (fffff801`03961178)] ds:fffff801`03961178=????????????????
Resetting default scope

STACK_TEXT: 
ffffd000`609a6168 fffff800`4d8f3092     : 00000000`0000007a fffff6fc`0081cca8 ffffffff`c00000c0 00002000`1edc3860 : nt!KeBugCheckEx
ffffd000`609a6170 fffff800`4d9dd1a0     : 00000000`00000002 ffffd000`609a62d8 fffff800`4db52ec0 ffffd000`00000000 : nt!MiWaitForInPageComplete+0x722
ffffd000`609a6260 fffff800`4d856492     : 00000000`c0033333 00000000`00000000 ffffd000`609a6420 fffff801`03995b0d : nt!MiIssueHardFault+0x330
ffffd000`609a6320 fffff800`4d958b9d     : ffffe001`c0165c10 00000000`00000000 49db118e`1b833600 c449c362`b3c00bce : nt!MmAccessFault+0x6f2
ffffd000`609a6420 fffff801`03995b0d     : 00000000`00000004 00000000`00000001 ffffe001`c06ae8c0 00000000`00000001 : nt!KiPageFault+0x31d
ffffd000`609a65b0 fffff800`4dbeee35     : ffffe001`c0165c10 00000000`00000000 00000000`00000000 00000000`000000c8 : srv2!SrvCleanup+0xd8cd
ffffd000`609a65e0 fffff800`4dbf3d0a     : ffffe001`c0441c60 ffffe001`be2b29a0 ffffe001`c0441c70 ffffe001`c0441c00 : nt!IopCloseFile+0x12d
ffffd000`609a6670 fffff800`4dbf3b03     : 00000000`00000000 00000000`ffff8001 00000000`00000000 00000000`00000000 : nt!ObpDecrementHandleCount+0x1b6
ffffd000`609a6710 fffff800`4dc09722     : ffffc000`3a168c00 00000000`00000018 ffffc000`415eff08 00000000`00000010 : nt!ObCloseHandleTableEntry+0x313
ffffd000`609a67e0 fffff800`4dc093f1     : 00000000`00040001 ffffd000`609a6940 ffffe001`bffe18c0 ffffe001`c018b480 : nt!ExSweepHandleTable+0xba
ffffd000`609a6840 fffff800`4dc091bc     : 00000000`00040000 00000000`00000000 00000000`00000000 ffffe001`bffe18c0 : nt!ObKillProcess+0x31
ffffd000`609a6870 fffff800`4dbd7d87     : ffffe001`bffe18c0 ffffc000`39d56060 ffffd000`609a6940 00000000`00000000 : nt!PspRundownSingleProcess+0xa4
ffffd000`609a6900 fffff800`4dc7e31c     : ffff3b06`c0000005 ffffe001`c018b480 ffffd000`609a6c00 ffffe001`c018b528 : nt!PspExitThread+0x573
ffffd000`609a6a10 fffff800`4d8610aa     : ffffe001`c018b580 ffffe001`c0041ec0 ffffe001`c0041ed8 00000000`00000000 : nt!KiSchedulerApcTerminate+0x18
ffffd000`609a6a40 fffff800`4d950950     : 00000000`00000bd0 ffffd000`609a6ac0 fffff800`4d9c6c44 00000000`00000000 : nt!KiDeliverApc+0x2fa
ffffd000`609a6ac0 fffff800`4d95b48a     : ffffe001`c018b480 00000000`ffffffff 00000000`00000000 ffffe001`c03c7240 : nt!KiInitiateUserApc+0x70
ffffd000`609a6c00 00007ffd`831e074a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000d6`3891f618 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`831e074a


SYMBOL_NAME:  srv2!SrvCleanup+d8cd

MODULE_NAME: srv2

IMAGE_NAME:  srv2.sys

IMAGE_VERSION:  6.3.9600.19309

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  d8cd

FAILURE_BUCKET_ID:  0x7a_c00000c0_srv2!SrvCleanup

OS_VERSION:  8.1.9600.19780

BUILDLAB_STR:  winblue_ltsb

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {3a6323a7-ea7b-e310-6e94-3d23a0e06178}

Followup:     MachineOwner
---------

0: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.5, DMIVersion 0, Size=1960]
BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 080015
BiosReleaseDate = 04/15/2010
SystemManufacturer = BIOSTAR Group
SystemProductName = G41-M7
SystemFamily = To Be Filled By O.E.M.
SystemVersion = ' '
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = BIOSTAR Group
BaseBoardProduct = G41-M7
BaseBoardVersion = ' '

Kod:

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6e000b40c90, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00002000579f8880, current process (virtual address for lock type 3, or PTE)
Arg4: ffffc00168192cd8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

Unable to load image atapi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atapi.sys

************* Symbol Loading Error Summary **************
Module name            Error
atapi                  The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
fffff801dba9ee58: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff801dbb5b308

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2296

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 19131

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_ltsb

    Key  : WER.OS.Timestamp
    Value: 2020-07-11T06:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.19780


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7a

BUGCHECK_P1: fffff6e000b40c90

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: 2000579f8880

BUGCHECK_P4: ffffc00168192cd8

ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXDISK: 1

DISKSEC_ORG_ID:  WDC

DISKSEC_MODEL:  WDC WD3200AVVS-63L2B0         

DISKSEC_MANUFACTURING_ID:       WD-WCAV1858930

DISKSEC_ISSUE_DESC_STR: 

DISKSEC_TOTAL_SIZE: 188

DISKSEC_REASON: 1

DISKSEC_PUBLIC_TOTAL_SECTION_SIZE: 54

DISKSEC_PUBLIC_OFFSET: 12c

DISKSEC_PUBLIC_DATA_SIZE: 0

DISKSEC_PRIVATE_TOTAL_SECTION_SIZE: 8

DISKSEC_PRIVATE_OFFSET: 180

DISKSEC_PRIVATE_DATA_SIZE: 0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffd0008bbe7950 -- (.trap 0xffffd0008bbe7950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc00168192c30 rbx=0000000000000000 rcx=ffffe001c2d0aaf8
rdx=ffffe001c10a1a20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800a6af07e5 rsp=ffffd0008bbe7ae0 rbp=ffffd0008bbe7c80
 r8=ffffd0008bbe7c08  r9=ffffd0008bbe7c18 r10=ffffd0008bbe7c10
r11=ffffe001c2d0aaf8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
Ntfs!NtfsDecodeFileObject+0x21:
fffff800`a6af07e5 488b80a8000000  mov     rax,qword ptr [rax+0A8h] ds:ffffc001`68192cd8=????????????????
Resetting default scope

STACK_TEXT: 
ffffd000`8bbe7698 fffff801`db8f4092     : 00000000`0000007a fffff6e0`00b40c90 ffffffff`c000000e 00002000`579f8880 : nt!KeBugCheckEx
ffffd000`8bbe76a0 fffff801`db9de1a0     : 00000000`00000002 ffffd000`8bbe7808 fffff801`dbb53dc0 ffffd000`00000000 : nt!MiWaitForInPageComplete+0x722
ffffd000`8bbe7790 fffff801`db857492     : 00000000`c0033333 00000000`00000000 ffffd000`8bbe7950 ffffc001`68192cd8 : nt!MiIssueHardFault+0x330
ffffd000`8bbe7850 fffff801`db959b9d     : ffffe001`c2d0aaf8 00000000`00000800 ffffc001`67e2c900 ffffc905`ea23f988 : nt!MmAccessFault+0x6f2
ffffd000`8bbe7950 fffff800`a6af07e5     : 00000000`00000008 ffffe001`c10dd030 ffffe001`c1106538 00000000`00000000 : nt!KiPageFault+0x31d
ffffd000`8bbe7ae0 fffff800`a6bdd2f4     : ffffd000`8bbe7d38 00000000`00000000 ffffd000`8bbe7e00 00000000`00000000 : Ntfs!NtfsDecodeFileObject+0x21
ffffd000`8bbe7b20 fffff800`a6bc70b4     : ffffe001`c2d0aaf8 ffffe001`c2d0aaf8 ffffc001`68192c30 00000000`00000000 : Ntfs!NtfsMarkHandle+0x64
ffffd000`8bbe7c00 fffff800`a6bc75b0     : 00000000`00000000 ffffd000`8bbe7c80 00000000`00000001 ffffd000`8bbe7c80 : Ntfs!NtfsUserFsRequest+0x474
ffffd000`8bbe7c40 fffff800`a6379263     : ffffe001`c13c3010 ffffffff`80000200 00000000`00000000 ffffe001`c10a76a0 : Ntfs!NtfsFsdFileSystemControl+0x2e0
ffffd000`8bbe7d90 fffff800`a6345173     : ffffe001`c10a76a0 ffffc001`681915a0 ffffe001`c13c3010 ffffe001`c11060b8 : CLFS!CClfsContainer::MarkContainer+0x13f
ffffd000`8bbe7e20 fffff800`a637408e     : ffffe001`c10da000 ffffe001`c1106000 00000000`00000007 00000000`00000001 : CLFS!CClfsContainer::UnmarkSystemLogContainer+0x13
ffffd000`8bbe7e50 fffff800`a6373430     : ffffe001`c10da000 ffffe001`c1106000 ffffe001`bfc9ecd0 ffffe001`bfc9ecd0 : CLFS!CClfsBaseFilePersisted::UnmarkContainerQ+0xa2
ffffd000`8bbe7ec0 fffff800`a63685da     : ffffe001`c1106000 00000000`00000001 00000000`00000000 ffffe001`00000000 : CLFS!CClfsLogFcbPhysical::UnmarkLogFileContainers+0x60
ffffd000`8bbe7f10 fffff800`a6368657     : ffffe001`bfc2c040 00000000`00000000 ffffe001`00000000 ffffe001`00000013 : CLFS!CClfsLogCcb::Cleanup+0xbe
ffffd000`8bbe7f60 fffff800`a63641c9     : ffffe001`bfc9ecd0 ffffe001`bffd8780 00000000`00000000 ffffe001`bffd8780 : CLFS!CClfsRequest::Cleanup+0x5f
ffffd000`8bbe7fb0 fffff800`a63640b9     : ffffe001`bfc9ecd0 ffffe001`bfc9ecd0 00000000`00000000 00000000`00000001 : CLFS!ClfsDispatchIoRequest+0xe9
ffffd000`8bbe8000 fffff801`dbbefe35     : ffffe001`bfc9ecd0 ffffe001`bfc2c040 00000000`00000000 00000000`00000001 : CLFS!CClfsDriver::LogIoDispatch+0x21
ffffd000`8bbe8030 fffff801`dbbf29a3     : ffffe001`bfc93310 ffffd000`8bbe8179 00000000`00000000 00000000`00000000 : nt!IopCloseFile+0x12d
ffffd000`8bbe80c0 fffff801`db95c3e3     : 00000000`00000000 fffff800`a6358010 00000000`00000000 00000000`00000200 : nt!NtClose+0x1c3
ffffd000`8bbe81e0 fffff801`db9504a0     : fffff800`a6368e14 00000000`00000000 fffff800`a636af35 ffffe001`c1107dd0 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`8bbe8378 fffff800`a6368e14     : 00000000`00000000 fffff800`a636af35 ffffe001`c1107dd0 ffffc001`68179000 : nt!KiServiceLinkage
ffffd000`8bbe8380 fffff800`a6bd9b7b     : 00000000`00000108 ffffe001`c27ca2e8 ffffe001`c27ca2e8 ffffc001`68179000 : CLFS!ClfsCloseLogFileObject+0x6c
ffffd000`8bbe83c0 fffff800`a6bda394     : ffffe001`c27ca2e8 ffffc001`68179000 ffffe001`c10dd180 ffffe001`c27ca201 : Ntfs!TxfShutdownRm+0x92c
ffffd000`8bbe84a0 fffff800`a6b0cd63     : ffffe001`c27ca2e8 ffffe001`c10dd180 00000000`00000000 ffffe001`c27ca201 : Ntfs!TxfShutdownVolume+0x130
ffffd000`8bbe8550 fffff800`a6bef3ac     : 00000000`00000001 ffffd000`8bbe8740 00000000`00000000 00000000`00000000 : Ntfs!TxfSurpriseShutdownVolume+0xdf
ffffd000`8bbe85a0 fffff800`a6bef65a     : ffffe001`c27ca2e8 ffffd000`8bbe8701 ffffd000`8bbe8710 ffffd000`8bbe8700 : Ntfs!NtfsCommonPnp+0x6cf
ffffd000`8bbe8660 fffff800`a64030da     : ffffe001`c2c278a0 00000000`00000000 ffffd000`00000000 ffffe001`c27ca2e8 : Ntfs!NtfsFsdPnp+0x186
ffffd000`8bbe8700 fffff800`a64010c2     : ffffd000`8bbe87c0 ffffe001`c10ab160 ffffd000`8bbe88b0 ffffe001`c13c3010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x25a
ffffd000`8bbe87a0 fffff801`dbbab01e     : ffffe001`c10ab160 00000000`00000000 ffffd000`8bbe88b0 00000000`0000000b : fltmgr!FltpDispatch+0xb2
ffffd000`8bbe8800 fffff801`dbcbbfb8     : 00000000`00000017 ffffd000`8bbe88c9 ffffe001`c0cd47c0 ffffe001`c0cd77d0 : nt!IopSynchronousCall+0xfe
ffffd000`8bbe8870 fffff801`dbcb94b7     : ffffc001`67ed1e80 ffffc001`67c01790 00000000`00000000 00000000`00000000 : nt!IopRemoveDevice+0xe0
ffffd000`8bbe8930 fffff801`dbcbb939     : ffffe001`c0cd47c0 00000000`00000000 ffffc001`67c01790 ffffc001`67c01790 : nt!PnpSurpriseRemoveLockedDeviceNode+0xbb
ffffd000`8bbe8990 fffff801`dbcbb852     : 00000000`00000000 ffffc001`67c01790 ffffe001`c0cd47c0 fffff801`dbcb96f2 : nt!PnpDeleteLockedDeviceNode+0xad
ffffd000`8bbe89d0 fffff801`dbcbaeb9     : ffffe001`c0cd77d0 ffffd000`00000002 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x9a
ffffd000`8bbe8a50 fffff801`dbb94159     : ffffc001`67ed1e00 00000000`00000001 ffffc001`00000003 ffffe001`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x78d
ffffd000`8bbe8bb0 fffff801`dbb94587     : ffffc001`67ed1e80 00000000`00000000 00000000`00000000 fffff801`dbb94268 : nt!PnpProcessTargetDeviceEvent+0x9d
ffffd000`8bbe8bf0 fffff801`db8795bf     : fffff801`dbb94268 ffffc001`7217b8b0 ffffe001`c07d3880 ffffe001`bfc4d740 : nt!PnpDeviceEventWorker+0x31f
ffffd000`8bbe8c50 fffff801`db8cf93e     : 39333233`12333733 ffffd000`8b7dc180 00000000`00000080 ffffe001`bfc2c040 : nt!ExpWorkerThread+0x69f
ffffd000`8bbe8d00 fffff801`db953f66     : ffffd000`8b7dc180 ffffe001`c07d3880 ffffe001`c0739580 00000000`00000000 : nt!PspSystemThreadStartup+0x18a
ffffd000`8bbe8d60 00000000`00000000     : ffffd000`8bbe9000 ffffd000`8bbe3000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME:  CLFS!CClfsContainer::MarkContainer+13f

MODULE_NAME: CLFS

IMAGE_NAME:  CLFS.SYS

IMAGE_VERSION:  6.3.9600.19697

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  13f

FAILURE_BUCKET_ID:  0x7a_c000000e_CLFS!CClfsContainer::MarkContainer

OS_VERSION:  8.1.9600.19780

BUILDLAB_STR:  winblue_ltsb

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {42d88476-2b26-b3a6-f1f5-39c16aa0da80}

Followup:     MachineOwner
---------

1: kd> lmvm CLFS
Browse full module list
start             end                 module name
fffff800`a633c000 fffff800`a639e000   CLFS       (pdb symbols)          C:\ProgramData\Dbg\sym\clfs.pdb\503D35E3874F4CCABCCFC8F76D4DD0DA2\clfs.pdb
    Loaded symbol image file: CLFS.SYS
    Mapped memory image file: C:\ProgramData\Dbg\sym\CLFS.SYS\5E91F87462000\CLFS.SYS
    Image path: CLFS.SYS
    Image name: CLFS.SYS
    Browse all global symbols  functions  data
    Timestamp:        Sat Apr 11 20:03:48 2020 (5E91F874)
    CheckSum:         0006887D
    ImageSize:        00062000
    File version:     6.3.9600.19697
    Product version:  6.3.9600.19697
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     clfs.sys
        OriginalFilename: Clfs.Sys
        ProductVersion:   6.3.9600.19697
        FileVersion:      6.3.9600.19697 (winblue_ltsb.200411-0600)
        FileDescription:  Common Log File System Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

Assecreed · 21 Eylül 2020

Birde HDD'in kablosunu kontrol eder misiniz? 0xC000000E hatası ya disk sorununu ya da diskin bağlantısı ile ilgili sorunları belirtir. Ama altındaki yazıda
DISK_HARDWARE_ERROR: There was error with disk hardware
yazması disk hatası olduğunu açıklıyor.
Ama yinede kabloyu kontrol etmenizde fayda var. Önceki konuda diskin durumu o kadar kötü değildi.

aaltan21 · 21 Eylül 2020

Assecreed dedi:
Bir de HDD'in kablosunu kontrol eder misiniz? 0xC000000E hatası ya disk sorununu ya da diskin bağlantısı ile ilgili sorunları belirtir. Ama altındaki yazıda.
DISK_HARDWARE_ERROR: There was error with disk hardware.
Yazması disk hatası olduğunu açıklıyor.
Ama yine de kabloyu kontrol etmenizde fayda var. Önceki konuda diskin durumu o kadar kötü değildi.

Evet, hatta 1 hafta önceye kadar böyle bir sorun bile yoktu diskle. 2 tane kablom var diğer kabloyu takmayı denerim kablodan kaynaklı olduğunu düşündüğün için. Ancak benim anlamadığım bad sector hatalarını silmesine yani o bölgeyi artık veri yazılamaz hale getirmesine rağmen hala donma kasma mavi ekran sorunları var.

Assecreed · 21 Eylül 2020

HD Tune ile Health sekmesini yeniden paylaşın ve error scan yapın.
Başka sorunlar olmalı.

aaltan21 · 21 Eylül 2020

Assecreed dedi:
aylaşın ve e

Assecreed dedi:
HD Tune ile Health sekmesini yeniden paylaşın ve error scan yapın.
Başka sorunlar olmalı.

Untitled.png

drive.google.com

Buyrun health sekmesi böyle.Anladığım kadarıyla 3 tane daha bad sector oluşmuş en son silme işleminden sonra.

ViooYa · 21 Eylül 2020

Mümkün olan en kısa zamanda yedeğinizi alıp kurtulun bu diskten. Artarak devam edecektir.

Çözüldü KERNEL_DATA_INPAGE_ERROR mavi ekran hatası

Ayrıntılı düzenleme

aaltan21

Femtopat

ViooYa

Trieetz

Kilopat

ViooYa

Megapat

aaltan21

Femtopat

Recep Baltaş

Technopat

Assecreed

Megapat

aaltan21

Femtopat

Assecreed

Megapat

aaltan21

Femtopat

Untitled.png

ViooYa

Megapat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz