Valorant yüzünden KMODE_EXCEPTION_NOT_HANDLED mavi ekran hatası

Sizde de herkeste olduğu gibi Vanguard sorunlu. Çözüm ise kaldırmak ki biliyorsunuz. Kesin çözüm ise Valorant'ın güncelleme yayımlamasını beklemek gibi görünüyor.

[CODE title="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: fffff80540f3f9d0, 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: 5499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 36997

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

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

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

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: fffff80540f3f9d0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

DPC_STACK_BASE: FFFFF80546672FB0

STACK_TEXT:
fffff805`466710d8 fffff805`434a695e : 00000000`0000001e ffffffff`c0000096 fffff805`40f3f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff805`466710e0 fffff805`433cb1af : fffff805`43711000 fffff805`43200000 0005e38c`00ab7000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff805`46671120 fffff805`432fa2d5 : 00000000`00000000 00000000`00000000 fffff805`46671690 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
fffff805`46671150 fffff805`432fe86e : fffff805`46672088 fffff805`46671dd0 fffff805`46672088 ffffe60f`f829ad30 : nt!RtlDispatchException+0x4a5
fffff805`466718a0 fffff805`433d431d : fffff805`3ee40180 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16e
fffff805`46671f50 fffff805`433d00a2 : 00000000`00000000 fffff80d`bb2119b6 00000000`00000009 00000000`00000200 : nt!KiExceptionDispatch+0x11d
fffff805`46672130 fffff805`40f3f9d0 : ffffe60f`f829ad30 fffff805`466723c0 00000000`00000000 fffff805`00000000 : nt!KiGeneralProtectionFault+0x322
fffff805`466722c0 ffffe60f`f829ad30 : fffff805`466723c0 00000000`00000000 fffff805`00000000 ffffe60f`00000020 : vgk+0x4f9d0
fffff805`466722c8 fffff805`466723c0 : 00000000`00000000 fffff805`00000000 ffffe60f`00000020 00000000`000b000b : 0xffffe60f`f829ad30
fffff805`466722d0 00000000`00000000 : fffff805`00000000 ffffe60f`00000020 00000000`000b000b ffffe60f`f8afc530 : 0xfffff805`466723c0


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: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

*******************************************************************************
* *
* 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: fffff80ff26cf9d0, 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: 5733

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 44862

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

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

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

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: fffff80ff26cf9d0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffe08377210000 -- (.trap 0xffffe08377210000)
Unable to read trap frame at ffffe083`77210000

STACK_TEXT:
fffff800`82a69ec8 fffff800`7caa695e : 00000000`0000001e ffffffff`c0000096 fffff80f`f26cf9d0 00000000`00000000 : nt!KeBugCheckEx
fffff800`82a69ed0 fffff800`7c9cb1af : fffff800`7cd11000 fffff800`7c800000 0005e38c`00ab7000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff800`82a69f10 fffff800`7c8fa2d5 : 00000000`00000000 00000000`00000000 fffff800`82a6a480 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
fffff800`82a69f40 fffff800`7c8fe86e : fffff800`82a6ae78 fffff800`82a6abc0 fffff800`82a6ae78 ffffe083`7daaa7e0 : nt!RtlDispatchException+0x4a5
fffff800`82a6a690 fffff800`7c9d431d : 00000000`00000000 ffffe083`7721000e ffffe083`77210000 ffffe083`7667fa50 : nt!KiDispatchException+0x16e
fffff800`82a6ad40 fffff800`7c9d00a2 : ffffe083`00000000 fffff800`7c91e7a7 ffffe083`75e02340 00000000`000000ff : nt!KiExceptionDispatch+0x11d
fffff800`82a6af20 fffff80f`f26cf9d0 : ffffe083`7daaa7e0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x322
fffff800`82a6b0b0 ffffe083`7daaa7e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vgk+0x4f9d0
fffff800`82a6b0b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe083`7daaa7e0


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: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

*******************************************************************************
* *
* 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: fffff8001725f9d0, 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 USBPORT.SYS

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5124

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 31767

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

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

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

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: fffff8001725f9d0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff800`1c269ec8 fffff800`19aa695e : 00000000`0000001e ffffffff`c0000096 fffff800`1725f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff800`1c269ed0 fffff800`199cb1af : fffff800`19d11000 fffff800`19800000 0005e38c`00ab7000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffff800`1c269f10 fffff800`198fa2d5 : 00000000`00000000 00000000`00000000 fffff800`1c26a480 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0xf
fffff800`1c269f40 fffff800`198fe86e : fffff800`1c26ae78 fffff800`1c26abc0 fffff800`1c26ae78 ffffb90e`4bbda190 : nt!RtlDispatchException+0x4a5
fffff800`1c26a690 fffff800`199d431d : 00000000`00000000 fffff800`19923736 00000000`00000002 00000000`00000000 : nt!KiDispatchException+0x16e
fffff800`1c26ad40 fffff800`199d00a2 : 00000000`00000005 fffff800`1999f9ee 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
fffff800`1c26af20 fffff800`1725f9d0 : ffffb90e`4bbda190 ffffb90e`479e6080 ffffb90e`479e6080 fffff800`199215a3 : nt!KiGeneralProtectionFault+0x322
fffff800`1c26b0b0 ffffb90e`4bbda190 : ffffb90e`479e6080 ffffb90e`479e6080 fffff800`199215a3 fffff800`14be0180 : vgk+0x4f9d0
fffff800`1c26b0b8 ffffb90e`479e6080 : ffffb90e`479e6080 fffff800`199215a3 fffff800`14be0180 00000000`00000100 : 0xffffb90e`4bbda190
fffff800`1c26b0c0 ffffb90e`479e6080 : fffff800`199215a3 fffff800`14be0180 00000000`00000100 ffffb90e`41a3c910 : 0xffffb90e`479e6080
fffff800`1c26b0c8 fffff800`199215a3 : fffff800`14be0180 00000000`00000100 ffffb90e`41a3c910 fffff800`00000000 : 0xffffb90e`479e6080
fffff800`1c26b0d0 fffff80a`d3ab3b5e : ffffb90e`479e61f0 fffff800`19821050 00000000`00000138 fffff80a`d3ab23e2 : nt!KiReadyThread+0x33
fffff800`1c26b100 fffff800`179d3abd : ffffb90e`4bbda440 ffffb90e`4bbda2f0 ffffb90e`4bbda308 fffff800`1c26b1b0 : HIDPARSE!HidP_GetUsages+0x7e
fffff800`1c26b170 fffff800`199200a9 : 00000000`00000000 ffffb90e`446de000 00000000`00000001 fffff800`00000000 : mouhid!MouHid_ReadComplete+0x75d
fffff800`1c26b210 fffff800`1991ff77 : 00000000`00000008 00000000`00000006 ffffb90e`4639b6d0 00000000`00000000 : nt!IopfCompleteRequest+0x119
fffff800`1c26b320 fffff80a`d3a7acac : ffffb90e`4639b6c0 00000000`00000007 ffffb90e`4639b6d0 00000000`00000007 : nt!IofCompleteRequest+0x17
fffff800`1c26b350 fffff80a`d3a7a7ba : ffffb90e`4bf7f6a0 ffffb90e`4bf7f602 ffffb90e`46eff6f0 00000000`00000007 : HIDCLASS!HidpDistributeInterruptReport+0x258
fffff800`1c26b420 fffff800`199200a9 : ffffb90e`4b9ca300 ffffb90e`4b9ca300 fffff800`1c26b501 00000000`00000001 : HIDCLASS!HidpInterruptReadComplete+0x34a
fffff800`1c26b4c0 fffff800`1991ff77 : ffffffff`ffffffff ffffb90e`44acc100 ffffb90e`4bef6580 01000000`00100000 : nt!IopfCompleteRequest+0x119
fffff800`1c26b5d0 fffff80a`d3663392 : ffffb90e`44e61660 ffffb90e`47e9632c ffffb90e`00000000 ffffffff`ffffffff : nt!IofCompleteRequest+0x17
fffff800`1c26b600 ffffb90e`44e61660 : ffffb90e`47e9632c ffffb90e`00000000 ffffffff`ffffffff 00000000`00000000 : USBPORT+0x13392
fffff800`1c26b608 ffffb90e`47e9632c : ffffb90e`00000000 ffffffff`ffffffff 00000000`00000000 fffff800`1c26b6a8 : 0xffffb90e`44e61660
fffff800`1c26b610 ffffb90e`00000000 : ffffffff`ffffffff 00000000`00000000 fffff800`1c26b6a8 00000000`00000000 : 0xffffb90e`47e9632c
fffff800`1c26b618 ffffffff`ffffffff : 00000000`00000000 fffff800`1c26b6a8 00000000`00000000 fffff800`1c26b688 : 0xffffb90e`00000000
fffff800`1c26b620 00000000`00000000 : fffff800`1c26b6a8 00000000`00000000 fffff800`1c26b688 00000000`00000000 : 0xffffffff`ffffffff


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: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
---------[/CODE]
 
Sorun basit ve çözüm yok... İsyan bir öncü eski çekirdek 2 dörtlü işlemcilerde oyunun kullanımını geri çekti.
 
Son düzenleyen: Moderatör:
Bakar mısınız aklıma takıldı benim de
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı