R9 3900x 2080 sistemde mavi ekran hataları

İşletim sistemi
Windows 10

Zeffy Eibon

Hectopat
Katılım
2 Temmuz 2019
Mesajlar
20
RAM
Corsair Dominator Platinum 16x2 32 GB, CL 16 DDR4 - 3200Mhz
SSD veya HDD modeli
Sistemin kurulu olduğu Corsair MP510 480 GB
Ekran kartı
MSİ RTX 2080
Anakart
Gigabyte X570 Aorus Pro
İşlemci
R9 3900x
Merhaba arkadaşlar,
Sistemimin canı sıkkın iken ve ilgi istediği zaman verdiği bazı hatalar ve sıkıntılar var.

Genel olarak yaşadığım problemler;

XMP açıp RAM'leri 3200'e çektiğim zaman mavi ekran alma ya da PC'nin kendini tekrardan başlatma sıklığı artıyor, XMP kapatıp manuel olarak RAM'leri 3200'e çektiğim zaman daha nadir hata ve kapatma alıyorum ama yine de hata alıp RAM'ler kendilerini daha düşük bir frekansa çekip öyle çalışmaya devam ediyor.

RAM'lerin frekansı düştüğü zaman ise otomatik olarak basit sabit 144FPS almam gereken oyunlarda FPS düşüşleri yaşıyorum.

Windows'un RAM testi ve Memtest86 ile yaptığım testlerde bazen hiç hata bulamazken bazen de hata çıkıyor, tam olarak problemin ne olduğunu algılayamadım, net bir şey ortaya çıkınca ona göre garanti servisleri ile güreşmeye başlayacağım sanırım.

Bunlar için yardım rica ediyorum.

 
Sistemimin canı sıkkınken ve ilgi istediği zaman verdiği bazı hatalar ve sıkıntılar var.
Garanti servisleri ile güreşmeye başlayacağım sanırım.
😆


- RAM'leri tek tek denemeniz gerekebilir.
- Mesela birini sökün, diğeri takılı kalsın. XMP açın ve mavi ekran senaryolarını canlandırın.
- Daha sonra tam tersini diğer RAM için de yapın, gibi gibi.

- Ayrıca, Memtest86'yı XMP kapalıyken de yapmış mıydınız?
- Yapmadıysanız XMP kapatıp yapın bir de. Ama 2 RAM de takılı olsun.


8 Temmuz'daki mavi ekranı Corsair iCUE yazılımı açıkken almışsınız.
Kod:
PROCESS_NAME:  iCUE.exe

İyimser yaklaşarak hatanın bu yazılımdan kaynaklandığını varsayalım. Çünkü plakası alınmış, ofsayt yazılımlardan biri. Şimdilik bu yazılımı kaldırın.

4 Temmuz'daki mavi ekran donanımsal gibi görünüyor. İşlemciniz aşırı ısınıyor mu? Soğutucu bloğu düzgün hizalı mı? İşlemcide herhangi bir overclock var mıydı? Overclock / undervolt varsa geri alın, stabil olmayabilir.

3 Temmuz'daki mavi ekranda 3D Studio MAX programını görüyoruz. Ama mavi ekrana sebep olan programın bu olduğunu düşünmüyorum, bilgi olarak ekledim sadece. Bu programın güncellemesi varsa mutlaka yapın.
Kod:
PROCESS_NAME:  3dsmax.exe

28 Haziran'daki mavi ekran ise NVIDIA ekran kartı sürücüsü tarafından kaynaklanmış.


* BIOS eskimiş. F35 kullanıyorsunuz.
* F36 veya F37b sürümlerinden birine güncelleyebilirsiniz.


* BIOS güncellemesinden sonra BIOS'a girin ve "Load Optimized Defaults" yapın, kaydedin ve çıkın. Daha sonra tekrar BIOS'a girin ve ayarlarınızı yapın.


* Chipset sürücülerini de güncelleyin.
  • Denetim masası > Program ekle / kaldırdan "AMD Chipset Software" silin.
  • Aşağıdan güncel olanı indirin ama kurmayın.
  • İndirdikten sonra interneti kesin ve PC'yi yeniden başlatın.
  • PC açılınca yeni chipset sürücülerini kurun.
  • İnterneti bağlayabilirsiniz.

28 Haziran'daki NVIDIA sürücü problemine ithafen DDU ile temizlik önereceğim.

  • Güncel sürücüyü indirin: 536.40 WHQL
  • İnterneti kesin.
  • Daha sonra DDU ile Sürücü Kaldırma rehberini takip edin.
  • Sürücüyü kaldırdıktan sonra bilgisayar yeniden başlayacak.
  • Bilgisayar açılınca indirdiğiniz sürücüyü kurun.
  • İşlemler bitince interneti bağlayın.

Dökümler:
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffdb8c3a102880, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffffdb8c3a1027d8, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1796

    Key  : Analysis.Elapsed.mSec
    Value: 8334

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : FailFast.Name
    Value: STACK_COOKIE_CHECK_FAILURE

    Key  : FailFast.Type
    Value: 2

    Key  : Failure.Bucket
    Value: 0x139_MISSING_GSFRAME_win32kbase!_report_gsfailure

    Key  : Failure.Hash
    Value: {f22c2e43-4b0d-a5dc-7d6c-399075f6e217}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  139

BUGCHECK_P1: 2

BUGCHECK_P2: ffffdb8c3a102880

BUGCHECK_P3: ffffdb8c3a1027d8

BUGCHECK_P4: 0

FILE_IN_CAB:  070823-23093-01.dmp

TRAP_FRAME:  ffffdb8c3a102880 -- (.trap 0xffffdb8c3a102880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000dd900 rbx=0000000000000000 rcx=0000000000000002
rdx=0200000010000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffff9f626eccb835 rsp=ffffdb8c3a102a18 rbp=ffffdb8c3a102b20
 r8=0000084148d7d200  r9=ffff9f626ee4aea0 r10=0000fffff80614d6
r11=ffffbb7b3da00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32kbase!_report_gsfailure+0x5:
ffff9f62`6eccb835 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffffdb8c3a1027d8 -- (.exr 0xffffdb8c3a1027d8)
ExceptionAddress: ffff9f626eccb835 (win32kbase!_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:  iCUE.exe

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:
ffffdb8c`3a102558 fffff806`14e10029     : 00000000`00000139 00000000`00000002 ffffdb8c`3a102880 ffffdb8c`3a1027d8 : nt!KeBugCheckEx
ffffdb8c`3a102560 fffff806`14e10590     : 00000000`00000344 ffffa28a`a09c9080 ffffa28a`8e042080 000000c2`d45f95f0 : nt!KiBugCheckDispatch+0x69
ffffdb8c`3a1026a0 fffff806`14e0e55d     : ffffdb8c`3a102970 00000000`00000050 00000000`00000001 0000015a`e57731d0 : nt!KiFastFailDispatch+0xd0
ffffdb8c`3a102880 ffff9f62`6eccb835     : ffff9f62`6ec2e2d9 ffffa28a`980dabf0 00000000`00989680 00000000`00000001 : nt!KiRaiseSecurityCheckFailure+0x31d
ffffdb8c`3a102a18 ffff9f62`6ec2e2d9     : ffffa28a`980dabf0 00000000`00989680 00000000`00000001 ffffa28a`980dabf0 : win32kbase!_report_gsfailure+0x5
ffffdb8c`3a102a20 ffff9f62`6ec2dea8     : ffffa28a`980dabf0 ffff9f31`07229680 00000000`00000000 ffffa28a`980dabf0 : win32kbase!EtwTraceAcquiredExclusiveUserCrit+0x299
ffffdb8c`3a102c20 ffff9f62`6f57dcfb     : 00000000`0000000a 00000000`000104fc 00000096`2f2f7588 00000000`0000000a : win32kbase!EnterCrit+0xe8
ffffdb8c`3a102d40 00000000`0000000a     : 00000000`000104fc 00000096`2f2f7588 00000000`0000000a 00007ff7`00000000 : win32kfull+0x5dcfb
ffffdb8c`3a102d48 00000000`000104fc     : 00000096`2f2f7588 00000000`0000000a 00007ff7`00000000 00000000`00000000 : 0xa
ffffdb8c`3a102d50 00000096`2f2f7588     : 00000000`0000000a 00007ff7`00000000 00000000`00000000 00000000`00000001 : 0x104fc
ffffdb8c`3a102d58 00000000`0000000a     : 00007ff7`00000000 00000000`00000000 00000000`00000001 00000096`2f2f7788 : 0x00000096`2f2f7588
ffffdb8c`3a102d60 00007ff7`00000000     : 00000000`00000000 00000000`00000001 00000096`2f2f7788 ffffa28a`8e042080 : 0xa
ffffdb8c`3a102d68 00000000`00000000     : 00000000`00000001 00000096`2f2f7788 ffffa28a`8e042080 ffff9f62`6f03825f : 0x00007ff7`00000000


SYMBOL_NAME:  win32kbase!_report_gsfailure+5

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.3155

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  5

FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_win32kbase!_report_gsfailure

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f22c2e43-4b0d-a5dc-7d6c-399075f6e217}

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80030411cc9, Address of the instruction which caused the BugCheck
Arg3: ffff800b08e52fb0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1546

    Key  : Analysis.Elapsed.mSec
    Value: 4333

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: IP_MISALIGNED_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {716d112a-8330-4bbb-160c-ec98297019d2}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80030411cc9

BUGCHECK_P3: ffff800b08e52fb0

BUGCHECK_P4: 0

FILE_IN_CAB:  070423-20890-01.dmp

CONTEXT:  ffff800b08e52fb0 -- (.cxr 0xffff800b08e52fb0)
rax=ffffe5035d0fbe80 rbx=ffffd202d14e9e80 rcx=0000000000000804
rdx=00000000000003a0 rsi=00000000000007a0 rdi=ffffd202e200e0c0
rip=fffff80030411cc9 rsp=ffff800b08e539b0 rbp=ffff800b08e53b80
 r8=ffffe5035d0fa001  r9=ffffe50373511940 r10=0000fffff800304b
r11=ffff777833a00000 r12=ffff800b08e53b10 r13=0000000000000000
r14=0000000000000000 r15=ffffd202e8e4b080
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
nt!ObpReferenceObjectByHandleWithTag+0xf9:
fffff800`30411cc9 0000            add     byte ptr [rax],al ds:002b:ffffe503`5d0fbe80=87
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

MISALIGNED_IP:
nt!ObpReferenceObjectByHandleWithTag+f9
fffff800`30411cc9 0000            add     byte ptr [rax],al

STACK_TEXT:
ffff800b`08e539b0 fffff800`30411bbe     : ffffd202`e200e0c0 00000000`00000002 ffffd202`d14e9e80 00000000`00000001 : nt!ObpReferenceObjectByHandleWithTag+0xf9
ffff800b`08e53a40 fffff800`304b5004     : 00000000`000008b0 ffffd202`e8e4b080 00000000`18abf128 ffff800b`08e53aa8 : nt!ObReferenceObjectByHandle+0x2e
ffff800b`08e53a90 fffff800`3020f7f8     : 00000000`00002710 00000000`00000000 00000000`00000000 ffffd202`00000000 : nt!NtPulseEvent+0x64
ffff800b`08e53b00 00000000`77331cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`18abf108 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77331cfc


SYMBOL_NAME:  nt!ObpReferenceObjectByHandleWithTag+f9

IMAGE_VERSION:  10.0.19041.3155

STACK_COMMAND:  .cxr 0xffff800b08e52fb0 ; kb

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

FAILURE_BUCKET_ID:  IP_MISALIGNED_AuthenticAMD.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {716d112a-8330-4bbb-160c-ec98297019d2}

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


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8070b2baded, Address of the instruction which caused the BugCheck
Arg3: ffffd601b0b06920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1374

    Key  : Analysis.Elapsed.mSec
    Value: 3303

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: AV_nt!MiDeletePagablePteRange

    Key  : Failure.Hash
    Value: {bd740f0a-cd5e-1789-5a63-18d4c191cb91}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8070b2baded

BUGCHECK_P3: ffffd601b0b06920

BUGCHECK_P4: 0

FILE_IN_CAB:  070323-28750-01.dmp

CONTEXT:  ffffd601b0b06920 -- (.cxr 0xffffd601b0b06920)
rax=00000000ffffffff rbx=ffffc5875a5d6800 rcx=ffffc5875a5d6740
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000001
rip=fffff8070b2baded rsp=ffffe687310f4550 rbp=ffffe687310f4650
 r8=cfffffffffffffff  r9=ffff844200779980 r10=ffffc5875a5d6740
r11=ffff844221108fff r12=0000000000000000 r13=ffffe687310f48e8
r14=ffffc5875a5d6740 r15=ffff844200779980
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!MiDeletePagablePteRange+0x59d:
fffff807`0b2baded f08123ffffffbf  lock and dword ptr [rbx],0BFFFFFFFh ds:002b:ffffc587`5a5d6800=00000001
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  3dsmax.exe

STACK_TEXT:
ffffe687`310f4550 fffff807`0b27e830     : 00000000`00000001 ffffe687`00000000 ffffc587`5a5d6590 ffffc587`61fe3080 : nt!MiDeletePagablePteRange+0x59d
ffffe687`310f4860 fffff807`0b685e79     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x360
ffffe687`310f4970 fffff807`0b685c52     : ffffc587`53a39d20 00000000`00000000 ffffc587`5a5d60c0 00000000`00000000 : nt!MiUnmapVad+0x49
ffffe687`310f49a0 fffff807`0b685ac9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnmapViewOfSection+0x152
ffffe687`310f4a80 fffff807`0b68571c     : ffffc587`61fe3080 000001dd`ac11a730 000000a0`c71efff0 ffffc587`5a5d60c0 : nt!NtUnmapViewOfSectionEx+0x99
ffffe687`310f4ad0 fffff807`0b40f7f8     : 00000000`00000001 00000000`00000000 ffffe687`310f4b80 ffffc587`62760bd0 : nt!NtUnmapViewOfSection+0xc
ffffe687`310f4b00 00007fff`1b48d524     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000a0`c71efee8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`1b48d524


SYMBOL_NAME:  nt!MiDeletePagablePteRange+59d

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.3155

STACK_COMMAND:  .cxr 0xffffd601b0b06920 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  59d

FAILURE_BUCKET_ID:  AV_nt!MiDeletePagablePteRange

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {bd740f0a-cd5e-1789-5a63-18d4c191cb91}

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


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffce7c2c200000, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8025aea681d, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1468

    Key  : Analysis.Elapsed.mSec
    Value: 7592

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Failure.Bucket
    Value: AV_R_(null)_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f899ea14-805d-2454-345d-ba405310c43d}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  50

BUGCHECK_P1: ffffce7c2c200000

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8025aea681d

BUGCHECK_P4: 2

FILE_IN_CAB:  062823-13375-01.dmp

READ_ADDRESS: fffff80233afb390: 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
 ffffce7c2c200000

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff84842948b260 -- (.trap 0xffff84842948b260)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8025aea681d rsp=ffff84842948b3f0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=ffffce7c2c200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
nvlddmkm+0xfb681d:
fffff802`5aea681d 498b14d3        mov     rdx,qword ptr [r11+rdx*8] ds:ffffce7c`2c200000=????????????????
Resetting default scope

STACK_TEXT:
ffff8484`2948afb8 fffff802`3324af53     : 00000000`00000050 ffffce7c`2c200000 00000000`00000000 ffff8484`2948b260 : nt!KeBugCheckEx
ffff8484`2948afc0 fffff802`3306e7b0     : 00000000`00000102 00000000`00000000 ffff8484`2948b2e0 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffff8484`2948b0c0 fffff802`3320bad8     : 00000000`00000000 00000000`00000000 00000001`000de19c fffff802`5a89f6a0 : nt!MmAccessFault+0x400
ffff8484`2948b260 fffff802`5aea681d     : ffff9884`faa0e9d8 ffff9884`faa0ea60 ffff9885`0a8ba000 00000000`00000000 : nt!KiPageFault+0x358
ffff8484`2948b3f0 ffff9884`faa0e9d8     : ffff9884`faa0ea60 ffff9885`0a8ba000 00000000`00000000 00000000`00000000 : nvlddmkm+0xfb681d
ffff8484`2948b3f8 ffff9884`faa0ea60     : ffff9885`0a8ba000 00000000`00000000 00000000`00000000 fffff802`337b70b9 : 0xffff9884`faa0e9d8
ffff8484`2948b400 ffff9885`0a8ba000     : 00000000`00000000 00000000`00000000 fffff802`337b70b9 00000000`00000000 : 0xffff9884`faa0ea60
ffff8484`2948b408 00000000`00000000     : 00000000`00000000 fffff802`337b70b9 00000000`00000000 ffff9884`faa0ea60 : 0xffff9885`0a8ba000


SYMBOL_NAME:  nvlddmkm+fb681d

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  fb681d

FAILURE_BUCKET_ID:  AV_R_(null)_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f899ea14-805d-2454-345d-ba405310c43d}

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


- RAM'leri tek tek denemeniz gerekebilir.
- Mesela birini sökün, diğeri takılı kalsın. XMP açın ve mavi ekran senaryolarını canlandırın.
- Daha sonra tam tersini diğer RAM için de yapın, gibi gibi.

- Ayrıca, Memtest86'yı XMP kapalıyken de yapmış mıydınız?
- Yapmadıysanız XMP kapatıp yapın bir de. Ama 2 RAM de takılı olsun.


8 Temmuz'daki mavi ekranı Corsair iCUE yazılımı açıkken almışsınız.
Kod:
PROCESS_NAME:  iCUE.exe

İyimser yaklaşarak hatanın bu yazılımdan kaynaklandığını varsayalım. Çünkü plakası alınmış, ofsayt yazılımlardan biri. Şimdilik bu yazılımı kaldırın.

4 Temmuz'daki mavi ekran donanımsal gibi görünüyor. İşlemciniz aşırı ısınıyor mu? Soğutucu bloğu düzgün hizalı mı? İşlemcide herhangi bir overclock var mıydı? Overclock / undervolt varsa geri alın, stabil olmayabilir.

3 Temmuz'daki mavi ekranda 3D Studio MAX programını görüyoruz. Ama mavi ekrana sebep olan programın bu olduğunu düşünmüyorum, bilgi olarak ekledim sadece. Bu programın güncellemesi varsa mutlaka yapın.
Kod:
PROCESS_NAME:  3dsmax.exe

28 Haziran'daki mavi ekran ise NVIDIA ekran kartı sürücüsü tarafından kaynaklanmış.


* BIOS eskimiş. F35 kullanıyorsunuz.
* F36 veya F37b sürümlerinden birine güncelleyebilirsiniz.


* BIOS güncellemesinden sonra BIOS'a girin ve "Load Optimized Defaults" yapın, kaydedin ve çıkın. Daha sonra tekrar BIOS'a girin ve ayarlarınızı yapın.


* Chipset sürücülerini de güncelleyin.
  • Denetim masası > Program ekle / kaldırdan "AMD Chipset Software" silin.
  • Aşağıdan güncel olanı indirin ama kurmayın.
  • İndirdikten sonra interneti kesin ve PC'yi yeniden başlatın.
  • PC açılınca yeni chipset sürücülerini kurun.
  • İnterneti bağlayabilirsiniz.

28 Haziran'daki NVIDIA sürücü problemine ithafen DDU ile temizlik önereceğim.

  • Güncel sürücüyü indirin: 536.40 WHQL
  • İnterneti kesin.
  • Daha sonra DDU ile Sürücü Kaldırma rehberini takip edin.
  • Sürücüyü kaldırdıktan sonra bilgisayar yeniden başlayacak.
  • Bilgisayar açılınca indirdiğiniz sürücüyü kurun.
  • İşlemler bitince interneti bağlayın.

Dökümler:
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffdb8c3a102880, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffffdb8c3a1027d8, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1796

    Key  : Analysis.Elapsed.mSec
    Value: 8334

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : FailFast.Name
    Value: STACK_COOKIE_CHECK_FAILURE

    Key  : FailFast.Type
    Value: 2

    Key  : Failure.Bucket
    Value: 0x139_MISSING_GSFRAME_win32kbase!_report_gsfailure

    Key  : Failure.Hash
    Value: {f22c2e43-4b0d-a5dc-7d6c-399075f6e217}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  139

BUGCHECK_P1: 2

BUGCHECK_P2: ffffdb8c3a102880

BUGCHECK_P3: ffffdb8c3a1027d8

BUGCHECK_P4: 0

FILE_IN_CAB:  070823-23093-01.dmp

TRAP_FRAME:  ffffdb8c3a102880 -- (.trap 0xffffdb8c3a102880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000dd900 rbx=0000000000000000 rcx=0000000000000002
rdx=0200000010000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffff9f626eccb835 rsp=ffffdb8c3a102a18 rbp=ffffdb8c3a102b20
 r8=0000084148d7d200  r9=ffff9f626ee4aea0 r10=0000fffff80614d6
r11=ffffbb7b3da00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32kbase!_report_gsfailure+0x5:
ffff9f62`6eccb835 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffffdb8c3a1027d8 -- (.exr 0xffffdb8c3a1027d8)
ExceptionAddress: ffff9f626eccb835 (win32kbase!_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:  iCUE.exe

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:
ffffdb8c`3a102558 fffff806`14e10029     : 00000000`00000139 00000000`00000002 ffffdb8c`3a102880 ffffdb8c`3a1027d8 : nt!KeBugCheckEx
ffffdb8c`3a102560 fffff806`14e10590     : 00000000`00000344 ffffa28a`a09c9080 ffffa28a`8e042080 000000c2`d45f95f0 : nt!KiBugCheckDispatch+0x69
ffffdb8c`3a1026a0 fffff806`14e0e55d     : ffffdb8c`3a102970 00000000`00000050 00000000`00000001 0000015a`e57731d0 : nt!KiFastFailDispatch+0xd0
ffffdb8c`3a102880 ffff9f62`6eccb835     : ffff9f62`6ec2e2d9 ffffa28a`980dabf0 00000000`00989680 00000000`00000001 : nt!KiRaiseSecurityCheckFailure+0x31d
ffffdb8c`3a102a18 ffff9f62`6ec2e2d9     : ffffa28a`980dabf0 00000000`00989680 00000000`00000001 ffffa28a`980dabf0 : win32kbase!_report_gsfailure+0x5
ffffdb8c`3a102a20 ffff9f62`6ec2dea8     : ffffa28a`980dabf0 ffff9f31`07229680 00000000`00000000 ffffa28a`980dabf0 : win32kbase!EtwTraceAcquiredExclusiveUserCrit+0x299
ffffdb8c`3a102c20 ffff9f62`6f57dcfb     : 00000000`0000000a 00000000`000104fc 00000096`2f2f7588 00000000`0000000a : win32kbase!EnterCrit+0xe8
ffffdb8c`3a102d40 00000000`0000000a     : 00000000`000104fc 00000096`2f2f7588 00000000`0000000a 00007ff7`00000000 : win32kfull+0x5dcfb
ffffdb8c`3a102d48 00000000`000104fc     : 00000096`2f2f7588 00000000`0000000a 00007ff7`00000000 00000000`00000000 : 0xa
ffffdb8c`3a102d50 00000096`2f2f7588     : 00000000`0000000a 00007ff7`00000000 00000000`00000000 00000000`00000001 : 0x104fc
ffffdb8c`3a102d58 00000000`0000000a     : 00007ff7`00000000 00000000`00000000 00000000`00000001 00000096`2f2f7788 : 0x00000096`2f2f7588
ffffdb8c`3a102d60 00007ff7`00000000     : 00000000`00000000 00000000`00000001 00000096`2f2f7788 ffffa28a`8e042080 : 0xa
ffffdb8c`3a102d68 00000000`00000000     : 00000000`00000001 00000096`2f2f7788 ffffa28a`8e042080 ffff9f62`6f03825f : 0x00007ff7`00000000


SYMBOL_NAME:  win32kbase!_report_gsfailure+5

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.3155

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  5

FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_win32kbase!_report_gsfailure

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f22c2e43-4b0d-a5dc-7d6c-399075f6e217}

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80030411cc9, Address of the instruction which caused the BugCheck
Arg3: ffff800b08e52fb0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1546

    Key  : Analysis.Elapsed.mSec
    Value: 4333

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: IP_MISALIGNED_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {716d112a-8330-4bbb-160c-ec98297019d2}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80030411cc9

BUGCHECK_P3: ffff800b08e52fb0

BUGCHECK_P4: 0

FILE_IN_CAB:  070423-20890-01.dmp

CONTEXT:  ffff800b08e52fb0 -- (.cxr 0xffff800b08e52fb0)
rax=ffffe5035d0fbe80 rbx=ffffd202d14e9e80 rcx=0000000000000804
rdx=00000000000003a0 rsi=00000000000007a0 rdi=ffffd202e200e0c0
rip=fffff80030411cc9 rsp=ffff800b08e539b0 rbp=ffff800b08e53b80
 r8=ffffe5035d0fa001  r9=ffffe50373511940 r10=0000fffff800304b
r11=ffff777833a00000 r12=ffff800b08e53b10 r13=0000000000000000
r14=0000000000000000 r15=ffffd202e8e4b080
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
nt!ObpReferenceObjectByHandleWithTag+0xf9:
fffff800`30411cc9 0000            add     byte ptr [rax],al ds:002b:ffffe503`5d0fbe80=87
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

MISALIGNED_IP:
nt!ObpReferenceObjectByHandleWithTag+f9
fffff800`30411cc9 0000            add     byte ptr [rax],al

STACK_TEXT:
ffff800b`08e539b0 fffff800`30411bbe     : ffffd202`e200e0c0 00000000`00000002 ffffd202`d14e9e80 00000000`00000001 : nt!ObpReferenceObjectByHandleWithTag+0xf9
ffff800b`08e53a40 fffff800`304b5004     : 00000000`000008b0 ffffd202`e8e4b080 00000000`18abf128 ffff800b`08e53aa8 : nt!ObReferenceObjectByHandle+0x2e
ffff800b`08e53a90 fffff800`3020f7f8     : 00000000`00002710 00000000`00000000 00000000`00000000 ffffd202`00000000 : nt!NtPulseEvent+0x64
ffff800b`08e53b00 00000000`77331cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`18abf108 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77331cfc


SYMBOL_NAME:  nt!ObpReferenceObjectByHandleWithTag+f9

IMAGE_VERSION:  10.0.19041.3155

STACK_COMMAND:  .cxr 0xffff800b08e52fb0 ; kb

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

FAILURE_BUCKET_ID:  IP_MISALIGNED_AuthenticAMD.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {716d112a-8330-4bbb-160c-ec98297019d2}

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


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8070b2baded, Address of the instruction which caused the BugCheck
Arg3: ffffd601b0b06920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1374

    Key  : Analysis.Elapsed.mSec
    Value: 3303

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: AV_nt!MiDeletePagablePteRange

    Key  : Failure.Hash
    Value: {bd740f0a-cd5e-1789-5a63-18d4c191cb91}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8070b2baded

BUGCHECK_P3: ffffd601b0b06920

BUGCHECK_P4: 0

FILE_IN_CAB:  070323-28750-01.dmp

CONTEXT:  ffffd601b0b06920 -- (.cxr 0xffffd601b0b06920)
rax=00000000ffffffff rbx=ffffc5875a5d6800 rcx=ffffc5875a5d6740
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000001
rip=fffff8070b2baded rsp=ffffe687310f4550 rbp=ffffe687310f4650
 r8=cfffffffffffffff  r9=ffff844200779980 r10=ffffc5875a5d6740
r11=ffff844221108fff r12=0000000000000000 r13=ffffe687310f48e8
r14=ffffc5875a5d6740 r15=ffff844200779980
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!MiDeletePagablePteRange+0x59d:
fffff807`0b2baded f08123ffffffbf  lock and dword ptr [rbx],0BFFFFFFFh ds:002b:ffffc587`5a5d6800=00000001
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  3dsmax.exe

STACK_TEXT:
ffffe687`310f4550 fffff807`0b27e830     : 00000000`00000001 ffffe687`00000000 ffffc587`5a5d6590 ffffc587`61fe3080 : nt!MiDeletePagablePteRange+0x59d
ffffe687`310f4860 fffff807`0b685e79     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x360
ffffe687`310f4970 fffff807`0b685c52     : ffffc587`53a39d20 00000000`00000000 ffffc587`5a5d60c0 00000000`00000000 : nt!MiUnmapVad+0x49
ffffe687`310f49a0 fffff807`0b685ac9     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnmapViewOfSection+0x152
ffffe687`310f4a80 fffff807`0b68571c     : ffffc587`61fe3080 000001dd`ac11a730 000000a0`c71efff0 ffffc587`5a5d60c0 : nt!NtUnmapViewOfSectionEx+0x99
ffffe687`310f4ad0 fffff807`0b40f7f8     : 00000000`00000001 00000000`00000000 ffffe687`310f4b80 ffffc587`62760bd0 : nt!NtUnmapViewOfSection+0xc
ffffe687`310f4b00 00007fff`1b48d524     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000a0`c71efee8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`1b48d524


SYMBOL_NAME:  nt!MiDeletePagablePteRange+59d

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.3155

STACK_COMMAND:  .cxr 0xffffd601b0b06920 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  59d

FAILURE_BUCKET_ID:  AV_nt!MiDeletePagablePteRange

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {bd740f0a-cd5e-1789-5a63-18d4c191cb91}

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


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffce7c2c200000, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8025aea681d, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1468

    Key  : Analysis.Elapsed.mSec
    Value: 7592

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Failure.Bucket
    Value: AV_R_(null)_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f899ea14-805d-2454-345d-ba405310c43d}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  50

BUGCHECK_P1: ffffce7c2c200000

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8025aea681d

BUGCHECK_P4: 2

FILE_IN_CAB:  062823-13375-01.dmp

READ_ADDRESS: fffff80233afb390: 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
 ffffce7c2c200000

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff84842948b260 -- (.trap 0xffff84842948b260)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8025aea681d rsp=ffff84842948b3f0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=ffffce7c2c200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
nvlddmkm+0xfb681d:
fffff802`5aea681d 498b14d3        mov     rdx,qword ptr [r11+rdx*8] ds:ffffce7c`2c200000=????????????????
Resetting default scope

STACK_TEXT:
ffff8484`2948afb8 fffff802`3324af53     : 00000000`00000050 ffffce7c`2c200000 00000000`00000000 ffff8484`2948b260 : nt!KeBugCheckEx
ffff8484`2948afc0 fffff802`3306e7b0     : 00000000`00000102 00000000`00000000 ffff8484`2948b2e0 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffff8484`2948b0c0 fffff802`3320bad8     : 00000000`00000000 00000000`00000000 00000001`000de19c fffff802`5a89f6a0 : nt!MmAccessFault+0x400
ffff8484`2948b260 fffff802`5aea681d     : ffff9884`faa0e9d8 ffff9884`faa0ea60 ffff9885`0a8ba000 00000000`00000000 : nt!KiPageFault+0x358
ffff8484`2948b3f0 ffff9884`faa0e9d8     : ffff9884`faa0ea60 ffff9885`0a8ba000 00000000`00000000 00000000`00000000 : nvlddmkm+0xfb681d
ffff8484`2948b3f8 ffff9884`faa0ea60     : ffff9885`0a8ba000 00000000`00000000 00000000`00000000 fffff802`337b70b9 : 0xffff9884`faa0e9d8
ffff8484`2948b400 ffff9885`0a8ba000     : 00000000`00000000 00000000`00000000 fffff802`337b70b9 00000000`00000000 : 0xffff9884`faa0ea60
ffff8484`2948b408 00000000`00000000     : 00000000`00000000 fffff802`337b70b9 00000000`00000000 ffff9884`faa0ea60 : 0xffff9885`0a8ba000


SYMBOL_NAME:  nvlddmkm+fb681d

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  fb681d

FAILURE_BUCKET_ID:  AV_R_(null)_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f899ea14-805d-2454-345d-ba405310c43d}

Followup:     MachineOwner
---------
Cevap için teşekkür ederim.

Öncelikle icue yazılımını kaldırıp driver ve bios güncellemelerini yapacağım, daha sonra ramleri hem XMP açık şekilde 3200 MHZ'de ve stok değerlerinde test edip sonuçları paylaşacağım.

@EgeN7

Rapor veriyorum;

Güvenli modda ekran kartı sürücüsünü kaldırıp kendim tekrardan sıfırdan kurdum.
Chipset ve Bios güncellemelerini yaptım.
iCue yazılımını kaldırdım, artık onsuz yoluma devam ediyorum.

Isınma olayına da gelecek olursak;

Kasam Phantex Evolve X kasa içerisinde 2 Be quiet fan + 2 adet de Phantex'in kendi fanı mevcut, işlemciyi de NZXT kraken x72 ile soğutuyorum. 4.4 GHZ'de 50-55 derecede falan çalışıyor ama fanlar duruma göre RPM'i ayarla modunda olduğu için bazen kafa ağrıtıyor o yüzden işlemciyi belli bir MHZ'e sabitlediğimde ve işlemciyi maksimum kullanacak bir işlem yaptığımda ondan dolayı bazen öyle bir kapanma gerçekleşiyor.

Bununla alakalı aldığım son hata; Mini.rar

Şimdi gelelim RAM konusuna;

Ramleri 2000 MHZ'den 3200 MHZ'ye kadar aşağı yukarı tüm seçeneklerde denedim, XMP açık-kapalı şekilde 3000 MHZ'ye kadar yaptığım hiçbir testte hata almadım, bellekleri 3200Mhz'ye çektiğimde ise windows bellek testi programı donanımsal hata algıladı.

Yaklaşık 2-3 gündür XMP Açık şekilde 3000 Mhz'de kullanıyorum ve herhangi bir mavi ekran vb. sorun oluşmadı.
Tek karşılaştığım hata şu oldu; hava sıcak ve uzun zamandır kasayı temizlemediğim için kasaya bir bıcı bıcı yaptırayım dedim ve oturttum leğene, sağını solunu, bellekleri söktüm bir güzel temizledim, hazır açmışken işlemci macununu da tazeleyeyim dedim ve kasayı tekrar topladım.
Bilgisayar güç tuşuna bastığımda Anakart üzerinde DRAM ışığı yanacak şekilde çakılı kaldı, iki ramın yerlerini değiştirdikten sonra ( 2. ve 4. slot) normal bir şekilde açıldı ve şu an kullanmaya devam ediyorum.

Hastamızın durumu nedir? Yaşayacak mı? Eskisi gibi top oynayabilecek mi?

Şimdiden teşekkür ederim.
 
Son düzenleme:
Bununla alakalı aldığım son hata; Mini.rar
Bu yeni paylaştığınız arşivin içinde 070823-23093-01.dmp var, bunu zaten ilk mesajınızda da yüklemiştiniz.

Hastamızın durumu nedir? Yaşayacak mı? Eskisi gibi top oynayabilecek mi?
Bazen temizlikten sonra vs. bu tip olaylar olabiliyor. Ufak bir kir, toz veya buna benzer bir şey kontak noktasında iletimsel olarak bir engele yol açmış olabilir. Yerlerini değiştirdikten sonra çözüldüyse bir problem yok.
 

Geri
Yukarı