Ryzen 5 7600X sistem açılışında mavi ekran hataları

EgeN7 dedi:

Aldığınız hatalar çok sık rastlanan hatalar değil.

RAM'ler ile ilgili olma ihtimali var. Zaten kendiniz de bahsetmişsiniz. DDR5, AM5, LGA 1700, Ryzen 7000 serisi gibi yeni platformlar hakkında çok bilgim yok ama problemler yaşandığını sıkça duyuyorum. Doğal, yeni bir teknoloji ve bazı sistemlerde çözülmesi zaman alacak gibi görünüyor.

BIOS güncellemesi önereceğim belki bir RAM iyileştirmesi gelmiştir ama güncel sürümler beta sürümler şu an.

RAM konusu dışında, herhangi bir eski/yeni sistem durumunuz var mı bilmiyorum ancak sorayım.

Eski sisteminizde kullandığınız bir SSD veya HDD'yi yeni sisteminize mi eklediniz? Öyle bir durum olduysa eski diskteki sürücülerle bir çakışma söz konusu olabilir. En azından daha önce sorun yaşayan biri bu şekilde olduğunu söylemiş. Kaynak: Clipsp.sys??

Veya temiz kurulum yerine yükseltme, sıfırlama gibi seçenekler kullandınız mı daha önce?

Ama sisteminizi baştan beri temiz kurulumla, düzgün yüklenmiş bir Windows ile kullanıyorsanız durum başka.

İlk etapta şunları yapın.

CMD'yi yönetici olarak çalıştırıp aşağıdaki komutları sırayla yazın. Sonuçları paylaşırsınız.

SFC /scannow
DISM /Online /Cleanup-Image /RestoreHealth


Dökümler:

Kod:Panoya kopyala

*** WARNING: Unable to verify timestamp for clipsp.sys
*******************************************************************************
*                                                                             *
*                        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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80354cbea3c, The address that the exception occurred at
Arg3: ffffbc833f4c6178, Parameter 0 of the exception
Arg4: ffffbc833f4c59b0, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 453

    Key  : Analysis.Elapsed.mSec
    Value: 5194

    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: 62

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Failure.Bucket
    Value: AV_clipsp!unknown_function

    Key  : Failure.Hash
    Value: {b39617f4-db38-ae5a-185a-0fa66e986fff}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80354cbea3c

BUGCHECK_P3: ffffbc833f4c6178

BUGCHECK_P4: ffffbc833f4c59b0

FILE_IN_CAB:  052823-8390-01.dmp

EXCEPTION_PARAMETER1:  ffffbc833f4c6178

EXCEPTION_PARAMETER2:  ffffbc833f4c59b0

WRITE_ADDRESS: fffff803576fb390: 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
 ffffbc833f4c59b0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:
ffffbc83`3f4c5138 fffff803`56f12f5f     : 00000000`0000001e ffffffff`c0000005 fffff803`54cbea3c ffffbc83`3f4c6178 : nt!KeBugCheckEx
ffffbc83`3f4c5140 fffff803`56e178b6     : ffffbc83`3f4c59b0 fffff803`56d119a5 ffffbc83`3f4c63b8 fffff803`54cbea3c : nt!KiFatalFilter+0x1f
ffffbc83`3f4c5180 fffff803`56dcfec2     : fffff803`00000002 fffff803`56ad0944 ffffbc83`3f4c1000 ffffbc83`3f4c8000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffbc83`3f4c51c0 fffff803`56e066b2     : fffff803`56ad0944 ffffbc83`3f4c57a0 fffff803`56dcfe20 00000000`00000000 : nt!_C_specific_handler+0xa2
ffffbc83`3f4c5230 fffff803`56ce5b37     : ffffbc83`3f4c57a0 00000000`00000000 ffffbc83`3f4c6f50 fffff803`56cad488 : nt!RtlpExecuteHandlerForException+0x12
ffffbc83`3f4c5260 fffff803`56ce7b06     : ffffbc83`3f4c6178 ffffbc83`3f4c5eb0 ffffbc83`3f4c6178 00000000`c1ee945b : nt!RtlDispatchException+0x297
ffffbc83`3f4c5980 fffff803`56e1016c     : 00000000`00000003 ffffce02`23123590 00000000`00000000 ffffbc83`3f4c6239 : nt!KiDispatchException+0x186
ffffbc83`3f4c6040 fffff803`56e0b75a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x12c
ffffbc83`3f4c6220 fffff803`54cbea3c     : fffff803`54cab36a ffffbc83`3f4c63e0 ffffbc83`3f4c64e0 00000000`c000000d : nt!KiGeneralProtectionFault+0x31a
ffffbc83`3f4c63b8 fffff803`54cab36a     : ffffbc83`3f4c63e0 ffffbc83`3f4c64e0 00000000`c000000d 00000000`00000001 : clipsp+0x1ea3c
ffffbc83`3f4c63c0 ffffbc83`3f4c63e0     : ffffbc83`3f4c64e0 00000000`c000000d 00000000`00000001 00000000`00000000 : clipsp+0xb36a
ffffbc83`3f4c63c8 ffffbc83`3f4c64e0     : 00000000`c000000d 00000000`00000001 00000000`00000000 03f2a1c4`3f6b379f : 0xffffbc83`3f4c63e0
ffffbc83`3f4c63d0 00000000`c000000d     : 00000000`00000001 00000000`00000000 03f2a1c4`3f6b379f 1f12916a`bc8cb6f6 : 0xffffbc83`3f4c64e0
ffffbc83`3f4c63d8 00000000`00000001     : 00000000`00000000 03f2a1c4`3f6b379f 1f12916a`bc8cb6f6 9377d444`5ce55f37 : 0xc000000d
ffffbc83`3f4c63e0 00000000`00000000     : 03f2a1c4`3f6b379f 1f12916a`bc8cb6f6 9377d444`5ce55f37 97831de0`7169a08a : 0x1


SYMBOL_NAME:  clipsp+1ea3c

MODULE_NAME: clipsp

IMAGE_NAME:  clipsp.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1ea3c

FAILURE_BUCKET_ID:  AV_clipsp!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b39617f4-db38-ae5a-185a-0fa66e986fff}

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


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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffb00359c7e8f0, memory referenced.
Arg2: 0000000000000010, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: ffffb00359c7e8f0, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 218

    Key  : Analysis.Elapsed.mSec
    Value: 6225

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Failure.Bucket
    Value: AV_X_(null)_BAD_IP_CI!Gvb3afc4

    Key  : Failure.Hash
    Value: {706923f5-79d8-2289-192c-321e9d377cd0}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  50

BUGCHECK_P1: ffffb00359c7e8f0

BUGCHECK_P2: 10

BUGCHECK_P3: ffffb00359c7e8f0

BUGCHECK_P4: 2

FILE_IN_CAB:  052823-8593-01.dmp

READ_ADDRESS: fffff803574fb390: 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
 ffffb00359c7e8f0

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff8607fb7e6940 -- (.trap 0xffff8607fb7e6940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb00359c7e8f0 rbx=0000000000000000 rcx=ffff8607fb7e6c60
rdx=6249ca65c9583506 rsi=0000000000000000 rdi=0000000000000000
rip=ffffb00359c7e8f0 rsp=ffff8607fb7e6ad8 rbp=ffff8607fb7e6c50
 r8=0000000000000097  r9=0000000083de60b7 r10=0000ffffb00359c7
r11=ffffacfcea800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
ffffb003`59c7e8f0 ??              ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
ffffb003`59c7e8f0 ??              ???

STACK_TEXT:
ffff8607`fb7e6698 fffff803`56c4af53     : 00000000`00000050 ffffb003`59c7e8f0 00000000`00000010 ffff8607`fb7e6940 : nt!KeBugCheckEx
ffff8607`fb7e66a0 fffff803`56a6e7b0     : 00000000`00000000 00000000`00000010 ffff8607`fb7e69c0 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffff8607`fb7e67a0 fffff803`56c0bad8     : 00000000`0004907e 00000001`00000000 001fffff`00000000 00000000`001fffff : nt!MmAccessFault+0x400
ffff8607`fb7e6940 ffffb003`59c7e8f0     : fffff803`59cbc7cf ffff8607`fb7e6b00 5ba402f6`df8263ad 00000000`00000241 : nt!KiPageFault+0x358
ffff8607`fb7e6ad8 fffff803`59cbc7cf     : ffff8607`fb7e6b00 5ba402f6`df8263ad 00000000`00000241 5891c283`2ab9bc22 : 0xffffb003`59c7e8f0
ffff8607`fb7e6ae0 fffff803`59cb8c4d     : 00000000`00000000 00000000`00000241 ffffa902`8e91e000 ffffa902`8e91e034 : CI!Gvb3afc4+0x137
ffff8607`fb7e6e50 fffff803`59c09e7b     : 83a89215`4132ef92 ffffa902`8e91e000 ffffa902`8e91e034 00000000`00000241 : CI!peauthvbn_SetDebugCredentialsData+0x41
ffff8607`fb7e6ea0 fffff803`59c7adac     : ffffa902`8e91e000 00000000`00000000 00000000`00000000 00000000`00000000 : CI!PEAuthSetDebugCredentialsData+0x57
ffff8607`fb7e6ed0 fffff803`59c7a548     : 00000000`00000000 00000000`00000000 ffffffff`80002c90 833e6d70`00000000 : CI!PEPerformInitializationChecks+0x104
ffff8607`fb7e6f50 fffff803`59c45c4b     : ffffe40e`00000000 00000000`00000000 fffff803`f7247e80 ffff8607`fb000000 : CI!PEProcessDispatch+0xd0
ffff8607`fb7e6fa0 fffff803`f72546f6     : ffffa902`8e91e000 ffff8607`fb7e7190 00000000`00000000 00000000`00000018 : CI!CiGetPEInformation+0x3b
ffff8607`fb7e6fd0 ffffa902`8e91e000     : ffff8607`fb7e7190 00000000`00000000 00000000`00000018 00000000`00000001 : peauth+0x446f6
ffff8607`fb7e6fd8 ffff8607`fb7e7190     : 00000000`00000000 00000000`00000018 00000000`00000001 fffff803`f725212f : 0xffffa902`8e91e000
ffff8607`fb7e6fe0 00000000`00000000     : 00000000`00000018 00000000`00000001 fffff803`f725212f ffffa902`8e91e000 : 0xffff8607`fb7e7190


SYMBOL_NAME:  CI!Gvb3afc4+137

MODULE_NAME: CI

IMAGE_NAME:  CI.dll

IMAGE_VERSION:  10.0.19041.3031

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  137

FAILURE_BUCKET_ID:  AV_X_(null)_BAD_IP_CI!Gvb3afc4

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {706923f5-79d8-2289-192c-321e9d377cd0}

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

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