Mavi ekran hatası

Detaylı bilgi verir misin? Laptop mu kullanıyorsun? Masaüstü mü? Kısa zaman önce herhangi bir parçan arızalandı mı? Mavi ekran yedikten sonra herhangi bir yazı çıkıyor mu?

Zaten dump dosyalarını yolladım çeşit çeşit hata isimleri alıyorum kernel_data_ınpage_error critical process died vb hatalar yedim masaüstü arzalı parçam yok kasamda.

kaonashii99 dedi:

Arızalı parçam yok kasamda.

Genişletmek için tıkla...

Emin misiniz? O halde sürpriz! Sisteme takılı depolama biriminiz arızalı. Lütfen HD Tune 5.75 indirin ve oradaki Health sekmesinin ekran alıntısını paylaşın. Son olarak "Quick Scan" tiki kapalıyken Error scan yapın.

[CODE title="Dökümler"]*******************************************************************************
* *
* 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: ffffd00ef7a13120, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7718

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 28694

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

Key : Analysis.System
Value: CreateObject

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

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 7a

BUGCHECK_P1: 20

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: ffffd00ef7a13120

BUGCHECK_P4: 0

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

DISK_HARDWARE_ERROR: There was error with disk hardware

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8609`8d6df5e8 fffff800`4129e57c : 00000000`0000007a 00000000`00000020 ffffffff`c000000e ffffd00e`f7a13120 : nt!KeBugCheckEx
ffff8609`8d6df5f0 fffff800`41120afb : 00000000`00000000 00000000`c000000e 00000000`00000000 00000000`00100000 : nt!MiWriteComplete+0x14ac3c
ffff8609`8d6df6a0 fffff800`41067ce0 : ffffd00e`f7a240c0 ffffd00e`f8376088 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x4b
ffff8609`8d6df6d0 fffff800`41065b77 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1b0
ffff8609`8d6df780 fffff800`41064d7f : 00000000`00000002 00000000`00000001 ffff8609`8d6df970 00000000`00000000 : nt!KiSwapThread+0x827
ffff8609`8d6df830 fffff800`41043d5e : ffffd00e`00000000 fffff800`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffff8609`8d6df8d0 fffff800`411baf1e : ffffd00e`00000004 fffff800`00000012 fffff800`41a50bc0 ffff8800`1eb2c180 : nt!KeWaitForMultipleObjects+0x2be
ffff8609`8d6df9e0 fffff800`41117e25 : ffffd00e`f7a240c0 ffffd00e`f7a240c0 00000000`00000080 fffff800`411bad80 : nt!MiModifiedPageWriter+0x19e
ffff8609`8d6dfc10 fffff800`411fd0d8 : ffff8800`1eb2c180 ffffd00e`f7a240c0 fffff800`41117dd0 00824c98`00000034 : nt!PspSystemThreadStartup+0x55
ffff8609`8d6dfc60 00000000`00000000 : ffff8609`8d6e0000 ffff8609`8d6da000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nt!MiWriteComplete+14ac3c

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 14ac3c

FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWriteComplete

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fcc12098-ee04-35bd-5cea-593a2c6ec31d}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffff9f0f84f430c0, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 8968

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 20164

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

Key : Analysis.System
Value: CreateObject

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

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: ef

BUGCHECK_P1: ffff9f0f84f430c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: services.exe

CRITICAL_PROCESS: services.exe

EXCEPTION_RECORD: ffff9f0f84f43800 -- (.exr 0xffff9f0f84f43800)
ExceptionAddress: 0000000000000000
ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0

ERROR_CODE: (NTSTATUS) 0x855350c0 - <Unable to get error code text>

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

EXCEPTION_STR: 0x0

STACK_TEXT:
ffff8707`a5132d88 fffff800`4ad06962 : 00000000`000000ef ffff9f0f`84f430c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8707`a5132d90 fffff800`4ac49f61 : 00000000`00000001 fffff800`4a75971d 00000000`00000002 fffff800`4a758d37 : nt!PspCatchCriticalBreak+0x10e
ffff8707`a5132e30 fffff800`4ab09ca4 : ffff9f0f`00000000 00000000`00000000 ffff9f0f`84f430c0 ffff9f0f`84f434f8 : nt!PspTerminateAllThreads+0x1409f5
ffff8707`a5132ea0 fffff800`4ab09fcc : ffff9f0f`84f430c0 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffff8707`a5132ee0 fffff800`4a8074b8 : ffff9f0f`84f430c0 ffff9f0f`855350c0 ffff8707`a5132fd0 fffff800`4ab1e2e2 : nt!NtTerminateProcess+0x9c
ffff8707`a5132f50 fffff800`4a7f98e0 : fffff800`4a89154d ffff8707`a5133a58 ffff8707`a5133a58 ffffffff`ffffffff : nt!KiSystemServiceCopyEnd+0x28
ffff8707`a51330e8 fffff800`4a89154d : ffff8707`a5133a58 ffff8707`a5133a58 ffffffff`ffffffff 00007ff6`e0381000 : nt!KiServiceLinkage
ffff8707`a51330f0 fffff800`4a807bac : ffff9f0f`84f43800 fffff800`4a7540e6 00000000`00003200 ffff8707`a5133b00 : nt!KiDispatchException+0x166b4d
ffff8707`a5133920 fffff800`4a803d43 : 000000e7`2d560df0 00000227`a3885360 ffff8707`a5133b80 ffff9f0f`00000000 : nt!KiExceptionDispatch+0x12c
ffff8707`a5133b00 00007ffc`1b5d41b2 : 00000000`00000000 000000e7`00000000 000000e7`2d551700 000000e7`2d551708 : nt!KiPageFault+0x443
000000e7`2d5516e0 00000000`00000000 : 000000e7`00000000 000000e7`2d551700 000000e7`2d551708 00007ff6`e0381000 : 0x00007ffc`1b5d41b2

SYMBOL_NAME: nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 10e

FAILURE_BUCKET_ID: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_855350c0_nt!PspCatchCriticalBreak

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ff942ff9-516c-9625-86b0-24b5c4a16ad9}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffff800d4b7ce0c0, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 10499

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-5QPUIS0

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 23970

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

Key : Analysis.System
Value: CreateObject

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

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: ef

BUGCHECK_P1: ffff800d4b7ce0c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: csrss.exe

CRITICAL_PROCESS: csrss.exe

EXCEPTION_RECORD: ffff800d4b7ce800 -- (.exr 0xffff800d4b7ce800)
ExceptionAddress: 0000000000000000
ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0

ERROR_CODE: (NTSTATUS) 0x4d5680c0 - <Unable to get error code text>

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

EXCEPTION_STR: 0x0

STACK_TEXT:
ffffe805`be5a2d88 fffff806`5b106962 : 00000000`000000ef ffff800d`4b7ce0c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffe805`be5a2d90 fffff806`5b049f61 : 00000000`00000001 fffff806`5ab5971d 00000000`00000002 fffff806`5ab58d37 : nt!PspCatchCriticalBreak+0x10e
ffffe805`be5a2e30 fffff806`5af09ca4 : ffff800d`00000000 00000000`00000000 ffff800d`4b7ce0c0 ffff800d`4b7ce4f8 : nt!PspTerminateAllThreads+0x1409f5
ffffe805`be5a2ea0 fffff806`5af09fcc : ffff800d`4b7ce0c0 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffffe805`be5a2ee0 fffff806`5ac074b8 : ffff800d`4b7ce0c0 ffff800d`4d5680c0 ffffe805`be5a2fd0 fffff806`5af1e2e2 : nt!NtTerminateProcess+0x9c
ffffe805`be5a2f50 fffff806`5abf98e0 : fffff806`5ac9154d ffffe805`be5a3a58 ffffe805`be5a3a58 ffffffff`ffffffff : nt!KiSystemServiceCopyEnd+0x28
ffffe805`be5a30e8 fffff806`5ac9154d : ffffe805`be5a3a58 ffffe805`be5a3a58 ffffffff`ffffffff 00007ffd`283e3000 : nt!KiServiceLinkage
ffffe805`be5a30f0 fffff806`5ac07bac : ffff800d`4b7ce800 fffff806`5aa0ecc6 00000000`00000c00 ffffe805`be5a3b00 : nt!KiDispatchException+0x166b4d
ffffe805`be5a3920 fffff806`5ac03d43 : 00000000`0004b66c 00000000`00000000 ffffe805`be5a3b80 ffff800d`40a92df0 : nt!KiExceptionDispatch+0x12c
ffffe805`be5a3b00 00007ffd`2acd41b2 : 00000000`00000000 000000e9`00000000 000000e9`c78c1500 000000e9`c78c1508 : nt!KiPageFault+0x443
000000e9`c78c14e0 00000000`00000000 : 000000e9`00000000 000000e9`c78c1500 000000e9`c78c1508 00007ffd`283e3000 : 0x00007ffd`2acd41b2

SYMBOL_NAME: nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.804

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 10e

FAILURE_BUCKET_ID: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_4d5680c0_nt!PspCatchCriticalBreak

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d3d405e7-3d72-c8ef-2dc1-2cff8896fdb4}

Followup: MachineOwner
---------[/CODE]

HDD mi yoksa SSD mi peki 3 mavi ekranıda depolamadan dolayı mı yemişim

Mavi ekranların nedeni dediğim gibi diskten dolayı. Hem SSD'nin hem de HDD'nin S.M.A.R.T. verilerini tek tek paylaşın ve HDD'ye error scan uygulayın.

HDD şu an kasamla bağlantısını kestim garantiye yollayıcam burada ben dediğiniz programla verileri paylaşmıştım bir hata gözükmüyordu şu an kontrol edeceğim mavi ekran yiyip yemediğimi olursa bir daha alırsam artık bilmiyorum.

Muhtemel olarak SSD diskiniz arızalı olabilir çünkü pagefile yani sanal RAM sorun çıkartmış. Sanal RAM'i HDD'ye atamadıysanız ve normalde olduğu gibi SSD'ye atadıysanız sorun SSD'de olmalı. Her iki diskin de verilerini paylaşın. Size durumu iyi dese dahi verileri okuyup anlamak şart.

İstenmişti ve aynı hataları söylemişlerdi testlerde ki sonuçlar bunlardı.

SSD diskinizin sağlığı kaç ay öncesinde epey düşükmüş. HD Tune 5.75 ile onun da erilerini paylaşıp ona da error scan yapar mısınız?