Çözüldü Monster Abra A5 v17.2 laptopta DRIVER_NOT_LESS_OR_EQUAL Mavi Ekran Hatası

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

EmreTosun

Hectopat
Katılım
19 Haziran 2019
Mesajlar
67
Çözümler
1
RAM
16GB (2x8GB) DDR4 1.2V 3200MHz SODIMM
SSD veya HDD modeli
512GB SAMSUNG PM991A M.2 SSD
Ekran kartı
nVIDIA® GeForce® RTX3050 TI Max-Performance 4GB GD
Anakart
Mobile Intel® HM570 Chipset
İşlemci
Intel® Tiger Lake Core™ i5-11400H 6C/12T; 12MB L3;
Monster Abra A5 v17.2 modelini kullanıyorum aldığım günden beri Valorant oynarken düzenli düzensiz
DRIVER_NOT_LESS_OR_EQUAL mavi ekran hatası alıyorum. Minidump dosyasına baktığımda kbdclss.sys yani klavye driverindan dolayı olduğunu anladım. Siz değerli hocalarımdan anlayan varsa minidump dosyalarından son 2 tanesini kod olarak bırakıyorum. Yardımcı olabilecek olan varsa çok sevinirim. Şimdiden teşekkür ederim.

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

Loading Dump File [C:\Users\dogus\Desktop\022523-19390-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 22621 MP (12 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Machine Name:
Kernel base = 0xfffff802`14000000 PsLoadedModuleList = 0xfffff802`14c13450
Debug session time: Sat Feb 25 22:45:50.833 2023 (UTC + 3:00)
System Uptime: 0 days 23:58:20.008
Loading Kernel Symbols.
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..................................................
Loading User Symbols.
Loading unloaded module list.
........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`14428c50 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff802`162df330=000000000000000a
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffcb903791b26c, memory referenced.
Arg2: 0000000000000002, IRQL.
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg4: fffff8025ef632d2, address which referenced memory.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1280.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 4121.

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0xd1.

 Key : Bugcheck.Code.Register
 Value: 0xa.

 Key : Dump.Attributes.AsUlong
 Value: 1808.

 Key : Dump.Attributes.DiagDataWrittenToHeader
 Value: 1

 Key : Dump.Attributes.ErrorCode
 Value: 0

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Dump.Attributes.LastLine
 Value: Dump completed successfully.

 Key : Dump.Attributes.ProgressPercentage
 Value: 0

FILE_IN_CAB: 022523-19390-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b.

DUMP_FILE_ATTRIBUTES: 0x1808.
 Kernel Generated Triage Dump.

BUGCHECK_CODE: d1.

BUGCHECK_P1: ffffcb903791b26c.

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8025ef632d2.

READ_ADDRESS: fffff80214d1c468: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
 ffffcb903791b26c.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64

DPC_STACK_BASE: FFFFF802162DFFB0.

TRAP_FRAME: fffff802162df470 -- (.trap 0xfffff802162df470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffcb8f282780c0 rbx=0000000000000000 rcx=ffffcb8f282780c0
rdx=000000010f6a31ac rsi=0000000000000000 rdi=0000000000000000
rip=fffff8025ef632d2 rsp=fffff802162df608 rbp=fffff802162df680
 r8=00000000000000c0 r9=0000000000000038 r10=ffffcb8f12bf8000
r11=ffffcb903791b32c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc.
kbdclass!memcpy+0x92:
fffff802`5ef632d2 0f100411 movups xmm0,xmmword ptr [rcx+rdx] ds:ffffcb90`3791b26c=????????????????????????????????
Resetting default scope.

STACK_TEXT:
fffff802`162df328 fffff802`1443e2a9 : 00000000`0000000a ffffcb90`3791b26c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff802`162df330 fffff802`14439934 : ffffcb8f`16226180 fffff802`30212e82 00000000`00000000 ffffcb8f`16226030 : nt!KiBugCheckDispatch+0x69
fffff802`162df470 fffff802`5ef632d2 : fffff802`5ef65b5d 00000000`df94da64 fffff802`162df680 ffffcb8f`27a598a0 : nt!KiPageFault+0x474
fffff802`162df608 fffff802`5ef65b5d : 00000000`df94da64 fffff802`162df680 ffffcb8f`27a598a0 fffff802`5ef22d5c : kbdclass!memcpy+0x92
fffff802`162df610 fffff802`5ef51511 : ffffcb8f`0ec8baa0 fffff802`162df7d8 ffffcb8f`0ecad310 fffff802`162df7d8 : kbdclass!KeyboardClassServiceCallback+0x16d
fffff802`162df6b0 ffffcb8f`0ec8baa0 : fffff802`162df7d8 ffffcb8f`0ecad310 fffff802`162df7d8 00000000`00000008 : HKKbdFltr+0x1511
fffff802`162df6b8 fffff802`162df7d8 : ffffcb8f`0ecad310 fffff802`162df7d8 00000000`00000008 fffff802`162df730 : 0xffffcb8f`0ec8baa0
fffff802`162df6c0 ffffcb8f`0ecad310 : fffff802`162df7d8 00000000`00000008 fffff802`162df730 ffffcb8f`0ec8b950 : 0xfffff802`162df7d8
fffff802`162df6c8 fffff802`162df7d8 : 00000000`00000008 fffff802`162df730 ffffcb8f`0ec8b950 fffff802`5ef513f0 : 0xffffcb8f`0ecad310
fffff802`162df6d0 00000000`00000008 : fffff802`162df730 ffffcb8f`0ec8b950 fffff802`5ef513f0 fffff802`0ee63180 : 0xfffff802`162df7d8
fffff802`162df6d8 fffff802`162df730 : ffffcb8f`0ec8b950 fffff802`5ef513f0 fffff802`0ee63180 fffff802`5ef2b848 : 0x8.
fffff802`162df6e0 ffffcb8f`0ec8b950 : fffff802`5ef513f0 fffff802`0ee63180 fffff802`5ef2b848 ffffcb8f`0ec8baa0 : 0xfffff802`162df730
fffff802`162df6e8 fffff802`5ef513f0 : fffff802`0ee63180 fffff802`5ef2b848 ffffcb8f`0ec8baa0 fffff802`162df769 : 0xffffcb8f`0ec8b950
fffff802`162df6f0 fffff802`0ee63180 : fffff802`5ef2b848 ffffcb8f`0ec8baa0 fffff802`162df769 ffffcb8f`0ec93d60 : HKKbdFltr+0x13f0
fffff802`162df6f8 fffff802`5ef2b848 : ffffcb8f`0ec8baa0 fffff802`162df769 ffffcb8f`0ec93d60 fffff802`5ef30258 : 0xfffff802`0ee63180
fffff802`162df700 fffff802`142bd7aa : 00000000`00000000 ffffcb8f`00000010 00000000`00000000 ffffde81`877cd830 : i8042prt!I8042KeyboardIsrDpc+0x1a8
fffff802`162df7d0 fffff802`142bcfb4 : 00000000`00000022 ffffcb8f`21d73080 fffff802`00000000 00000000`00000010 : nt!KiExecuteAllDpcs+0x54a
fffff802`162dfd20 fffff802`144320c5 : 00000000`00000000 00000000`00000000 ffffcb8f`1c6af080 00000256`80eaec80 : nt!KiRetireDpcList+0xfe4
fffff802`162dffb0 fffff802`1443206f : fffffa0a`75e23349 fffff802`142bf699 00000000`00000000 ffffcb8f`2424f460 : nt!KxSwapStacksAndRetireDpcList+0x5
fffffa0a`75e232b0 fffff802`142bf699 : 00000000`00000000 ffffcb8f`2424f460 00000000`00040246 fffff802`142c594b : nt!KiPlatformSwapStacksAndCallReturn
fffffa0a`75e232c0 fffff802`1443183b : 00000257`8efd77c8 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!KiDispatchInterrupt+0xd9
fffffa0a`75e233b0 fffff802`1442ae71 : 00000000`00000000 ffffcb8f`22adcfe0 fffffa0a`00000000 ffffcb8f`00000000 : nt!KiDpcInterruptBypass+0x1b
fffffa0a`75e233e0 00007ff6`4053cac0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1
000000f1`f7f7c988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`4053cac0

SYMBOL_NAME: kbdclass!memcpy+92

MODULE_NAME: kbdclass.

IMAGE_NAME: kbdclass.sys

IMAGE_VERSION: 10.0.23145.1000

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 92.

FAILURE_BUCKET_ID: AV_kbdclass!memcpy

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {dfec7698-3775-c204-13ee-4d0f5bb2791c}

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


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

Loading Dump File [C:\Users\dogus\Desktop\022423-19375-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 22621 MP (12 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Machine Name:
Kernel base = 0xfffff802`68600000 PsLoadedModuleList = 0xfffff802`69213450
Debug session time: Fri Feb 24 22:47:00.478 2023 (UTC + 3:00)
System Uptime: 3 days 2:53:41.014
Loading Kernel Symbols.
...............................................................
................................................................
................................................................
....................................................
Loading User Symbols.
Loading unloaded module list.
............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`68a28c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8003`f98468c0=000000000000000a
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffff8f8a12264000, memory referenced.
Arg2: 0000000000000002, IRQL.
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg4: fffff802b2363349, address which referenced memory.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 2015.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 10720.

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0xd1.

 Key : Bugcheck.Code.Register
 Value: 0xa.

 Key : Dump.Attributes.AsUlong
 Value: 1808.

 Key : Dump.Attributes.DiagDataWrittenToHeader
 Value: 1

 Key : Dump.Attributes.ErrorCode
 Value: 0

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Dump.Attributes.LastLine
 Value: Dump completed successfully.

 Key : Dump.Attributes.ProgressPercentage
 Value: 0

FILE_IN_CAB: 022423-19375-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b.

DUMP_FILE_ATTRIBUTES: 0x1808.
 Kernel Generated Triage Dump.

BUGCHECK_CODE: d1.

BUGCHECK_P1: ffff8f8a12264000.

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff802b2363349.

READ_ADDRESS: fffff8026931c468: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
unable to get nt!MmSpecialPagesInUse
 ffff8f8a12264000.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

TRAP_FRAME: ffff8003f9846a00 -- (.trap 0xffff8003f9846a00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8f89f85c0920 rbx=0000000000000000 rcx=ffff8f89f85c0d70
rdx=0000000019ca326c rsi=0000000000000000 rdi=0000000000000000
rip=fffff802b2363349 rsp=ffff8003f9846b98 rbp=ffff8003f9846c10
 r8=0000000000000020 r9=0000000000000001 r10=ffff8f89f8db1000
r11=ffff8f8a1226403c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc.
kbdclass!memcpy+0x109:
fffff802`b2363349 0f105c1120 movups xmm3,xmmword ptr [rcx+rdx+20h] ds:ffff8f8a`12263ffc=????????????????????????????????
Resetting default scope.

STACK_TEXT:
ffff8003`f98468b8 fffff802`68a3e2a9 : 00000000`0000000a ffff8f8a`12264000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8003`f98468c0 fffff802`68a39934 : 00000273`c2a6116b fffff802`838b2e82 00000000`00000000 ffff8f89`f8a65030 : nt!KiBugCheckDispatch+0x69
ffff8003`f9846a00 fffff802`b2363349 : fffff802`b2365cc5 00000000`eeb8e414 ffff8003`f9846c10 ffff8f8a`0ea65aa0 : nt!KiPageFault+0x474
ffff8003`f9846b98 fffff802`b2365cc5 : 00000000`eeb8e414 ffff8003`f9846c10 ffff8f8a`0ea65aa0 fffff802`b2322d5c : kbdclass!memcpy+0x109
ffff8003`f9846ba0 fffff802`b2351511 : ffff8f89`f8a5fae0 ffff8003`f9846d68 ffff8f89`f8a88310 ffff8003`f9846d68 : kbdclass!KeyboardClassServiceCallback+0x2d5
ffff8003`f9846c40 ffff8f89`f8a5fae0 : ffff8003`f9846d68 ffff8f89`f8a88310 ffff8003`f9846d68 00000000`00000008 : HKKbdFltr+0x1511
ffff8003`f9846c48 ffff8003`f9846d68 : ffff8f89`f8a88310 ffff8003`f9846d68 00000000`00000008 ffff8003`f9846cc0 : 0xffff8f89`f8a5fae0
ffff8003`f9846c50 ffff8f89`f8a88310 : ffff8003`f9846d68 00000000`00000008 ffff8003`f9846cc0 ffff8f89`f8a5f990 : 0xffff8003`f9846d68
ffff8003`f9846c58 ffff8003`f9846d68 : 00000000`00000008 ffff8003`f9846cc0 ffff8f89`f8a5f990 fffff802`b23513f0 : 0xffff8f89`f8a88310
ffff8003`f9846c60 00000000`00000008 : ffff8003`f9846cc0 ffff8f89`f8a5f990 fffff802`b23513f0 ffffe400`8f4c2180 : 0xffff8003`f9846d68
ffff8003`f9846c68 ffff8003`f9846cc0 : ffff8f89`f8a5f990 fffff802`b23513f0 ffffe400`8f4c2180 fffff802`b232b848 : 0x8.
ffff8003`f9846c70 ffff8f89`f8a5f990 : fffff802`b23513f0 ffffe400`8f4c2180 fffff802`b232b848 ffff8f89`f8a5fae0 : 0xffff8003`f9846cc0
ffff8003`f9846c78 fffff802`b23513f0 : ffffe400`8f4c2180 fffff802`b232b848 ffff8f89`f8a5fae0 ffff8003`f9846cf9 : 0xffff8f89`f8a5f990
ffff8003`f9846c80 ffffe400`8f4c2180 : fffff802`b232b848 ffff8f89`f8a5fae0 ffff8003`f9846cf9 ffff8f89`f8a62dd0 : HKKbdFltr+0x13f0
ffff8003`f9846c88 fffff802`b232b848 : ffff8f89`f8a5fae0 ffff8003`f9846cf9 ffff8f89`f8a62dd0 fffff802`b2330258 : 0xffffe400`8f4c2180
ffff8003`f9846c90 fffff802`688bd7aa : 00000000`00000000 ffff8f89`00000010 00000000`00000000 ffffe400`91540d30 : i8042prt!I8042KeyboardIsrDpc+0x1a8
ffff8003`f9846d60 fffff802`688bcfb4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x54a
ffff8003`f98472b0 fffff802`68a2da4e : 00000000`00000000 ffffe400`8f4c2180 ffff8f89`f3ccf040 ffff8f8a`0b9cb080 : nt!KiRetireDpcList+0xfe4
ffff8003`f9847540 00000000`00000000 : ffff8003`f9848000 ffff8003`f9841000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: kbdclass!memcpy+109

MODULE_NAME: kbdclass.

IMAGE_NAME: kbdclass.sys

IMAGE_VERSION: 10.0.23145.1000

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 109.

FAILURE_BUCKET_ID: AV_kbdclass!memcpy

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {dfec7698-3775-c204-13ee-4d0f5bb2791c}

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

Anladığım kadarıyla iki minidump dosyası da aynı sıkıntıyı yazmış ama yine ikisini de paylaşmak istedim.

minidump dosyalarının orijinaline bakmak isteyen hocalarım için.

@Recep Baltaş abi sana zahmet bakabilir misin?
 
Son düzenleme:
Çözüm
Merhabalar Monster cihazınızın bir driverından dolayı bu hatayı alıyorsunuz. Çözümü sayın Plyra başka bir konuda şu şekilde açıklamış. Takip edip işlemleri uygulayın. Sorununuz çözülür. Ya da monster uygulamalarını kaldırın.

Plyra 15 Haziran 2022
Genişletmek için tıkla...
Alıntı yapılan konunun linki : Çözüldü: Monster Abra V17.1 kbdclass.sys mavi ekran hatası
Tarihe göre sırala Puana göre sırala
Merhabalar Monster cihazınızın bir driverından dolayı bu hatayı alıyorsunuz. Çözümü sayın Plyra başka bir konuda şu şekilde açıklamış. Takip edip işlemleri uygulayın. Sorununuz çözülür. Ya da monster uygulamalarını kaldırın.

Plyra 15 Haziran 2022
Genişletmek için tıkla...
Alıntı yapılan konunun linki : Çözüldü: Monster Abra V17.1 kbdclass.sys mavi ekran hatası
 
Artı 0 Eksi
Çözüm

Teşekkürler.

Çözüm olarak işaretlemek için yazıyorum. Forumda diğer benzer konulardan birinde gördüğüm ve aldığım tavsiye üzerine Control Center uygulamasını kaldırdığımdan beri 1 kere bile mavi ekrana düşmedim. İşin özeti Control Center uygulamasını kaldırın, çözülüyor.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
Monster Abra A5 V17.2 laptopta oyun oynarken mavi ekran hatası
Mesaj
3
Görüntüleme
2.015
zeceria
  • Soru
Monster Abra A5 v17.2 mavi ekran hatası
Mesaj
1
Görüntüleme
193
yusuf küçükkk
  • Çözüldü
Çözüldü  Monster Abra A5 v17.2 mavi ekran hatası
Mesaj
6
Görüntüleme
1.200
Emrullah Enes
  • Soru
Monster Abra A5 v17.2 kbdclass.sys mavi ekran hatası
Mesaj
4
Görüntüleme
810
omerbab03030
F
  • Soru
Monster Abra A5 v17.2 0x000000d1 Mavi Ekran Hatası
Mesaj
9
Görüntüleme
902
Teru

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

Toplam: 2 (üye: 0, misafir: 2)
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…