RTX 4060 Ti sistemde oyunlarda mavi ekran hatası

İşletim sistemi
Windows 10

kraujas

Hectopat
Katılım
1 Ağustos 2019
Mesajlar
25
RAM
GSkill DDR5 6000 Mhz CL 36 2x16
SSD veya HDD modeli
Samsung SATA SSD-Sandisk Ultra M2 NVME
Ekran kartı
GIGABYTE GeForce RTX 4060 Ti AORUS ELITE
Anakart
Asus B650m Plus
İşlemci
Ryzen 7 7700x
G.Skill DDR5 6000 MHz CL 36 2x16.
Samsung SATA 480 GB SSD-SanDisk Ultra 1 TB M.2 NVMe.
Gigabyte GeForce RTX 4060 Ti Aorus Elite.
ASUS B650M Plus.
Ryzen 7 7700X.
Windows 10.



Arkadaşlar genelde Diablo IV oynarken bilgisayar kilitleniyor ya mavi ekrana düşüyorum yada oyun çöküyor. Minidump dosyalarını paylaştım yardımcı olursanız sevinirim.
 
BIOS güncel olmasına bazı sürücüler güncel değil.

Kod:
start end module name
fffff801`85490000 fffff801`8549d000 amdgpio2 (deferred)
 Image path: \SystemRoot\System32\drivers\amdgpio2.sys
 Image name: amdgpio2.sys
 Browse all global symbols functions data
 Timestamp: Wed Mar 11 14:15:48 2020 (5E68C864)
 CheckSum: 0000FA1F
 ImageSize: 0000D000
 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 Information from resource tables:

Chipset güncelle.

Kod:
start end module name
fffff801`61400000 fffff801`61518000 rt640x64 (deferred)
 Image path: \SystemRoot\System32\drivers\rt640x64.sys
 Image name: rt640x64.sys
 Browse all global symbols functions data
 Timestamp: Tue May 11 06:30:41 2021 (6099FA61)
 CheckSum: 0012905D
 ImageSize: 00118000
 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 Information from resource tables:

Realtek Ethernet sürücücüsünü güncelle.


Ekran kartı sürücücüsünü DDU ile kaldırıp en güncel ekran kartı sürücüsünü (WHQL) NVIDIA internet sitesinden edinin.


Kod:
15: 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: fffff8025bc89a5e, Address of the instruction which caused the BugCheck
Arg3: ffffd1026af1e600, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2655

    Key  : Analysis.Elapsed.mSec
    Value: 2644

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: AV_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {7eea5677-f68d-2154-717e-887e07e55cd3}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8025bc89a5e

BUGCHECK_P3: ffffd1026af1e600

BUGCHECK_P4: 0

FILE_IN_CAB:  062023-9093-01.dmp

CONTEXT:  ffffd1026af1e600 -- (.cxr 0xffffd1026af1e600)
rax=fffff8025bc89a40 rbx=fffebd0a17f90010 rcx=fffebd0a17f90010
rdx=ffffbd0a08982000 rsi=0000000000000000 rdi=ffffbd0a08984010
rip=fffff8025bc89a5e rsp=ffffd1026af1f000 rbp=ffffd1026af1f109
 r8=0000000000000001  r9=0000000000000016 r10=0000000000000000
r11=ffffd6feb6200000 r12=fffebd0a17f90010 r13=0000000000000000
r14=ffffd7001183de78 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nvlddmkm+0xf99a5e:
fffff802`5bc89a5e 4c8bb180000000  mov     r14,qword ptr [rcx+80h] ds:002b:fffebd0a`17f90090=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT: 
ffffd102`6af1f000 00000000`00000000     : ffffd700`1183de78 00000000`00000000 fffebd0a`17f90010 ffffd102`6af1f109 : nvlddmkm+0xf99a5e


SYMBOL_NAME:  nvlddmkm+f99a5e

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr 0xffffd1026af1e600 ; kb

BUCKET_ID_FUNC_OFFSET:  f99a5e

FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup:     MachineOwner
---------
 
BIOS güncel olmasına bazı sürücüler güncel değil.

Kod:
start end module name.
fffff801`85490000 fffff801`8549d000 amdgpio2 (deferred)
 Image path: \SystemRoot\System32\drivers\amdgpio2.sys
 Image name: amdgpio2.sys
 Browse all global symbols functions data.
 Timestamp: Wed Mar 11 14:15:48 2020 (5E68C864)
 CheckSum: 0000FA1F.
 ImageSize: 0000D000.
 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 Information from resource tables:

Chipset güncelle.

Kod:
start end module name.
fffff801`61400000 fffff801`61518000 rt640x64 (deferred)
 Image path: \SystemRoot\System32\drivers\rt640x64.sys
 Image name: rt640x64.sys
 Browse all global symbols functions data.
 Timestamp: Tue May 11 06:30:41 2021 (6099FA61)
 CheckSum: 0012905D.
 ImageSize: 00118000.
 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 Information from resource tables:

Realtek Ethernet sürücücüsünü güncelle.


Ekran kartı sürücücüsünü DDU ile kaldırıp en güncel ekran kartı sürücüsünü (WHQL) NVIDIA internet sitesinden edinin.


Kod:
15: 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: fffff8025bc89a5e, Address of the instruction which caused the BugCheck.
Arg3: ffffd1026af1e600, Address of the context record for the exception that caused the BugCheck.
Arg4: 0000000000000000, zero.

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

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 2655.

 Key : Analysis.Elapsed.mSec
 Value: 2644.

 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: 421.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x3b.

 Key : Failure.Bucket
 Value: AV_nvlddmkm!unknown_function

 Key : Failure.Hash
 Value: {7eea5677-f68d-2154-717e-887e07e55cd3}

 Key : WER.OS.Branch
 Value: vb_release.

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 3b.

BUGCHECK_P1: c0000005.

BUGCHECK_P2: fffff8025bc89a5e.

BUGCHECK_P3: ffffd1026af1e600.

BUGCHECK_P4: 0

FILE_IN_CAB: 062023-9093-01.dmp

CONTEXT: ffffd1026af1e600 -- (.cxr 0xffffd1026af1e600)
rax=fffff8025bc89a40 rbx=fffebd0a17f90010 rcx=fffebd0a17f90010
rdx=ffffbd0a08982000 rsi=0000000000000000 rdi=ffffbd0a08984010
rip=fffff8025bc89a5e rsp=ffffd1026af1f000 rbp=ffffd1026af1f109
 r8=0000000000000001 r9=0000000000000016 r10=0000000000000000
r11=ffffd6feb6200000 r12=fffebd0a17f90010 r13=0000000000000000
r14=ffffd7001183de78 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc.
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00050282
nvlddmkm+0xf99a5e:
fffff802`5bc89a5e 4c8bb180000000 mov r14,qword ptr [rcx+80h] ds:002b:fffebd0a`17f90090=????????????????
Resetting default scope.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

STACK_TEXT:
ffffd102`6af1f000 00000000`00000000 : ffffd700`1183de78 00000000`00000000 fffebd0a`17f90010 ffffd102`6af1f109 : nvlddmkm+0xf99a5e

SYMBOL_NAME: nvlddmkm+f99a5e

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xffffd1026af1e600 ; kb.

BUCKET_ID_FUNC_OFFSET: f99a5e.

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

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

Söylediklerinin hepsini yaptım. Sorun bunlar mı peki? Bellek testi yapmama gerek var mı?
 
Suanlik gerek yok eğer yine mavi ekran verirse yeni minidump dosyasını tekrardan yükle.
 
Tamamdır teşekkür ederim.
Suanlik gerek yok eğer yine mavi ekran verirse yeni minidump dosyasını tekrardan yükle.

Yeni bir dosyamız var. Sorun ne merak içerisindeyim. Müsait olduğunda inceler misin?

Suanlik gerek yok eğer yine mavi ekran verirse yeni minidump dosyasını tekrardan yükle.

Mavi ekran sorunu almadım farklı oyunlarda denemeler yaptım. PUBG, Diablo IV, Tom Clancy's Rainbow Six: Siege bu oyunlarda çökmeler meydana geldi sık sık.

Memtest86 sonuçları
WhatsApp Image 2023-06-26 at 04.27.49 (2).jpeg
WhatsApp Image 2023-06-26 at 04.27.49.jpeg
WhatsApp Image 2023-06-26 at 04.27.49 (1).jpeg


@lazye

@Kullanıcı311

Son görselde biraz blur olmuş ancak error yok.
 
Son düzenleme:
CPU-Z şimdilik silin. Chipset sürücüsünü Denetim Masası'ndan önce kaldırın sonrasında yeniden yükleyin. Chipset sürücüsü güncellenmemiş görünüyor.

Ekran kartının güç pinleri tam olarak yerleştirildiğinden emin olun. Sonrasında OCCT testi yapın.

OCCT 3D ve VRAM testi gerçekleştirin her ikisi için ayrı ayrı 15 DK yeterlidir. Ekran görüntülerinde burada paylaşın.


CMD yönetici olarak çalışıtırın sfc/scannow komutunu kullanın.


Disk testi yapın.


Kod:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the BugCheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the BugCheck
Arg4: fffff804744ae920, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3156

    Key  : Analysis.Elapsed.mSec
    Value: 6080

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : Failure.Bucket
    Value: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler

    Key  : Failure.Hash
    Value: {9ac18088-8c91-40fd-01fb-5255bc467cba}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  139

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: fffff804744ae920

FILE_IN_CAB:  062523-9921-01.dmp

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff804`744ae168 fffff804`7040626b     : 00000000`00000139 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff804`744ae170 fffff804`70406722     : fffff804`70406250 00000000`00000000 00000000`00000000 00000000`00000000 : nt!guard_icall_handler+0x1b
fffff804`744ae1a0 fffff804`702e5b37     : fffff804`744ae710 00000000`00000000 fffff804`744ae920 fffff804`70406324 : nt!RtlpExecuteHandlerForException+0x12
fffff804`744ae1d0 fffff804`702e7b06     : fffff804`74497f98 fffff804`744aee20 fffff804`74497f98 fffff804`6c194180 : nt!RtlDispatchException+0x297
fffff804`744ae8f0 fffff804`703fd142     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff804`744aefb0 fffff804`703fd110     : fffff804`70410165 ffffb90d`9d4e56b0 00000000`387028be 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff804`74497e58 fffff804`70410165     : ffffb90d`9d4e56b0 00000000`387028be 00000000`00000000 ffffb90d`9d4e56b8 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff804`74497e60 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125


SYMBOL_NAME:  nt!guard_icall_handler+1b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1b

FAILURE_BUCKET_ID:  0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9ac18088-8c91-40fd-01fb-5255bc467cba}

Followup:     MachineOwner
---------
 
Eve yeni geldim chipset sürücülerini güncelleyip testlere başlayacağım.

CPU-Z şimdilik silin. Chipset sürücüsünü Denetim Masası'ndan önce kaldırın sonrasında yeniden yükleyin. Chipset sürücüsü güncellenmemiş görünüyor.

Ekran kartının güç pinleri tam olarak yerleştirildiğinden emin olun. Sonrasında OCCT testi yapın.

OCCT 3D ve VRAM testi gerçekleştirin her ikisi için ayrı ayrı 15 DK yeterlidir. Ekran görüntülerinde burada paylaşın.


CMD yönetici olarak çalışıtırın sfc/scannow komutunu kullanın.


Disk testi yapın.


Kod:
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the BugCheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the BugCheck
Arg4: fffff804744ae920, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3156

    Key  : Analysis.Elapsed.mSec
    Value: 6080

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : Failure.Bucket
    Value: 0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler

    Key  : Failure.Hash
    Value: {9ac18088-8c91-40fd-01fb-5255bc467cba}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  139

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: fffff804744ae920

FILE_IN_CAB:  062523-9921-01.dmp

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffff804`744ae168 fffff804`7040626b     : 00000000`00000139 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff804`744ae170 fffff804`70406722     : fffff804`70406250 00000000`00000000 00000000`00000000 00000000`00000000 : nt!guard_icall_handler+0x1b
fffff804`744ae1a0 fffff804`702e5b37     : fffff804`744ae710 00000000`00000000 fffff804`744ae920 fffff804`70406324 : nt!RtlpExecuteHandlerForException+0x12
fffff804`744ae1d0 fffff804`702e7b06     : fffff804`74497f98 fffff804`744aee20 fffff804`74497f98 fffff804`6c194180 : nt!RtlDispatchException+0x297
fffff804`744ae8f0 fffff804`703fd142     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff804`744aefb0 fffff804`703fd110     : fffff804`70410165 ffffb90d`9d4e56b0 00000000`387028be 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff804`74497e58 fffff804`70410165     : ffffb90d`9d4e56b0 00000000`387028be 00000000`00000000 ffffb90d`9d4e56b8 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff804`74497e60 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125


SYMBOL_NAME:  nt!guard_icall_handler+1b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1b

FAILURE_BUCKET_ID:  0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_handler

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9ac18088-8c91-40fd-01fb-5255bc467cba}

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

Testleri yaptım yonga setini güncelledim. Cmd scannow komutunu çalıştırdım.

Sanıyorum bu kadar testin üzerine problem yazılım kaynaklı. En sağlıklısı temiz bir kurulum değil mi?
 

Dosya Ekleri

  • ssdokuma.png
    ssdokuma.png
    64,3 KB · Görüntüleme: 41
  • ssd.png
    ssd.png
    32,7 KB · Görüntüleme: 30
  • sagliktesti.png
    sagliktesti.png
    12,1 KB · Görüntüleme: 38
  • m2okuma.png
    m2okuma.png
    61,3 KB · Görüntüleme: 34
  • m2.png
    m2.png
    31,3 KB · Görüntüleme: 41
  • cmd.png
    cmd.png
    24,6 KB · Görüntüleme: 31
  • 4060.png
    4060.png
    263,1 KB · Görüntüleme: 33
  • yonga.png
    yonga.png
    357,7 KB · Görüntüleme: 23
Son düzenleme:
Hayır bu şekilde kulanmaya devam edin ekran kartın da şu an bir sorun gözükmüyor. Ayrıca VRAM testi yaptın mı? Onun ekran görüntüsü mevcut değil. Ama Toshiba SSD sağlığı düşmüş %85'e dikkatimi çekti Diablo IV hangi SSD kurulu Toshiba da mı?
 

Technopat Haberler

Yeni konular

Geri
Yukarı