Çözüldü Valorant güncellerken mavi ekran

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

LiBeRTuSs

Centipat
Katılım
31 Aralık 2020
Mesajlar
3.072
Makaleler
4
Çözümler
8
Yer
Adana, Türkiye
Valorant'ta yeni güncellemeyi güncellerken mavi ekran hatası aldım. Hiçbir Anti-Virüs yazılımı kullanmıyorum.

Sistem özellikleri:
  • E7500.
  • GT 430 2 GB.
  • 4 GB RAM.
  • 462 GB HDD.


Umarım doğru yapabilmişimdir. İlk defa yapıyorum upload etme işlerini.
 
Son düzenleyen: Moderatör:
Çözüm
Şu an Valorant güncelleme ile sıkıntılı bir hal almış durumda. Sizin de dökümünüzde sorunun kaynağı Vanguard diye belirtiliyor. Size tavsiyem yeni güncelleme yayımlanana kadar Vanguard'ı silmenizdir. Güncelleme sonrası da sorununuz çözülecek bu arada.

Dökümler:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff800b7cae9d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8656

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 47037

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

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

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

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: fffff800b7cae9d0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RiotClientUxRe

DPC_STACK_BASE:  FFFFF80245DAFFB0

STACK_TEXT: 
fffff802`45dae238 fffff802`4466bc4e     : 00000000`0000001e ffffffff`c0000096 fffff800`b7cae9d0 00000000`00000000 : nt!KeBugCheckEx
fffff802`45dae240 fffff802`445e0eed     : fffff802`45dae9b0 00000000`00000000 fffff802`45daf1a8 fffff802`45dae3b0 : nt!KiFatalExceptionHandler+0x22
fffff802`45dae280 fffff802`44563125     : 00000000`00000001 fffff802`44489000 fffff802`45daf101 fffff802`00000000 : nt!RtlpExecuteHandlerForException+0xd
fffff802`45dae2b0 fffff802`445674de     : fffff802`45daf1a8 fffff802`45daeeb0 fffff802`45daf1a8 ffffe001`894ef190 : nt!RtlDispatchException+0x1a5
fffff802`45dae980 fffff802`445e55c2     : ffffe001`00000004 00000000`00000000 00000000`00000000 fffff802`45daf168 : nt!KiDispatchException+0x646
fffff802`45daf070 fffff802`445e3afe     : ffffe001`89303030 00000000`00000000 fffff802`45daf240 ffffe001`89303030 : nt!KiExceptionDispatch+0xc2
fffff802`45daf250 fffff800`b7cae9d0     : ffffe001`860a76c0 00000000`00000000 00000000`00000002 ffffe001`8a1a2c80 : nt!KiGeneralProtectionFault+0xfe
fffff802`45daf3e0 ffffe001`860a76c0     : 00000000`00000000 00000000`00000002 ffffe001`8a1a2c80 00000000`00000000 : vgk+0x4f9d0
fffff802`45daf3e8 00000000`00000000     : 00000000`00000002 ffffe001`8a1a2c80 00000000`00000000 ffffe001`88ee1b70 : 0xffffe001`860a76c0


SYMBOL_NAME:  vgk+4f9d0

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  4f9d0

FAILURE_BUCKET_ID:  0x1E_c0000096_vgk!unknown_function

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {a12159ce-3331-0cde-43dd-ad042f045e26}

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

Enes3078

Gigapat
Sosyal Tayfı
Katılım
28 Nisan 2020
Mesajlar
11.672
Makaleler
7
Çözümler
282
Yer
Malatya
Şu an Valorant güncelleme ile sıkıntılı bir hal almış durumda. Sizin de dökümünüzde sorunun kaynağı Vanguard diye belirtiliyor. Size tavsiyem yeni güncelleme yayımlanana kadar Vanguard'ı silmenizdir. Güncelleme sonrası da sorununuz çözülecek bu arada.

Dökümler:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff800b7cae9d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 8656

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 47037

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

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

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

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: fffff800b7cae9d0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RiotClientUxRe

DPC_STACK_BASE:  FFFFF80245DAFFB0

STACK_TEXT: 
fffff802`45dae238 fffff802`4466bc4e     : 00000000`0000001e ffffffff`c0000096 fffff800`b7cae9d0 00000000`00000000 : nt!KeBugCheckEx
fffff802`45dae240 fffff802`445e0eed     : fffff802`45dae9b0 00000000`00000000 fffff802`45daf1a8 fffff802`45dae3b0 : nt!KiFatalExceptionHandler+0x22
fffff802`45dae280 fffff802`44563125     : 00000000`00000001 fffff802`44489000 fffff802`45daf101 fffff802`00000000 : nt!RtlpExecuteHandlerForException+0xd
fffff802`45dae2b0 fffff802`445674de     : fffff802`45daf1a8 fffff802`45daeeb0 fffff802`45daf1a8 ffffe001`894ef190 : nt!RtlDispatchException+0x1a5
fffff802`45dae980 fffff802`445e55c2     : ffffe001`00000004 00000000`00000000 00000000`00000000 fffff802`45daf168 : nt!KiDispatchException+0x646
fffff802`45daf070 fffff802`445e3afe     : ffffe001`89303030 00000000`00000000 fffff802`45daf240 ffffe001`89303030 : nt!KiExceptionDispatch+0xc2
fffff802`45daf250 fffff800`b7cae9d0     : ffffe001`860a76c0 00000000`00000000 00000000`00000002 ffffe001`8a1a2c80 : nt!KiGeneralProtectionFault+0xfe
fffff802`45daf3e0 ffffe001`860a76c0     : 00000000`00000000 00000000`00000002 ffffe001`8a1a2c80 00000000`00000000 : vgk+0x4f9d0
fffff802`45daf3e8 00000000`00000000     : 00000000`00000002 ffffe001`8a1a2c80 00000000`00000000 ffffe001`88ee1b70 : 0xffffe001`860a76c0


SYMBOL_NAME:  vgk+4f9d0

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  4f9d0

FAILURE_BUCKET_ID:  0x1E_c0000096_vgk!unknown_function

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {a12159ce-3331-0cde-43dd-ad042f045e26}

Followup:     MachineOwner
---------
 
Çözüm
KS
LiBeRTuSs

LiBeRTuSs

Centipat
Katılım
31 Aralık 2020
Mesajlar
3.072
Makaleler
4
Çözümler
8
Yer
Adana, Türkiye
Şu an Valorant güncelleme ile sıkıntılı bir hal almış durumda. Sizin de dökümünüzde sorunun kaynağı Vanguard diye belirtiliyor. Size tavsiyem yeni güncelleme yayımlanana kadar Vanguard'ı silmenizdir. Güncelleme sonrası da sorununuz çözülecek bu arada.

Dökümler:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints.
the driver/function that caused the problem. Always note this address.
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled.
Arg2: fffff800b7cae9d0, The address that the exception occurred at.
Arg3: 0000000000000000, Parameter 0 of the exception.
Arg4: 0000000000000000, Parameter 1 of the exception.

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

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 8656.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 47037.

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

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

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

 Key : WER.OS.Branch
 Value: winblue_r4.

 Key : WER.OS.Timestamp
 Value: 2014-10-28T15:00:00Z

 Key : WER.OS.Version
 Value: 8.1.9600.17415

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000096.

BUGCHECK_P2: fffff800b7cae9d0.

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RiotClientUxRe.

DPC_STACK_BASE: FFFFF80245DAFFB0.

STACK_TEXT:
fffff802`45dae238 fffff802`4466bc4e : 00000000`0000001e ffffffff`c0000096 fffff800`b7cae9d0 00000000`00000000 : nt!KeBugCheckEx
fffff802`45dae240 fffff802`445e0eed : fffff802`45dae9b0 00000000`00000000 fffff802`45daf1a8 fffff802`45dae3b0 : nt!KiFatalExceptionHandler+0x22
fffff802`45dae280 fffff802`44563125 : 00000000`00000001 fffff802`44489000 fffff802`45daf101 fffff802`00000000 : nt!RtlpExecuteHandlerForException+0xd
fffff802`45dae2b0 fffff802`445674de : fffff802`45daf1a8 fffff802`45daeeb0 fffff802`45daf1a8 ffffe001`894ef190 : nt!RtlDispatchException+0x1a5
fffff802`45dae980 fffff802`445e55c2 : ffffe001`00000004 00000000`00000000 00000000`00000000 fffff802`45daf168 : nt!KiDispatchException+0x646
fffff802`45daf070 fffff802`445e3afe : ffffe001`89303030 00000000`00000000 fffff802`45daf240 ffffe001`89303030 : nt!KiExceptionDispatch+0xc2
fffff802`45daf250 fffff800`b7cae9d0 : ffffe001`860a76c0 00000000`00000000 00000000`00000002 ffffe001`8a1a2c80 : nt!KiGeneralProtectionFault+0xfe
fffff802`45daf3e0 ffffe001`860a76c0 : 00000000`00000000 00000000`00000002 ffffe001`8a1a2c80 00000000`00000000 : vgk+0x4f9d0
fffff802`45daf3e8 00000000`00000000 : 00000000`00000002 ffffe001`8a1a2c80 00000000`00000000 ffffe001`88ee1b70 : 0xffffe001`860a76c0

SYMBOL_NAME: vgk+4f9d0

MODULE_NAME: vgk.

IMAGE_NAME: vgk.sys

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 4f9d0.

FAILURE_BUCKET_ID: 0x1E_c0000096_vgk!unknown_function

OS_VERSION: 8.1.9600.17415

BUILDLAB_STR: winblue_r4.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 8.1

FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}

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

Hocam, Vanguard'ı sildim. Normal bir şekilde şu an güncelleniyor. Vanguard'ı tekrar yüklüyor. Tekrar mavi ekran verir mi yoksa, normal bir şekilde oynayabilecek miyim? Arkadaşlarıma sordum onlarda böyle bir şey olmamış. Ben ticket attım haberleri olsun diye zaten.
 

Enes3078

Gigapat
Sosyal Tayfı
Katılım
28 Nisan 2020
Mesajlar
11.672
Makaleler
7
Çözümler
282
Yer
Malatya
Arkadaşlarınız 00:00'da yayımlanan güncelleme ile oynamadılarsa sorun yaşamamaları muhtemel. Vanguard'ın ise sorun çıkarması alışıldık bir durum artık. Bazılarına güncelleme gelmiş ve güncellemeyi yaparak sorunu çözmüşler. Siz de güncellemeyi bekleyin derim. Bu arada kaldırıp kurmak bu defa işe yaramıyormuş. Yani sistem tekrar mavi ekran verebilir, bilginize.

İşin ilginç yanı Valorant'tan da henüz bir haber yok 🤔
 
KS
LiBeRTuSs

LiBeRTuSs

Centipat
Katılım
31 Aralık 2020
Mesajlar
3.072
Makaleler
4
Çözümler
8
Yer
Adana, Türkiye
Arkadaşlarınız 00:00'da yayımlanan güncelleme ile oynamadılarsa sorun yaşamamaları muhtemel. Vanguard'ın ise sorun çıkarması alışıldık bir durum artık. Bazılarına güncelleme gelmiş ve güncellemeyi yaparak sorunu çözmüşler. Siz de güncellemeyi bekleyin derim. Bu arada kaldırıp kurmak bu defa işe yaramıyormuş. Yani sistem tekrar mavi ekran verebilir, bilginize.

İşin ilginç yanı Valorant'tan da henüz bir haber yok 🤔

Tekrar mavi ekran hatası aldım hocam. Güncelleme normal bir şekilde bitmişti. Oradan yeniden başlat yazısı geldi ve yeniden başlattım. Sistem açıldı ve Valorant'a tıkladım. Ondan sonra tekrar mavi ekran verdi. Yani kısacası bu kısımdayken verdi:

VALORANT.png


Gene Vanguard ile mi alakalı?

 

Enes3078

Gigapat
Sosyal Tayfı
Katılım
28 Nisan 2020
Mesajlar
11.672
Makaleler
7
Çözümler
282
Yer
Malatya
Aslında son bir şey var. COMODO Firewall yazılımını kaldırıp tekrar deneyin. Yine olursa mecburen güncelleme bekleyeceksiniz.

Dökümler:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8014d4e49d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6983

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 26178

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

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

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

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: fffff8014d4e49d0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffd001`7bfb5fe8 fffff803`7186fc4e     : 00000000`0000001e ffffffff`c0000096 fffff801`4d4e49d0 00000000`00000000 : nt!KeBugCheckEx
ffffd001`7bfb5ff0 fffff803`717e4eed     : ffffd001`7bfb6760 00000000`00000000 ffffd001`7bfb6f58 ffffd001`7bfb6160 : nt!KiFatalExceptionHandler+0x22
ffffd001`7bfb6030 fffff803`71767125     : 00000000`00000001 fffff803`7168d000 ffffd001`7bfb6f00 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd
ffffd001`7bfb6060 fffff803`7176b4de     : ffffd001`7bfb6f58 ffffd001`7bfb6c60 ffffd001`7bfb6f58 ffffe000`956ec9c0 : nt!RtlDispatchException+0x1a5
ffffd001`7bfb6730 fffff803`717e95c2     : 00000000`0015f400 00000001`00000000 00000000`00000000 ffffd001`7bfb6f18 : nt!KiDispatchException+0x646
ffffd001`7bfb6e20 fffff803`717e7afe     : 00000000`00000010 00000000`00000002 ffffe000`96864000 fffff803`716c4740 : nt!KiExceptionDispatch+0xc2
ffffd001`7bfb7000 fffff801`4d4e49d0     : ffffd001`7bf8e180 00000000`00000002 00000000`00000002 ffffe000`96701e18 : nt!KiGeneralProtectionFault+0xfe
ffffd001`7bfb7190 ffffd001`7bf8e180     : 00000000`00000002 00000000`00000002 ffffe000`96701e18 00000000`00000001 : vgk+0x4f9d0
ffffd001`7bfb7198 00000000`00000002     : 00000000`00000002 ffffe000`96701e18 00000000`00000001 00000000`00000000 : 0xffffd001`7bf8e180
ffffd001`7bfb71a0 00000000`00000002     : ffffe000`96701e18 00000000`00000001 00000000`00000000 00000000`00000001 : 0x2
ffffd001`7bfb71a8 ffffe000`96701e18     : 00000000`00000001 00000000`00000000 00000000`00000001 fffff803`716c5da5 : 0x2
ffffd001`7bfb71b0 00000000`00000001     : 00000000`00000000 00000000`00000001 fffff803`716c5da5 ffffe000`955d9420 : 0xffffe000`96701e18
ffffd001`7bfb71b8 00000000`00000000     : 00000000`00000001 fffff803`716c5da5 ffffe000`955d9420 fffff801`4b82ea43 : 0x1


SYMBOL_NAME:  vgk+4f9d0

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  4f9d0

FAILURE_BUCKET_ID:  0x1E_c0000096_vgk!unknown_function

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {a12159ce-3331-0cde-43dd-ad042f045e26}

Followup:     MachineOwner
---------
 
KS
LiBeRTuSs

LiBeRTuSs

Centipat
Katılım
31 Aralık 2020
Mesajlar
3.072
Makaleler
4
Çözümler
8
Yer
Adana, Türkiye
Aslında son bir şey var.comodo firewall yazılımını kaldırıp tekrar deneyin. Yine olursa mecburen güncelleme bekleyeceksiniz.

Dökümler:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints.
the driver/function that caused the problem. Always note this address.
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled.
Arg2: fffff8014d4e49d0, The address that the exception occurred at.
Arg3: 0000000000000000, Parameter 0 of the exception.
Arg4: 0000000000000000, Parameter 1 of the exception.

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

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 6983.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 26178.

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

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

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

 Key : WER.OS.Branch
 Value: winblue_r4.

 Key : WER.OS.Timestamp
 Value: 2014-10-28T15:00:00Z

 Key : WER.OS.Version
 Value: 8.1.9600.17415

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000096.

BUGCHECK_P2: fffff8014d4e49d0.

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

STACK_TEXT:
ffffd001`7bfb5fe8 fffff803`7186fc4e : 00000000`0000001e ffffffff`c0000096 fffff801`4d4e49d0 00000000`00000000 : nt!KeBugCheckEx
ffffd001`7bfb5ff0 fffff803`717e4eed : ffffd001`7bfb6760 00000000`00000000 ffffd001`7bfb6f58 ffffd001`7bfb6160 : nt!KiFatalExceptionHandler+0x22
ffffd001`7bfb6030 fffff803`71767125 : 00000000`00000001 fffff803`7168d000 ffffd001`7bfb6f00 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd
ffffd001`7bfb6060 fffff803`7176b4de : ffffd001`7bfb6f58 ffffd001`7bfb6c60 ffffd001`7bfb6f58 ffffe000`956ec9c0 : nt!RtlDispatchException+0x1a5
ffffd001`7bfb6730 fffff803`717e95c2 : 00000000`0015f400 00000001`00000000 00000000`00000000 ffffd001`7bfb6f18 : nt!KiDispatchException+0x646
ffffd001`7bfb6e20 fffff803`717e7afe : 00000000`00000010 00000000`00000002 ffffe000`96864000 fffff803`716c4740 : nt!KiExceptionDispatch+0xc2
ffffd001`7bfb7000 fffff801`4d4e49d0 : ffffd001`7bf8e180 00000000`00000002 00000000`00000002 ffffe000`96701e18 : nt!KiGeneralProtectionFault+0xfe
ffffd001`7bfb7190 ffffd001`7bf8e180 : 00000000`00000002 00000000`00000002 ffffe000`96701e18 00000000`00000001 : vgk+0x4f9d0
ffffd001`7bfb7198 00000000`00000002 : 00000000`00000002 ffffe000`96701e18 00000000`00000001 00000000`00000000 : 0xffffd001`7bf8e180
ffffd001`7bfb71a0 00000000`00000002 : ffffe000`96701e18 00000000`00000001 00000000`00000000 00000000`00000001 : 0x2.
ffffd001`7bfb71a8 ffffe000`96701e18 : 00000000`00000001 00000000`00000000 00000000`00000001 fffff803`716c5da5 : 0x2.
ffffd001`7bfb71b0 00000000`00000001 : 00000000`00000000 00000000`00000001 fffff803`716c5da5 ffffe000`955d9420 : 0xffffe000`96701e18
ffffd001`7bfb71b8 00000000`00000000 : 00000000`00000001 fffff803`716c5da5 ffffe000`955d9420 fffff801`4b82ea43 : 0x1.

SYMBOL_NAME: vgk+4f9d0

MODULE_NAME: vgk.

IMAGE_NAME: vgk.sys

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 4f9d0.

FAILURE_BUCKET_ID: 0x1E_c0000096_vgk!unknown_function

OS_VERSION: 8.1.9600.17415

BUILDLAB_STR: winblue_r4.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 8.1

FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}

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

Öyle bir yazılım yok hocam. Kalıntısı falan mı var acaba nereden gördünüz? Daha önce yüklemiştim sanırım Comodo.
 

Enes3078

Gigapat
Sosyal Tayfı
Katılım
28 Nisan 2020
Mesajlar
11.672
Makaleler
7
Çözümler
282
Yer
Malatya
Sistemde Firewall yazılımı ile alakalı kalıntısı kalmışsa mümkün. Yine de bir şey olacağını sanmam. Deneyin bakalım yeni güncellemeyi. Ben hala ümitliyim bugün çıkaracaklarından :)
 
KS
LiBeRTuSs

LiBeRTuSs

Centipat
Katılım
31 Aralık 2020
Mesajlar
3.072
Makaleler
4
Çözümler
8
Yer
Adana, Türkiye
Sistemde firewall yazılımı ile alakalı kalıntısı kalmışsa mümkün. Yine de bir şey olacağını sanmam. Deneyin bakalım yeni güncellemeyi. Ben hala ümitliyim bugün çıkaracaklarından :)

Windows 8.1 güvenlik duvarı var hocam sadece. Acaba Comodo Firewall'ı geri yükleyip silersem, kalıntısı gider mi? Kalıntısı olduğunu pek sanmıyorum.
@Enes3078 hocam, son olarak durum vereyim, sorun dediğiniz gibi Vanguard'da. Az önce hizmetlerden Vanguard açtım ve açtığım gibi mavi ekran verdi. Güncellemeyi bekleyeceğim. Ek olarak Kaspersky'ın güvenlik duvarı var şu an. Sonuç aynı yani.
 
Son düzenleme:
Yukarı