Çözüldü Valorant'ta APC_INDEX_MISMATCH mavi ekran hatası

Kuşçu · 19 Mart 2021

İyi günler. Sistemim Windows 8'di ama bazı problemlerden ötürü Windows 10'a formatladım. Şimdi ben bu Valorant'ı açınca mavi ekran alıyorum. Dump dosyalarının linkini aşağıya bırakıyorum.

Minidump (11)

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

Bora Dere · 19 Mart 2021

Gördüğüm kadarıyla sistemde Comodo AV yüklü. Bunu kaldırın. Şu anda genel bir problem var gibi görünüyor. Yakında düzeltirler diye düşünüyorum.

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: 00007ffd4ea0d694, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffff8f0038284cc0, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3936

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 20016

    Key  : Analysis.Init.CPU.mSec
    Value: 671

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

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

    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


BUGCHECK_CODE:  1

BUGCHECK_P1: 7ffd4ea0d694

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffff8f0038284cc0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

STACK_TEXT: 
ffff8f00`38284a88 fffff802`24c07169     : 00000000`00000001 00007ffd`4ea0d694 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffff8f00`38284a90 fffff802`24c07033     : ffff980b`407d7040 fffff802`24da3ce0 00000000`00000000 00000000`c0000034 : nt!KiBugCheckDispatch+0x69
ffff8f00`38284bd0 00007ffd`4ea0d694     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
000000ed`f1bfcc48 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`4ea0d694


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.631

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_c8_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5a6c51bb-69b1-ab30-119a-d55aa3c0e3eb}

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: 00007ff96fc2d694, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffffd88789e9cc0, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4890

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 19128

    Key  : Analysis.Init.CPU.mSec
    Value: 733

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

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

    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


BUGCHECK_CODE:  1

BUGCHECK_P1: 7ff96fc2d694

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffffd88789e9cc0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

STACK_TEXT: 
fffffd88`789e9a88 fffff807`31a07169     : 00000000`00000001 00007ff9`6fc2d694 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffffd88`789e9a90 fffff807`31a07033     : ffffa083`66e60640 fffff807`31ba3ce0 00000000`00000000 00000000`c0000034 : nt!KiBugCheckDispatch+0x69
fffffd88`789e9bd0 00007ff9`6fc2d694     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
000000ed`6bbfd788 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`6fc2d694


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.631

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_c8_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5a6c51bb-69b1-ab30-119a-d55aa3c0e3eb}

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: 00007ffc98aed694, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffbd0db9995cc0, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4171

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 22277

    Key  : Analysis.Init.CPU.mSec
    Value: 702

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

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

    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


BUGCHECK_CODE:  1

BUGCHECK_P1: 7ffc98aed694

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffffbd0db9995cc0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

STACK_TEXT: 
ffffbd0d`b9995a88 fffff804`23207169     : 00000000`00000001 00007ffc`98aed694 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffbd0d`b9995a90 fffff804`23207033     : ffffa88d`4628c040 fffff804`233a3ce0 00000000`00000000 00000000`c0000034 : nt!KiBugCheckDispatch+0x69
ffffbd0d`b9995bd0 00007ffc`98aed694     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000037`b414ce98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`98aed694


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.631

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_c8_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5a6c51bb-69b1-ab30-119a-d55aa3c0e3eb}

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

KojiroHyuga04 · 19 Mart 2021

Bora Dere dedi:

Gördüğüm kadarıyla sistemde Comodo AV yüklü. Bunu kaldırın. Şu anda genel bir problem var gibi görünüyor. Yakında düzeltirler diye düşünüyorum.

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: 00007ffd4ea0d694, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffff8f0038284cc0, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3936

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 20016

    Key  : Analysis.Init.CPU.mSec
    Value: 671

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

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

    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


BUGCHECK_CODE:  1

BUGCHECK_P1: 7ffd4ea0d694

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffff8f0038284cc0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

STACK_TEXT:
ffff8f00`38284a88 fffff802`24c07169     : 00000000`00000001 00007ffd`4ea0d694 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffff8f00`38284a90 fffff802`24c07033     : ffff980b`407d7040 fffff802`24da3ce0 00000000`00000000 00000000`c0000034 : nt!KiBugCheckDispatch+0x69
ffff8f00`38284bd0 00007ffd`4ea0d694     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
000000ed`f1bfcc48 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`4ea0d694


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.631

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_c8_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5a6c51bb-69b1-ab30-119a-d55aa3c0e3eb}

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: 00007ff96fc2d694, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffffd88789e9cc0, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4890

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 19128

    Key  : Analysis.Init.CPU.mSec
    Value: 733

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

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

    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


BUGCHECK_CODE:  1

BUGCHECK_P1: 7ff96fc2d694

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: fffffd88789e9cc0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

STACK_TEXT:
fffffd88`789e9a88 fffff807`31a07169     : 00000000`00000001 00007ff9`6fc2d694 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffffd88`789e9a90 fffff807`31a07033     : ffffa083`66e60640 fffff807`31ba3ce0 00000000`00000000 00000000`c0000034 : nt!KiBugCheckDispatch+0x69
fffffd88`789e9bd0 00007ff9`6fc2d694     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
000000ed`6bbfd788 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`6fc2d694


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.631

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_c8_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5a6c51bb-69b1-ab30-119a-d55aa3c0e3eb}

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: 00007ffc98aed694, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffbd0db9995cc0, Call type (0 - system call, 1 - worker routine)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4171

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 22277

    Key  : Analysis.Init.CPU.mSec
    Value: 702

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

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

    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


BUGCHECK_CODE:  1

BUGCHECK_P1: 7ffc98aed694

BUGCHECK_P2: 0

BUGCHECK_P3: ffff

BUGCHECK_P4: ffffbd0db9995cc0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

STACK_TEXT:
ffffbd0d`b9995a88 fffff804`23207169     : 00000000`00000001 00007ffc`98aed694 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
ffffbd0d`b9995a90 fffff804`23207033     : ffffa88d`4628c040 fffff804`233a3ce0 00000000`00000000 00000000`c0000034 : nt!KiBugCheckDispatch+0x69
ffffbd0d`b9995bd0 00007ffc`98aed694     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
00000037`b414ce98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`98aed694


SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.631

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fe

FAILURE_BUCKET_ID:  0x1_SysCallNum_c8_nt!KiSystemServiceExitPico

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5a6c51bb-69b1-ab30-119a-d55aa3c0e3eb}

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

Hocam çok hızlısınız maşallah.
İnceleyecektim siz benden önce davrandınız.

Kuşçu · 19 Mart 2021

Hocam Comodo'yu kaldırdım ancak sorun devam ediyor. Bir de hocam, bu minidumpla sorunun ekran kartında olup olmadıgı da goruluyor mu? Sorun ekran kartında değilse bilgilendirebilir misiniz?

Bora Dere · 19 Mart 2021

Detaylı incelememiştim. AV'ler (özellikle Comodo) ile ilgili sorun çıkardığını görünce sadece ona bakmıştım.

Şimdi detaylı inceledim. Ekran kartıyla ilgili sorun görünüyor bu arada. Şüphelenmenizin özel bir sebebi var mı? Bir ayar falan yaptıysanız geri alın. Sürücüsünü DDU ile kaldırıp güncellemeyi deneyebilirsiniz. BIOS'ta disk ile ilgili bir ayar yaptınız mı?

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...

www.technopat.net

Kuşçu · 19 Mart 2021

Bora Dere dedi:
Detaylı incelememiştim. AV'ler (özellikle Comodo) ile ilgili sorun çıkardığını görünce sadece ona bakmıştım.

Ekran kartıyla ilgili sorun görünüyor bu arada. Şüphelenmenizin özel bir sebebi var mı? Bir ayar falan yaptıysanız geri alın. Sürücüsünü DDU ile kaldırıp güncellemeyi deneyebilirsiniz. BIOS'ta disk ile ilgili bir ayar yaptınız mı?

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...

www.technopat.net

Disk ile ilgili ayarım şu oldu; iki harddisk vardı, birini öne çıkardım. Tek yaptığım buydu.

Ekran kartından şüphelenme nedenim şuydu; Windows 10'u kurdum, Windows hemen bir eski GT710 sürücüsü attı ve bu sürücü varken farede takılmalar oluyordu. Sonra ben de GeForce Experience'tan son sürümü kurdum. Fare takılmaları geçti ancak oyunun kapanmasıyla ilgili olabileceğini düşündüm.

Bora Dere · 19 Mart 2021

İlgili olabilir. Sürücü kaldırıp kurma dediğim gibi çözecektir büyük ihtimalle. Yalnız ekran kartınızın birden fazla versiyonu var. GPU-Z indirip ekran görüntüsü paylaşır mısınız? Ona göre sürücü vereceğim.

GPU-Z

GPU-Z, ekran kartı ve grafik işlemciniz hakkında hayati bilgiler sağlamak için tasarlanmış hafif bir yardımcı sistem programıdır. BIOS sürümünü, API sürümlerini ve birçok teknik detayı edinmenize yarar.

www.technopat.net

Kuşçu · 19 Mart 2021

Bora Dere dedi:
İlgili olabilir. Sürücü kaldırıp kurma dediğim gibi çözecektir büyük ihtimalle. Yalnız ekran kartınızın birden fazla versiyonu var. GPU-Z indirip ekran görüntüsü paylaşır mısınız? Ona göre sürücü vereceğim.

GPU-Z

GPU-Z, ekran kartı ve grafik işlemciniz hakkında hayati bilgiler sağlamak için tasarlanmış hafif bir yardımcı sistem programıdır. BIOS sürümünü, API sürümlerini ve birçok teknik detayı edinmenize yarar.

www.technopat.net

yapımmı ddu yu

Bora Dere · 19 Mart 2021

Süper. Kepler mimarili imiş. Son sürücüyü destekler. Fakat sizdeki de son sürümmüş. Belki kurulumda bir sıkıntı olmuş olabilir. DDU ile kaldırıp benim attığımı kurmanızda fayda var.

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

www.nvidia.com

Kuşçu · 19 Mart 2021

Tamam hocam sağ olun.

Bora Dere dedi:
Süper. Kepler mimarili imiş. Son sürücüyü destekler. Fakat sizdeki de son sürümmüş. Belki kurulumda bir sıkıntı olmuş olabilir. DDU ile kaldırıp benim attığımı kurmanızda fayda var.

Driver Details | NVIDIA

Download the <dd~LanguageName> <dd~Name> for <dd~OSName> systems. Released <dd~ReleaseDateTime>

www.nvidia.com

Hocam çok sağ olun. Fare donmuyor, mavi ekran yok, her şey tamam. Allah razı olsun.

Çözüldü Valorant'ta APC_INDEX_MISMATCH mavi ekran hatası

Ayrıntılı düzenleme

Kuşçu

Hectopat

Minidump (11)

Bora Dere

Driver Details | NVIDIA

Bora Dere

Moderasyon Ekibi Üyesi

KojiroHyuga04

Moderasyon Ekibi Üyesi

Kuşçu

Hectopat

Bora Dere

Moderasyon Ekibi Üyesi

Rehber: DDU ile Sürücü Kaldırma Rehberi

Kuşçu

Hectopat

Rehber: DDU ile Sürücü Kaldırma Rehberi

Bora Dere

Moderasyon Ekibi Üyesi

GPU-Z

Kuşçu

Hectopat

GPU-Z

Bora Dere

Moderasyon Ekibi Üyesi

Driver Details | NVIDIA

Kuşçu

Hectopat

Driver Details | NVIDIA

Benzer konular

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz