Vanguard mavi ekran hatasına sebep oluyor

Durum
Mesaj gönderimine kapalı.
İşletim sistemi
Windows 10

Berat Poyraz

Femtopat
Katılım
29 Aralık 2020
Mesajlar
10
Daha fazla  
Cinsiyet
Erkek
Herkese merhabalar. Valorant'ı kurdum, Vanguard'ı da. Yeniden başlattım, oyunu açtım, bilgisayarım mavi ekran verdi. Her seferinde böyle yapıyor. Aylarca çözüm bulamadım. Yardımcı olunuz.
 
Bu tarz konular doğru kategoriye açılmazsa işte böyle herkes gelip bir şeyler deyip ortadan çekilirler... Lütfen "Mavi Ekran Hata Analizi" kategorisinde açın şu konuları. Yukarıdaki mesajıma ek olarak Olay Görüntüleyicisi'nden "Sistem" logunu paylaşman iyi olur. Rehber aşağıda mevcut. @Berat Poyraz.

dump dosyası
 
2 aydır bende mavi ekranlar alıyordum çözümü olabilir bak . Sende Valorant oynuyormusun eğer oynuyorsan Vanguard ı sil 1 2 gün kullan PC yi bakalım vercek mi. BIOS unu güncelle, windows güncellemelerini yap. Driverlarını filan güncelle ekran kartını ddu ile kaldırıp en yenisini yükle olmazsa 1 2 önceki sürüm whql filan dene. Komut istemini yönetici olarak çalıştır ve sfc /scannow komutunu girip enter tıkla. Sonra Pc ni yeninden başlat. Bios gir ayarlarını default yap, MSİ anakartlarda F6 tuşuyla olması lazım. Antivürüs programı, afterburner, cpu z vb gibi programlar varsa sil. Bir RAM testi yap Memtest ile, videoları var. HD Tune ile ssd sağlığına bak sonra error test mi ne var test i yap hata çıkacakmı bakalım. Ramlari düzgün taktığından emin ol ve silgiyle uçlarını sil. Oyunlar oynarken arkada çok şey açık kalmasın. Birde sıcaklık değerlerini kontrol et. İşlemci ve ekran kartı kullanımlarına bak. Uğraşamam diyipte yapmamazlık yapma.
 
Artı -2 Eksi
Hocam büyük ihtimalle Vanguard başka bir programla çakıştığından dolayı mavi ekran hatası alıyorsunuz. Genelde RGB tarzı programlarla veya Anakartın kendi uygulamaları ile çakışabiliyor.
 
Artı -2 Eksi
Hocam büyük ihtimalle Vanguard başka bir programla çakıştığından dolayı mavi ekran hatası alıyorsunuz. Genelde RGB tarzı programlarla veya anakartın kendi uygulamaları ile çakışabiliyor.

Dostum birazcık daha açıklayabilir misin?

Bu tarz konular doğru kategoriye açılmazsa işte böyle herkes gelip bir şeyler deyip ortadan çekilirler... Lütfen "mavi ekran hata analizi" kategorisinde açın şu konuları. Yukarıdaki mesajıma ek olarak olay görüntüleyicisi'nden "sistem" logunu paylaşman iyi olur. Rehber aşağıda mevcut. @Berat Poyraz.


@Enes3078 TeamViewer'den yardımcı olabilir misin?
 
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a025e7e908e5a0, Reserved
Arg2: b3b7326e3b89a5e2, Reserved
Arg3: fffff8061c391050, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3187

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 27092

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

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

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

    Key  : WER.OS.Branch
    Value: rs3_release_svc_escrow

    Key  : WER.OS.Timestamp
    Value: 2018-05-02T19:08:00Z

    Key  : WER.OS.Version
    Value: 10.0.16299.431


BUGCHECK_CODE:  109

BUGCHECK_P1: a3a025e7e908e5a0

BUGCHECK_P2: b3b7326e3b89a5e2

BUGCHECK_P3: fffff8061c391050

BUGCHECK_P4: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffa40a`057769c8 00000000`00000000     : 00000000`00000109 a3a025e7`e908e5a0 b3b7326e`3b89a5e2 fffff806`1c391050 : nt!KeBugCheckEx


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff8061c391050-fffff8061c39105d  14 bytes - ndis!NdisMIndicateStatusEx
    [ 48 83 ec 38 48 8b 81 c8:ff 25 00 00 00 00 f6 71 ]
14 errors : !ndis (fffff8061c391050-fffff8061c39105d)

SYMBOL_NAME:  ndis!NdisMIndicateStatusEx+0

MODULE_NAME: ndis

IMAGE_NAME:  ndis.sys

IMAGE_VERSION:  10.0.16299.246

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  0x109_1_ndis!NdisMIndicateStatusEx

OS_VERSION:  10.0.16299.431

BUILDLAB_STR:  rs3_release_svc_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {388ef19e-dfa3-b48f-f0ef-3e9846cb9bed}

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

Ağ sürücünüz güncel değil güncelleyebilir misiniz?
 
dostum birazcık daha açıklayabilir misin
Hocam Valorant ilk çıktığında aylarca sorunsuz oynadım ama bir gün anakartımın RGB renklerini bilgisayardan kontrol etmek için programını indirdim ve indirir indirmez Vanguard kendisini kapatıp bilgisayara mavi ekran verdirdi. Ne zaman sildiysem o zaman düzeldi ve sorunun başkalarında da aynı olduğunu anladım. Belki sende ki sorunda bu olabilir ama başka bir şey olabilme ihtimalide var tabi.
 
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a025e7e908e5a0, Reserved
Arg2: b3b7326e3b89a5e2, Reserved
Arg3: fffff8061c391050, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3187

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 27092

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

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

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

    Key  : WER.OS.Branch
    Value: rs3_release_svc_escrow

    Key  : WER.OS.Timestamp
    Value: 2018-05-02T19:08:00Z

    Key  : WER.OS.Version
    Value: 10.0.16299.431


BUGCHECK_CODE:  109

BUGCHECK_P1: a3a025e7e908e5a0

BUGCHECK_P2: b3b7326e3b89a5e2

BUGCHECK_P3: fffff8061c391050

BUGCHECK_P4: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffa40a`057769c8 00000000`00000000     : 00000000`00000109 a3a025e7`e908e5a0 b3b7326e`3b89a5e2 fffff806`1c391050 : nt!KeBugCheckEx


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff8061c391050-fffff8061c39105d  14 bytes - ndis!NdisMIndicateStatusEx
    [ 48 83 ec 38 48 8b 81 c8:ff 25 00 00 00 00 f6 71 ]
14 errors : !ndis (fffff8061c391050-fffff8061c39105d)

SYMBOL_NAME:  ndis!NdisMIndicateStatusEx+0

MODULE_NAME: ndis

IMAGE_NAME:  ndis.sys

IMAGE_VERSION:  10.0.16299.246

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  0x109_1_ndis!NdisMIndicateStatusEx

OS_VERSION:  10.0.16299.431

BUILDLAB_STR:  rs3_release_svc_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {388ef19e-dfa3-b48f-f0ef-3e9846cb9bed}

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

Ağ sürücünüz güncel değil güncelleyebilir misiniz?
bu kadar mı hocam ?
 
Bilip bilmeyen herkesin konuştuğu bu konuyu çözme vakti gelmiş... Aşağıdaki linkten sürücünüzü indirip kurun. Sorun çözülürse de belirtin. (Bu dump'a göre konuştum. Hala diğer dumplara ihtiyacımız var.)



[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a025e7e908e5a0, Reserved
Arg2: b3b7326e3b89a5e2, Reserved
Arg3: fffff8061c391050, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
2a : Type 4 pool corruption
2b : Modification of a function or .pdata
2c : Image integrity corruption
2d : Processor misconfiguration
2e : Type 5 process list corruption
2f : Process shadow corruption
30 : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6125

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 41822

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

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

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

Key : WER.OS.Branch
Value: rs3_release_svc_escrow

Key : WER.OS.Timestamp
Value: 2018-05-02T19:08:00Z

Key : WER.OS.Version
Value: 10.0.16299.431


BUGCHECK_CODE: 109

BUGCHECK_P1: a3a025e7e908e5a0

BUGCHECK_P2: b3b7326e3b89a5e2

BUGCHECK_P3: fffff8061c391050

BUGCHECK_P4: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa40a`057769c8 00000000`00000000 : 00000000`00000109 a3a025e7`e908e5a0 b3b7326e`3b89a5e2 fffff806`1c391050 : nt!KeBugCheckEx


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
fffff8061c391050-fffff8061c39105d 14 bytes - ndis!NdisMIndicateStatusEx
[ 48 83 ec 38 48 8b 81 c8:ff 25 00 00 00 00 f6 71 ]
14 errors : !ndis (fffff8061c391050-fffff8061c39105d)

SYMBOL_NAME: ndis!NdisMIndicateStatusEx+0

MODULE_NAME: ndis

IMAGE_NAME: ndis.sys

IMAGE_VERSION: 10.0.16299.246

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x109_1_ndis!NdisMIndicateStatusEx

OS_VERSION: 10.0.16299.431

BUILDLAB_STR: rs3_release_svc_escrow

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {388ef19e-dfa3-b48f-f0ef-3e9846cb9bed}

Followup: MachineOwner
---------[/CODE]


Minidump üzerinden bulabiliyorsun. İşte bu yüzden işi bilirkişilere bırakın. 😉
Çok istersen buyur sana sistem modeli: NP270E5E-X01TR
 
Durum
Mesaj gönderimine kapalı.

Geri
Yukarı