Çözüldü R5 3500 ve RTX 2060 mavi ekran hataları

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

YavuzAkbay

Kilopat
Katılım
30 Mart 2014
Mesajlar
155
Çözümler
3
Yer
North-Rhine Westphalia
Daha fazla  
Cinsiyet
Erkek
Meslek
Data Analyst
Arkadaşlar, İtopya'dan arkadaşıma bilgisayar topladık. Arkadaşımla farklı şehirlerde olduğumuzdan dolayı kurulumunu biz değil İtopya'nın kendisine yaptırdık ve bilgisayarı bu şekilde satın aldık. Bilgisayara Windows 10'un en son sürümünü kurduk ve Windows'un tüm güncellemelerini, ekran kartı sürücülerini, BIOS sürücülerini kurduk. Ve o günden beri her gün her birkaç saatte bir mavi ekranımız eksik olmadı. Farklı mavi ekranlardaki bilgiler çok çeşitli olduğu için sorunun kaynağını hiçbir şekilde çözemedik.
Bilgisayar yeni olmasına rağmen monitör, klavye, mouse eski. Bunun yanında monitör bilgisayara VGA'dan DisplayPort'a çevirici ile bağlı.

Anakart: Gigabyte B450M S2H.
Bellek: XPG Gammix D30 2x8.
Ekran kartı: Gigabyte RTX 2060 OC 6 GB.
İşlemci: Ryzen 5 3500.

Minidump
 
Çözüm
Fareniz için direkt uygun bir sürücü bulamadım. Bazı yerlerde farenizin sürücüsü olarak HP Z6000 modelinin sürücüsü verilmiş ancak güvenemediğimden paylaşmayacağım. Yedek fareniz varsa şu anki kullandığınız fareyi bir süre sisteminizden çıkartmanızı öneririm.

SSD'niz SU630 imiş. Umarım ondan kaynaklı sorun yaşamıyorsunuzdur, zira SSD'niz kronik sorunlu. Ek bir HDD'niz varsa bir süre Windows'u ona kurup SSD'yi bir süre sisteminizden çıkartmayı deneyebilirsiniz.

Bir de CrystalDiskMark ile hız testi yapabilir misiniz?
Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8024dadb4ae, Address of the instruction which caused the bugcheck
Arg3: ffff890b90019b30, 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: 6608

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 73883

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

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

BUGCHECK_P3: ffff890b90019b30

BUGCHECK_P4: 0

CONTEXT:  ffff890b90019b30 -- (.cxr 0xffff890b90019b30)
rax=00000000ffffffff rbx=ffffaa8ff009e080 rcx=fffff8024e44f848
rdx=0000000000000000 rsi=ffffaa8fedb65728 rdi=ffffaa8f00000000
rip=fffff8024dadb4ae rsp=ffff890b9001a530 rbp=ffff890b9001ab80
 r8=00000000ffffffff  r9=0000000000000000 r10=fffff8024dadb3f0
r11=ffff890b9001a560 r12=0000000000000000 r13=ffffffffffffffff
r14=ffff9405365d6b30 r15=ffff94053aebe000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!ExAcquirePushLockSharedEx+0xbe:
fffff802`4dadb4ae 894728          mov     dword ptr [rdi+28h],eax ds:002b:ffffaa8f`00000028=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT: 
ffff890b`9001a530 fffff802`5947dc50     : ffffaa8f`edb61000 ffff890b`00000000 ffff9405`00000000 00000000`00000000 : nt!ExAcquirePushLockSharedEx+0xbe
ffff890b`9001a580 fffff802`4dc05fb8     : ffffaa8f`f009e080 ffffaa8f`f009e080 000001ef`2a982020 00000000`00000000 : dxgkrnl!DxgkEscape+0x810
ffff890b`9001ab00 00007ffa`f5b14be4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000c0`4b85c218 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`f5b14be4


SYMBOL_NAME:  dxgkrnl!DxgkEscape+810

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.19041.546

STACK_COMMAND:  .cxr 0xffff890b90019b30 ; kb

BUCKET_ID_FUNC_OFFSET:  810

FAILURE_BUCKET_ID:  0x3B_c0000005_dxgkrnl!DxgkEscape

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b01ccee0-8f60-5a92-256e-31ae6f710d7d}

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8067fefb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5702

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 83232

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

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

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8067fefb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff609c0cd1600 -- (.trap 0xfffff609c0cd1600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000100084 rbx=0000000000000000 rcx=ffff9e0c08d11c80
rdx=ffff9e0c09c95908 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8067f4be212 rsp=fffff609c0cd1790 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000002
r11=fffff609c0cd1768 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiAcquireKobjectLockSafe+0x32:
fffff806`7f4be212 8b03            mov     eax,dword ptr [rbx] ds:00000000`00000000=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

IRP_ADDRESS: ffff9e0c09c95788

STACK_TEXT: 
ffffdd81`c74e8c88 fffff806`7f687a98     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`7fefb320 : nt!KeBugCheckEx
ffffdd81`c74e8c90 fffff806`7f52b7cd     : 00000387`2b249c9c ffffdd81`c74cf180 00000000`00000246 00000000`00010a4b : nt!KeAccumulateTicks+0x15dda8
ffffdd81`c74e8cf0 fffff806`7f52bd71     : 00000000`0000ec00 00000000`00009eb9 ffffdd81`c74cf180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffdd81`c74e8d40 fffff806`7f526823     : ffffdd81`c74cf180 00000000`00000000 fffff806`7fe319a8 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffdd81`c74e8e80 fffff806`7f52e382     : fffff609`c0cd1600 fffff609`c0cd1680 fffff609`c0cd1600 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffdd81`c74e8f30 fffff806`7f42ecd5     : 00000002`7b079a48 ffff9e0b`ff2c8ac0 ffff9e0b`ff2c8b70 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffdd81`c74e8f60 fffff806`7f5f604a     : fffff609`c0cd1680 ffff9e0b`ff2c8ac0 ffff9e0c`08d11c88 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffdd81`c74e8fb0 fffff806`7f5f65b7     : ffff9e0c`08d11c80 00000000`7246704e 00000000`00000001 00000000`5246704e : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff609`c0cd1600 fffff806`7f4be212     : ffffdd81`c74cf180 fffff806`7f4c4bca ffff9e0c`0a7937c8 00000244`b1a80418 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff609`c0cd1790 fffff806`7f4874e3     : ffff9e0c`08d11c80 ffff9e0c`09c95860 fffff609`c0cd17e0 00000000`00000000 : nt!KiAcquireKobjectLockSafe+0x32
fffff609`c0cd17c0 fffff806`7f4c45fa     : 00000000`00000001 ffff9e0c`09c95860 ffff9e0c`01396cd0 fffff806`7e994906 : nt!KeInsertQueueEx+0x8f
fffff609`c0cd1830 fffff806`7f8c267a     : ffff9e0c`09c95800 00000000`00000000 ffff9e0c`08d11c80 ffff9e0c`09c95860 : nt!IopCompleteRequest+0x58a
fffff609`c0cd18f0 fffff806`7f8b8e7f     : ffffb586`00000000 fffff609`c0cd1b80 00000091`a5bfd910 fffff609`c0cd1b80 : nt!IopSynchronousServiceTail+0x2fa
fffff609`c0cd1990 fffff806`7f605fb8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000244`a8e90e60 : nt!NtWriteFile+0x66f
fffff609`c0cd1a90 00007ffb`f412be94     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000091`a5bfd898 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`f412be94


SYMBOL_NAME:  nt!KeAccumulateTicks+15dda8

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  15dda8

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff8007046a870, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff8007046a7c8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4562

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 9617

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

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

BUGCHECK_P1: 3

BUGCHECK_P2: fffff8007046a870

BUGCHECK_P3: fffff8007046a7c8

BUGCHECK_P4: 0

TRAP_FRAME:  fffff8007046a870 -- (.trap 0xfffff8007046a870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff86838ae9e158 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffa080c4ad6d80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80069e114e9 rsp=fffff8007046aa00 rbp=fffff8006862b180
 r8=0000000000000100  r9=0000000000000000 r10=fffff80069cc2f00
r11=fffff8006862b180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KiSignalThread+0x150569:
fffff800`69e114e9 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff8007046a7c8 -- (.exr 0xfffff8007046a7c8)
ExceptionAddress: fffff80069e114e9 (nt!KiSignalThread+0x0000000000150569)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y   n tabanl  bir arabelle in ta t   n  alg lad . Bu ta ma, k t  niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT: 
fffff800`7046a548 fffff800`69e06569     : 00000000`00000139 00000000`00000003 fffff800`7046a870 fffff800`7046a7c8 : nt!KeBugCheckEx
fffff800`7046a550 fffff800`69e06990     : ffff8683`89a29820 fffff800`6edc55f6 ffff8683`89a29820 fffff800`7046a738 : nt!KiBugCheckDispatch+0x69
fffff800`7046a690 fffff800`69e04d23     : ffff8683`89ae2ac0 fffff800`6edb85fc ffff8683`89ae2b30 ffff8683`89ae2ac0 : nt!KiFastFailDispatch+0xd0
fffff800`7046a870 fffff800`69e114e9     : ffff8683`830146c0 00000000`000000b0 ffff8683`890fc3a8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x323
fffff800`7046aa00 fffff800`69c1016d     : fffff800`6862b180 00000000`00000000 ffff8683`8ae9e080 fffff800`7046aaf9 : nt!KiSignalThread+0x150569
fffff800`7046aa40 fffff800`69cc34fc     : ffff8683`8ae9e080 fffff800`6edb719d ffff8683`8ae9e000 ffff8683`89ae20d0 : nt!KiSignalThreadForApc+0xb5
fffff800`7046aa70 fffff800`69cc2fd7     : 00000000`00000000 fffff800`7046ab06 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x50c
fffff800`7046ab60 fffff800`7c245056     : 00000000`00000018 fffff800`7046ac00 ffff8683`8fe15010 ffff8683`000b000b : nt!IofCompleteRequest+0x17
fffff800`7046ab90 fffff800`7c223aa7     : 00000000`00000002 ffff8683`895f1f10 ffff8683`85cab190 fffff800`7046ac74 : mouclass!MouseClassServiceCallback+0x476
fffff800`7046ac30 fffff800`69cc310e     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : mouhid!MouHid_ReadComplete+0x757
fffff800`7046acd0 fffff800`69cc2fd7     : 00000000`00000000 ffff8683`89afd606 ffff8683`87efdd50 00000000`00000000 : nt!IopfCompleteRequest+0x11e
fffff800`7046adc0 fffff800`7c18aef5     : ffff8683`8ad8b4d8 ffff8683`89ae3102 00000000`00000000 00000000`00000009 : nt!IofCompleteRequest+0x17
fffff800`7046adf0 fffff800`7c18a7ed     : ffff8683`89ae31d0 ffff8683`89ae3102 ffff8683`89ae31d0 00000000`00000009 : HIDCLASS!HidpDistributeInterruptReport+0x3f5
fffff800`7046aef0 fffff800`69cc310e     : ffff8683`89afc620 ffff8683`89afc620 fffff800`7046b001 00000000`00000701 : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff800`7046af90 fffff800`69cc2fd7     : 00000000`00000001 00000000`00000000 ffff8683`89acdbf0 00000000`00000002 : nt!IopfCompleteRequest+0x11e
fffff800`7046b080 fffff800`6edb811a     : 00000000`00000000 ffff8683`89a1edc0 ffff8683`89afc620 00000000`00000001 : nt!IofCompleteRequest+0x17
fffff800`7046b0b0 fffff800`6edb5bbf     : ffff8683`89b83002 fffff800`7c7a4402 ffff8683`89afc620 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff800`7046b140 fffff800`7c142360     : 00000000`00000000 ffff8683`8e82a460 ffff8683`89a15eb0 0000797c`717d5b98 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff800`7046b1a0 00000000`00000000     : ffff8683`8e82a460 ffff8683`89a15eb0 0000797c`717d5b98 0000000f`00000028 : HPubA407+0x2360


SYMBOL_NAME:  mouclass!MouseClassServiceCallback+476

MODULE_NAME: mouclass

IMAGE_NAME:  mouclass.sys

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  476

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_mouclass!MouseClassServiceCallback

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {19eabd28-80b6-28d3-485c-6d6a06644567}

Followup:     MachineOwner
---------
 
Memtest86 ile bellek testlerini tamamladım ve bellekte hiç sorun bulunamadı. Aynı şekilde HD Tune ile tüm disklere "Error Scan" yaptım ve bir soruna rastlanmadı (1. ekran görüntüsü). HDD Sentinel ekran görüntüsü de ikinci ekran görüntüsü. DDU ile sürücüleri kaldırıp NVIDIA'nın en güncel sürücüsü olan 456.71 kurulumunu gerçekleştirdim. Kullandığımız fare ise HP X4000 Kablosuz fare. Çipset sürücülerimizi ise verdiğiniz linkten güncelledik.

1.jpg


2.jpg
 
Fareniz için direkt uygun bir sürücü bulamadım. Bazı yerlerde farenizin sürücüsü olarak HP Z6000 modelinin sürücüsü verilmiş ancak güvenemediğimden paylaşmayacağım. Yedek fareniz varsa şu anki kullandığınız fareyi bir süre sisteminizden çıkartmanızı öneririm.

SSD'niz SU630 imiş. Umarım ondan kaynaklı sorun yaşamıyorsunuzdur, zira SSD'niz kronik sorunlu. Ek bir HDD'niz varsa bir süre Windows'u ona kurup SSD'yi bir süre sisteminizden çıkartmayı deneyebilirsiniz.

Bir de CrystalDiskMark ile hız testi yapabilir misiniz?
 
Çözüm
Fareyi çıkarttım ve saatlerce bu şekilde kullandım, şimdiye kadar bir sorun yok. Aynı şekilde CrystalDiskMark ile hız testimi de gerçekleştirdim.
 

Dosya Ekleri

  • d3f699a0-19ca-4c5e-8f9e-70c33423de1d.jpg
    d3f699a0-19ca-4c5e-8f9e-70c33423de1d.jpg
    35,7 KB · Görüntüleme: 23

Yeni konular

Geri
Yukarı