"KMODE_EXCEPTION_NOT_HANDLED" mavi ekran hatası

İşletim sistemi
Windows 10

OKY4Y

Zeptopat
Katılım
14 Haziran 2025
Mesajlar
3
Daha fazla  
Cinsiyet
Erkek
Minidump Rapor Linki
https://drive.google.com/file/d/1Qx8kgW9cNG2q75BrEquXy2l5DS_6KNBQ/view?usp=drive_link
RAM
Corsair Vengeance LPX DDR4 3200 MHZ 8 GB Ram
SSD veya HDD modeli
MLD M300 1TB
Ekran kartı
4060 Tİ
Anakart
MSI B760-P WİFİ DDR4
İşlemci
İ9 14900 KF
Merhaba. Sürekli mavi ekran veriyor. PC 3 gün önce bir abiden satın aldığımda Windows 11 yüklüydü onda hata veriyordu. Windows 10 kurduk formatlayıp bunda da aynı hatayı yapıyor. Kafayı yedirtecek dereceye geldi yardım ederseniz memnun olurum.
Not : 32 GB Ram vardı bilerek test için çıkarıp tek tek denedim hangisi bozuk acaba diye ama yinede aynı hataları hepsinde aldım . Şu anda sadece 8 gb ram taktım bilerek testi kolay olsun diye Ayrıca hatayı valorant oyununu açmaya çalıştığımda veriyor .Normal kullanımda çok nadir yapıyor .
Minidump:
 
Son düzenleme:
Alınan hataların hepsi Vanguard kaynaklı olmuş anladığım kadarıyla.

Kod:
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8048a870775, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2515

    Key  : Analysis.Elapsed.mSec
    Value: 2647

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Failure.Bucket
    Value: AV_R_vgk!unknown_function

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8048a870775

    Key  : Failure.Exception.IP.Module
    Value: vgk

    Key  : Failure.Exception.IP.Offset
    Value: 0x1140775

    Key  : Failure.Hash
    Value: {b93bf423-3535-1218-531c-8c08e172e67f}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8048a870775

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB:  061425-5656-01.dmp

FAULTING_THREAD:  ffffd308ab120040

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff80326afb390: 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
 ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SkypeApp.exe

STACK_TEXT:
ffff8108`f9af9998 fffff803`2629755b     : 00000000`0000001e ffffffff`c0000005 fffff804`8a870775 00000000`00000000 : nt!KeBugCheckEx
ffff8108`f9af99a0 fffff803`262128ec     : 00002843`00000022 884bbbfc`57c54109 00034380`7333c010 8b041404`0040108c : nt!KiDispatchException+0x14beeb
ffff8108`f9afa060 fffff803`2620dcef     : 7bf6ac47`bc543aff 00000000`00000000 00c1eb4a`a4bccd50 43248404`07623088 : nt!KiExceptionDispatch+0x12c
ffff8108`f9afa240 fffff804`8a870775     : 00000001`ffffffff fffffff6`00000002 ffff8108`f9afa5b0 ffff8108`f9afa40c : nt!KiGeneralProtectionFault+0x32f
ffff8108`f9afa3d0 00000001`ffffffff     : fffffff6`00000002 ffff8108`f9afa5b0 ffff8108`f9afa40c 00000000`00000000 : vgk+0x1140775
ffff8108`f9afa3d8 fffffff6`00000002     : ffff8108`f9afa5b0 ffff8108`f9afa40c 00000000`00000000 00180410`018302ff : 0x00000001`ffffffff
ffff8108`f9afa3e0 ffff8108`f9afa5b0     : ffff8108`f9afa40c 00000000`00000000 00180410`018302ff 00000002`00000048 : 0xfffffff6`00000002
ffff8108`f9afa3e8 ffff8108`f9afa40c     : 00000000`00000000 00180410`018302ff 00000002`00000048 ffff8108`f9afa610 : 0xffff8108`f9afa5b0
ffff8108`f9afa3f0 00000000`00000000     : 00180410`018302ff 00000002`00000048 ffff8108`f9afa610 00000000`00000073 : 0xffff8108`f9afa40c


SYMBOL_NAME:  vgk+1140775

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND: .process /r /p 0xffffd30896edd080; .thread 0xffffd308ab120040 ; kb

BUCKET_ID_FUNC_OFFSET:  1140775

FAILURE_BUCKET_ID:  AV_R_vgk!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b93bf423-3535-1218-531c-8c08e172e67f}

Vanguard yazılımını kaldırın. Sonra da yeniden yükleyin. Ardından sistemi gözetleyip haber verin.
 

Teşekkürler deneyip tekrar dönüyorum.
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…