eonistaken
Femtopat
- Katılım
- 15 Mayıs 2021
- Mesajlar
- 8
Daha fazla
- Cinsiyet
- Erkek
Minidump dosyası: minidump.rar
Son düzenleyen: Moderatör:
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: fffff80242c4f9d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2859
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 13051
Key : Analysis.Init.CPU.mSec
Value: 453
Key : Analysis.Init.Elapsed.mSec
Value: 1267
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: fffff80242c4f9d0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff802`42882158 fffff802`400f5c6e : 00000000`0000001e ffffffff`c0000096 fffff802`42c4f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff802`42882160 fffff802`3ffffbaf : fffff802`400f5c4c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff802`428821a0 fffff802`3fe87547 : fffff802`42882710 00000000`00000000 fffff802`42874fb0 fffff802`3fffdd35 : nt!RtlpExecuteHandlerForException+0xf
fffff802`428821d0 fffff802`3fe86136 : fffff802`42874018 fffff802`42882e20 fffff802`42874018 ffffde8d`2ccecaf0 : nt!RtlDispatchException+0x297
fffff802`428828f0 fffff802`3fff7b82 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff802`42882fb0 fffff802`3fff7b50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff802`42873ed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
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.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}
Followup: MachineOwner
---------
Sorunun kaynağı Vanguard. Vanguard kaldırmanız sorunu çözecektir.
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: ffffffffc0000096, The exception code that was not handled. Arg2: fffff80242c4f9d0, The address that the exception occurred at. Arg3: 0000000000000000, Parameter 0 of the exception. Arg4: 0000000000000000, Parameter 1 of the exception. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2859. Key : Analysis.DebugAnalysisManager Value: Create. Key : Analysis.Elapsed.mSec Value: 13051. Key : Analysis.Init.CPU.mSec Value: 453. Key : Analysis.Init.Elapsed.mSec Value: 1267. Key : Analysis.Memory.CommitPeak.Mb Value: 73. Key : WER.OS.Branch Value: vb_release. Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 1e. BUGCHECK_P1: ffffffffc0000096. BUGCHECK_P2: fffff80242c4f9d0. BUGCHECK_P3: 0 BUGCHECK_P4: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System. STACK_TEXT: fffff802`42882158 fffff802`400f5c6e : 00000000`0000001e ffffffff`c0000096 fffff802`42c4f9d0 00000000`00000000 : nt!KeBugCheckEx fffff802`42882160 fffff802`3ffffbaf : fffff802`400f5c4c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22 fffff802`428821a0 fffff802`3fe87547 : fffff802`42882710 00000000`00000000 fffff802`42874fb0 fffff802`3fffdd35 : nt!RtlpExecuteHandlerForException+0xf fffff802`428821d0 fffff802`3fe86136 : fffff802`42874018 fffff802`42882e20 fffff802`42874018 ffffde8d`2ccecaf0 : nt!RtlDispatchException+0x297 fffff802`428828f0 fffff802`3fff7b82 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186 fffff802`42882fb0 fffff802`3fff7b50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12 fffff802`42873ed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue 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.19041.1 BUILDLAB_STR: vb_release. OSPLATFORM_TYPE: x64. OSNAME: Windows 10. FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26} Followup: MachineOwner. ---------
Vanguard kaldırdıktan sonra Vanguard'ın tekrar yüklenmediğinden emin misiniz? Bu durumda eminseniz gelecek yeni yamayı beklemelisiniz.Aynısını 4-5 kere denemiştim fakat düzelmedi. Yorumun için teşekkürler.
Vanguard kaldırdıktan sonra Vanguard'ın tekrar yüklenmediğinden emin misiniz? Bu durumda eminseniz gelecek yeni yamayı beklemelisiniz.
Bu sitenin çalışmasını sağlamak için gerekli çerezleri ve deneyiminizi iyileştirmek için isteğe bağlı çerezleri kullanıyoruz.