KMODE_EXCEPTION_NOT_HANDLED mavi ekran hatası

UmuT_35

Kilopat
Katılım
12 Mart 2019
Mesajlar
732
Çözümler
3
Daha fazla  
Cinsiyet
Erkek

Temiz kurulum ve BIOS güncellemesi yaptığım halde aynı hatayı almaya devam ediyorum. Çözümü ne olabilir ?
 
Merhaba. Alınan hatalar Vanguard kaynaklı.

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: fffff8044be139da, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

*** WARNING: Unable to verify timestamp for vgk.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2625

    Key  : Analysis.Elapsed.mSec
    Value: 6225

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

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

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

    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  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_R_vgk!unknown_function

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

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

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

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


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8044be139da

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB:  062425-20234-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff9103a134d040

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff8049cbc44c0: 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:  svchost.exe

TRAP_FRAME:  fff5467cb7596af9 -- (.trap 0xfff5467cb7596af9)
Unable to read trap frame at fff5467c`b7596af9
Resetting default scope

STACK_TEXT: 
fffff60a`67b96938 fffff804`9bfdb15b     : 00000000`0000001e ffffffff`c0000005 fffff804`4be139da 00000000`00000000 : nt!KeBugCheckEx
fffff60a`67b96940 fffff804`9c2b9745     : 4e80984e`0f56cebf ff2be2d4`7a59d970 fff5467c`b7596af9 fffff60a`6dd56a2a : nt!KiDispatchException+0xb0b
fffff60a`67b97050 fffff804`9c2b4425     : ffffe608`6efd62a3 000019f7`91029d5c 00000000`00000000 ffffffff`ffffffed : nt!KiExceptionDispatch+0x145
fffff60a`67b97230 fffff804`4be139da     : 00000000`00000000 fffff60a`67b97548 00000000`00000000 ffff9103`a134d040 : nt!KiGeneralProtectionFault+0x365
fffff60a`67b973c0 00000000`00000000     : fffff60a`67b97548 00000000`00000000 ffff9103`a134d040 ffffbe81`58651180 : vgk+0xe439da


SYMBOL_NAME:  vgk+e439da

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND: .process /r /p 0xffff9103956d3040; .thread 0xffff9103a134d040 ; kb

BUCKET_ID_FUNC_OFFSET:  e439da

FAILURE_BUCKET_ID:  AV_R_vgk!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b93bf423-3535-1218-531c-8c08e172e67f}
Vanguard anti-cheat yazılımı hata vermiş. Vanguard yazılımını kaldırıp yeniden kurun.
 

Technopat Haberler

Yeni konular

Geri
Yukarı