Windows 10 2004 mavi ekran hatası

İşletim sistemi
Windows 10

Osmanqll

Centipat
Katılım
29 Ekim 2020
Mesajlar
29
Daha fazla  
Cinsiyet
Erkek
Sistemimi yeni topladım, uyumluluk problemi yok sanırım ama Windows kurulumundan itibaren sürekli mavi ekran alıyorum. 3-4 kez yeniden Windows'u kurdum ama yine de değişen bir şey olmadı. Windows sürümü Windows 10 2004, ne yapmam lazım? Kafayı yedim, yardım ederseniz çok sevinirim.
 
Tarihe göre sırala Puana göre sırala

Minidump Dosyalarını Paylaşın

23.06.2025 tarihinde yapılan güncel rehbere aşağıdaki linkten erişebilirsiniz: https://www.technopat.net/sosyal/konu/minidump-nedir-nasil-paylasilir.3817531/ Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi...
www.technopat.net
 
Artı 0 Eksi

Minidump.rar

drive.google.com

Yapabilecek bir şey var mı?
 
Son düzenleme:
Artı 0 Eksi
Evet, var. Öncelikle bellek testi yapın.

Memtest86 USB'den Çalışan RAM Test Programı

RAM'lerinizi test etmek için kullanabileceğiniz en kapsamlı yazılım Memtest86'dır. Aracı USB belleğe yazmak için: Bu video rehberde Memtest86 ile belleklerinizi nasıl test edeceğinizi öğrenebilirsiniz: Adım adım: Öncelikle yazılımı buradan indirin. UEFI desteği olmayan eski sistemler...
www.technopat.net

Sonra depolama birimlerinize HD Tune Pro ile sağlık ve hata taraması yapın. Ve sistem bileşenlerinizi belirtin.

Ayrıca ekran kartınızın sürücüsünü DDU ile kaldırıp güncelleyin.

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net

Kod: 
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000088821ff710, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80175eeb17c, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5765

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8379

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

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

BUGCHECK_P1: 88821ff710

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80175eeb17c

WRITE_ADDRESS: fffff801768fa388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8017680f2a8: Unable to get Flags value from nt!KdVersionBlock
fffff8017680f2a8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 00000088821ff710

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

TRAP_FRAME:  ffffad0ec158e440 -- (.trap 0xffffad0ec158e440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000088821ff710 rbx=0000000000000000 rcx=000000000000000f
rdx=0000000000008000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80175eeb17c rsp=ffffad0ec158e5d0 rbp=0000000000000000
 r8=00000000011d8bc5  r9=00000000039bf7c0 r10=0000000000000000
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiDirectSwitchThread+0x6cc:
fffff801`75eeb17c 8808            mov     byte ptr [rax],cl ds:00000088`821ff710=??
Resetting default scope

STACK_TEXT: 
ffffad0e`c158e2f8 fffff801`75fef929     : 00000000`0000000a 00000088`821ff710 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffad0e`c158e300 fffff801`75febc29     : ffffb484`4ee80620 00000000`00000001 00000000`00003931 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffad0e`c158e440 fffff801`75eeb17c     : 00000000`00000000 fffff801`75fef1e0 00000000`00000000 fffff801`75e272af : nt!KiPageFault+0x469
ffffad0e`c158e5d0 fffff801`75e3e89d     : 00000000`00000001 00000000`00000001 00000000`00000000 ffff9984`00000000 : nt!KiDirectSwitchThread+0x6cc
ffffad0e`c158e690 fffff801`75eece60     : ffff9984`ae13d548 ffff9984`00000000 ffff9984`ae13d548 00000000`00000000 : nt!KiExitDispatcher+0x1dd
ffffad0e`c158e700 fffff801`75e2f413     : ffffffff`ffffffff ffff9984`00000001 00000000`00000001 00000000`00000001 : nt!KeReleaseSemaphoreEx+0x120
ffffad0e`c158e780 fffff801`762ecce3     : ffff9984`b0a9f080 ffff9984`b0a9f508 ffff9984`00000010 ffffffff`ffffffff : nt!AlpcpSignalAndWait+0x243
ffffad0e`c158e820 fffff801`762033bd     : ffffffff`00000000 00000000`00000000 ffff9984`ae0299a0 ffff9984`ae0299a0 : nt!AlpcpCompleteDeferSignalRequestAndWait+0x57
ffffad0e`c158e860 fffff801`76202419     : ffff9984`b0a9f080 00000000`00001401 00000000`00000000 ffffad0e`c158e948 : nt!AlpcpReceiveMessagePort+0x3ad
ffffad0e`c158e8f0 fffff801`76201f5e     : ffffad0e`c158ea30 ffff9984`ae0299a0 0000006a`ebfbf4d8 00000000`00000000 : nt!AlpcpReceiveMessage+0x339
ffffad0e`c158e9d0 fffff801`75fef378     : ffff9984`b0a9f080 ffffad0e`c158eb80 0000006a`ebfbf468 ffffad0e`c158eaa8 : nt!NtAlpcSendWaitReceivePort+0xfe
ffffad0e`c158ea90 00007ffb`b18cbf04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000006a`ebfbf448 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`b18cbf04


SYMBOL_NAME:  nt!KiDirectSwitchThread+6cc

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  6cc

FAILURE_BUCKET_ID:  AV_nt!KiDirectSwitchThread

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f852e30f-dbe6-5ff1-d3f6-a35884600010}

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



IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000005681, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8040caafe9e, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7202

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8452

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

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

BUGCHECK_P1: 5681

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8040caafe9e

READ_ADDRESS: fffff8040d4fa388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8040d40f2a8: Unable to get Flags value from nt!KdVersionBlock
fffff8040d40f2a8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000000000005681

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  explorer.exe

TRAP_FRAME:  ffffa709ab994db0 -- (.trap 0xffffa709ab994db0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa67d72e00001 rbx=0000000000000000 rcx=fffff8040d44c800
rdx=000000000122b130 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8040caafe9e rsp=ffffa709ab994f40 rbp=ffffad8006d02720
 r8=000000000000023a  r9=e2ea3a20002453b0 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiInsertPageInList+0xfe:
fffff804`0caafe9e 458b4608        mov     r8d,dword ptr [r14+8] ds:00000000`00000008=????????
Resetting default scope

STACK_TEXT: 
ffffa709`ab994c68 fffff804`0cbef929     : 00000000`0000000a 00000000`00005681 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffa709`ab994c70 fffff804`0cbebc29     : ffffad80`06d04310 fffff804`0cb30124 ffffad80`06d02000 fffff804`0caaacbd : nt!KiBugCheckDispatch+0x69
ffffa709`ab994db0 fffff804`0caafe9e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469
ffffa709`ab994f40 fffff804`0caafc45     : 00000000`00000000 80000002`453b0863 00000000`00245626 04101dea`5dbc0026 : nt!MiInsertPageInList+0xfe
ffffa709`ab994fe0 fffff804`0ca8e8c7     : 00000002`456268c0 00000000`00000000 00000000`00000006 ffffa709`ab995230 : nt!MiPfnShareCountIsZero+0x345
ffffa709`ab995040 fffff804`0cab7d3f     : 00000000`00000000 00000000`00000000 00000000`53440000 00000000`00000000 : nt!MiMakePageAvoidRead+0xba7
ffffa709`ab9951e0 fffff804`0cab847c     : ffffd082`7f675000 00000000`16984040 ffffa709`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0x28f
ffffa709`ab9952b0 fffff804`0cad20ea     : ffff8203`bb232a20 00000000`16984040 ffffa709`ab9954a8 00000000`00080000 : nt!CcMapAndCopyInToCache+0x41c
ffffa709`ab995450 fffff804`11c99abb     : ffffa709`ab9955c0 00000000`00100000 00000000`53500000 00000000`00100000 : nt!CcCopyWriteEx+0xea
ffffa709`ab9954d0 fffff804`0bae73fb     : 00000000`00000000 ffffa709`ab9958e8 ffffa709`ab9958a8 00000000`1690f040 : Ntfs!NtfsCopyWriteA+0x44b
ffffa709`ab995800 fffff804`0bae44d7     : ffffa709`ab995910 ffffa709`ab9958a8 ffff8203`bc9d4b20 ffff8203`bc9d4a20 : FLTMGR!FltpPerformFastIoCall+0x16b
ffffa709`ab995860 fffff804`0bb1b215     : ffffa709`ab996000 ffffa709`ab990000 ffff8203`bdac1798 ffff8203`b863ad60 : FLTMGR!FltpPassThroughFastIo+0x107
ffffa709`ab9958e0 fffff804`0ce2b42d     : ffff8203`bdac34b0 00000000`0726cc70 00000000`0726cc70 00000000`00000000 : FLTMGR!FltpFastIoWrite+0x165
ffffa709`ab995990 fffff804`0cbef378     : 00000000`00000000 00000000`00002814 00000000`00000000 00000000`0e3aade0 : nt!NtWriteFile+0x43d
ffffa709`ab995a90 00007ffa`ab6cae94     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0726cbf8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`ab6cae94


SYMBOL_NAME:  nt!MiInsertPageInList+fe

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  fe

FAILURE_BUCKET_ID:  AV_nt!MiInsertPageInList

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a90f9f23-588e-d5a6-a0a3-950e9fb27bf8}

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



IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80104f02c0b, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6281

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7503

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

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

BUGCHECK_P1: b8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80104f02c0b

READ_ADDRESS: fffff801058fa388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8010580f2a8: Unable to get Flags value from nt!KdVersionBlock
fffff8010580f2a8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 00000000000000b8

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SecHealthUI.exe

TRAP_FRAME:  ffff9a0cd9adfb00 -- (.trap 0xffff9a0cd9adfb00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=000000003f800000
rdx=0000000000000fbc rsi=0000000000000000 rdi=0000000000000000
rip=00007ffbfdf7d23e rsp=0000006d9bcfe590 rbp=0000000000000000
 r8=0000006d9bcfe5c0  r9=0000000000001000 r10=00000fff7fbed8f4
r11=4010000000000018 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
0033:00007ffb`fdf7d23e ??              ???
Resetting default scope

STACK_TEXT: 
ffff9a0c`d9adde28 fffff801`04fef929     : 00000000`0000000a 00000000`000000b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff9a0c`d9adde30 fffff801`04febc29     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9a0c`d9addf70 fffff801`04f02c0b     : 00000000`00000002 ffffd683`5d44d0c0 00000000`00000000 ffff8f00`00000000 : nt!KiPageFault+0x469
ffff9a0c`d9ade100 fffff801`04e1374e     : ffffd683`5d44d740 ffffd683`00000000 ffff9a0c`d9ade290 ffff8f47`80000000 : nt!MiUnlockPageTableInternal+0xb
ffff9a0c`d9ade140 fffff801`04e12a4a     : 00000000`00000000 ffff9e11`00000002 00000000`00000000 00000000`00000000 : nt!MiUserFault+0x78e
ffff9a0c`d9ade1d0 fffff801`04febb1e     : 00000000`00000000 ffffd683`5a981df0 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x16a
ffff9a0c`d9ade370 fffff801`04e7ae64     : 00000000`00000000 ffff9a0c`d9ade640 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
ffff9a0c`d9ade500 fffff801`04e7b76f     : ffff9a0c`d9adee08 ffff9a0c`d9ade500 ffff9e40`c629100f ffff9e11`88ccc800 : nt!KiOpDecode+0x10c
ffff9a0c`d9ade560 fffff801`04e7b1e1     : ffff9a0c`d9adee08 ffff9a0c`d9adeb40 ffff9a0c`d9ade640 00000000`0010005f : nt!KiPreprocessFault+0xbf
ffff9a0c`d9ade610 fffff801`04fefa6c     : ffff9a0c`d9adef30 00000000`00001000 ffff9a0c`d9adeeb0 ffff8000`00000000 : nt!KiDispatchException+0x141
ffff9a0c`d9adecd0 fffff801`04febc03     : ffff9a0c`d9adf040 00000260`d6f130a8 ffffffff`ffffffff fffff801`04e689c6 : nt!KiExceptionDispatch+0x12c
ffff9a0c`d9adeeb0 fffff801`04e7b710     : 00000000`00000001 ffff9a0c`d9adf3c0 ffffd683`5f118538 fffff801`04e2a730 : nt!KiPageFault+0x443
ffff9a0c`d9adf040 fffff801`04e7b1e1     : ffff9a0c`d9adfa58 ffff9a0c`d9adf790 00000000`0010005f 00000260`de411a4c : nt!KiPreprocessFault+0x60
ffff9a0c`d9adf0f0 fffff801`04fefa6c     : ffff9a0c`d9adfb80 00000000`00001000 ffff9a0c`d9adfb00 ffff8000`00000000 : nt!KiDispatchException+0x141
ffff9a0c`d9adf920 fffff801`04febc03     : ffffd683`5e1b7080 ffffd683`5f1c8ce0 00000000`00000000 ffff9a0c`d9adfb80 : nt!KiExceptionDispatch+0x12c
ffff9a0c`d9adfb00 00007ffb`fdf7d23e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x443
0000006d`9bcfe590 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`fdf7d23e


SYMBOL_NAME:  nt!MiUnlockPageTableInternal+b

IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  Unknown_Image

MODULE_NAME: Unknown_Module

FAILURE_BUCKET_ID:  RAISED_IRQL_USER_FAULT_AV

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1ae3b702-9567-a461-faae-d89b06459582}

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



DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff806494fa318, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6906

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8463

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

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

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff806494fa318

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffda8847b804f0 -- (.trap 0xffffda8847b804f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000005d2e1634 rbx=0000000000000000 rcx=ffffda8847b806f8
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80648a33397 rsp=ffffda8847b80680 rbp=ffffca800c75c180
 r8=ffffa204433f0730  r9=ffffa204436491c0 r10=7ffffffffffffffc
r11=ffffda8847b80848 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x17:
fffff806`48a33397 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  services.exe

STACK_TEXT: 
ffffca80`0c7aee18 fffff806`48c59472     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`494fa318 : nt!KeBugCheckEx
ffffca80`0c7aee20 fffff806`48aca2ed     : 00000109`1e52faf8 00000000`00000000 ffffda88`47b80500 ffffca80`0c75c180 : nt!KeAccumulateTicks+0x18bff2
ffffca80`0c7aee80 fffff806`48aca16a     : ffffa204`3b4c60e0 ffffda88`47b80570 ffffca80`00004d47 ffffca80`00000000 : nt!KeClockInterruptNotify+0xbd
ffffca80`0c7aef30 fffff806`48a08705     : ffffa204`3b4c60e0 fffff806`48b43b07 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffffca80`0c7aef60 fffff806`48bdf4ca     : ffffda88`47b80570 ffffa204`3b4c60e0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffca80`0c7aefb0 fffff806`48bdfa37     : ffffda88`47b806f8 ffffa204`43649080 00000000`00000082 fffff806`48bdfac4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffda88`47b804f0 fffff806`48a33397     : 00000000`00000010 00000000`00040286 ffffda88`47b806a8 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffda88`47b80680 fffff806`48a35bf8     : ffffa204`44def7f0 fffff806`48a25bbb ffffa204`44def080 00000000`00000000 : nt!KeYieldProcessorEx+0x17
ffffda88`47b806b0 fffff806`48a3354f     : ffffca80`0c75c180 00000000`5d2e1634 ffffa204`4364a180 ffffa204`43649080 : nt!KiSignalThread+0x1a8
ffffda88`47b806f0 fffff806`48a358ec     : 00000000`00000000 ffffda88`00000000 ffffa204`43524a80 ffffa204`44def080 : nt!KiWakeQueueWaiter+0xbf
ffffda88`47b80740 fffff806`48a2f2e5     : ffffda88`47b80930 00000000`00000000 ffffa204`435fb5a0 00000000`00000000 : nt!IoSetIoCompletionEx2+0x10c
ffffda88`47b807b0 fffff806`48e04326     : 00000000`00000000 ffffa204`44def508 4ae3e630`00000011 00000201`88ac95c8 : nt!AlpcpSignalAndWait+0x115
ffffda88`47b80850 fffff806`48e03f8b     : ffffda88`47b80930 00000201`88ac95c8 00000201`88cc8370 00000000`7e000000 : nt!AlpcpReceiveSynchronousReply+0x56
ffffda88`47b808b0 fffff806`48e02036     : ffffa204`43f51a80 00000000`00020000 00000201`88cc8370 00000201`88ac95c8 : nt!AlpcpProcessSynchronousRequest+0x37b
ffffda88`47b809d0 fffff806`48bef378     : ffffa204`44def080 ffffda88`47b80b80 00000070`cf07e0f8 ffffda88`47b80aa8 : nt!NtAlpcSendWaitReceivePort+0x1d6
ffffda88`47b80a90 00007ffb`de78bf04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000070`cf07e0d8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`de78bf04


SYMBOL_NAME:  nt!KeAccumulateTicks+18bff2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  18bff2

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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



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: ffffffff80000003, The exception code that was not handled
Arg2: fffff8070df31633, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: fffff8070dfb90c0, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 10624

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12939

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

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

BUGCHECK_P2: fffff8070df31633

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8070dfb90c0

EXCEPTION_PARAMETER2:  fffff8070dfb90c0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  SkypeApp.exe

STACK_TEXT: 
fffff28e`35257b78 fffff807`0e02edf9     : 00000000`0000001e ffffffff`80000003 fffff807`0df31633 00000000`00000000 : nt!KeBugCheckEx
fffff28e`35257b80 fffff807`0dfefa6c     : ffffffff`ffffffff fffff28e`00000032 fffff28e`35258340 00000000`00000120 : nt!KiDispatchException+0x1b3d59
fffff28e`35258240 fffff807`0dfe93d6     : 00000000`00000001 00000000`000000ff 00000000`00000000 02100050`00000000 : nt!KiExceptionDispatch+0x12c
fffff28e`35258420 fffff807`0df31634     : fffff28e`35258618 fffff28e`35258658 00000000`00000000 fffff28e`352586c0 : nt!KiBreakpointTrap+0x316
fffff28e`352585b0 fffff807`0dfb90fb     : fffff807`128708c2 fffff807`1283b6b8 00000000`00000000 00000000`00000000 : nt!KeCheckStackAndTargetAddress+0x54
fffff28e`352585e0 fffff807`0dfe68e2     : fffff807`1283b6b8 fffff28e`35258bc0 fffff807`12818dab 00000000`00000000 : nt!_C_specific_handler+0x3b
fffff28e`35258650 fffff807`0de32fb7     : fffff28e`35258bc0 00000000`00000000 fffff28e`35259800 fffff807`128708c2 : nt!RtlpExecuteHandlerForException+0x12
fffff28e`35258680 fffff807`0de7b226     : fffff28e`35259598 fffff28e`352592d0 fffff28e`35259598 00000000`00000004 : nt!RtlDispatchException+0x297
fffff28e`35258da0 fffff807`0dfefa6c     : fffff28e`352596c0 00000000`00001000 fffff28e`35259640 ffff8000`00000000 : nt!KiDispatchException+0x186
fffff28e`35259460 fffff807`0dfebc03     : ffffb98a`3cf726d0 00000000`00000008 fffff28e`35259780 fffff28e`35259788 : nt!KiExceptionDispatch+0x12c
fffff28e`35259640 00000000`00000000     : fffff28e`35259840 fffff28e`35259f01 00000000`00000000 00000000`00020410 : nt!KiPageFault+0x443


SYMBOL_NAME:  nt!KeCheckStackAndTargetAddress+53

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.264

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  53

FAILURE_BUCKET_ID:  0x1E_80000003_nt!KeCheckStackAndTargetAddress

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8bf4701b-5b4d-2023-a998-fc7dbbdaa46f}

Followup:     MachineOwner
---------
 
Artı 0 Eksi

Çok teşekkür ederim. Memtest'i yaptım herhangi bir sorun çıkmadı HD Tune Pro'da test yaptım onda da sorun yok anakartın tüm driverlarını indirdim sorun çözüldü gibi dün geceden beri mavi ekran almadım şükür. Ekran kartınada temiz kurulum yaptım sadece şimdilik sorun yok. Seviliyorsunuz Technopat <3.
Evet ilk defa mavi ekran verdi şimdi ekran kartı driverlarını dediğiniz gibi yapacağım bakalım olacak mı?
Ekran kartı sürücülerini tamamen kaldırdım ve tekrar kurdum şimdi inşallah tekrar bir sıkıntı çıkmaz teşekkür ederim.
 
Son düzenleme:
Artı 0 Eksi
Rica ederim. Şöyle 1-2 gün daha sistemi gözlemleyin, yine mavi ekran alırsanız yeni oluşan dosyaları atarsınız. Sorun çözülmüşse de belirtirseniz sevinirim.
 
Artı 0 Eksi
Bora Dere dedi:
Rica ederim. Şöyle 1-2 gün daha sistemi gözlemleyin, yine mavi ekran alırsanız yeni oluşan dosyaları atarsınız. Sorun çözülmüşse de belirtirseniz sevinirim.
Genişletmek için tıkla...

Tabi ki söylerim minidum dosyasının içini siliyim mi yoksa üstüne mi yazıyor çünkü 5 veya 6 dosya var mavi ekrandan sonra hiç artmıyor zaten genelde 2 şey yüzünden mavi ekran veriyor. Kernel Security check failure ile başlayan hata bir de IRQL_NOT_LESS_OR_EQUAL ile başlayan hata.
 
Artı 0 Eksi
Silmenize gerek yok. Mavi ekrandaki sayacın 100% olmasını bekleyin, sonra minidump klasöründe yeni oluşan dosyayı atın. Bu yine mavi ekran alırsanız yapacağınız şey tabii, şimdilik gerekli değil.
 
Artı 0 Eksi
Bora Dere dedi:
Silmenize gerek yok. Mavi ekrandaki sayacın 100% olmasını bekleyin, sonra minidump klasöründe yeni oluşan dosyayı atın. Bu yine mavi ekran alırsanız yapacağınız şey tabii, şimdilik gerekli değil.
Genişletmek için tıkla...
Tamamdır. Teşekkür ederim.
Tekrar aldım mavi ekran minidump bu. Minidump.rar
Genelde YouTube'den video izlerken alıyorum. Programlarda ve oyunlarda herhangi bir sorun olmuyor.

Sistemi de yazıyım;
Gigabyte 1660 Super 6G GV-N166SOC-6GD GTX 192 Bit GDDR6 6 GB ekran kartı.
AMD Ryzen 5 3600 altı çekirdek 3.60 GHz işlemci.
G.Skill Ripjaws V F4-3600C18D-16gvk 16 GB DDR4 3600 MHz CL18 RAM.
Kingston A2000 SSD .
Gigabyte B450M S2H anakart.
Şimdi bunu verdi ;

103120-9718-01.rar

drive.google.com
Bora Dere dedi:
Silmenize gerek yok. Mavi ekrandaki sayacın 100% olmasını bekleyin, sonra minidump klasöründe yeni oluşan dosyayı atın. Bu yine mavi ekran alırsanız yapacağınız şey tabii, şimdilik gerekli değil.
Genişletmek için tıkla...

Bakma şansınız oldu mu?
 
Son düzenleme:
Artı 0 Eksi
Mesajı düzenleyerek yazdığınız için bildirim gelmemiş, konuları gezerken gördüm.

Bu dosyalar biraz tuhaf oluşmuş. Tam emin olamamakla beraber sorunu ekran kartında görüyorum. Karta OC, fan hızı ayarı gibi bir şey yapmış mıydınız? Ek olarak CMD'yi yönetici olarak çalıştırıp sfc /scannow komutunu girin.
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

B
  • Soru
Windows 10 2004 mavi ekran hatası
2
Mesaj
10
Görüntüleme
782
Murat5038
B
  • Soru
Windows 10 2004 Mavi Ekran Hatası
Mesaj
1
Görüntüleme
425
Recep Baltaş
  • Soru
Windows 10 2004 Mavi ekran hatası
Mesaj
5
Görüntüleme
1.445
mitmustafa
  • Çözüldü
Çözüldü  Windows 10 2004 Mavi Ekran Hatası
Mesaj
2
Görüntüleme
690
IbrahimKY
K
  • Soru
Windows 10 sürüm 2004 mavi ekran hatası
2 3
Mesaj
27
Görüntüleme
1.781
KBGul22222
K
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…