RAM takviyesi sonrası donma ve mavi ekran sorunları

0nurGS

Hectopat
Katılım
17 Aralık 2019
Mesajlar
131
Arkadaşlar merhaba,

Yaklaşık 2 ay önce bir sistem topladım. Sistemimi ilk başta 1*8 GB RAM olarak kullanıyordum fakat oyun performansı yetersiz olduğu için bir ay önce bir tane daha aynı RAM'den aldım ve 2*8 GB olarak kullanmaya başladım.

Ancak ne olduysa o günden sonra olmaya başladı.

Günlük kullanımda; sebebini anlamadığım mavi ekran hataları, oyundayken siyah ekranlar, mavi ekranlar veya oyundan atmalar başladı.

Hal böyle olunca memtest ve Windows Memory Diagnostic Test'i yaptım, ikisi de hata bulmadı. Hatta iki RAM'i de iki ayrı slotta ayrı ayrı test ettim (toplamda 6 test yaptım) yine sorun bulmadı. Ama aldığım mavi ekran hataları genellikle MEMORY_CORRUPTION hatalarıydı. Buraya eğer ki incelemek isterseniz diye DMP dosyalarımı bırakıyorum. Sorun büyük ihtimalle RAM'lerde fakat dün ekran kartı driverımda sorun olabileceğini düşünerek DDU ile kaldırıp tekrardan kurdum. PC yaklaşık 24 saattir açık olmasına ve 2 saat oyun oynamama rağmen henüz herhangi bir sorunla karşılaşmadım (normalde bu kadar sürede en az 2-3 kere karşılaşırdım). Sorunum şu an çözüldü mü çözülmedeğil mi bilmiyorum. Ekran kartı driveri böyle bir soruna neden olabilir mi? Eğer ki RAM'den kaynaklıysa Dual kit RAM almadığım için normal diyeceksiniz ancak epey araştırdım ve benim gibi neredeyse saat başı mavi ekran alacak kadar sorun yaşayanını görmedim.

  • Ryzen 5 2600.
  • B450M S2H.
  • RX 590 Nitro+.
  • VS550 PSU.
  • 2*8 Vengeance 3000 MHz CL 16 (2. RAM sonradan eklenen. İkisi de aynı RAM ve versiyon numaraları aynı.)
 
Bellekleri 2133MHz'e çekip mavi ekran alıyor musun kontrol eder misin?
Kod:
  Speed                         3000MHz
  Manufacturer                  Unknown
  Serial Number                       
  Asset Tag Number              [String Not Specified]
  Part Number                   CMK8GX4M1D3000C16

İki belleğinde bu program ile bilgisini paylaşır mısın?
Kod:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003472, The subtype of the bugcheck.
Arg2: ffff9e09af52c000
Arg3: 0000000000000000
Arg4: 91726a8cabf985b2

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F50

BIOS_DATE:  11/27/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 3472

BUGCHECK_P2: ffff9e09af52c000

BUGCHECK_P3: 0

BUGCHECK_P4: 91726a8cabf985b2

BUGCHECK_STR:  0x1a_3472

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-13-2020 21:20:01.0451

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff8040422210f to fffff804041c14e0

STACK_TEXT:
ffff9e09`aa53f9a8 fffff804`0422210f : 00000000`0000001a 00000000`00003472 ffff9e09`af52c000 00000000`00000000 : nt!KeBugCheckEx
ffff9e09`aa53f9b0 fffff804`040a7d55 : ffff9e09`aa53fa08 00000000`00000000 fffff804`04468940 fffff804`04468618 : nt!MiDeleteCachedKernelStack+0x179ef3
ffff9e09`aa53f9f0 fffff804`040a8d7e : fffff804`0446a400 00000000`ffffffff 00000000`00000001 ffffe08a`3e644010 : nt!MiAdjustCachedStacks+0x115
ffff9e09`aa53fa30 fffff804`042ca1b6 : 00000000`00000001 00000000`00000004 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xe6
ffff9e09`aa53faf0 fffff804`0418bb65 : 00000000`00000004 00000000`ffffffff fffff804`0446a400 00000000`00000462 : nt!MmWorkingSetManager+0x12
ffff9e09`aa53fb20 fffff804`0412a7a5 : ffffe08a`3e77e080 00000000`00000080 fffff804`0418ba10 f9834100`000130e9 : nt!KeBalanceSetManager+0x155
ffff9e09`aa53fc10 fffff804`041c8b2a : ffff9f80`9ded7180 ffffe08a`3e77e080 fffff804`0412a750 df450f48`f7450fde : nt!PspSystemThreadStartup+0x55
ffff9e09`aa53fc60 00000000`00000000 : ffff9e09`aa540000 ffff9e09`aa53a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  2a6e1e7c3f05b7fccdf590eb5641fc73927155d1

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  bde3fd6008aeadb362a2b4022a797119636f73bc

THREAD_SHA1_HASH_MOD:  cb5f414824c2521bcc505eaa03e92fa10922dad8

FOLLOWUP_IP:
nt!MiDeleteCachedKernelStack+179ef3
fffff804`0422210f cc              int     3

FAULT_INSTR_CODE:  ca3b4dcc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiDeleteCachedKernelStack+179ef3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  29371fe3

IMAGE_VERSION:  10.0.18362.628

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  179ef3

FAILURE_BUCKET_ID:  0x1a_3472_nt!MiDeleteCachedKernelStack

BUCKET_ID:  0x1a_3472_nt!MiDeleteCachedKernelStack

PRIMARY_PROBLEM_CLASS:  0x1a_3472_nt!MiDeleteCachedKernelStack

TARGET_TIME:  2020-02-12T11:43:24.000Z

OSBUILD:  18362

OSSERVICEPACK:  628

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1991-11-30 08:21:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  1b8b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_3472_nt!mideletecachedkernelstack

FAILURE_ID_HASH:  {a80c19df-5367-4436-078a-4b8662f56789}

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000003a835b, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0400022000228d5a, 0

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F50

BIOS_DATE:  11/27/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 99

BUGCHECK_P2: 3a835b

BUGCHECK_P3: 2

BUGCHECK_P4: 400022000228d5a

BUGCHECK_STR:  0x4E_99

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  win10-64bit-radeon-software-adrenalin-2019-edition

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-13-2020 21:19:57.0859

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80442c14a4f to fffff80442bc14e0

STACK_TEXT:
fffffd06`b5c6f158 fffff804`42c14a4f : 00000000`0000004e 00000000`00000099 00000000`003a835b 00000000`00000002 : nt!KeBugCheckEx
fffffd06`b5c6f160 fffff804`42a0f295 : ffffe283`dd62a038 ffffe283`0000002c ffffe283`dd62b011 00000003`a785e8c0 : nt!MiDecrementShareCount+0x190b4f
fffffd06`b5c6f1a0 fffff804`42fd5c6f : ffff820c`bdf40000 ffffbc80`2121d0b0 00000000`00000000 00000000`00000000 : nt!MmUnmapViewInSystemCache+0x9f5
fffffd06`b5c6f2b0 fffff804`42a0b6b2 : 00000000`10e80000 ffffe283`eb08f9a0 ffffe283`ecb43e80 00000000`00000001 : nt!CcUnmapVacb+0x63
fffffd06`b5c6f2f0 fffff804`42a7e9db : 00000000`10f00001 ffffe283`dd5f2a80 00000000`10700000 00000000`00000001 : nt!CcUnmapVacbArray+0x202
fffffd06`b5c6f360 fffff804`4301ef29 : 00000000`00000000 00000000`00000000 fffffd06`b5c6f4a0 fffffd06`b5c6f4b0 : nt!CcGetVirtualAddress+0x40b
fffffd06`b5c6f400 fffff804`42a7deb5 : 00000000`00000000 00000000`10f00000 00000000`000035e4 00000000`00000001 : nt!CcMapAndCopyFromCache+0x79
fffffd06`b5c6f4a0 fffff804`46e7a68d : fffffd06`b5c6f5f0 00000000`00000000 ffffbc80`00004000 00000000`00004000 : nt!CcCopyReadEx+0x135
fffffd06`b5c6f540 fffff804`462e5f77 : 00000000`00000000 00000000`000002b0 ffffe283`dd7c9540 00000000`00000000 : Ntfs!NtfsCopyReadA+0x2ed
fffffd06`b5c6f830 fffff804`462e2fa3 : fffffd06`b5c6f920 00000000`00000000 00000000`00000000 ffffe283`efdee010 : FLTMGR!FltpPerformFastIoCall+0x197
fffffd06`b5c6f890 fffff804`4631c7c5 : fffffd06`b5c6f9f8 fffffd06`b5c6fb80 ffffe283`eeff0080 ffffe283`edb963b0 : FLTMGR!FltpPassThroughFastIo+0xd3
fffffd06`b5c6f8f0 fffff804`42fe55bf : ffffe283`edb963b0 00000000`00000000 00000000`00000000 ffffe283`00000000 : FLTMGR!FltpFastIoRead+0x165
fffffd06`b5c6f9a0 fffff804`42bd2d18 : ffffe283`eeff0080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x39f
fffffd06`b5c6fa90 00000000`77451cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0580f308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77451cbc


THREAD_SHA1_HASH_MOD_FUNC:  27e7a13295b8a0ef7939fb582bc7a02757ea0a61

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b8e25005e3cdc9c318158a90e2b38c1b5be0000f

THREAD_SHA1_HASH_MOD:  e1ba9cfcf25ede23ae6417a3f58a65d04badb60a

FOLLOWUP_IP:
nt!MiDecrementShareCount+190b4f
fffff804`42c14a4f cc              int     3

FAULT_INSTR_CODE:  b848cc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiDecrementShareCount+190b4f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  29371fe3

IMAGE_VERSION:  10.0.18362.628

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  190b4f

FAILURE_BUCKET_ID:  0x4E_99_nt!MiDecrementShareCount

BUCKET_ID:  0x4E_99_nt!MiDecrementShareCount

PRIMARY_PROBLEM_CLASS:  0x4E_99_nt!MiDecrementShareCount

TARGET_TIME:  2020-02-12T10:58:02.000Z

OSBUILD:  18362

OSSERVICEPACK:  628

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1991-11-30 08:21:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  6876

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x4e_99_nt!midecrementsharecount

FAILURE_ID_HASH:  {add373c4-2fe4-723e-d1db-12fcb6adef02}

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

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F50

BIOS_DATE:  11/27/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80129048e17

BUGCHECK_P3: ffff928f3a621d60

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP:
nt!CmpNotifyChangeKey+e7
fffff801`29048e17 8b4808          mov     ecx,dword ptr [rax+8]

CONTEXT:  ffff928f3a621d60 -- (.cxr 0xffff928f3a621d60)
rax=0000000000000000 rbx=ffff9b0a27f8c000 rcx=0000000000000009
rdx=ffff9b0a3fce4630 rsi=ffff9b0a45eb53c0 rdi=0000000010000005
rip=fffff80129048e17 rsp=ffff928f3a622750 rbp=ffff9b0a2ae80370
r8=000000000000000a  r9=ffff928f3a622750 r10=ffff800112f00000
r11=ffff928f3a622748 r12=0000000000000001 r13=0000000000000000
r14=ffff9b0a4ae15a80 r15=ffff9b0a45eb53c0
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!CmpNotifyChangeKey+0xe7:
fffff801`29048e17 8b4808          mov     ecx,dword ptr [rax+8] ds:002b:00000000`00000008=????????
Resetting default scope

BUGCHECK_STR:  0x3B_c0000005

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-13-2020 21:19:53.0758

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80129048706 to fffff80129048e17

STACK_TEXT:
ffff928f`3a622750 fffff801`29048706 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9b0a`2ae80378 : nt!CmpNotifyChangeKey+0xe7
ffff928f`3a622800 fffff801`29044db0 : 00000000`0110e798 ffff928f`3a622b80 00000000`00000001 00000000`0110e798 : nt!NtNotifyChangeMultipleKeys+0x296
ffff928f`3a622a20 fffff801`28bd2d18 : ffffc28a`687ad080 00000000`0110e778 ffff928f`3a622aa8 00007ffe`ab314060 : nt!NtNotifyChangeKey+0x60
ffff928f`3a622a90 00007ffe`ad79e334 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0110e768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`ad79e334


THREAD_SHA1_HASH_MOD_FUNC:  f4a1ebb62142f4b4f6bbad64c6028d8395bcebac

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  74a7c1058c20472d777ee494242c72643285ef75

THREAD_SHA1_HASH_MOD:  d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP:
nt!CmpNotifyChangeKey+e7
fffff801`29048e17 8b4808          mov     ecx,dword ptr [rax+8]

FAULT_INSTR_CODE:  c108488b

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpNotifyChangeKey+e7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  29371fe3

IMAGE_VERSION:  10.0.18362.628

STACK_COMMAND:  .cxr 0xffff928f3a621d60 ; kb

BUCKET_ID_FUNC_OFFSET:  e7

FAILURE_BUCKET_ID:  0x3B_c0000005_nt!CmpNotifyChangeKey

BUCKET_ID:  0x3B_c0000005_nt!CmpNotifyChangeKey

PRIMARY_PROBLEM_CLASS:  0x3B_c0000005_nt!CmpNotifyChangeKey

TARGET_TIME:  2020-02-11T15:19:55.000Z

OSBUILD:  18362

OSSERVICEPACK:  628

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1991-11-30 08:21:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  422f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_c0000005_nt!cmpnotifychangekey

FAILURE_ID_HASH:  {52772d46-f7c5-1283-1d01-700d2f26b844}

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fc0e59868d58f, Reserved
Arg2: 0000000000000000, Reserved
Arg3: af53e0eca199f1e4, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F50

BIOS_DATE:  11/27/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: a39fc0e59868d58f

BUGCHECK_P2: 0

BUGCHECK_P3: af53e0eca199f1e4

BUGCHECK_P4: 101

PG_MISMATCH:  400000000000

MEMORY_CORRUPTOR:  ONE_BIT

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x109

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-13-2020 21:19:49.0331

ANALYSIS_VERSION: 10.0.18362.1 x86fre

STACK_TEXT:
ffffb600`08ec2e98 00000000`00000000 : 00000000`00000109 a39fc0e5`9868d58f 00000000`00000000 af53e0ec`a199f1e4 : nt!KeBugCheckEx


THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT

TARGET_TIME:  2020-02-10T17:28:49.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  2a4a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_one_bit

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

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

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: 000000000000001d, Type of memory safety violation
Arg2: fffffb89082ecfc0, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffffb89082ecf18, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  B450M S2H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F50

BIOS_DATE:  11/27/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  B450M S2H

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 1d

BUGCHECK_P2: fffffb89082ecfc0

BUGCHECK_P3: fffffb89082ecf18

BUGCHECK_P4: 0

TRAP_FRAME:  fffffb89082ecfc0 -- (.trap 0xfffffb89082ecfc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe38f054822b0 rbx=0000000000000000 rcx=000000000000001d
rdx=ffffe38f05485810 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80658be9ea7 rsp=fffffb89082ed150 rbp=ffffe38f054822b0
r8=ffffe38f05486850  r9=0000000000000000 r10=ffffe38f05485810
r11=ffffe38f054862b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!RtlAvlRemoveNode+0x1d1ff7:
fffff806`58be9ea7 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffffb89082ecf18 -- (.exr 0xfffffb89082ecf18)
ExceptionAddress: fffff80658be9ea7 (nt!RtlAvlRemoveNode+0x00000000001d1ff7)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 000000000000001d
Subcode: 0x1d FAST_FAIL_INVALID_BALANCED_TREE

CPU_COUNT: c

CPU_MHZ: d42

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x139

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

DEFAULT_BUCKET_ID:  FAIL_FAST_INVALID_BALANCED_TREE

ERROR_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  000000000000001d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-13-2020 21:19:47.0195

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff80658bd32e9 to fffff80658bc14e0

STACK_TEXT:
fffffb89`082ecc98 fffff806`58bd32e9 : 00000000`00000139 00000000`0000001d fffffb89`082ecfc0 fffffb89`082ecf18 : nt!KeBugCheckEx
fffffb89`082ecca0 fffff806`58bd3710 : 00000001`ffffff00 00000000`00000000 00000002`00000003 fffff806`00000000 : nt!KiBugCheckDispatch+0x69
fffffb89`082ecde0 fffff806`58bd1aa5 : 00000000`00000000 00000000`00000000 00000000`00000000 00001f80`00ff00ff : nt!KiFastFailDispatch+0xd0
fffffb89`082ecfc0 fffff806`58be9ea7 : ffffe38f`05484d70 00000000`00000001 00000000`00000000 fffff806`58d6f0a9 : nt!KiRaiseSecurityCheckFailure+0x325
fffffb89`082ed150 fffff806`590f0830 : 00000000`00000000 fffffb89`082ed259 00000000`00000001 ffffe38f`05485a40 : nt!RtlAvlRemoveNode+0x1d1ff7
fffffb89`082ed1a0 fffff806`590f0d9e : 00000000`00000080 00000000`00000000 00000000`00000000 ffffa080`0c5da7d0 : nt!MiProcessCrcList+0x570
fffffb89`082ed2c0 fffff806`590f3912 : 00000000`00000000 00000000`00000000 fffffb89`082ed4e0 00000000`00000000 : nt!MiCombineAllPhysicalMemory+0x30e
fffffb89`082ed3e0 fffff806`58ffffcd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiCombineIdenticalPages+0x20e
fffffb89`082ed650 fffff806`58bd2d18 : ffffe38f`074eb080 000000b2`85f4a000 fffffb89`082edb80 ffffe38f`01c40c60 : nt!NtSetSystemInformation+0x5dd
fffffb89`082edb00 00007ffa`814df534 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000b2`863ffa38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`814df534


THREAD_SHA1_HASH_MOD_FUNC:  7d78c74de58c1236df4d1f198d0b0dc05104105b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  4f7cdadf880777a3e2799bcbd7f302e96d9f7450

THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406

FOLLOWUP_IP:
nt!KiFastFailDispatch+d0
fffff806`58bd3710 c644242000      mov     byte ptr [rsp+20h],0

FAULT_INSTR_CODE:  202444c6

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiFastFailDispatch+d0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f6eba0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  d0

FAILURE_BUCKET_ID:  0x139_1d_INVALID_BALANCED_TREE_nt!KiFastFailDispatch

BUCKET_ID:  0x139_1d_INVALID_BALANCED_TREE_nt!KiFastFailDispatch

PRIMARY_PROBLEM_CLASS:  0x139_1d_INVALID_BALANCED_TREE_nt!KiFastFailDispatch

TARGET_TIME:  2020-02-06T06:30:22.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-08-22 03:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  3ec8

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_1d_invalid_balanced_tree_nt!kifastfaildispatch

FAILURE_ID_HASH:  {67ec97ad-ad0b-071e-ab87-6dc661e22d1b}

Followup:     MachineOwner
---------
 
Hocam, RAM özelliklerini SS olarak yükleyebildim ve henüz XMP profilini disabled konumuna getirmedim. En azından bu gecelik mavi ekran alacak mıyım beklemek istiyorum. Ama bekleme derseniz hemen kapatayım XMP profilini.
 

Dosya Ekleri

  • Adsız.png
    Adsız.png
    37,8 KB · Görüntüleme: 54
  • Adsız2.png
    Adsız2.png
    26,8 KB · Görüntüleme: 56
Tamam hocam bekliyorum ancak RAM özelliklerini neden istediniz? Yani hangi değere bakmak için? Herhangi bir şey demediğinize göre normal değerler?
DRAM'ler aynı mı diye bakmak istedim.
 
Aldığınız RAM'larin MHz'leri birbirine eş değerde olmak zorunda yani iki RAM'in birisi 3000 MHz ise diğeri de 3000 MHz olmak zorunda.

Eşit değil mi zaten?

DRAM'ler aynı mı diye bakmak istedim.
Hocam, şu saate kadar sorun almadım. Mesela aldım diyelim. Ardından bu sorun XMP profilini kapatınca da düzelmiş olsun. Sonuç olarak, 2133MHz'de kullanmak için almadım ben bu RAM'leri.

Ve hatta bu RAM'leri değiştirip Dual kit olarak çok daha istikrarlı iki RAM aldım diyelim. Yine 2133 MHz olarak mı kullanacağım sorun almamak için?
 
Hocam, şu saate kadar sorun almadım. Mesela aldım diyelim. Ardından bu sorun XMP profilini kapatınca da düzelmiş olsun. Sonuç olarak, 2133MHz'de kullanmak için almadım ben bu RAM'leri.

Ve hatta bu RAM'leri değiştirip Dual kit olarak çok daha istikrarlı iki RAM aldım diyelim. Yine 2133 MHz olarak mı kullanacağım sorun almamak için?
Problem Anakart, işlemci veya belleklerde olabilir, hiçbir zaman bilgisayar elimin altında olmadığı için kesin bir şey söyleyemiyorum.
 
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı