APC INDEX MISMATCH Mavi Ekran Hatası

  • Konuyu başlatan Silinen üye 294212
  • Başlangıç Tarihi
  • Mesaj 36
  • Görüntüleme 26.704
S

Silinen üye 294212

Ziyaretçi
Tekrardan merhabalar,

sanırım mavi ekran konusunda rekora gidiyorum. Bu sefer de farklı bir hata kodu aldım ve muhtemelen uyuşmayan program/driver ile alakalı olabilir. Bu mavi ekran hataları beni inanılmaz derece üzüyor ve yoruyor. Yardımlarınızı bekliyorum, teşekkürler.

Minidump
 
Son düzenleyen: Moderatör:
Bana göre öyle gibi geliyor, bu belleği 3200MHz'e çekerek bence CL16 yapabilirsin, ilk olarak bunu dene.

Memory kaynaklı mı çökmüş oluyor Firefox doğru mu anladım? Bundan mı kaynaklıdır?

Ayrıca 3200 MHz CL16 olarak güncelledim bu şekilde kullanacağım bir süre mavi ekran verirse bu sefer son çare ekran kartı sürücüsünün eski versiyonunu kurmak olacak.
 
Cevabını zaten vermiştim fakat tam açıklama olmamış galiba.

Bana göre evet bellek nedenli çöküyor.

Dün akşamdan beri bir kaç test yapıyorum cidden 3600 mhz frekansı bu konfigürasyonda hata veriyor. Belki anakartla alakalıdır, bilemiyorum.

Ayrıca 3600 MHz CL18 memory, 3200 MHz CL16 yaptığımda ürünün gerçek 3200 CL16 haliyle birebir aynı mı oluyor?
 
CL16'ya iniyor ise CL16'da çalışır fakat diğer değerlerin ne olduğunu bende bilmiyorum.

Son olarak da yine desteklerinizle sorunun kaynağını çözmüş olabilirim.


Sahip olduğum anakart VENGEANCE® RGB PRO 16GB (2 x 8GB) DDR4 DRAM 3600MHz C18 modelini destekliyor gibi görünüyor. Ancak ilgili RAM'in kendi sitesinde desteklediği işlemci modelleri listesi ise Intel 100 Series, Intel 200 Series, Intel 300 Series, Intel X299 bunlardan oluşuyor.

Intel bir işlemcide 3600 MHz için test edilen değerler 18-19-19-39 olarak görünüyor. Anakart uyumlu hale getirmeye çalışsa da bazı noktalarda sanırım problem yaşıyor. Bana zaten burada yazan değerlerin üstünde uygulatıyor.

Kısacası 3600 MHz değeri belki görebilirim doğru değerleri girerek ancak istikrarlı çalışacağını pek düşünmüyorum. Bu yüzden direkt uygunluğa sahip bir RAM ile değişim yapacağım. Diğerlerini iade etmiştim bunları da yenisini alıp iade edeceğim. Teşekkürler.
 
Son düzenleyen: Moderatör:
Merhaba,

RAM'lerime uyguladığım overclock sebebiyle mi yoksa farklı bir sebepten dolayı mı mavi ekran verdiği konusunda yardımcı olabilirseniz çok sevinirim. @MayCrasH

Minidump

Teşekkürler.
 
Son düzenleyen: Moderatör:
%95 bellek hatası.
Speed 3600MHz
Manufacturer Unknown
Serial Number
Asset Tag Number [String Not Specified]
Part Number CMT16GX4M2C3200C16
fffffb05`0b6a7508 fffff805`50dd32e9 : 00000000`0000000a 00000000`00000140 00000000`000000ff 00000000`00000054 : nt!KeBugCheckEx
fffffb05`0b6a7510 fffff805`50dcf62b : ffffffff`feced300 ffff9900`00000000 ffffffff`feced300 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffb05`0b6a7650 fffff805`50dee44f : 00004153`f17c50eb 00004153`f17c50eb ffff8786`2d419010 00000000`00000000 : nt!KiPageFault+0x46b
fffffb05`0b6a77e0 fffff805`50c215ce : 00000000`00000003 00000000`00000002 ffff8786`2d419100 00000000`00000008 : nt!PpmIdleExecuteTransition+0x1cccdf
fffffb05`0b6a7b00 fffff805`50dc4fe8 : ffffffff`00000000 ffff9900`7f944180 ffff8786`39f2e080 00000000`00000214 : nt!PoIdle+0x36e
fffffb05`0b6a7c60 00000000`00000000 : fffffb05`0b6a8000 fffffb05`0b6a2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48
Kod:
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000140, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000054, 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: fffff80550dee44f, address which referenced memory

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:  Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME:  MS-7B89

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  2.60

BIOS_DATE:  12/30/2019

BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT:  B450M MORTAR MAX (MS-7B89)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: 140

BUGCHECK_P2: ff

BUGCHECK_P3: 54

BUGCHECK_P4: fffff80550dee44f

READ_ADDRESS: fffff805511733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
0000000000000140

CURRENT_IRQL:  0

FAULTING_IP:
nt!PpmIdleExecuteTransition+1cccdf
fffff805`50dee44f 89b40240010000  mov     dword ptr [rdx+rax+140h],esi

CPU_COUNT: c

CPU_MHZ: ed8

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-09-2020 21:25:41.0693

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME:  fffffb050b6a7650 -- (.trap 0xfffffb050b6a7650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80550dee44f rsp=fffffb050b6a77e0 rbp=ffff87862d419010
r8=ffff87862d419330  r9=0000000001000000 r10=0000fffff8056154
r11=ffff88ff11e00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr ac po nc
nt!PpmIdleExecuteTransition+0x1cccdf:
fffff805`50dee44f 89b40240010000  mov     dword ptr [rdx+rax+140h],esi ds:00000000`00000140=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80550dd32e9 to fffff80550dc14e0

STACK_TEXT:
fffffb05`0b6a7508 fffff805`50dd32e9 : 00000000`0000000a 00000000`00000140 00000000`000000ff 00000000`00000054 : nt!KeBugCheckEx
fffffb05`0b6a7510 fffff805`50dcf62b : ffffffff`feced300 ffff9900`00000000 ffffffff`feced300 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffb05`0b6a7650 fffff805`50dee44f : 00004153`f17c50eb 00004153`f17c50eb ffff8786`2d419010 00000000`00000000 : nt!KiPageFault+0x46b
fffffb05`0b6a77e0 fffff805`50c215ce : 00000000`00000003 00000000`00000002 ffff8786`2d419100 00000000`00000008 : nt!PpmIdleExecuteTransition+0x1cccdf
fffffb05`0b6a7b00 fffff805`50dc4fe8 : ffffffff`00000000 ffff9900`7f944180 ffff8786`39f2e080 00000000`00000214 : nt!PoIdle+0x36e
fffffb05`0b6a7c60 00000000`00000000 : fffffb05`0b6a8000 fffffb05`0b6a2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48


THREAD_SHA1_HASH_MOD_FUNC:  fbc86847fe4eb6c3c1fac4537ef130091fd9343a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  17a964fcd2e6a8be504da1884370b6b2dfc4a249

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!PpmIdleExecuteTransition+1cccdf
fffff805`50dee44f 89b40240010000  mov     dword ptr [rdx+rax+140h],esi

FAULT_INSTR_CODE:  4002b489

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PpmIdleExecuteTransition+1cccdf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  29371fe3

IMAGE_VERSION:  10.0.18362.628

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1cccdf

FAILURE_BUCKET_ID:  AV_nt!PpmIdleExecuteTransition

BUCKET_ID:  AV_nt!PpmIdleExecuteTransition

PRIMARY_PROBLEM_CLASS:  AV_nt!PpmIdleExecuteTransition

TARGET_TIME:  2020-02-09T17:44:05.000Z

OSBUILD:  18362

OSSERVICEPACK:  628

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

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

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nt!ppmidleexecutetransition

FAILURE_ID_HASH:  {0ced0187-972d-f83e-de87-663d75806c32}

Followup:     MachineOwner
---------
 
%95 bellek hatası.


Kod:
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000140, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000054, 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: fffff80550dee44f, address which referenced memory

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:  Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME:  MS-7B89

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  2.60

BIOS_DATE:  12/30/2019

BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT:  B450M MORTAR MAX (MS-7B89)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: 140

BUGCHECK_P2: ff

BUGCHECK_P3: 54

BUGCHECK_P4: fffff80550dee44f

READ_ADDRESS: fffff805511733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
0000000000000140

CURRENT_IRQL:  0

FAULTING_IP:
nt!PpmIdleExecuteTransition+1cccdf
fffff805`50dee44f 89b40240010000  mov     dword ptr [rdx+rax+140h],esi

CPU_COUNT: c

CPU_MHZ: ed8

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-09-2020 21:25:41.0693

ANALYSIS_VERSION: 10.0.18362.1 x86fre

TRAP_FRAME:  fffffb050b6a7650 -- (.trap 0xfffffb050b6a7650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80550dee44f rsp=fffffb050b6a77e0 rbp=ffff87862d419010
r8=ffff87862d419330  r9=0000000001000000 r10=0000fffff8056154
r11=ffff88ff11e00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr ac po nc
nt!PpmIdleExecuteTransition+0x1cccdf:
fffff805`50dee44f 89b40240010000  mov     dword ptr [rdx+rax+140h],esi ds:00000000`00000140=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80550dd32e9 to fffff80550dc14e0

STACK_TEXT:
fffffb05`0b6a7508 fffff805`50dd32e9 : 00000000`0000000a 00000000`00000140 00000000`000000ff 00000000`00000054 : nt!KeBugCheckEx
fffffb05`0b6a7510 fffff805`50dcf62b : ffffffff`feced300 ffff9900`00000000 ffffffff`feced300 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffb05`0b6a7650 fffff805`50dee44f : 00004153`f17c50eb 00004153`f17c50eb ffff8786`2d419010 00000000`00000000 : nt!KiPageFault+0x46b
fffffb05`0b6a77e0 fffff805`50c215ce : 00000000`00000003 00000000`00000002 ffff8786`2d419100 00000000`00000008 : nt!PpmIdleExecuteTransition+0x1cccdf
fffffb05`0b6a7b00 fffff805`50dc4fe8 : ffffffff`00000000 ffff9900`7f944180 ffff8786`39f2e080 00000000`00000214 : nt!PoIdle+0x36e
fffffb05`0b6a7c60 00000000`00000000 : fffffb05`0b6a8000 fffffb05`0b6a2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x48


THREAD_SHA1_HASH_MOD_FUNC:  fbc86847fe4eb6c3c1fac4537ef130091fd9343a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  17a964fcd2e6a8be504da1884370b6b2dfc4a249

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!PpmIdleExecuteTransition+1cccdf
fffff805`50dee44f 89b40240010000  mov     dword ptr [rdx+rax+140h],esi

FAULT_INSTR_CODE:  4002b489

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PpmIdleExecuteTransition+1cccdf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  29371fe3

IMAGE_VERSION:  10.0.18362.628

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1cccdf

FAILURE_BUCKET_ID:  AV_nt!PpmIdleExecuteTransition

BUCKET_ID:  AV_nt!PpmIdleExecuteTransition

PRIMARY_PROBLEM_CLASS:  AV_nt!PpmIdleExecuteTransition

TARGET_TIME:  2020-02-09T17:44:05.000Z

OSBUILD:  18362

OSSERVICEPACK:  628

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

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

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nt!ppmidleexecutetransition

FAILURE_ID_HASH:  {0ced0187-972d-f83e-de87-663d75806c32}

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

Overclock ile mi alakalı yoksa farklı bir durumla mı alakalı yardımcı olur musun? Bir şeyler deniyordum bilgisayar başında değilken mavi ekran vermiş.

Minidump
 
Son düzenleyen: Moderatör:
Silinen üye 294212, lütfen çözüm olarak uygun mesajın önündeki simgesine tıklayarak bir cevabı çözüm olarak işaretlediğinizden emin olun.
Uyarı! Bu konu 5 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

Yeni konular

Geri
Yukarı