Çözüldü RX 5700 XT crash ve mavi ekran hatası

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

ENCORESTT

Hectopat
Katılım
18 Mart 2017
Mesajlar
18
Daha fazla  
Cinsiyet
Erkek
Apex Legends oyununu oynuyorum, fakat mavi ekran ve crash hatasını sürekli aldığımdan dolayı ne oyun zevkim kaldı ne de PC'yi açasım geliyor.

minidump

Konu için birçok yeri araştırdım internette lakin çözüm bulamadım.
Yardımlarınızı rica ediyorum, şimdiden teşekkür ederim.
 
Son düzenleyen: Moderatör:
Çözüm
Test büyük ihtimal problemsiz bitecektir, sistemi bu şekilde kullanın herhangi bir hız aşırtma işlemi yapmayın, 1 hafta kadar bu şekilde kalsın, sonrasında hız aşırtma işlemi yaparsınız, bellek hataları büyük ihtimal hız aşırtma nedenli olabilir.
Chipset sürücüsünü sen mi kurdun Windows mu kurdu?
DeviceInst is "PCI\VEN_1022&DEV_7901&SUBSYS_87C01043&REV_51\4&9b70dcb&0&0043"
ServiceName is "storahci"
Chipset sürücüsünü kaldır, tekrar kur.
Güç ve Uyku ayarlarını varsayılana döndür.

HDtune(Error scan, Health) sonuçlarını fotoğraf şeklinde paylaş.

Belleklerin kit mi aynı kutunda mı çıktı ikisi de?
CMK8GX4M1D3000C16
Kod:
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffa48973481060, Physical Device Object of the stack
Arg3: fffff804436678b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffa489735609c0, The blocked IRP

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  5220

BIOS_DATE:  09/12/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  PRIME B350-PLUS

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: 3

BUGCHECK_P2: ffffa48973481060

BUGCHECK_P3: fffff804436678b0

BUGCHECK_P4: ffffa489735609c0

DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: ffffa48970fe1060

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  f525018

MODULE_NAME: pci

FAULTING_MODULE: fffff804420b0000 pci

CPU_COUNT: c

CPU_MHZ: fa0

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-08-2020 00:20:14.0425

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_TEXT: 
fffff804`43667878 fffff804`3eaee3d7 : 00000000`0000009f 00000000`00000003 ffffa489`73481060 fffff804`436678b0 : nt!KeBugCheckEx
fffff804`43667880 fffff804`3eaee2e1 : ffffa489`73571228 00000000`00000001 fffff804`3b5fa100 fffff804`3b5fa180 : nt!PopIrpWatchdogBugcheck+0xef
fffff804`436678f0 fffff804`3e86ba89 : ffffa489`73571260 00000001`d13d8dca 00000001`00000002 ffffa489`77070010 : nt!PopIrpWatchdog+0x31
fffff804`43667940 fffff804`3e86a7e9 : 00000000`00000004 00000000`00989680 00000000`0000744f 00000000`00000067 : nt!KiProcessExpiredTimerList+0x169
fffff804`43667a30 fffff804`3e9c5024 : 00000000`00000000 fffff804`3b5fa180 fffff804`3ed91400 ffffa489`8039b580 : nt!KiRetireDpcList+0x4e9
fffff804`43667c60 00000000`00000000 : fffff804`43668000 fffff804`43662000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


THREAD_SHA1_HASH_MOD_FUNC:  418dcf5cc7a95525fe8ac8ffec7980c508fac304

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  380ee536789d4b77d82e9ab3a599c8d978e0118f

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.18362.418

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_IMAGE_pci.sys

PRIMARY_PROBLEM_CLASS:  0x9F_3_IMAGE_pci.sys

TARGET_TIME:  2020-01-07T16:59:43.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  4a1d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_image_pci.sys

FAILURE_ID_HASH:  {a89ab2d1-2459-89ee-9990-558bbc68ffab}

Followup:     MachineOwner
---------
INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000618, A runtime power worker thread has been blocked for too long.
Arg2: fffff804540463e0, POP_FX_WORK_ORDER_WATCHDOG_INFO WorkOrder
Arg3: ffff980d73f2d500
Arg4: 0000000000000000

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  5220

BIOS_DATE:  09/12/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  PRIME B350-PLUS

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: 618

BUGCHECK_P2: fffff804540463e0

BUGCHECK_P3: ffff980d73f2d500

BUGCHECK_P4: 0

BUGCHECK_STR:  0xa0_618

CPU_COUNT: c

CPU_MHZ: fa0

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-08-2020 00:20:18.0409

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80453ef27ec to fffff80453dc14e0

STACK_TEXT: 
ffffc08a`c9a298c8 fffff804`53ef27ec : 00000000`000000a0 00000000`00000618 fffff804`540463e0 ffff980d`73f2d500 : nt!KeBugCheckEx
ffffc08a`c9a298d0 fffff804`53ef6710 : ffffd481`c7100100 ffffd481`c7100180 ffffc08a`c9a29b10 00000000`000000e8 : nt!PopFxBugCheck+0x1c
ffffc08a`c9a29910 fffff804`53c6ba89 : fffff804`540463f0 00000000`00000080 00000000`00000002 ffff980d`00000002 : nt!PopFxWorkOrderWatchdog+0x20
ffffc08a`c9a29940 fffff804`53c6a7e9 : 00000000`0000001c 00000000`00989680 00000000`0002c4d0 00000000`000000e8 : nt!KiProcessExpiredTimerList+0x169
ffffc08a`c9a29a30 fffff804`53dc5024 : ffffffff`00000000 ffffd481`c7100180 ffffd481`c7111340 ffff980d`74f63080 : nt!KiRetireDpcList+0x4e9
ffffc08a`c9a29c60 00000000`00000000 : ffffc08a`c9a2a000 ffffc08a`c9a24000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


THREAD_SHA1_HASH_MOD_FUNC:  54a6c48e58dcb19a2fcb6f1f502312c7b23f2f10

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  7e41fa43d5260ebe4a0f113d3b220af4388552f1

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!PopFxBugCheck+1c
fffff804`53ef27ec cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PopFxBugCheck+1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  12dcb470

IMAGE_VERSION:  10.0.18362.535

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c

FAILURE_BUCKET_ID:  0xa0_618_nt!PopFxBugCheck

BUCKET_ID:  0xa0_618_nt!PopFxBugCheck

PRIMARY_PROBLEM_CLASS:  0xa0_618_nt!PopFxBugCheck

TARGET_TIME:  2020-01-07T16:27:04.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  2a08

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xa0_618_nt!popfxbugcheck

FAILURE_ID_HASH:  {4c2ec2fb-a62c-0da9-a5e7-a33f475a50a1}

Followup:     MachineOwner
---------
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: ffffc84a856bb4f0, memory referenced.
Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.
Arg3: fffff8023bc39c37, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  5220

BIOS_DATE:  09/12/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  PRIME B350-PLUS

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: ffffc84a856bb4f0

BUGCHECK_P2: 2

BUGCHECK_P3: fffff8023bc39c37

BUGCHECK_P4: 0

READ_ADDRESS: fffff8023c1733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
 ffffc84a856bb4f0

FAULTING_IP:
nt!ExAcquirePushLockExclusiveEx+107
fffff802`3bc39c37 f0480fba2e00    lock bts qword ptr [rsi],0

MM_INTERNAL_CODE:  0

CPU_COUNT: c

CPU_MHZ: fa0

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  Discord.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  01-08-2020 00:20:10.0848

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME:  ffffc38e3c826890 -- (.trap 0xffffc38e3c826890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffda0f1726a080
rdx=ffffc84a846bb4f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023bc39c37 rsp=ffffc38e3c826a20 rbp=ffffc38e3c826b80
 r8=ffffc38e3c826a68  r9=00000000757c2fdc r10=fffff8023bc39b30
r11=ffffc38e3c826a80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExAcquirePushLockExclusiveEx+0x107:
fffff802`3bc39c37 f0480fba2e00    lock bts qword ptr [rsi],0 ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8023bde3863 to fffff8023bdc14e0

STACK_TEXT: 
ffffc38e`3c8265e8 fffff802`3bde3863 : 00000000`00000050 ffffc84a`856bb4f0 00000000`00000002 ffffc38e`3c826890 : nt!KeBugCheckEx
ffffc38e`3c8265f0 fffff802`3bc72eef : ffffda0f`1726a080 00000000`00000002 00000000`00000000 ffffc84a`856bb4f0 : nt!MiSystemFault+0x1d6af3
ffffc38e`3c8266f0 fffff802`3bdcf520 : 00000000`00000000 00000000`00000000 00000000`006cf000 ffffc880`ff7c0100 : nt!MmAccessFault+0x34f
ffffc38e`3c826890 fffff802`3bc39c37 : ffffda0f`1726a080 ffffc84a`846bb4f0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x360
ffffc38e`3c826a20 ffffc811`7ead4a22 : ffffc84a`846bb490 00000000`00000000 ffffc84a`00000000 00000000`00000049 : nt!ExAcquirePushLockExclusiveEx+0x107
ffffc38e`3c826a60 ffffc811`7ea9bd4c : 00000000`00000000 00000000`00000049 00000000`00000048 ffffc84a`8610d8a0 : win32kbase!CAsyncKeyEventMonitor::OnKeyStateRequested+0x2a
ffffc38e`3c826a90 fffff802`3bdd2d18 : ffffda0f`1726a080 ffffc811`7ebc8678 00000000`00000049 ffffda0f`1e9a90e0 : win32kbase!NtUserGetAsyncKeyState+0x870ec
ffffc38e`3c826b00 00000000`776d1cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`1dadf2a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776d1cbc


THREAD_SHA1_HASH_MOD_FUNC:  45623ad0661cb88c4410b6fd1aa657e3b6b01b9c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d02bfcf4bcd91778a381044728ffd34d8b6c1cd3

THREAD_SHA1_HASH_MOD:  d974ef264762fa6a9116705c79e3a96f7e371fb3

FOLLOWUP_IP:
win32kbase!CAsyncKeyEventMonitor::OnKeyStateRequested+2a
ffffc811`7ead4a22 8b4304          mov     eax,dword ptr [rbx+4]

FAULT_INSTR_CODE:  4104438b

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32kbase!CAsyncKeyEventMonitor::OnKeyStateRequested+2a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.535

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2a

FAILURE_BUCKET_ID:  AV_INVALID_win32kbase!CAsyncKeyEventMonitor::OnKeyStateRequested

BUCKET_ID:  AV_INVALID_win32kbase!CAsyncKeyEventMonitor::OnKeyStateRequested

PRIMARY_PROBLEM_CLASS:  AV_INVALID_win32kbase!CAsyncKeyEventMonitor::OnKeyStateRequested

TARGET_TIME:  2020-01-02T21:34:40.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 18:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  4183

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_invalid_win32kbase!casynckeyeventmonitor::onkeystaterequested

FAILURE_ID_HASH:  {0255cd3f-8da6-774a-034c-36889696eec1}

Followup:     MachineOwner
---------
 
Merhaba, bu yöntemi denemenizi tavsiye edeceğim. Bu şekilde kendim 5700 XT GPU'mu düzeltebildim.
Mevcut sürücünüzü DDU ile kaldırdıktan sonra, https://www.amd.com/en/support/prev...d-radeon-rx-5700-series/amd-radeon-rx-5700-xt adresinden Adrenalin 2019 Edition 19.12.1 Optional sürümünü indirip kurmayı deneyebilir misiniz?
Daha sonrasında radeon ayarlarından herhangi bir ek özelliği aktif etmeyin. Test sonucunu paylaşırsanız beraber çözmeye çalışalım.
 
Evet bende @Zilyano nun önerisini yazacaktım. Yıllardır bir AMD kullanıcısı ve sevdalısı olarak, hep bir önceki recomended sürücülerini kullanırım.
 
@MayCrasH Chipset driver'ı formattan sonra manuel olarak kurdum, sürekli mavi ekran ve crash verdiği için bir format atmıştım.
RX570 ve Ryzen 1600 le bu kadar pek crash yemiyordum.
RAM'leri aynı yerden 2 ayrı kutuda aldım. Farbrika üretim numaraları mı oluyor neyse aynıydı.
Anakarta BIOS Update atıp Ryzen 3600 ekledim sisteme ve onunla birlikte RX5700XT fakat verdiğim paraya değmedi desem yeridir. Sorun anakartta mı ekran kartında mı RAM'de mi yoksa hepsinde mi bilmiyorum :/ :D.


@Zilyano 19.12.1 sürümünü şimdi kurdum lakin hangi testi istediğini anlamadım.
Sadece o oyuna mahsus mu mavi ekran hataları? Başka uygulamalarda veya oyunlarda oluyor mu?
Genellikle Apex oynuyorum, PUBG'de 1-2 kere crash aldığım olmuştu.

3D Mark programında testin ortasında çalışmayı durdurdu hatası veriyor malesef tamamlayamadım bir türlü
 

Dosya Ekleri

  • Screenshot_1.png
    Screenshot_1.png
    10,6 KB · Görüntüleme: 58
  • Screenshot_2.png
    Screenshot_2.png
    8,1 KB · Görüntüleme: 63
  • Screenshot_3.png
    Screenshot_3.png
    17,3 KB · Görüntüleme: 65
Son düzenleme:
AIDA64 raporu paylaşır mısın?
 
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı