Çözüldü CRITICAL_PROCESS_DIED ve diğer hatalar

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

mfs1907

Attopat
Katılım
27 Mayıs 2021
Mesajlar
4
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Merhaba; Legion Y520-15IKBM Laptop (Lenovo) - Type 80YY bilgisayarımda bir haftadır devam eden ve giderek sıklaşan mavi ekran hataları almaya başladım. Bunlardan en sık olanı CRITICAL_PROCESS_DIED hatası. FAT_FILE_SYSTEM ve UNEXPECTED_STORE_EXCEPTION hataları da aldım. Minidump dosyalarını da buraya ekliyorum fakat bunlardan iki tanesini sıkıştırmama sistem izin vermediği için kod olarak ekledim. Avast ve McAfee vardı sildim, Malverebytes kurup taradım sadece 1 şüpheli dosya buldu. HD Tune ve HD Sentinel'de de bir sorun bulunmadı. Memtest86 için USB-Boot yazılımı yüklerken image failed hatası aldım ve mavi ekran verdi. Sonrasında USB bellek neredeyse kullanılmaz hale geldiği için korkup başka bir USB denemedim. Yorumlarınızı endişeyle bekliyorum.

minidump.rar

drive.google.com

[CODE title="minidump"]
Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\LENOVO\Desktop\dump\052621-527921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`71a00000 PsLoadedModuleList = 0xfffff806`7262a1b0
Debug session time: Wed May 26 12:40:11.140 2021 (UTC + 3:00)
System Uptime: 0 days 1:57:00.883
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
..............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`71df6cf0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffaf01`36c7c5c0=0000000000000023
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

FAT_FILE_SYSTEM (23)
If you see FatExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000000e0121
Arg2: ffffaf0136c7d5e8
Arg3: ffffaf0136c7ce20
Arg4: fffff80673def403

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

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 6937

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 38215

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

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

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

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

BUGCHECK_CODE: 23

BUGCHECK_P1: e0121

BUGCHECK_P2: ffffaf0136c7d5e8

BUGCHECK_P3: ffffaf0136c7ce20

BUGCHECK_P4: fffff80673def403

EXCEPTION_RECORD: ffffaf0136c7d5e8 -- (.exr 0xffffaf0136c7d5e8)
ExceptionAddress: fffff80673def403 (volmgr!VmpQueryUniqueIdInternal+0x0000000000000037)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000040
Attempt to read from address 0000000000000040

CONTEXT: ffffaf0136c7ce20 -- (.cxr 0xffffaf0136c7ce20)
rax=0000000000000000 rbx=ffff9c88bcac9840 rcx=ffff9c88bcac9800
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80673def403 rsp=ffffaf0136c7d820 rbp=ffffaf0136c7d8d9
r8=ffffaf0136c7d8d2 r9=ffff9c88bcac9840 r10=0000000000000000
r11=ffffffffffffffff r12=0000000000000001 r13=0000000000000000
r14=ffffaf0136c7d8d0 r15=ffffaf0136c7d8d2
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050246
volmgr!VmpQueryUniqueIdInternal+0x37:
fffff806`73def403 488b5040 mov rdx,qword ptr [rax+40h] ds:002b:00000000`00000040=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

READ_ADDRESS: fffff806726fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000040

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000040

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
ffffaf01`36c7d820 fffff806`73defe7e : ffff9c88`bcac9840 00000000`00000000 ffff9c88`c43ac780 00000000`00100000 : volmgr!VmpQueryUniqueIdInternal+0x37
ffffaf01`36c7d850 fffff806`73df08fa : ffff9c88`d69e7010 ffff9c88`bcac9840 ffff9c88`d69e7010 00000000`00000072 : volmgr!VmpSetPartitionInformation+0x2d6a
ffffaf01`36c7d940 fffff806`73de17be : ffff9c88`bcac9840 ffffaf01`36c7d9c0 ffff9c88`d69e7010 ffff9c88`d69e7638 : volmgr!VmpGetPartitionInfoEx+0x47ce
ffffaf01`36c7d980 fffff806`71d185b5 : ffff9c88`d69e7010 ffff9c88`d69e7010 ffffffff`ffffffff fffff806`759cf000 : volmgr!VmDeviceControl+0x24e
ffffaf01`36c7d9e0 fffff806`71cec00e : ffff9c88`95e08800 ffffaf01`000000a0 00000000`00000000 ffff9c88`d69e7000 : nt!IofCallDriver+0x55
ffffaf01`36c7da20 fffff806`720a6f11 : ffffaf01`36c7db30 00000000`00000000 00000000`00000000 ffff9c88`95e02000 : nt!IoSynchronousCallDriver+0x4e
ffffaf01`36c7da80 fffff806`75a12082 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`71d15841 : nt!IoForwardIrpSynchronously+0x41
ffffaf01`36c7dab0 fffff806`759b3212 : ffff9c88`d69e7010 ffffaf01`36c7e101 ffff9c88`c9c1f180 00000000`00000000 : fvevol!IoctlDiskQuery+0x7a
ffffaf01`36c7dba0 fffff806`71d185b5 : ffff9c88`965477a0 fffff806`720e70ad ffffaf01`36c7e179 ffff9c88`c5ed19f0 : fvevol!FveFilterDeviceControl+0x202
ffffaf01`36c7dca0 fffff806`75a71033 : ffffaf01`36c7def0 fffff806`71d065ff 00000000`00070048 ffff9c88`d69e7010 : nt!IofCallDriver+0x55
ffffaf01`36c7dce0 fffff806`71d185b5 : ffffaf01`36c7df10 fffff806`00000090 ffff9c88`b72bd000 ffffaf01`36c7ddb0 : volume!VolumePassThrough+0x23
ffffaf01`36c7dd10 fffff806`89db1e53 : 00000000`00000000 fffff806`71ff373c ffff9c88`965477a0 00000000`00000001 : nt!IofCallDriver+0x55
ffffaf01`36c7dd50 fffff806`89dc248a : ffff9c88`c2631908 00000000`00000090 00000000`00000000 00000000`00000000 : fastfat!FatPerformDevIoCtrl+0xc7
ffffaf01`36c7dde0 fffff806`89dc2277 : 00000000`00000000 fffff806`733b7ac8 ffff9c88`00000001 00000000`00000000 : fastfat!FatMountVolume+0x1de
ffffaf01`36c7e060 fffff806`89dc21c2 : ffff9c88`c2631250 ffff9c88`bdc2be01 ffff9c88`bdc2be01 ffff9c88`b1bf0d01 : fastfat!FatCommonFileSystemControl+0x57
ffffaf01`36c7e090 fffff806`71d185b5 : 00000000`00000000 ffff9c88`c2631250 ffff9c88`c2631201 ffff9c88`bdc2be80 : fastfat!FatFsdFileSystemControl+0xb2
ffffaf01`36c7e0d0 fffff806`733ef8b2 : ffff9c88`b7d72050 ffff9c88`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffffaf01`36c7e110 fffff806`733ecb0d : ffff9c88`b1addbb0 ffff9c88`00000000 ffff9c88`b1bf0dc0 ffff9c88`c9bf8db0 : FLTMGR!FltpFsControlMountVolume+0x1e6
ffffaf01`36c7e1e0 fffff806`71d185b5 : ffffaf01`36c7e331 ffff9c88`b1addbb0 ffffaf01`36c7e331 fffff806`726458c0 : FLTMGR!FltpFsControl+0x11d
ffffaf01`36c7e240 fffff806`72034b99 : fffff806`726458d0 ffff9c88`bcac96f0 ffff9c88`b1addbb0 ffff9c88`cc0f7a40 : nt!IofCallDriver+0x55
ffffaf01`36c7e280 fffff806`71d19da5 : ffff9c88`c8b35f30 ffff9c88`c8b35f30 00000000`00000000 00000000`00000000 : nt!IopMountVolume+0x371
ffffaf01`36c7e390 fffff806`720e35f2 : 00000000`0012019f 00000000`00000000 ffffaf01`36c7e660 00000000`bcac9625 : nt!IopCheckVpbMounted+0x1b5
ffffaf01`36c7e3f0 fffff806`71ff23ce : ffff9c88`bcac96f0 00000000`00000000 ffff9c88`cc0f7a20 ffff9c88`cc0f7a01 : nt!IopParseDevice+0x942
ffffaf01`36c7e560 fffff806`7210147a : ffff9c88`cc0f7a00 ffffaf01`36c7e7c8 ffff9c88`00000040 ffff9c88`96548ae0 : nt!ObpLookupObjectName+0x3fe
ffffaf01`36c7e730 fffff806`72015c5f : 00000000`00000000 0000003a`8a6ff218 00000000`00000000 00000000`00000001 : nt!ObOpenObjectByNameEx+0x1fa
ffffaf01`36c7e860 fffff806`72015839 : 0000003a`8a6ff1d8 ffffaf01`00501802 0000003a`8a6ff218 0000003a`8a6ff1e0 : nt!IopCreateFile+0x40f
ffffaf01`36c7e900 fffff806`71e08bee : 00000168`63c98980 fffff806`71fa5270 00000000`00000000 00000000`00000000 : nt!NtCreateFile+0x79
ffffaf01`36c7e990 00007ff9`36e0d8c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2b9
0000003a`8a6ff158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`36e0d8c4

SYMBOL_NAME: volmgr!VmpQueryUniqueIdInternal+37

MODULE_NAME: volmgr

IMAGE_NAME: volmgr.sys

IMAGE_VERSION: 10.0.19041.1023

STACK_COMMAND: .cxr 0xffffaf0136c7ce20 ; kb

BUCKET_ID_FUNC_OFFSET: 37

FAILURE_BUCKET_ID: 0x23_volmgr!VmpQueryUniqueIdInternal

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d0e2cbbb-f6c9-659f-dade-4145ab43ee0a}

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

NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2104.13002.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'

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

Loading Dump File [C:\Users\LENOVO\Desktop\dump\052721-194859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`59600000 PsLoadedModuleList = 0xfffff803`5a22a1b0
Debug session time: Thu May 27 07:55:20.660 2021 (UTC + 3:00)
System Uptime: 0 days 19:09:49.681
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`599f6cf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa8e`cb973520=000000000000001e
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff80359d0cbdf, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000002699a1dc008, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5530

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 72243

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

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

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

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

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000006

BUGCHECK_P2: fffff80359d0cbdf

BUGCHECK_P3: 0

BUGCHECK_P4: 2699a1dc008

EXCEPTION_PARAMETER2: 000002699a1dc008

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Registry

STACK_TEXT:
fffffa8e`cb973518 fffff803`59a3b84b : 00000000`0000001e ffffffff`c0000006 fffff803`59d0cbdf 00000000`00000000 : nt!KeBugCheckEx
fffffa8e`cb973520 fffff803`59a08dac : 00000000`00000000 fffff803`59898826 00000000`00008000 fffff803`59928041 : nt!KiDispatchException+0x1b589b
fffffa8e`cb973be0 fffff803`59a04f43 : 00000000`00000000 fffff803`5df133c0 00000000`00000000 00000000`000000b6 : nt!KiExceptionDispatch+0x12c
fffffa8e`cb973dc0 fffff803`59d0cbdf : 00000000`00000000 00000000`ffffffff 00000000`003c0000 ffffa804`de0a2000 : nt!KiPageFault+0x443
fffffa8e`cb973f50 fffff803`59d0c4be : 00000000`000001b0 00000000`003c0000 00000000`00043997 ffffa804`de0a2000 : nt!HvpFindFreeCellInBin+0xf
fffffa8e`cb973f80 fffff803`59d0be51 : ffffa804`de0a2050 fffffa8e`0000481c 00000000`00000258 ffffa804`0481b000 : nt!HvpFindFreeCell+0x126
fffffa8e`cb974000 fffff803`59d0a86c : ffffa804`00000002 00000000`00000200 ffffa804`de0a2000 fffffa8e`cb9740d0 : nt!HvpDoAllocateCell+0x7d
fffffa8e`cb974090 fffff803`59be103f : 00000000`00000000 ffffa804`de0a2000 00000269`99f5bcd4 fffffa8e`cb974160 : nt!HvReallocateCell+0xec
fffffa8e`cb974110 fffff803`59be4438 : 01d752b4`61841512 00000000`00000000 ffffa804`dbac03a0 00000000`00000003 : nt!CmpSetValueKeyExisting+0x233
fffffa8e`cb974190 fffff803`59be3c78 : fffffa8e`00000001 fffffa8e`cb974420 00000000`00000000 00000000`00000201 : nt!CmSetValueKey+0x508
fffffa8e`cb974330 fffff803`59a08bee : 00000000`ffffffff fffff803`5992512a fffffa8e`cb974640 00000000`00000000 : nt!NtSetValueKey+0x648
fffffa8e`cb974510 fffff803`599fab50 : fffff803`59c220f1 00000000`00000000 fffffa8e`cb974a80 ffffa804`f0c491b0 : nt!KiSystemServiceExitPico+0x2b9
fffffa8e`cb974718 fffff803`59c220f1 : 00000000`00000000 fffffa8e`cb974a80 ffffa804`f0c491b0 fffff803`00000000 : nt!KiServiceLinkage
fffffa8e`cb974720 fffff803`59c22619 : 00000000`0000024c 00000000`00000000 fffffa8e`cb974a80 00000000`0000024c : nt!ExpWnfWriteStateData+0x171
fffffa8e`cb974820 fffff803`59c2238e : ffffcf8c`66b63080 00000000`00000000 ffff3b79`3c750f34 00000000`00501802 : nt!ExpNtUpdateWnfStateData+0x27d
fffffa8e`cb974940 fffff803`59a08bee : ffffcf8c`66b63080 00000000`00000001 00000000`0000068e fffffa8e`cb974a80 : nt!NtUpdateWnfStateData+0x2e
fffffa8e`cb974990 00007ffc`6f6f07d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2b9
00000000`106be4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`6f6f07d4

SYMBOL_NAME: nt!HvpFindFreeCellInBin+f

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.985

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: f

FAILURE_BUCKET_ID: 0x1E_c0000006_nt!HvpFindFreeCellInBin

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5224d302-b884-490d-f136-e34dc204733d}

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

[/CODE]
 
Son düzenleyen: Moderatör:
Çözüm
Konuma cevap veren üyelere teşekkür ederim. Dün gece itibarıyla nvme ssd tamamen öldü ve söktüm, şu anda windows hdd'ye kurulu durumda ve çalışıyor. Herhangi bir hata almadım sonrasında. Konuyu kapatabiliriz diye düşünüyorum. Ayrıca Hdd'den windows kullanmanın nasıl bir çile olduğunu yeniden tecrübe etmek hiç de hoş olmadı. En kısa zamanda yeniden ssd alıp onun içine tekrar kurulum yapacağım.
Tarihe göre sırala Puana göre sırala
Verdiğiniz dökümde FAT_FILE_SYSTEM hatası var bu da diske işaret eder.
Avast kaldırın, hataya sebep olmuş.
McAfee kaldırın.
BIOS güncellemeniz var mı kontrol edin.
Diske HD Tune ile "Error Scan" yapın ama "Quick Scan" kapalı olsun.
MemTest'e gerek yok, RAM belleklerde arıza olduğunu düşünmüyorum.
 
Artı 0 Eksi
Ses düzenleyici kullanıyorsanız kaldırın.
Update ile sürücü güncellemelerini yapın.
sfc/scannow ve DISM komutunu uygulayın.
Avast silmişsiniz. Tekrar kurun ve Revo Uninstaller ile kökten kaldırın.
Memtest86 yapamamışsınız o zaman bellek tanılama yapın.


KojiroHyuga04 dedi:
Avast kaldırın, hataya sebep olmuş.
McAfee kaldırın.
BIOS güncellemeniz var mı kontrol edin.
Diske HD Tune ile "error scan" yapın ama "quick scan" kapalı olsun.
Genişletmek için tıkla...

Arkadaş Avast ve McAfee kaldırmış.
 
Artı 0 Eksi
Bunları dün yapmıştım aslında şimdi daha sık arıza verdi ve şu anda boot bile olamayacak hale geldi. Windows düzgün yüklenmemiş dedi. Sonra sıfırla dedim. Onda da hata verdi. Şimdi de uefi usb ile Windows kurulumu yapmak için uğraşıyorum ama ssd yi görmüyor. Sanırım nvme ssd bozulmuş düşünüyorum şu anda.
 
Artı 0 Eksi
Bellek tanilama yaptım ama results çıktısı alamadim log kaydında sadece Scheduled yazıyor. Sfc ve update i dün yapmıştım. Mavi ekran sıklaşmaya başladı ve şu anda açılmıyor bile. Geri kalan dediklerinizi yapamadan gitti resmen. Uefi den hdd ye Windows kurmayı deneyeceğim.
 
Artı 0 Eksi

Tamamdır.
 
Artı 0 Eksi
Konuma cevap veren üyelere teşekkür ederim. Dün gece itibarıyla nvme ssd tamamen öldü ve söktüm, şu anda windows hdd'ye kurulu durumda ve çalışıyor. Herhangi bir hata almadım sonrasında. Konuyu kapatabiliriz diye düşünüyorum. Ayrıca Hdd'den windows kullanmanın nasıl bir çile olduğunu yeniden tecrübe etmek hiç de hoş olmadı. En kısa zamanda yeniden ssd alıp onun içine tekrar kurulum yapacağım.
 
Artı 1 Eksi
Çözüm
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
DRIVER_IRQL_NOT_LESS_OR_EQUAL ve diğer hatalar
Mesaj
0
Görüntüleme
158
iaarda
A
  • Soru
Oyun oynarken SYSTEM_SERVICE_EXCEPTION ve diğer hatalar
Mesaj
0
Görüntüleme
131
ardamvp
A
B
  • Soru
"CRITICAL_PROCESS_DIED" ve "MEMORY_MANAGEMENT" hataları
2
Mesaj
16
Görüntüleme
999
Er73748
E
S
  • Soru
CRITICAL_PROCESS_DIED ve UNEXTEPTED_STORE_EXPECTION hataları
Mesaj
1
Görüntüleme
208
Bora Dere
  • Soru
SYSTEM_SERVICE_EXCEPTION ve CRITICAL_PROCESS_DIED mavi ekran hataları
Mesaj
2
Görüntüleme
328
Untouchablee
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…