APC_INDEX_MISTMACH ve IRQL_NOT_LESS_OR_EQUAL mavi ekran hatası

İşletim sistemi
Windows 10

jTaner

Centipat
Katılım
21 Aralık 2020
Mesajlar
5
Daha fazla  
Cinsiyet
Erkek
Fortnite oynarken mi çıkıyor hata? Epic Games sıkıntı çıkarıyor. Epic'i silip bir daha yüklemeyi dener misin?

Hayır Fortnite oynamıyorum Epic Games'te sadece GTA V yüklü çok oynamıyorum zaten onu da. GTA V ve Epic Games'i silsem düzelir mi sizce? Bu arada ben aldığımdan beri GeForce Experience harici hiçbir ekran kartı, BIOS vs şeyleri güncellemedim ondan kaynaklı olma ihtimali var mıdır?
 
Olabilir. BIOS ve ekran kartı sürücüsünü güncellemende fayda var. Epic'i silip bir daha dene.

Yukarıda sistemin linkini paylaşmıştım. Rica etsem ona uygun olan ekran kartı ve BIOS linklerini atar mısınız? Yanlış bir şey indirip daha da ilerletmek istemiyorum
Epic Games'i sildim başka bir şeyden olma ihtimali var mıdır
 
Dosyalarda Epic Games ile alakalı hiçbir şey görmedim. Öte yandan BIOS ve ekran kartıyla ilgili söylenenler doğru.

Bunlara ek olarak Windows'u güncelleyin. Ayrıca bu yazılımla SSD'nize FW kontrolü yapın. Ve Memtest uygulayın.

Kod:
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ffe2702c034, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffff820e747feb80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5686

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7583

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

BUGCHECK_P1: 7ffe2702c034

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffff820e747feb80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  EpicGamesLauncher.exe

STACK_TEXT: 
ffff820e`747fe9b8 fffff801`33007769     : 00000000`00000001 00007ffe`2702c034 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffff820e`747fe9c0 fffff801`33007633     : 000002a1`25eb39d0 ffff940d`3e1c6560 ffff820e`747feb18 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69
ffff820e`747feb00 00007ffe`2702c034     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
000000fd`7650f648 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`2702c034


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {52cd694c-15ec-48c3-924a-3539560711db}

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: fffff8021c8fa320, 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: 7202

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 14640

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

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8021c8fa320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffc700f7261490 -- (.trap 0xffffc700f7261490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000b22180c6 rbx=0000000000000000 rcx=ffffc700f72616a4
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8021be44567 rsp=ffffc700f7261620 rbp=ffffc700f72616b9
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeYieldProcessorEx+0x17:
fffff802`1be44567 4883c420 add rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: EpicGamesLauncher.exe

BAD_STACK_POINTER: ffffc700f7261620

STACK_TEXT:
ffffb280`a02bde18 fffff802`1c03aa0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`1c8fa320 : nt!KeBugCheckEx
ffffb280`a02bde20 fffff802`1be6f9a3 : 00001bef`e0970027 ffffb280`a02a4180 00000000`00000000 ffffb280`a02a4180 : nt!KeAccumulateTicks+0x1c880c
ffffb280`a02bde80 fffff802`1be6f48a : ffff9b0f`d13049a0 ffffc700`f7261510 ffffc700`f2c53b00 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffffb280`a02bdf30 fffff802`1bf27ef5 : ffff9b0f`d13049a0 ffff9b0f`d1304ac0 ffff9b0f`d1304b70 ffff7d63`de3bed14 : nt!HalpTimerClockIpiRoutine+0x1a
ffffb280`a02bdf60 fffff802`1bff722a : ffffc700`f7261510 ffff9b0f`d13049a0 fffff802`180ea180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb280`a02bdfb0 fffff802`1bff7797 : ffff9b0f`ddbd65c0 ffffc700`f7261529 ffffb280`a02a4180 fffff802`1bff77a4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffc700`f7261490 fffff802`1be44567 : 00000000`00000010 00000000`00000282 ffffc700`f7261648 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffc700`f7261620 fffff802`1c119a7e : 00000048`063200e6 00000000`00000006 ffffb280`a02b2000 ffff9b0f`d12c5200 : nt!KeYieldProcessorEx+0x17
ffffc700`f7261650 fffff802`1c02c6fc : ffffb280`a02a4180 00000000`00000000 00000000`00000004 ffffc700`f726175c : nt!KiHeteroChooseTargetProcessor+0x55e
ffffc700`f7261720 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeferredReadySingleThread+0x1e1bac


SYMBOL_NAME: nt!KeAccumulateTicks+1c880c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.685

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1c880c

FAILURE_BUCKET_ID: 0x133_ISR_STACKPTR_ERROR_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e29be0eb-3419-aa75-d38d-83d2e8ddbdc2}

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


APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ffb1dd4c074, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffee0f1714fb80, Call type (0 - system call, 1 - worker routine)

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4655

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 12973

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

BUGCHECK_P1: 7ffb1dd4c074

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffffee0f1714fb80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:
ffffee0f`1714f948 fffff803`3e207769 : 00000000`00000001 00007ffb`1dd4c074 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffee0f`1714f950 fffff803`3e207633 : ffffc409`4594b580 00000000`00000000 00000000`00000000 00000248`a0f74b10 : nt!KiBugCheckDispatch+0x69
ffffee0f`1714fa90 00007ffb`1dd4c074 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
000000ce`457ff3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`1dd4c074


SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.685

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x1_SysCallNum_6_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {86ef4402-c30f-c6ef-f6d3-34a22389d637}

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



APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007ffd31b0c034, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffea0856948b80, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3312

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 4896

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

BUGCHECK_P1: 7ffd31b0c034

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffffea0856948b80

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: EpicGamesLauncher.exe

STACK_TEXT:
ffffea08`569489b8 fffff801`39207769 : 00000000`00000001 00007ffd`31b0c034 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffea08`569489c0 fffff801`39207633 : 0000012f`165f9480 00000000`00000000 ffffea08`56948b18 ffffffff`fffe7960 : nt!KiBugCheckDispatch+0x69
ffffea08`56948b00 00007ffd`31b0c034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000013`80a5f6c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`31b0c034


SYMBOL_NAME: nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.685

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x1_SysCallNum_4_nt!KiSystemServiceExitPico

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {52cd694c-15ec-48c3-924a-3539560711db}

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



SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8058155a1d6, Address of the instruction which caused the bugcheck
Arg3: ffff8901a4ad2920, 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: 3968

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 5242

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

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8058155a1d6

BUGCHECK_P3: ffff8901a4ad2920

BUGCHECK_P4: 0

CONTEXT:  ffff8901a4ad2920 -- (.cxr 0xffff8901a4ad2920)
rax=ffffb60775a532e8 rbx=ffffb60775b09080 rcx=b60775a532b03085
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffb60775a532e0
rip=fffff8058155a1d6 rsp=fffffb00f237e940 rbp=fffffb00f237ea01
r8=0000000000000000 r9=0000005503d3b29f r10=0000000000000002
r11=fffff780000003b0 r12=0000000000000000 r13=b60775a532b03085
r14=0000000000000000 r15=ffffb60775b091c0
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
nt!KeAbPreWait+0x6:
fffff805`8155a1d6 0fb64120 movzx eax,byte ptr [rcx+20h] ds:002b:b60775a5`32b030a5=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: EpicGamesLauncher.exe

BAD_STACK_POINTER: ffff8901a4ad2018

STACK_TEXT:
fffffb00`f237e940 fffff805`8163470b : fffffb00`000000f4 fffff805`8182af81 ffff8901`a4f8e101 ffffb607`75b091c0 : nt!KeAbPreWait+0x6
fffffb00`f237e970 fffff805`8182c6a1 : ffffb607`75a532e0 00000000`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x1d031b
fffffb00`f237ea60 fffff805`8182c74a : ffffb607`75b09080 000000d6`a2f7f808 00000000`00000000 00000000`00000000 : nt!ObWaitForSingleObject+0x91
fffffb00`f237eac0 fffff805`816071b8 : 00000000`00000000 00000000`00000000 fffffb00`f237eb18 ffffffff`fffe7960 : nt!NtWaitForSingleObject+0x6a
fffffb00`f237eb00 00007ffd`4026c034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000d6`a2f7f7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`4026c034


SYMBOL_NAME: nt!KeAbPreWait+6

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.685

STACK_COMMAND: .cxr 0xffff8901a4ad2920 ; kb

BUCKET_ID_FUNC_OFFSET: 6

FAILURE_BUCKET_ID: 0x3B_c0000005_STACKPTR_ERROR_nt!KeAbPreWait

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ddcb9656-083d-2ea8-831a-b13145df4ef7}

Followup: MachineOwner
---------
 
Hayır. O, mavi ekran alındığı sırada ne yapıldığını belirtiyor. Bazen orada System bile yazar. Bu durumda sistemi kapatması gerekmeyecektir, değil mi?
 
PROCESS_NAME: chrome.exe
Gerçi burada da Chrome yazıyor. Dün gece görememişim. Ben burada yazan işlem crash olduğu için hata veriyor sanıyordum ama yanlış biliyorum sanırım.
DPC watchdog hatası genelde BIOS ce sürücüler ile alakalı bir problemde ortaya çıkıyor. APC hatası da aynı şekilde genellikle BIOS hatası. BIOS güncellemesi hataları ortadan kaldırabilir.
 
Son düzenleme:

Bu konuyu görüntüleyen kullanıcılar

Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…