Çözüldü KERNEL_SECURITY_CHECK_FAILURE (139)

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Durum
Mesaj gönderimine kapalı.

PLAYDAAY

Centipat
Katılım
5 Mayıs 2022
Mesajlar
131
Daha fazla  
Cinsiyet
Erkek
Sanırım sıcaklık sebebi ile 3-4 kez mavi ekran aldım. Mavi ekranı bir kere oyun oynarken, bir kere premier pro kullanırken aldım.



Minidump dosyalarını aldım. Fakat nasıl bakacagımı veya ne yapmam gerektigini bilmiyorum.
 
Çözüm
  1. Armoury Crate ile sürücü yüklemekte bir sorun yok. Ama hepsini yüklemeye de gerek yok. Elle chipset sürücüsü ve ekran kartı sürücüsü yüklemek yeterli. Aygıt Yöneticisi altında soru işareti olan donanım yoksa sorun yok.
  2. Sadece XMP 1 devreye almanız yeterli.
Sistemde herhangi bir overclock var mı?


Buradan MEUpdateTool ile güncelleme yaptınız mı?

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: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd188d711f240, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffffd188d711f198, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2858

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 85010

    Key  : Analysis.IO.Other.Mb
    Value: 16

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 23

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x139

    Key  : Bugcheck.Code.Register
    Value: 0x139

    Key  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    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


FILE_IN_CAB:  020323-7718-01.dmp

BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd188d711f240

BUGCHECK_P3: ffffd188d711f198

BUGCHECK_P4: 0

TRAP_FRAME:  ffffd188d711f240 -- (.trap 0xffffd188d711f240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8d0584c0bde0 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8013a4db228 rsp=ffffd188d711f3d0 rbp=ffff8d0584b48030
 r8=ffff8d0573ce4640  r9=0000000000000000 r10=0000000000000002
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms2!VidSchDdiNotifyDpc+0x15958:
fffff801`3a4db228 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffffd188d711f198 -- (.exr 0xffffd188d711f198)
ExceptionAddress: fffff8013a4db228 (dxgmms2!VidSchDdiNotifyDpc+0x0000000000015958)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

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

EXCEPTION_STR:  0xc0000409

STACK_TEXT: 
ffffd188`d711ef18 fffff801`06e0e129     : 00000000`00000139 00000000`00000003 ffffd188`d711f240 ffffd188`d711f198 : nt!KeBugCheckEx
ffffd188`d711ef20 fffff801`06e0e690     : ffffd188`d711f202 fffff801`06cc70fa 00000000`00000000 ffff8d05`84b6e6d0 : nt!KiBugCheckDispatch+0x69
ffffd188`d711f060 fffff801`06e0c65d     : ffff8d05`84b6e658 ffff8d05`84b6e658 ffff8d05`84c0be90 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffd188`d711f240 fffff801`3a4db228     : 00000000`00000000 00000000`00989680 00000000`00000101 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x31d
ffffd188`d711f3d0 fffff801`1cd5d5d2     : ffffd188`d711f4c9 00000000`00000000 ffff8d05`7c024d88 00000490`59f1a737 : dxgmms2!VidSchDdiNotifyDpc+0x15958
ffffd188`d711f480 fffff801`2c9c50b1     : ffff8d05`7be6e030 00000000`00000000 ffff8d05`7be6e030 ffff8d05`7c022000 : dxgkrnl!DxgNotifyDpcCB+0x92
ffffd188`d711f530 ffff8d05`7be6e030     : 00000000`00000000 ffff8d05`7be6e030 ffff8d05`7c022000 fffff801`2c9c5036 : nvlddmkm+0x650b1
ffffd188`d711f538 00000000`00000000     : ffff8d05`7be6e030 ffff8d05`7c022000 fffff801`2c9c5036 ffff8d05`7c022000 : 0xffff8d05`7be6e030


SYMBOL_NAME:  dxgmms2!VidSchDdiNotifyDpc+15958

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.2311

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  15958

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!VidSchDdiNotifyDpc

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2680cc95-c3eb-4ecf-e7af-fb371282c295}

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80174c22d49, The address that the exception occurred at
Arg3: ffff958ee8736fb8, Exception Record Address
Arg4: ffff958ee87367f0, Context Record Address

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 2437

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 22312

    Key  : Analysis.IO.Other.Mb
    Value: 14

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 20

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1000007e

    Key  : Bugcheck.Code.Register
    Value: 0x7e

    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


FILE_IN_CAB:  013123-8015-01.dmp

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80174c22d49

BUGCHECK_P3: ffff958ee8736fb8

BUGCHECK_P4: ffff958ee87367f0

EXCEPTION_RECORD:  ffff958ee8736fb8 -- (.exr 0xffff958ee8736fb8)
ExceptionAddress: fffff80174c22d49 (nt!RtlSubtreePredecessor+0x0000000000000009)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000440000001c
Attempt to read from address 000000440000001c

CONTEXT:  ffff958ee87367f0 -- (.cxr 0xffff958ee87367f0)
rax=000000440000000c rbx=ffff850cf9485298 rcx=ffff850cf9485298
rdx=ffffabcae5705a2a rsi=ffffffffffffffff rdi=ffffabcae5705a2a
rip=fffff80174c22d49 rsp=ffff958ee87371f8 rbp=ffffffffffffffff
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80174c22b00
r11=000000000000049a r12=0000000000008000 r13=ffff958ee8737830
r14=ffffab83e5705a20 r15=00000000ffff7fff
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!RtlSubtreePredecessor+0x9:
fffff801`74c22d49 488b4810        mov     rcx,qword ptr [rax+10h] ds:002b:00000044`0000001c=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff801756fa390: 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
 000000440000001c

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000440000001c

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
ffff958e`e87371f8 fffff801`74c22bb4     : 00000000`00000706 ffff850c`f8252010 ffff958e`e8737830 00000000`00000000 : nt!RtlSubtreePredecessor+0x9
ffff958e`e8737200 fffff801`72e68b10     : 00000000`00000000 fffff801`74c7979e ffffab83`d89df040 ffffab83`e5705a08 : nt!RtlDeleteNoSplay+0xb4
ffff958e`e8737230 fffff801`72e9aa51     : ffffab83`e57059a0 ffffffff`00000000 ffff850c`00000000 ffffffff`ffffffff : FLTMGR!TreeUnlinkMulti+0x90
ffff958e`e8737280 fffff801`72e9abd8     : ffffab83`e57059a0 ffffab83`cf3f45a0 00000000`00000705 ffffffff`ffffffff : FLTMGR!DeleteNameCacheNodes+0xa1
ffff958e`e87372e0 fffff801`72e9b10a     : ffffab83`e57059a0 ffffab83`e57059a8 ffffab83`e57059a0 ffffab83`e57059a0 : FLTMGR!CleanupStreamListCtrl+0x80
ffff958e`e8737320 fffff801`74fd7139     : ffff850c`f82521a8 ffffab83`e57059a8 ffff850c`00000000 ffff958e`e8737830 : FLTMGR!DeleteStreamListCtrlCallback+0xba
ffff958e`e8737360 fffff801`791c25db     : ffff850c`f8252170 ffff958e`e87374a8 ffff958e`e8737830 00000000`00000703 : nt!FsRtlTeardownPerStreamContexts+0xc9
ffff958e`e87373a0 fffff801`791c2366     : ffff850c`f8252170 ffff850c`36b66d60 ffff850c`00000000 ffffab83`cf4195e0 : Ntfs!NtfsDeleteScb+0x17b
ffff958e`e8737440 fffff801`790a97b5     : ffff850c`f8252010 ffff850c`f8252170 ffff850c`f8252170 ffff850c`f8252170 : Ntfs!NtfsRemoveScb+0x66
ffff958e`e87374a0 fffff801`791c20fc     : ffff958e`e8737830 00000000`00000000 ffff850c`f8252010 ffffab83`cf418100 : Ntfs!NtfsPrepareFcbForRemoval+0x75
ffff958e`e87374e0 fffff801`790a8f76     : ffff958e`e8737830 ffff850c`f8252170 ffff850c`f8252528 ffff850c`f8252010 : Ntfs!NtfsTeardownStructures+0x9c
ffff958e`e8737560 fffff801`79184532     : ffff958e`e8737830 fffff801`79198fc0 00000000`00000000 ffffab83`00000000 : Ntfs!NtfsDecrementCloseCounts+0xf6
ffff958e`e87375c0 fffff801`7919a364     : ffff958e`e8737830 ffff850c`f8252170 ffff850c`f8252010 ffffab83`cf418180 : Ntfs!NtfsCommonClose+0xac2
ffff958e`e8737690 fffff801`79199048     : 00000000`0000001c fffff801`75724440 00000000`00000000 00000000`00000000 : Ntfs!NtfsFspCloseInternal+0x244
ffff958e`e87377f0 fffff801`74cbdef5     : ffffab83`d89df040 fffff801`7503aa30 ffffab83`c22aca20 ffffab83`00000000 : Ntfs!NtfsFspClose+0x88
ffff958e`e8737ab0 fffff801`74c55485     : ffffab83`d89df040 00000000`00000080 ffffab83`c22e7140 0043004f`00520050 : nt!ExpWorkerThread+0x105
ffff958e`e8737b50 fffff801`74e02cc8     : ffffd180`8ac00180 ffffab83`d89df040 fffff801`74c55430 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff958e`e8737ba0 00000000`00000000     : ffff958e`e8738000 ffff958e`e8731000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!RtlSubtreePredecessor+9

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2546

STACK_COMMAND:  .cxr 0xffff958ee87367f0 ; kb

BUCKET_ID_FUNC_OFFSET:  9

FAILURE_BUCKET_ID:  AV_nt!RtlSubtreePredecessor

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9c83f313-8194-6a8e-da2b-014e09f29178}

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: 000000006b54a4a1, memory referenced
Arg2: 00000000000000ff, 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: fffff80519d1bf8b, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1952

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10601

    Key  : Analysis.IO.Other.Mb
    Value: 14

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 20

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa

    Key  : Bugcheck.Code.Register
    Value: 0xa

    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


FILE_IN_CAB:  012923-8640-01.dmp

BUGCHECK_CODE:  a

BUGCHECK_P1: 6b54a4a1

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80519d1bf8b

READ_ADDRESS: fffff8051a6fa390: 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
 000000006b54a4a1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  checkBoardSupport.exe

TRAP_FRAME:  ffffcb846b549d50 -- (.trap 0xffffcb846b549d50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000f905f600 rbx=0000000000000000 rcx=000000006b54a4a1
rdx=fffff5fe01a00000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80519d1bf8b rsp=ffffcb846b549ee8 rbp=fffff8051a64f500
 r8=0000000000000000  r9=000000000000000e r10=fffff80519d1bec0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=2         nv dn di ng nz na pe nc
nt!MiAgePte+0xcb:
fffff805`19d1bf8b 0021            add     byte ptr [rcx],ah ds:00000000`6b54a4a1=??
Resetting default scope

MISALIGNED_IP:
nt!MiAgePte+cb
fffff805`19d1bf8b 0021            add     byte ptr [rcx],ah

STACK_TEXT: 
ffffcb84`6b549c08 fffff805`19e0e129     : 00000000`0000000a 00000000`6b54a4a1 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffcb84`6b549c10 fffff805`19e09ce3     : 0000007f`fffffff8 00000000`00000000 fffff5bf`fc13f138 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffcb84`6b549d50 fffff805`19d1bf8b     : fffff580`f91a1c70 ffffa900`04dd07e0 00000000`00000000 ffffcb84`6b54a3a0 : nt!KiPageFault+0x463
ffffcb84`6b549ee8 ffffcb84`6b54a4a0     : fffff5fe`01a00000 00000000`00000000 83000001`9f02a847 00000000`00000000 : nt!MiAgePte+0xcb
ffffcb84`6b549f88 fffff5fe`01a00000     : 00000000`00000000 83000001`9f02a847 00000000`00000000 00000000`00000000 : 0xffffcb84`6b54a4a0
ffffcb84`6b549f90 00000000`00000000     : 83000001`9f02a847 00000000`00000000 00000000`00000000 fffff5fe`01a00ff8 : 0xfffff5fe`01a00000


SYMBOL_NAME:  nt!MiAgePte+cb

IMAGE_VERSION:  10.0.19041.2546

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  GenuineIntel.sys

MODULE_NAME: GenuineIntel

FAILURE_BUCKET_ID:  IP_MISALIGNED_GenuineIntel.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e930d917-b247-3f7f-23cb-88a0c9f1b274}

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: 00000000000000d8, 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: fffff8032700b379, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2874

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 25786

    Key  : Analysis.IO.Other.Mb
    Value: 17

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 25

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa

    Key  : Bugcheck.Code.Register
    Value: 0xa

    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


FILE_IN_CAB:  020323-7453-01.dmp

BUGCHECK_CODE:  a

BUGCHECK_P1: d8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8032700b379

READ_ADDRESS: fffff80327afa390: 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
 00000000000000d8 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steamwebhelper.exe

TRAP_FRAME:  ffffe4003ee170d0 -- (.trap 0xffffe4003ee170d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00007ffa3466ff00 rbx=0000000000000000 rcx=0000000000005a4d
rdx=00007ffa34670000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803271363c5 rsp=ffffe4003ee17268 rbp=ffffe4003ee17550
 r8=0000000000000000  r9=ffffe4003ee172a8 r10=0000000000000000
r11=ffffab855a8d9ed0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlImageNtHeaderEx+0x35:
fffff803`271363c5 66390a          cmp     word ptr [rdx],cx ds:00007ffa`34670000=????
Resetting default scope

STACK_TEXT:  
ffffe400`3ee169e8 fffff803`2720e129     : 00000000`0000000a 00000000`000000d8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffe400`3ee169f0 fffff803`27209ce3     : 00000000`00000001 ffffab85`5edccc40 ffffe400`3ee16d68 ffffab85`368ffe18 : nt!KiBugCheckDispatch+0x69
ffffe400`3ee16b30 fffff803`2700b379     : 00007ffa`34670000 ffffab85`59f8e708 ffff94bf`fd1a3300 ffff94bf`fd1a3388 : nt!KiPageFault+0x463
ffffe400`3ee16cc0 fffff803`270a6f0b     : 00000000`00000001 ffff94bf`fd1a3380 00000000`00000000 ffffe400`3ee16e30 : nt!MiResolvePageFileFault+0x9d1
ffffe400`3ee16df0 fffff803`270a4af9     : 00000000`00000000 fffff803`00000003 00000000`c0000016 00000000`00000000 : nt!MiDispatchFault+0x72b
ffffe400`3ee16f30 fffff803`27209bd8     : ffffab85`57deb6d0 fffff803`2707995b ffffab85`57deb080 ffffab85`368ffe08 : nt!MmAccessFault+0x189
ffffe400`3ee170d0 fffff803`271363c5     : fffff803`2713637e 00000000`00000000 00000000`00000001 ffffd400`5db32270 : nt!KiPageFault+0x358
ffffe400`3ee17268 fffff803`2713637e     : 00000000`00000000 00000000`00000001 ffffd400`5db32270 00000000`00000000 : nt!RtlImageNtHeaderEx+0x35
ffffe400`3ee17270 fffff803`274ef394     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : nt!RtlImageNtHeader+0x1e
ffffe400`3ee172a0 fffff803`2746af22     : ffffe69e`0777f8a0 ffffe6cb`6fdc8b2c ffffab85`525db001 00000000`00000302 : nt!EtwpEnumerateAddressSpace+0x274
ffffe400`3ee17450 fffff803`274e63ba     : ffffab85`525db080 ffffab85`525db080 00000000`00000001 00000000`00000000 : nt!EtwTraceProcess+0x1be
ffffe400`3ee176e0 fffff803`274f131e     : ffffab85`57deb4b8 00000000`00000000 ffffe400`3ee178d0 00000000`00000000 : nt!PspExitProcess+0x4e
ffffe400`3ee17710 fffff803`27435cd8     : 00000000`c0000005 00000000`00000001 ffffe400`3ee17920 00000030`6424e000 : nt!PspExitThread+0x5b2
ffffe400`3ee17810 fffff803`27080ad7     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff803`270a70d6 : nt!KiSchedulerApcTerminate+0x38
ffffe400`3ee17850 fffff803`271ff4e0     : 00000000`00000000 ffffe400`3ee17900 ffffe400`3ee17ac0 00000000`00000000 : nt!KiDeliverApc+0x487
ffffe400`3ee17900 fffff803`2720d99f     : ffffab85`57deb080 ffffab85`58dd5460 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70
ffffe400`3ee17a40 00007ffa`3470d144     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
00000030`6484fa98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`3470d144


SYMBOL_NAME:  nt!MiResolvePageFileFault+9d1

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.2546

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  9d1

FAILURE_BUCKET_ID:  AV_nt!MiResolvePageFileFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {792a0b16-e499-d3be-c970-fb2f83008d00}

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

27: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.5, DMIVersion 0, Size=5940]
BiosMajorRelease = 8
BiosMinorRelease = 14
BiosVendor = American Megatrends Inc.
BiosVersion = 0814
BiosReleaseDate = 01/18/2023
SystemManufacturer = ASUS
SystemProductName = System Product Name
SystemFamily = To be filled by O.E.M.
SystemVersion = System Version
SystemSKU = SKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = ProArt Z790-CREATOR WIFI
BaseBoardVersion = Rev 1.xx
 
Sistemde overclock var mı bilmiyorum. Aldıgım firmadan BIOS güncellemesi ve ayarları yapılmış halde geldi. Ekstra bir şey yapmadım. BIOS güncellemesinde hata yaparsam bilgisayarda ciddi sorun olabilecegini biliyorum. Bilmedigim bir şeyi yapmaktan korktuğum için BIOS ayarları ve güncellemesi yapmadım.

AI Suite 3 programı kurulu ve veriler şu şekilde;
 

Dosya Ekleri

  • 1.jpg
    1.jpg
    144,6 KB · Görüntüleme: 51
  • 3.jpg
    3.jpg
    176,2 KB · Görüntüleme: 41
  • 4.jpg
    4.jpg
    145,3 KB · Görüntüleme: 61
  • 5.jpg
    5.jpg
    137,2 KB · Görüntüleme: 39
Son düzenleyen: Moderatör:
Sanırım sıcaklık sebebi ile 3-4 kez mavi ekran aldım. Mavi ekranı bir kere oyun oynarken, bir kere Premiere Pro kullanırken aldım.


Minidump dosyalarını aldım. Fakat nasıl bakacagımı veya ne yapmam gerektigini bilmiyorum.

Windows Update yapıldı mı?
Manuel olarak driver güncellemesi yaptınız mı? Yapıldıysa sistemle çakışacak bir driver kurmadığınızdan emin olun.
Dump dosyasına baktığımda kernel veri yapılarında kritik bir sorun olduğu söyleniyor, öte bir yandan bazı dosyaların doğrulanamadığından bahsetmiş ki bunları tekrar tekrar doğrulamaya çalışmış fakat sonuç çıkmayınca da mavi ekran vermiş olabilir. Öte yandan okuduklarıma göre sisteme fazla yük binildiğinden olabildiği söyleniyor 0x139 hatasına baktığımda. Ya da Windows dosyaları bozuk olabilir.
 
Armoury Crate isimli program bilgisayara Windows kurduktan sonra kurdum ve bütün driverları kendisi yükledi. Manuel olarak driver kurmadım. Program içinde bütün driverların kurulabildigi bir düzen ile geliyor. Kendisi hepsini kuruyor. Ekstra olarak kurmam gereken driverlar varsa kurabilirim ama bunların hangileri oldugunu bilmiyorum.
 
Son düzenleyen: Moderatör:
Armoury Crate isimli program bilgisayara Windows kurduktan sonra kurdum ve bütün driverları kendisi yükledi. Manuel olarak driver kurmadım. Program içinde bütün driverların kurulabildigi bir düzen ile geliyor. Kendisi hepsini kuruyor. Ekstra olarak kurmam gereken driverlar varsa kurabilirim ama bunların hangileri oldugunu bilmiyorum.

K. B deprem bölgesinde olduğum için geç cevap verebiliyorum. Otomatik driver güncellemesi yapan programlar genelde sıkıntılıdır bunun yerine driverları manuel olarak güncellemenizi tavsiye ederim. İndirdiğiniz programlardan biri sistemle uyumlu olmadığından vermiş olabilir. BIOS güncellemeyi de unutmayın.
 
Son düzenleyen: Moderatör:
Armoury Crate sıradan bir sürücü güncelleme aracı değil. Sorunun donanımsal olduğunu düşünüyorum ben açıkçası.

Oyunlarda BSOD almaya devam ederseniz sistemi veya ekran kartını bir servise vermeniz gerekebilir.
 
BIOS'a gir ve optimize defults save yap. Tüm ASUS araçlarını sil. Logitech araçlarını sil ve ben söylene kadar yükleme. Ağ kartı ve ses sürücünü güneclle.
NVIDIA ekarn kartı sürücünü Imzamdaki rehbere göre sil ve güncel sürücüyü indir yükle.
Ayrıca imzadaki rehbere göre disk testi yap.
 
Son düzenleyen: Moderatör:
Öncelikle ilginiz için çok teşekkür ederim.

1-İlk olarak dist testi yapmak rehberinden programları indirdim ve testlerimi yaptım. 1 tanesi açılmadı bende onun yerine Samsung'un kendi SSD test sistemi ile testleri resim olarak ekledim.
2-Denetim Masası'ndan ASUS yazılı bütün programları kaldırdım. Logitech G HUB uygulamasını sildim.
3-Ekran kartı sürücü kaldırma rehberindeki programı kurdum ve yazıldıgı şekli ile hepsini kaldırdım.
4-BIOS ayarlarına gittim ve var olan ayarları Auto yaptım hepsini. Zaten pek seçenegim yoktu. Bunları da resim olarak bu ileti altında paylaşıyorum.

Şimdi ASUS, NVIDIA sürücüleri silindi. BIOS ayarları Auto olarak duruyor. Disk testleri yapıldı.

Bundan sonra hangi işlemleri sırası ile yapmalıyım?

İletiye cevap verene kadar herhangi bir işlem yapmıyorum. Yönlendirmenize göre işlemleri devam etmek istiyorum.
 

Dosya Ekleri

  • 1.jpg
    1.jpg
    306,4 KB · Görüntüleme: 17
  • 2.jpg
    2.jpg
    676,9 KB · Görüntüleme: 30
  • 3.jpg
    3.jpg
    175,9 KB · Görüntüleme: 15
  • 4.jpg
    4.jpg
    209,6 KB · Görüntüleme: 16
  • 5.jpg
    5.jpg
    138,9 KB · Görüntüleme: 29
  • 6.jpg
    6.jpg
    210,6 KB · Görüntüleme: 27
  • 7.jpg
    7.jpg
    159,3 KB · Görüntüleme: 25
  • 8.jpg
    8.jpg
    189,8 KB · Görüntüleme: 26
  • 9.jpg
    9.jpg
    237 KB · Görüntüleme: 23
  • 329324135_1378382562955755_8436868571076890790_n.jpg
    329324135_1378382562955755_8436868571076890790_n.jpg
    280,5 KB · Görüntüleme: 23
  • 330112864_914622459974742_1757905983434437857_n.jpg
    330112864_914622459974742_1757905983434437857_n.jpg
    285,5 KB · Görüntüleme: 11
  • 330261918_931551691525525_6692966832097795048_n.jpg
    330261918_931551691525525_6692966832097795048_n.jpg
    267,2 KB · Görüntüleme: 36
  • 330415229_1618990338617162_6342865910626848881_n.jpg
    330415229_1618990338617162_6342865910626848881_n.jpg
    251,6 KB · Görüntüleme: 23
  • 330453415_889048412144990_7277394671959251744_n.jpg
    330453415_889048412144990_7277394671959251744_n.jpg
    275 KB · Görüntüleme: 19
  • 330578616_5953625664706791_5033874570220646830_n.jpg
    330578616_5953625664706791_5033874570220646830_n.jpg
    234,7 KB · Görüntüleme: 24
  • 330588033_6204887136190942_6856931757546204730_n.jpg
    330588033_6204887136190942_6856931757546204730_n.jpg
    268,5 KB · Görüntüleme: 44
Son düzenleyen: Moderatör:
Durum
Mesaj gönderimine kapalı.

Geri
Yukarı