Hata denetimi kodları

wudi456

Decapat
Katılım
17 Ekim 2020
Mesajlar
76
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
"Bu bilgisayar bir hata denetiminde yeniden başlatıldı. Yapılan hata denetimi: 0x00000018 (0xfFFFAC049CAC20C0, 0xffffac04ad48e9e0, 0x0000000000000001, 0x9000000000000001). döküm şuraya kaydedildi: C:\Windows\MEMORY.DMP. rapor kimliği: B92BF192-5D9E-486A-97E2-028258500EC5."

Böyle bir sorunla karşılaştım. 0x18'i sadece ön kimlik doğrulama bilgileri geçersizdi gibi bir şeye denk geldiğini gördüm. Yardımınızı istiyorum.
 
Son düzenleyen: Moderatör:
Bir kez daha atsam tekrar bakma şansınız var mı?
Anladığım kadarıyla yeniden mavi ekran aldınız. Dosyalarınızı atabilir misiniz? Bakalım.

Mavi ekran almayıp DCOM10016 hatası aldıysanız çok bir fikrim yok maalesef. Yazılımsal sorun da olabilir, donanımsal sorun da olabilir. Bu durumda şu konuya bakabilirsiniz:
 
Anladığım kadarıyla yeniden mavi ekran aldınız. Dosyalarınızı atabilir misiniz? Bakalım.

Mavi ekran almayıp DCOM10016 hatası aldıysanız çok bir fikrim yok maalesef. Yazılımsal sorun da olabilir, donanımsal sorun da olabilir. Bu durumda şu konuya bakabilirsiniz:
Biraz geç yazdım kusura bakmayın dosya2.rar şöyle atayım . Temmuz ayından beri uğraşıyorum kaç defa teknik servise gitti geldi. O yüzden artık canım sıkılmış durumda şimdiden iyi incelemeler
 
  • Vanguard'ı hâlâ kaldırmamışsınız.
  • Logitech yazılımları hâlâ duruyor.
  • Çipset sürücülerinizi güncellediniz mi?
  • Klavye ve fare dışındaki USB cihazlarınızı çıkardınız mı?
  • BIOS'u sıfırlayıp MemTest86 ile bellek testi yaptınız mı?
  • DDU ile GPU sürücülerini kaldırıp WHQL onaylı sürücüyü yeniden kurdunuz mu?
Önceki mesajımda söylediklerim aynen geçerli.

Kod:
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
    buffer overrun.
Arg2: ffff83087f2d1190, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff83087f2d10e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7515

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 50987

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  139

BUGCHECK_P1: 2

BUGCHECK_P2: ffff83087f2d1190

BUGCHECK_P3: ffff83087f2d10e8

BUGCHECK_P4: 0

TRAP_FRAME:  ffff83087f2d1190 -- (.trap 0xffff83087f2d1190)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c0000005 rbx=0000000000000000 rcx=0000000000000002
rdx=ffffb88909721ac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80214018de5 rsp=ffff83087f2d1328 rbp=ffff8e0e8aeb4e70
 r8=ffffb88909721ac0  r9=ffffb888feb41960 r10=ffffb888faeb0bf0
r11=ffffb8890a162740 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
USBXHCI!_report_gsfailure+0x5:
fffff802`14018de5 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff83087f2d10e8 -- (.exr 0xffff83087f2d10e8)
ExceptionAddress: fffff80214018de5 (USBXHCI!_report_gsfailure+0x0000000000000005)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000002
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

WATSON_BKT_EVENT:  BEX

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y   n tabanl  bir arabelle in ta t   n  alg lad . Bu ta ma, k t  niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_STR:  0xc0000409

STACK_TEXT: 
ffff8308`7f2d0e68 fffff802`05806569     : 00000000`00000139 00000000`00000002 ffff8308`7f2d1190 ffff8308`7f2d10e8 : nt!KeBugCheckEx
ffff8308`7f2d0e70 fffff802`05806990     : 00000000`00000000 ffffa480`3dea5180 00000000`10000000 00000002`c0000027 : nt!KiBugCheckDispatch+0x69
ffff8308`7f2d0fb0 fffff802`05804d23     : ffffb889`03aef000 ffffb889`03aef000 00000000`00000000 ffff8308`7f2d1418 : nt!KiFastFailDispatch+0xd0
ffff8308`7f2d1190 fffff802`14018de5     : fffff802`14077bb2 ffff8e0e`826bee80 ffff8e0e`86b1d820 00000000`001273c7 : nt!KiRaiseSecurityCheckFailure+0x323
ffff8308`7f2d1328 fffff802`14077bb2     : ffff8e0e`826bee80 ffff8e0e`86b1d820 00000000`001273c7 ffff8308`7f2d1418 : USBXHCI!_report_gsfailure+0x5
ffff8308`7f2d1330 ffff8cc1`c0613f20     : 00000000`0000003c 6e92632d`00000000 ffffdba0`6aaab108 ffff8c90`4488fe5e : USBXHCI!TelemetryData_pInitWerContext+0x33a
ffff8308`7f2d16a0 00000000`0000003c     : 6e92632d`00000000 ffffdba0`6aaab108 ffff8c90`4488fe5e 00000000`00004014 : 0xffff8cc1`c0613f20
ffff8308`7f2d16a8 6e92632d`00000000     : ffffdba0`6aaab108 ffff8c90`4488fe5e 00000000`00004014 ffff8e0e`8de99900 : 0x3c
ffff8308`7f2d16b0 ffffdba0`6aaab108     : ffff8c90`4488fe5e 00000000`00004014 ffff8e0e`8de99900 00000000`c0000001 : 0x6e92632d`00000000
ffff8308`7f2d16b8 ffff8c90`4488fe5e     : 00000000`00004014 ffff8e0e`8de99900 00000000`c0000001 ffff8cc1`c0609000 : 0xffffdba0`6aaab108
ffff8308`7f2d16c0 00000000`00004014     : ffff8e0e`8ba4ba30 fffff802`135e1eda ffffb889`04c7c790 fffff802`05665d19 : win32kbase!CInpPushLock::UnLockShared+0x1e
ffff8308`7f2d16f0 ffff8e0e`8ba4ba30     : fffff802`135e1eda ffffb889`04c7c790 fffff802`05665d19 ffff8308`7f2d1828 : 0x4014
ffff8308`7f2d16f8 fffff802`135e1eda     : ffffb889`04c7c790 fffff802`05665d19 ffff8308`7f2d1828 ffff8e0e`8ba4ba30 : 0xffff8e0e`8ba4ba30
ffff8308`7f2d1700 fffff802`134e4b04     : ffffb888`00000002 fffff802`00000000 ffff8e0e`8de99990 ffff8308`00000002 : dxgkrnl!DxgkKernelModeWaitForSynchronizationObjectFromGpu+0x16
ffff8308`7f2d1740 fffff802`134e4c2c     : ffff8e0e`8de99900 ffff8e0e`8885bcb0 00000000`00000000 00000000`00000000 : dxgkrnl!CAdapter::SignalTokenSync+0x64
ffff8308`7f2d17c0 fffff802`134f14af     : ffff8e0e`8cb73d80 ffff8e0e`8ba4ba30 00000000`00004014 fffff802`034bc820 : dxgkrnl!CFlipExBuffer::SignalGpuFence+0xdc
ffff8308`7f2d1820 fffff802`134f43ba     : 00000000`00000001 ffff8e0e`8885bcb0 ffff8cc1`c0609000 00000000`00000000 : dxgkrnl!CFlipToken::InFrame+0x38f
ffff8308`7f2d1880 ffff8c90`4486bff3     : ffffb889`0caea901 ffff8cc1`c0609000 ffff8e0e`877c9960 ffff8e0e`8cb73d80 : dxgkrnl!CTokenManager::ReleaseToFrame+0x2ea
ffff8308`7f2d1930 ffff8c90`4486bda6     : ffff8cc1`c07121d0 ffff8308`7f2d1a78 ffff8308`7f2d1a28 00000000`00000001 : win32kbase!NtDCompositionBeginFrame+0x3e3
ffff8308`7f2d19f0 ffff8c90`4514ea01     : 00000000`00000000 ffffb889`04c7c080 00000000`00000000 00000000`00000000 : win32kbase!NtDCompositionBeginFrame+0x196
ffff8308`7f2d1ad0 fffff802`05805fb8     : ffffb889`04c7c080 00000000`000003e8 00000000`00000000 00000000`00000274 : win32k!NtDCompositionBeginFrame+0x15
ffff8308`7f2d1b00 00007ffc`b27e3404     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000009d`cdeff248 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`b27e3404


SYMBOL_NAME:  win32kbase!CInpPushLock::UnLockShared+1e

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e

FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_win32kbase!CInpPushLock::UnLockShared

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0dd2301f-781f-2c10-442d-ea6c17c38271}

Followup:     MachineOwner
---------
 
  • Vanguard'ı hâlâ kaldırmamışsınız.
  • Logitech yazılımları hâlâ duruyor.
  • Çipset sürücülerinizi güncellediniz mi?
  • Klavye ve fare dışındaki USB cihazlarınızı çıkardınız mı?
  • BIOS'u sıfırlayıp MemTest86 ile bellek testi yaptınız mı?
  • DDU ile GPU sürücülerini kaldırıp WHQL onaylı sürücüyü yeniden kurdunuz mu?
Önceki mesajımda söylediklerim aynen geçerli.

Kod:
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
    buffer overrun.
Arg2: ffff83087f2d1190, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff83087f2d10e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7515

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 50987

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  139

BUGCHECK_P1: 2

BUGCHECK_P2: ffff83087f2d1190

BUGCHECK_P3: ffff83087f2d10e8

BUGCHECK_P4: 0

TRAP_FRAME:  ffff83087f2d1190 -- (.trap 0xffff83087f2d1190)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c0000005 rbx=0000000000000000 rcx=0000000000000002
rdx=ffffb88909721ac0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80214018de5 rsp=ffff83087f2d1328 rbp=ffff8e0e8aeb4e70
r8=ffffb88909721ac0  r9=ffffb888feb41960 r10=ffffb888faeb0bf0
r11=ffffb8890a162740 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
USBXHCI!_report_gsfailure+0x5:
fffff802`14018de5 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff83087f2d10e8 -- (.exr 0xffff83087f2d10e8)
ExceptionAddress: fffff80214018de5 (USBXHCI!_report_gsfailure+0x0000000000000005)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000002
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

WATSON_BKT_EVENT:  BEX

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y   n tabanl  bir arabelle in ta t   n  alg lad . Bu ta ma, k t  niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000002

EXCEPTION_STR:  0xc0000409

STACK_TEXT:
ffff8308`7f2d0e68 fffff802`05806569     : 00000000`00000139 00000000`00000002 ffff8308`7f2d1190 ffff8308`7f2d10e8 : nt!KeBugCheckEx
ffff8308`7f2d0e70 fffff802`05806990     : 00000000`00000000 ffffa480`3dea5180 00000000`10000000 00000002`c0000027 : nt!KiBugCheckDispatch+0x69
ffff8308`7f2d0fb0 fffff802`05804d23     : ffffb889`03aef000 ffffb889`03aef000 00000000`00000000 ffff8308`7f2d1418 : nt!KiFastFailDispatch+0xd0
ffff8308`7f2d1190 fffff802`14018de5     : fffff802`14077bb2 ffff8e0e`826bee80 ffff8e0e`86b1d820 00000000`001273c7 : nt!KiRaiseSecurityCheckFailure+0x323
ffff8308`7f2d1328 fffff802`14077bb2     : ffff8e0e`826bee80 ffff8e0e`86b1d820 00000000`001273c7 ffff8308`7f2d1418 : USBXHCI!_report_gsfailure+0x5
ffff8308`7f2d1330 ffff8cc1`c0613f20     : 00000000`0000003c 6e92632d`00000000 ffffdba0`6aaab108 ffff8c90`4488fe5e : USBXHCI!TelemetryData_pInitWerContext+0x33a
ffff8308`7f2d16a0 00000000`0000003c     : 6e92632d`00000000 ffffdba0`6aaab108 ffff8c90`4488fe5e 00000000`00004014 : 0xffff8cc1`c0613f20
ffff8308`7f2d16a8 6e92632d`00000000     : ffffdba0`6aaab108 ffff8c90`4488fe5e 00000000`00004014 ffff8e0e`8de99900 : 0x3c
ffff8308`7f2d16b0 ffffdba0`6aaab108     : ffff8c90`4488fe5e 00000000`00004014 ffff8e0e`8de99900 00000000`c0000001 : 0x6e92632d`00000000
ffff8308`7f2d16b8 ffff8c90`4488fe5e     : 00000000`00004014 ffff8e0e`8de99900 00000000`c0000001 ffff8cc1`c0609000 : 0xffffdba0`6aaab108
ffff8308`7f2d16c0 00000000`00004014     : ffff8e0e`8ba4ba30 fffff802`135e1eda ffffb889`04c7c790 fffff802`05665d19 : win32kbase!CInpPushLock::UnLockShared+0x1e
ffff8308`7f2d16f0 ffff8e0e`8ba4ba30     : fffff802`135e1eda ffffb889`04c7c790 fffff802`05665d19 ffff8308`7f2d1828 : 0x4014
ffff8308`7f2d16f8 fffff802`135e1eda     : ffffb889`04c7c790 fffff802`05665d19 ffff8308`7f2d1828 ffff8e0e`8ba4ba30 : 0xffff8e0e`8ba4ba30
ffff8308`7f2d1700 fffff802`134e4b04     : ffffb888`00000002 fffff802`00000000 ffff8e0e`8de99990 ffff8308`00000002 : dxgkrnl!DxgkKernelModeWaitForSynchronizationObjectFromGpu+0x16
ffff8308`7f2d1740 fffff802`134e4c2c     : ffff8e0e`8de99900 ffff8e0e`8885bcb0 00000000`00000000 00000000`00000000 : dxgkrnl!CAdapter::SignalTokenSync+0x64
ffff8308`7f2d17c0 fffff802`134f14af     : ffff8e0e`8cb73d80 ffff8e0e`8ba4ba30 00000000`00004014 fffff802`034bc820 : dxgkrnl!CFlipExBuffer::SignalGpuFence+0xdc
ffff8308`7f2d1820 fffff802`134f43ba     : 00000000`00000001 ffff8e0e`8885bcb0 ffff8cc1`c0609000 00000000`00000000 : dxgkrnl!CFlipToken::InFrame+0x38f
ffff8308`7f2d1880 ffff8c90`4486bff3     : ffffb889`0caea901 ffff8cc1`c0609000 ffff8e0e`877c9960 ffff8e0e`8cb73d80 : dxgkrnl!CTokenManager::ReleaseToFrame+0x2ea
ffff8308`7f2d1930 ffff8c90`4486bda6     : ffff8cc1`c07121d0 ffff8308`7f2d1a78 ffff8308`7f2d1a28 00000000`00000001 : win32kbase!NtDCompositionBeginFrame+0x3e3
ffff8308`7f2d19f0 ffff8c90`4514ea01     : 00000000`00000000 ffffb889`04c7c080 00000000`00000000 00000000`00000000 : win32kbase!NtDCompositionBeginFrame+0x196
ffff8308`7f2d1ad0 fffff802`05805fb8     : ffffb889`04c7c080 00000000`000003e8 00000000`00000000 00000000`00000274 : win32k!NtDCompositionBeginFrame+0x15
ffff8308`7f2d1b00 00007ffc`b27e3404     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000009d`cdeff248 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`b27e3404


SYMBOL_NAME:  win32kbase!CInpPushLock::UnLockShared+1e

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e

FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_win32kbase!CInpPushLock::UnLockShared

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0dd2301f-781f-2c10-442d-ea6c17c38271}

Followup:     MachineOwner
---------
Nvidia sürücüsünü kaldırdıktan sonra ne yapacağım.
 
Son düzenleme:
ACPI.sys diye bir dosya görüyorum, BIOS üzerinden bilgisayarın donanımlarla iletişim kuran sürücü olduğunu öğrendim.

Bu hatadan pek emin olamadım ama MemTest86 yapmanız iyi olacaktır.

Karta FurMark yaparsanız da güzel olur.

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: fffff806073ba828, 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: 3858

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 5140

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff806073ba828

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff80602cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80602c0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80602c0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WmiPrvSE.exe

BAD_STACK_POINTER:  fffff80608a80158

STACK_TEXT:
fffff806`08a80158 fffff806`024f465e     : 00000000`0000001e ffffffff`c0000005 fffff806`073ba828 00000000`00000000 : nt!KeBugCheckEx
fffff806`08a80160 fffff806`023fd462     : fffff806`024f463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff806`08a801a0 fffff806`02252d97     : fffff806`08a80710 00000000`00000000 fffff806`08a72fb0 fffff806`023fb5e5 : nt!RtlpExecuteHandlerForException+0x12
fffff806`08a801d0 fffff806`022519a6     : fffff806`08a71c38 fffff806`08a80e20 fffff806`08a71c38 00000000`00000000 : nt!RtlDispatchException+0x297
fffff806`08a808f0 fffff806`023f5432     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff806`08a80fb0 fffff806`023f5400     : fffff806`024066a5 fffff806`08a71aa0 00000000`00000030 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff806`08a71af8 fffff806`024066a5     : fffff806`08a71aa0 00000000`00000030 00000000`00000000 fffff806`07442820 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff806`08a71b00 fffff806`024023e0     : ffffda05`e7015c00 ffffda05`ed3c8030 ffffda05`ed3a8930 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff806`08a71ce0 fffff806`073ba828     : ffffda05`ed3a8930 ebd88e05`00000000 00000000`00000000 000025fa`12f17848 : nt!KiGeneralProtectionFault+0x320
fffff806`08a71e70 fffff806`022cd805     : 00000000`00220003 ffffda05`ed102e10 00000000`00000000 ffffda05`ed269010 : Wdf01000!FxDevice::DispatchWithLock+0x118 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
fffff806`08a71ed0 fffff806`0751b58d     : ffffda05`ed102e10 ffffda05`ed269010 ffffda05`e7015c00 00000000`00000030 : nt!IofCallDriver+0x55
fffff806`08a71f10 fffff806`075110d5     : ffffda05`ea613440 00000000`00000007 ffffda05`ed2693f8 00000000`00000fff : ACPI!ACPIIrpDispatchDeviceControl+0xad
fffff806`08a71f50 fffff806`022cd805     : 00000000`00000007 00000000`00000000 fffff806`08a72079 ffffda05`ed26cd30 : ACPI!ACPIDispatchIrp+0xc5
fffff806`08a71fd0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55


SYMBOL_NAME:  ACPI!ACPIIrpDispatchDeviceControl+ad

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  ad

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_ACPI!ACPIIrpDispatchDeviceControl

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c137d1bb-0a6c-562a-f96a-20d6070bdf42}

Followup:     MachineOwner
---------
 
ACPI.sys diye bir dosya görüyorum, BIOS üzerinden bilgisayarın donanımlarla iletişim kuran sürücü olduğunu öğrendim.

Bu hatadan pek emin olamadım ama MemTest86 yapmanız iyi olacaktır.

Karta FurMark yaparsanız da güzel olur.

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: fffff806073ba828, 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: 3858

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 5140

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff806073ba828

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff80602cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80602c0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80602c0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WmiPrvSE.exe

BAD_STACK_POINTER:  fffff80608a80158

STACK_TEXT:
fffff806`08a80158 fffff806`024f465e     : 00000000`0000001e ffffffff`c0000005 fffff806`073ba828 00000000`00000000 : nt!KeBugCheckEx
fffff806`08a80160 fffff806`023fd462     : fffff806`024f463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff806`08a801a0 fffff806`02252d97     : fffff806`08a80710 00000000`00000000 fffff806`08a72fb0 fffff806`023fb5e5 : nt!RtlpExecuteHandlerForException+0x12
fffff806`08a801d0 fffff806`022519a6     : fffff806`08a71c38 fffff806`08a80e20 fffff806`08a71c38 00000000`00000000 : nt!RtlDispatchException+0x297
fffff806`08a808f0 fffff806`023f5432     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff806`08a80fb0 fffff806`023f5400     : fffff806`024066a5 fffff806`08a71aa0 00000000`00000030 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff806`08a71af8 fffff806`024066a5     : fffff806`08a71aa0 00000000`00000030 00000000`00000000 fffff806`07442820 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff806`08a71b00 fffff806`024023e0     : ffffda05`e7015c00 ffffda05`ed3c8030 ffffda05`ed3a8930 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff806`08a71ce0 fffff806`073ba828     : ffffda05`ed3a8930 ebd88e05`00000000 00000000`00000000 000025fa`12f17848 : nt!KiGeneralProtectionFault+0x320
fffff806`08a71e70 fffff806`022cd805     : 00000000`00220003 ffffda05`ed102e10 00000000`00000000 ffffda05`ed269010 : Wdf01000!FxDevice::DispatchWithLock+0x118 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
fffff806`08a71ed0 fffff806`0751b58d     : ffffda05`ed102e10 ffffda05`ed269010 ffffda05`e7015c00 00000000`00000030 : nt!IofCallDriver+0x55
fffff806`08a71f10 fffff806`075110d5     : ffffda05`ea613440 00000000`00000007 ffffda05`ed2693f8 00000000`00000fff : ACPI!ACPIIrpDispatchDeviceControl+0xad
fffff806`08a71f50 fffff806`022cd805     : 00000000`00000007 00000000`00000000 fffff806`08a72079 ffffda05`ed26cd30 : ACPI!ACPIDispatchIrp+0xc5
fffff806`08a71fd0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55


SYMBOL_NAME:  ACPI!ACPIIrpDispatchDeviceControl+ad

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  ad

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_ACPI!ACPIIrpDispatchDeviceControl

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c137d1bb-0a6c-562a-f96a-20d6070bdf42}

Followup:     MachineOwner
---------
Bütün parçaları garantiye yollamamı önerir misiniz ?
 
ACPI.sys diye bir dosya görüyorum, BIOS üzerinden bilgisayarın donanımlarla iletişim kuran sürücü olduğunu öğrendim.

Bu hatadan pek emin olamadım ama MemTest86 yapmanız iyi olacaktır.

Karta FurMark yaparsanız da güzel olur.

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: fffff806073ba828, 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: 3858

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-62N06FT

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 5140

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff806073ba828

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff80602cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80602c0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80602c0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WmiPrvSE.exe

BAD_STACK_POINTER:  fffff80608a80158

STACK_TEXT:
fffff806`08a80158 fffff806`024f465e     : 00000000`0000001e ffffffff`c0000005 fffff806`073ba828 00000000`00000000 : nt!KeBugCheckEx
fffff806`08a80160 fffff806`023fd462     : fffff806`024f463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff806`08a801a0 fffff806`02252d97     : fffff806`08a80710 00000000`00000000 fffff806`08a72fb0 fffff806`023fb5e5 : nt!RtlpExecuteHandlerForException+0x12
fffff806`08a801d0 fffff806`022519a6     : fffff806`08a71c38 fffff806`08a80e20 fffff806`08a71c38 00000000`00000000 : nt!RtlDispatchException+0x297
fffff806`08a808f0 fffff806`023f5432     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff806`08a80fb0 fffff806`023f5400     : fffff806`024066a5 fffff806`08a71aa0 00000000`00000030 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff806`08a71af8 fffff806`024066a5     : fffff806`08a71aa0 00000000`00000030 00000000`00000000 fffff806`07442820 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff806`08a71b00 fffff806`024023e0     : ffffda05`e7015c00 ffffda05`ed3c8030 ffffda05`ed3a8930 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff806`08a71ce0 fffff806`073ba828     : ffffda05`ed3a8930 ebd88e05`00000000 00000000`00000000 000025fa`12f17848 : nt!KiGeneralProtectionFault+0x320
fffff806`08a71e70 fffff806`022cd805     : 00000000`00220003 ffffda05`ed102e10 00000000`00000000 ffffda05`ed269010 : Wdf01000!FxDevice::DispatchWithLock+0x118 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
fffff806`08a71ed0 fffff806`0751b58d     : ffffda05`ed102e10 ffffda05`ed269010 ffffda05`e7015c00 00000000`00000030 : nt!IofCallDriver+0x55
fffff806`08a71f10 fffff806`075110d5     : ffffda05`ea613440 00000000`00000007 ffffda05`ed2693f8 00000000`00000fff : ACPI!ACPIIrpDispatchDeviceControl+0xad
fffff806`08a71f50 fffff806`022cd805     : 00000000`00000007 00000000`00000000 fffff806`08a72079 ffffda05`ed26cd30 : ACPI!ACPIDispatchIrp+0xc5
fffff806`08a71fd0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55


SYMBOL_NAME:  ACPI!ACPIIrpDispatchDeviceControl+ad

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

IMAGE_VERSION:  10.0.19041.508

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  ad

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_ACPI!ACPIIrpDispatchDeviceControl

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c137d1bb-0a6c-562a-f96a-20d6070bdf42}

Followup:     MachineOwner
---------
Bu arada ekstra bir test yapmıştım MemTestten bugün onu söylemeyi unuttum fotoğraflarını aldım size atmamı ister misiniz ?
Test 13 te bütün problemler çıktı ve 10000 den fazlaydı Highest error adress : 0x41e80813c 16 gb gözüküyor
 

Yeni konular

Geri
Yukarı