Hard diskten "tık" sesi ve mavi ekran hatası

İşletim sistemi
Windows 10

Wazquelin

Centipat
Katılım
16 Mayıs 2022
Mesajlar
16
Daha fazla  
Cinsiyet
Erkek
SSD veya HDD modeli
Turbox SSD 128 gb harddisk modeli bilmiyorum 500 g
Ekran kartı
rx 570
İşlemci
i5 3470

Sanırım tık sesi hard diskten geliyor. Discord'da arkadaşlarımla falan konuşurken bir anda sesleri kesiliyor. Oyun anlık takılıyor. Bununla alakalı mı bilmiyorum ama arada Valorant'ı açmaya çalıştığımda tık sesi ile beraber mavi ekran yiyorum.

@Recep Baltaş
 

Dosya Ekleri

  • hata.png
    hata.png
    71,7 KB · Görüntüleme: 32
Son düzenleme:
Kod:
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\alien\AppData\Local\Temp\Rar$DIa2004.46212\092322-141328-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 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`20000000 PsLoadedModuleList = 0xfffff800`20c2a290
Debug session time: Fri Sep 23 20:25:50.223 2022 (UTC + 3:00)
System Uptime: 0 days 0:03:36.916
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`203f8fa0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffee08`f2459dc0=000000000000007a
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffb665c200b5d0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000483, error status (normally i/o status code)
Arg3: 000020009390f880, current process (virtual address for lock type 3, or PTE)
Arg4: ffffcb84016bac68, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 4624

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 19624

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

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

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

Key  : Bugcheck.Code.DumpHeader
Value: 0x7a

Key  : Bugcheck.Code.Register
Value: 0x7a

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB:  092322-141328-01.dmp

BUGCHECK_CODE:  7a

BUGCHECK_P1: ffffb665c200b5d0

BUGCHECK_P2: ffffffffc0000483

BUGCHECK_P3: 20009390f880

BUGCHECK_P4: ffffcb84016bac68

ERROR_CODE: (NTSTATUS) 0xc0000483 -  nemli bir cihaz donan m hatas  nedeniyle istek ba ar s z oldu.

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffee08f245a160 -- (.trap 0xffffee08f245a160)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcb840003eb38 rbx=0000000000000000 rcx=ffffcb84016bac68
rdx=ffffb88f999a6bf0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80020330fcc rsp=ffffee08f245a2f0 rbp=ffffb88f999a6be8
r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80020330f80
r11=ffffcdfd24e00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlDeleteNoSplay+0x4c:
fffff800`20330fcc 488909          mov     qword ptr [rcx],rcx ds:ffffcb84`016bac68=00003910390e3904
Resetting default scope

STACK_TEXT: 
ffffee08`f2459db8 fffff800`202f1c69     : 00000000`0000007a ffffb665`c200b5d0 ffffffff`c0000483 00002000`9390f880 : nt!KeBugCheckEx
ffffee08`f2459dc0 fffff800`202ef4f5     : ffffee08`00001000 ffffee08`f2459f00 ffffee08`f2459f50 fffff800`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffffee08`f2459eb0 fffff800`20239a48     : 00000000`c0033333 00000000`00000000 ffffcb84`016bac68 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffee08`f2459fc0 fffff800`2040715e     : 00000000`00000000 00000000`00000220 ffffcb83`e6c00100 fffff800`20224252 : nt!MmAccessFault+0x468
ffffee08`f245a160 fffff800`20330fcc     : 00000000`00000009 00000000`00000000 00000000`00000103 00000000`00000000 : nt!KiPageFault+0x35e
ffffee08`f245a2f0 fffff800`1cc28b10     : 00000000`00000000 fffff800`2020e45e ffffb88f`8c7b7140 ffffb88f`999a6be8 : nt!RtlDeleteNoSplay+0x4c
ffffee08`f245a320 fffff800`1cc5a63b     : ffffb88f`999a6bf0 fffff800`00000000 00000000`00000000 ffffffff`ffffffff : FLTMGR!TreeUnlinkMulti+0x90
ffffee08`f245a370 fffff800`1cc5aba2     : ffffb88f`999a6be8 ffffcb83`fb7cc010 ffffffff`ffffffff ffffb88f`8f1c2588 : FLTMGR!FltpDeleteContextList+0x4b
ffffee08`f245a3a0 fffff800`1cc5b10a     : ffffb88f`999a6ba0 ffffb88f`999a6ba8 ffffb88f`999a6ba0 ffffb88f`999a6ba0 : FLTMGR!CleanupStreamListCtrl+0x4a
ffffee08`f245a3e0 fffff800`20658939     : ffffcb83`fb7cc1a8 ffffb88f`999a6ba8 00000000`00000000 00000000`00000705 : FLTMGR!DeleteStreamListCtrlCallback+0xba
ffffee08`f245a420 fffff800`22f53ddb     : ffffcb83`fb7cc170 00000000`00000000 00000000`00000705 ffffee08`f245a568 : nt!FsRtlTeardownPerStreamContexts+0xc9
ffffee08`f245a460 fffff800`22f53616     : ffffee08`f245a8f0 ffff70fa`33320705 ffffcb83`fb7cc470 ffffee08`f245a6c2 : Ntfs!NtfsDeleteScb+0x6cb
ffffee08`f245a500 fffff800`22e39795     : 00000000`00000002 ffffcb83`fb7cc170 00000000`00000000 00000000`00000001 : Ntfs!NtfsRemoveScb+0x66
ffffee08`f245a560 fffff800`22f533ac     : ffffee08`f245a8f0 00000000`00000000 ffffcb83`fb7cc010 ffffb88f`8f1c3100 : Ntfs!NtfsPrepareFcbForRemoval+0x75
ffffee08`f245a5a0 fffff800`22e38f56     : ffffee08`f245a8f0 ffffcb83`fb7cc170 ffffcb83`fb7cc470 ffffcb83`fb7cc010 : Ntfs!NtfsTeardownStructures+0x9c
ffffee08`f245a620 fffff800`22f1530f     : ffffee08`f245a8f0 fffff800`22f29e20 00000000`00000000 ffffcb83`fb7cc000 : Ntfs!NtfsDecrementCloseCounts+0xf6
ffffee08`f245a680 fffff800`22f2b1c4     : ffffee08`f245a8f0 ffffcb83`fb7cc170 ffffcb83`fb7cc010 ffffb88f`8f1c3180 : Ntfs!NtfsCommonClose+0xadf
ffffee08`f245a750 fffff800`22f29ea8     : 00000000`0000001c fffff800`20d25440 00000000`00000000 00000000`00000000 : Ntfs!NtfsFspCloseInternal+0x244
ffffee08`f245a8b0 fffff800`20252b65     : ffffb88f`8c7b7140 fffff800`202f6df0 ffffb88f`8c688ca0 ffffb88f`00000000 : Ntfs!NtfsFspClose+0x88
ffffee08`f245ab70 fffff800`20271d25     : ffffb88f`8c7b7140 00000000`00000080 ffffb88f`8c689040 00000000`00000000 : nt!ExpWorkerThread+0x105
ffffee08`f245ac10 fffff800`20400628     : fffff800`1b94d180 ffffb88f`8c7b7140 fffff800`20271cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffee08`f245ac60 00000000`00000000     : ffffee08`f245b000 ffffee08`f2455000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!MiWaitForInPageComplete+7d9

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.2006

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  7d9

FAILURE_BUCKET_ID:  0x7a_c0000483_nt!MiWaitForInPageComplete

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e8dd9efb-9408-9f35-7b8e-33c3443ec6de}

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

Diskiniz ile alakalı bir problem gibi duruyor, HD Tune ile diskinizi tarayıp bad sector var mı diye kontrol edin.
 
Kod:
Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64.
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\alien\AppData\Local\Temp\Rar$DIa2004.46212\092322-141328-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 19041 MP (4 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`20000000 PsLoadedModuleList = 0xfffff800`20c2a290
Debug session time: Fri Sep 23 20:25:50.223 2022 (UTC + 3:00)
System Uptime: 0 days 0:03:36.916
Loading Kernel Symbols.
...............................................................
................................................................
.......................................................
Loading User Symbols.
Loading unloaded module list.
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`203f8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffee08`f2459dc0=000000000000007a
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: ffffb665c200b5d0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000483, error status (normally i/o status code)
Arg3: 000020009390f880, current process (virtual address for lock type 3, or PTE)
Arg4: ffffcb84016bac68, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4624.

Key : Analysis.DebugAnalysisManager
Value: Create.

Key : Analysis.Elapsed.mSec
Value: 19624.

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x7a.

Key : Bugcheck.Code.Register
Value: 0x7a.

Key : WER.OS.Branch
Value: vb_release.

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 092322-141328-01.dmp

BUGCHECK_CODE: 7a.

BUGCHECK_P1: ffffb665c200b5d0.

BUGCHECK_P2: ffffffffc0000483.

BUGCHECK_P3: 20009390f880.

BUGCHECK_P4: ffffcb84016bac68.

ERROR_CODE: (NTSTATUS) 0xc0000483 - nemli bir cihaz donan m hatas nedeniyle istek ba ar s z oldu.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

TRAP_FRAME: ffffee08f245a160 -- (.trap 0xffffee08f245a160)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcb840003eb38 rbx=0000000000000000 rcx=ffffcb84016bac68
rdx=ffffb88f999a6bf0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80020330fcc rsp=ffffee08f245a2f0 rbp=ffffb88f999a6be8
r8=ffffffffffffffff r9=ffffffffffffffff r10=fffff80020330f80
r11=ffffcdfd24e00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc.
nt!RtlDeleteNoSplay+0x4c:
fffff800`20330fcc 488909 mov qword ptr [rcx],rcx ds:ffffcb84`016bac68=00003910390e3904
Resetting default scope.

STACK_TEXT:
ffffee08`f2459db8 fffff800`202f1c69 : 00000000`0000007a ffffb665`c200b5d0 ffffffff`c0000483 00002000`9390f880 : nt!KeBugCheckEx
ffffee08`f2459dc0 fffff800`202ef4f5 : ffffee08`00001000 ffffee08`f2459f00 ffffee08`f2459f50 fffff800`00000000 : nt!MiWaitForInPageComplete+0x7d9
ffffee08`f2459eb0 fffff800`20239a48 : 00000000`c0033333 00000000`00000000 ffffcb84`016bac68 00000000`00000000 : nt!MiIssueHardFault+0x3c5
ffffee08`f2459fc0 fffff800`2040715e : 00000000`00000000 00000000`00000220 ffffcb83`e6c00100 fffff800`20224252 : nt!MmAccessFault+0x468
ffffee08`f245a160 fffff800`20330fcc : 00000000`00000009 00000000`00000000 00000000`00000103 00000000`00000000 : nt!KiPageFault+0x35e
ffffee08`f245a2f0 fffff800`1cc28b10 : 00000000`00000000 fffff800`2020e45e ffffb88f`8c7b7140 ffffb88f`999a6be8 : nt!RtlDeleteNoSplay+0x4c
ffffee08`f245a320 fffff800`1cc5a63b : ffffb88f`999a6bf0 fffff800`00000000 00000000`00000000 ffffffff`ffffffff : FLTMGR!TreeUnlinkMulti+0x90
ffffee08`f245a370 fffff800`1cc5aba2 : ffffb88f`999a6be8 ffffcb83`fb7cc010 ffffffff`ffffffff ffffb88f`8f1c2588 : FLTMGR!FltpDeleteContextList+0x4b
ffffee08`f245a3a0 fffff800`1cc5b10a : ffffb88f`999a6ba0 ffffb88f`999a6ba8 ffffb88f`999a6ba0 ffffb88f`999a6ba0 : FLTMGR!CleanupStreamListCtrl+0x4a
ffffee08`f245a3e0 fffff800`20658939 : ffffcb83`fb7cc1a8 ffffb88f`999a6ba8 00000000`00000000 00000000`00000705 : FLTMGR!DeleteStreamListCtrlCallback+0xba
ffffee08`f245a420 fffff800`22f53ddb : ffffcb83`fb7cc170 00000000`00000000 00000000`00000705 ffffee08`f245a568 : nt!FsRtlTeardownPerStreamContexts+0xc9
ffffee08`f245a460 fffff800`22f53616 : ffffee08`f245a8f0 ffff70fa`33320705 ffffcb83`fb7cc470 ffffee08`f245a6c2 : Ntfs!NtfsDeleteScb+0x6cb
ffffee08`f245a500 fffff800`22e39795 : 00000000`00000002 ffffcb83`fb7cc170 00000000`00000000 00000000`00000001 : Ntfs!NtfsRemoveScb+0x66
ffffee08`f245a560 fffff800`22f533ac : ffffee08`f245a8f0 00000000`00000000 ffffcb83`fb7cc010 ffffb88f`8f1c3100 : Ntfs!NtfsPrepareFcbForRemoval+0x75
ffffee08`f245a5a0 fffff800`22e38f56 : ffffee08`f245a8f0 ffffcb83`fb7cc170 ffffcb83`fb7cc470 ffffcb83`fb7cc010 : Ntfs!NtfsTeardownStructures+0x9c
ffffee08`f245a620 fffff800`22f1530f : ffffee08`f245a8f0 fffff800`22f29e20 00000000`00000000 ffffcb83`fb7cc000 : Ntfs!NtfsDecrementCloseCounts+0xf6
ffffee08`f245a680 fffff800`22f2b1c4 : ffffee08`f245a8f0 ffffcb83`fb7cc170 ffffcb83`fb7cc010 ffffb88f`8f1c3180 : Ntfs!NtfsCommonClose+0xadf
ffffee08`f245a750 fffff800`22f29ea8 : 00000000`0000001c fffff800`20d25440 00000000`00000000 00000000`00000000 : Ntfs!NtfsFspCloseInternal+0x244
ffffee08`f245a8b0 fffff800`20252b65 : ffffb88f`8c7b7140 fffff800`202f6df0 ffffb88f`8c688ca0 ffffb88f`00000000 : Ntfs!NtfsFspClose+0x88
ffffee08`f245ab70 fffff800`20271d25 : ffffb88f`8c7b7140 00000000`00000080 ffffb88f`8c689040 00000000`00000000 : nt!ExpWorkerThread+0x105
ffffee08`f245ac10 fffff800`20400628 : fffff800`1b94d180 ffffb88f`8c7b7140 fffff800`20271cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffee08`f245ac60 00000000`00000000 : ffffee08`f245b000 ffffee08`f2455000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nt!MiWaitForInPageComplete+7d9

MODULE_NAME: nt.

IMAGE_VERSION: 10.0.19041.2006

STACK_COMMAND: .cxr; .ecxr ; kb.

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 7d9.

FAILURE_BUCKET_ID: 0x7a_c0000483_nt!MiWaitForInPageComplete

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {e8dd9efb-9408-9f35-7b8e-33c3443ec6de}

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

Diskiniz ile alakalı bir problem gibi duruyor, HD Tune ile diskinizi tarayıp bad sector var mı diye kontrol edin.

İlk taramayı yaptığımda bu ilk attığım ssdeki hatayı alıyorum. Hata taramasını quick şekilde yaptığıda 2. ssdeki gibi oldu. Quick olmadan tarattığımda 3. ssteki gibi sürekli kırmızı verdi ve kırmızı verdiğinde anlattığım tık sesi geliyordu bilgisayardan devamında tekrardan mavi ekran yedim zaten o yüzden testin devamını yapamdım.
 

Dosya Ekleri

  • disk.png
    disk.png
    22,7 KB · Görüntüleme: 21
  • quick.png
    quick.png
    28,6 KB · Görüntüleme: 17
  • mavi ekran.png
    mavi ekran.png
    19,1 KB · Görüntüleme: 19
İlk taramayı yaptığımda bu ilk attığım ssdeki hatayı alıyorum. Hata taramasını quick şekilde yaptığıda 2. ssdeki gibi oldu. Quick olmadan tarattığımda 3. ssteki gibi sürekli kırmızı verdi ve kırmızı verdiğinde anlattığım tık sesi geliyordu bilgisayardan devamında tekrardan mavi ekran yedim zaten o yüzden testin devamını yapamdım.

Diskiniz kaç yıllık.
 
Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
Böyle bir ses mi?
 
Diskiniz kaç yıllık.

Bilgisayarla beraber almıştım yaklaşık 1.5 yıldır kullanıyorum.

Lafı uzatmaya gerek yok. Disk ölmüş. Bad sectorden dolayı okuma yazma yapamıyor ve sistem hata veriyor. Ayrıca bad sector taraması yaparken "quick scan" tiki kapalı olacak şekilde yapılmalıdır.

Kapalı olduğunda yarısında mavi ekran verdi.

Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
Böyle bir ses mi?

Tam olarak olmasa da benziyor sanırım.
 
Kapalı olduğunda yarısında mavi ekran verdi.

Tekrar ediyorum. Tık sesi kafa vurma sesidir. Diskte bozuk alanlar mevcut. İşletim sistemi diske kurulu olduğu için sistem mavi ekran veriyor. Çünkü kararsızlık yaratıyor. Yeni bir disk alın ve temiz kurulum yapın.
 

Geri
Yukarı