Sistem mavi ekran veriyor ve kilitleniyor

İşletim sistemi
Windows 11

Chipset güncellendi ama o ara ekran gitti geldi ve bu uyarı çıktı.




Merhaba dediklerinizi yaptım veaire yaptım restart attım PC'ye yine mavi ekran yedim mavi ekranda DRIVER_VERIFIER_DETECTED_VIOLATION diye bir şey yazdı sonra geri yükle ekranı çıktı geri yükle dedim sistem onarılmanı deneniyor falan dedi en sonunda açıldı ne oldu şimdi anlamadım vallahi.

ek olarak tekrar mini dump dosyamı paylaşıyorum.

For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`3ba2efa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb80b`40606ce0=00000000000000c4
0: kd> !analyze -v
*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff8069b29243a, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 0000000000000000, Pool Tag (if provided).

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 953

Key : Analysis.Elapsed.mSec
Value: 1477

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0xc4

Key : Bugcheck.Code.TargetModel
Value: 0xc4

Key : Failure.Bucket
Value: 0xc4_2000_VRF_vgk!unknown_function

Key : Failure.Hash
Value: {4cf836d1-3aaa-e980-1de0-37871feda2d3}

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: c4

BUGCHECK_P1: 2000

BUGCHECK_P2: fffff8069b29243a

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 111624-14031-01.dmp

FAULTING_THREAD: ffffa80ceb571140

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffb80b`40606cd8 fffff806`3c0e33c1 : 00000000`000000c4 00000000`00002000 fffff806`9b29243a 00000000`00000000 : nt!KeBugCheckEx
ffffb80b`40606ce0 fffff806`3bbe7412 : fffff806`3c227cb0 00000000`00002000 fffff806`9b29243a 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x14d
ffffb80b`40606d80 fffff806`3c0d9970 : 00000000`00000000 fffff806`3c227cb0 fffff806`9b29243a 28b43acc`63e56785 : nt!VfReportIssueWithOptions+0x102
ffffb80b`40606dd0 fffff806`3c0d605e : 00000000`00000000 00000000`656e6f4e 00000000`00000000 00000000`00000054 : nt!VfCheckPoolType+0x90
ffffb80b`40606e10 fffff806`9b29243a : ffffa80c`f32f1950 ffffb80b`40607200 ffffa80c`eb4ed9e0 00000000`00000056 : nt!VerifierExAllocatePoolWithTag+0x9e
ffffb80b`40606e70 ffffa80c`f32f1950 : ffffb80b`40607200 ffffa80c`eb4ed9e0 00000000`00000056 ffffb80b`406074a0 : vgk+0xa243a
ffffb80b`40606e78 ffffb80b`40607200 : ffffa80c`eb4ed9e0 00000000`00000056 ffffb80b`406074a0 fffff806`9b3175cb : 0xffffa80c`f32f1950
ffffb80b`40606e80 ffffa80c`eb4ed9e0 : 00000000`00000056 ffffb80b`406074a0 fffff806`9b3175cb ffffa80c`f32f1950 : 0xffffb80b`40607200
ffffb80b`40606e88 00000000`00000056 : ffffb80b`406074a0 fffff806`9b3175cb ffffa80c`f32f1950 00000001`67727453 : 0xffffa80c`eb4ed9e0
ffffb80b`40606e90 ffffb80b`406074a0 : fffff806`9b3175cb ffffa80c`f32f1950 00000001`67727453 00000000`00000000 : 0x56
ffffb80b`40606e98 fffff806`9b3175cb : ffffa80c`f32f1950 00000001`67727453 00000000`00000000 00000000`00000000 : 0xffffb80b`406074a0
ffffb80b`40606ea0 ffffa80c`f32f1950 : 00000001`67727453 00000000`00000000 00000000`00000000 53f7a2f5`02eff82f : vgk+0x1275cb
ffffb80b`40606ea8 00000001`67727453 : 00000000`00000000 00000000`00000000 53f7a2f5`02eff82f ffffb80b`40607220 : 0xffffa80c`f32f1950
ffffb80b`40606eb0 00000000`00000000 : 00000000`00000000 53f7a2f5`02eff82f ffffb80b`40607220 00000000`000002a0 : 0x00000001`67727453


SYMBOL_NAME: vgk+a243a

MODULE_NAME: vgk

IMAGE_NAME: vgk.sys

STACK_COMMAND: .process /r /p 0xffffa80ceb4f6040; .thread 0xffffa80ceb571140 ; kb

BUCKET_ID_FUNC_OFFSET: a243a

FAILURE_BUCKET_ID: 0xc4_2000_VRF_vgk!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4cf836d1-3aaa-e980-1de0-37871feda2d3}

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

@kadircivekk @turko35408
 
Son düzenleme:
@kadircivekk Windows Defender > Giriş > Cihaz Güvenliği > Çekirdek Yalıtım > Bellek bütünlüğü'nü kapatın ve Valorant oyununa girin.

Vanguard yazılımını kaldırmak ta çözüm olabilir.

 

Sorun valorant mı yani, ama valo oynuyorum vanguard kaldırırsam oynayamam başka bir çözümü olmalı ya
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…