R7 4900H Mavi Ekran Hatası

İşletim sistemi
Windows 10

Ergunsen33

Femtopat
Katılım
7 Ocak 2021
Mesajlar
4
Daha fazla  
Cinsiyet
Erkek
Sistem özelliklerim:
  • Ryzen 7 4900H
  • 16 GB RAM 3200MHz
  • GTX 1660 Ti 6 GB.
  • Sürücülerin hepsi güncel, işlemci vb.
Sürekli mavi ekran hatası alıyorum 1 haftadır. PC 2 aylık. Daha değişik değişik stop code veriyor sürekli, yardım.
DMP dosyaları linki: mavi ekran hata dmp.rar
 
Son düzenleme:
Sorun donanımsal olarak gözüküyor. Aşağıdaki adımları sırasıyla uygulayıp hangi donanımda hata olduğunu bulabiliriz.
Hata aldığınız testleri belirtin.

Vanguard'ı kaldırın.

CMD'yi yönetici olarak çalıştırıp sfc /scannow komutunu uygulayın.

Memtest86 yapın.

HDD/SSD'nin sağlığını kontrol edin. HD Tune ile bad sector taraması yapın.

Ekran kartına ve işlemciye OCCT ile stres testi yapın. Daha sonra da 'Power' testi yapın. (20-25 dk yeterli olur)

Kod:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\maksu\Downloads\Compressed\010621-15890-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`38600000 PsLoadedModuleList = 0xfffff802`3922a2b0
Debug session time: Wed Jan  6 15:41:46.201 2021 (UTC + 3:00)
System Uptime: 0 days 1:21:59.859
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`389f5780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff087`308279e0=000000000000003b
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff802388e914e, Address of the instruction which caused the bugcheck
Arg3: fffff087308282e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 9546

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 17597

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

    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:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff802388e914e

BUGCHECK_P3: fffff087308282e0

BUGCHECK_P4: 0

CONTEXT:  fffff087308282e0 -- (.cxr 0xfffff087308282e0)
rax=0000000000000000 rbx=ffffd8829abba520 rcx=ffffd8829abba520
rdx=ffffd88289263d60 rsi=ffffd8829d015a60 rdi=ffffd8829a5e0010
rip=fffff802388e914e rsp=fffff08730828ce0 rbp=0000000000000000
r8=ffffd8829abba528  r9=ffffd8829abba538 r10=fffff802388e90e0
r11=fffff08730828e70 r12=0000000000000000 r13=fffff80234a8d456
r14=fffff08730828de0 r15=fffff08730828f60
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!SepIsSModeEnabled+0x3e:
fffff802`388e914e 00a07408b001    add     byte ptr [rax+1B00874h],ah ds:002b:00000000`01b00874=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  wermgr.exe

MISALIGNED_IP:
nt!SepIsSModeEnabled+3e
fffff802`388e914e 00a07408b001    add     byte ptr [rax+1B00874h],ah

STACK_TEXT:
fffff087`30828ce0 00000000`00000000     : ffffd882`99cc1a00 00000000`00000000 ffffd882`9b1ed901 ffffd882`9b1ed988 : nt!SepIsSModeEnabled+0x3e


SYMBOL_NAME:  nt!SepIsSModeEnabled+3e

IMAGE_NAME:  hardware

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .cxr 0xfffff087308282e0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}

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


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


Loading Dump File [C:\Users\maksu\Downloads\Compressed\010621-15765-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`47400000 PsLoadedModuleList = 0xfffff803`4802a2b0
Debug session time: Wed Jan  6 14:19:26.689 2021 (UTC + 3:00)
System Uptime: 0 days 14:49:24.843
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`477f5780 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffffa83`fde52c40=000000000000001e
0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80379b565e3, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 000000000000003a, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 9249

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 31130

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

    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:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80379b565e3

BUGCHECK_P3: 1

BUGCHECK_P4: 3a

WRITE_ADDRESS: fffff803480fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8034800f330: Unable to get Flags value from nt!KdVersionBlock
fffff8034800f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
000000000000003a

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000003a

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
fffffa83`fde52c38 fffff803`4789128d     : 00000000`0000001e ffffffff`c0000005 fffff803`79b565e3 00000000`00000001 : nt!KeBugCheckEx
fffffa83`fde52c40 fffff803`478078ac     : 00000000`00001000 fffffa83`fde534e0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x16688d
fffffa83`fde53300 fffff803`47803a43     : fffffa83`fde537b0 00000000`00000000 fffff803`477f1870 fffff803`476ec5ca : nt!KiExceptionDispatch+0x12c
fffffa83`fde534e0 fffff803`79b565e3     : fffffa83`fde53918 fffff803`796b5900 ffffcbe5`f2f977f8 00000000`00000003 : nt!KiPageFault+0x443
fffffa83`fde53678 fffffa83`fde53918     : fffff803`796b5900 ffffcbe5`f2f977f8 00000000`00000003 ffffcbe5`f2f971b0 : vgk+0x4e65e3
fffffa83`fde53680 fffff803`796b5900     : ffffcbe5`f2f977f8 00000000`00000003 ffffcbe5`f2f971b0 00000000`00000001 : 0xfffffa83`fde53918
fffffa83`fde53688 ffffcbe5`f2f977f8     : 00000000`00000003 ffffcbe5`f2f971b0 00000000`00000001 fffff802`39670000 : vgk+0x45900
fffffa83`fde53690 00000000`00000003     : ffffcbe5`f2f971b0 00000000`00000001 fffff802`39670000 ffffcbe5`f2f971b0 : 0xffffcbe5`f2f977f8
fffffa83`fde53698 ffffcbe5`f2f971b0     : 00000000`00000001 fffff802`39670000 ffffcbe5`f2f971b0 00000000`00000000 : 0x3
fffffa83`fde536a0 00000000`00000001     : fffff802`39670000 ffffcbe5`f2f971b0 00000000`00000000 00000000`00040282 : 0xffffcbe5`f2f971b0
fffffa83`fde536a8 fffff802`39670000     : ffffcbe5`f2f971b0 00000000`00000000 00000000`00040282 00000000`00000001 : 0x1
fffffa83`fde536b0 ffffcbe5`f2f971b0     : 00000000`00000000 00000000`00040282 00000000`00000001 ffffcbe5`f2f97000 : 0xfffff802`39670000
fffffa83`fde536b8 00000000`00000000     : 00000000`00040282 00000000`00000001 ffffcbe5`f2f97000 ffffcbe5`f2f977f8 : 0xffffcbe5`f2f971b0


SYMBOL_NAME:  vgk+4e65e3

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  4e65e3

FAILURE_BUCKET_ID:  0x1E_c0000005_W_vgk!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1bfbc9ad-5f02-de55-8455-dcb5c0875aa0}

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

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


Loading Dump File [C:\Users\maksu\Downloads\Compressed\010721-16031-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`53800000 PsLoadedModuleList = 0xfffff801`5442a2b0
Debug session time: Thu Jan  7 00:59:21.885 2021 (UTC + 3:00)
System Uptime: 0 days 0:24:23.545
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`53bf5780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff810b`7d4302e0=000000000000000a
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80153afc01e, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7359

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 10671

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

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

BUGCHECK_P1: 2

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80153afc01e

WRITE_ADDRESS: fffff801544fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8015440f330: Unable to get Flags value from nt!KdVersionBlock
fffff8015440f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000002

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  ffff810b7d430420 -- (.trap 0xffff810b7d430420)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff80151d83180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80153afc01e rsp=ffff810b7d4305b0 rbp=ffff810b7d430691
r8=ffff8d8c377cd080  r9=fffff80154524440 r10=000000000000ffff
r11=fffff80151d83180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeInsertQueueEx+0x56:
fffff801`53afc01e 0000            add     byte ptr [rax],al ds:00000000`00000002=??
Resetting default scope

MISALIGNED_IP:
nt!KeInsertQueueEx+56
fffff801`53afc01e 0000            add     byte ptr [rax],al

STACK_TEXT:
ffff810b`7d4302d8 fffff801`53c07769     : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff810b`7d4302e0 fffff801`53c03a69     : 00000048`061210f6 00000000`00000004 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff810b`7d430420 fffff801`53afc01e     : ffff8d8c`377cb1c0 ffff8d8c`377cd080 ffff810b`7d430691 fffff801`51d83180 : nt!KiPageFault+0x469
ffff810b`7d4305b0 00000000`00000001     : 00000000`00000000 00000000`0000ffff 00000000`00000000 00000000`00000000 : nt!KeInsertQueueEx+0x56
ffff810b`7d430620 00000000`00000000     : 00000000`0000ffff 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1


SYMBOL_NAME:  nt!KeInsertQueueEx+56

IMAGE_NAME:  hardware

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .thread ; .cxr ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}

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


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


Loading Dump File [C:\Users\maksu\Downloads\Compressed\010721-15984-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`17a00000 PsLoadedModuleList = 0xfffff800`1862a2b0
Debug session time: Thu Jan  7 00:34:35.697 2021 (UTC + 3:00)
System Uptime: 0 days 2:21:09.148
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`17df5780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`1dc11020=000000000000003b
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80017e06df1, Address of the instruction which caused the bugcheck
Arg3: fffff8001dc11920, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6890

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8186

    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:  3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80017e06df1

BUGCHECK_P3: fffff8001dc11920

BUGCHECK_P4: 0

CONTEXT:  fffff8001dc11920 -- (.cxr 0xfffff8001dc11920)
rax=0000000000000002 rbx=ffffcc8f875ac080 rcx=0000000100000002
rdx=0000000000000002 rsi=00000000ffffffff rdi=0000000000000000
rip=fffff80017e06df1 rsp=ffff8184ff0fbb00 rbp=ffff8184ff0fbb80
r8=0000000000000000  r9=0000000000000000 r10=00000000000009c4
r11=0000000000000246 r12=000000c98ebfed00 r13=000001cd8ac24f90
r14=0000000000000000 r15=00000000000003b0
iopl=0         nv up di pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050002
nt!KiSystemCall64+0x131:
fffff800`17e06df1 ff              ???
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

MISALIGNED_IP:
nt!KiSystemCall64+131
fffff800`17e06df1 ff              ???

BAD_STACK_POINTER:  fffff8001dc11018

STACK_TEXT:
ffff8184`ff0fbb00 00007fff`e31cc094     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemCall64+0x131
000000c9`8ebfec58 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`e31cc094


SYMBOL_NAME:  nt!KiSystemCall64+131

IMAGE_NAME:  hardware

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .cxr 0xfffff8001dc11920 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}

Followup:     MachineOwner
---------
 
1610022051344.png

OCCT Stres testi yapayım dedim 30 saniye sonra crashed dedi sorun ne anlamadım göstermiyorda
1610022403998.png

sfc scannow sorun bulmadı
 
Son düzenleme:
Hangi bileşenin testtinde?
Sorun donanımsal olduğu için değişim veya iade yapabilirsiniz. İade almayabilirler de değişim talep edebilirsiniz.
Şu an işlemciye ve ekran kartına yapıyorum sıkıntı cıkmıyor fakat OCCT secip genel test yaptıgımda crashed diyor o hataya bakabiliyor muyuz ? pc aldıgımda boyle bi sorun yoktu 1 haftadır oldu
 

Yeni konular

Geri
Yukarı