Çözüldü Ryzen 3600 sistem mavi ekran hataları

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

Alper Gökmen

Hectopat
Katılım
23 Temmuz 2020
Mesajlar
34
Çözümler
2
Sürekli Google üzerinden video izlerken (YouTube'da) veya film falan izlerken (Chrome üzerinden yine) mavi ekran hatası alıyorum.
(Minidump Dosyası linki) işlemci ve anakartı servise gönderdim bir şey çıkmadı.

Sistem özellikleri:

AMD Ryzen 5 3600.

MSI RTX 2060 Super Gaming X.

Corsair vegeance 3200 MHz (8x2)

Seagate Barracuda 1 TB 7200 RPM HDD.

Corsair MP510 480GB SSD.

Cooler Master Elite V3.
 
Son düzenleyen: Moderatör:
Çözüm
A
Sercan Baydar dedi:
Sonuç olarak çözüm bulamadınız hala o zaman?
Genişletmek için tıkla...

Maalesef mavi ekran almam çok sayıda azaldı ama hala alıyorum haftada 3 bazen hiç, bu konuyu açtığım zamanlarda 15 20'şer dakikada 1 hata alıyordum Google'dan YouTube'dan video vs izleyemiyordum.

Sistemi DDR5'e geçirme kararı verdim zaten anakart ve işlemci kaynaklı bir problem olduğunu düşünüyordum ve bu yükseltme sonrası mavi ekran sorunun ortadan kalktı bu tarz sorunu olan bir arkadaş varsa (oyun açıkken mavi ekran yemeyip PC boştayken ya da basit işler için kullanılırken sürekli mavi ekran yiyorsa) bu 2 parçadan birinden şüphelenebilirler.
Tarihe göre sırala Puana göre sırala
Alper Gökmen dedi:
KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE hatası aldım.
Microsoft (r) Windows debugger version 10.0.20153.1000 AMD64.
Copyright (C) Microsoft corporation. All rights reserved.

Loading dump file [C:\WINDOWS\MEMORY.DMP]
Kernel bitmap dump file: Kernel address space is available, user address space may not be available.

************* Path validation summary **************
Response time (ms) location.
Deferred srv*
Symbol Search path is: Srv*
Executable Search path is:
Windows 10 kernel version 19041 MP (12 procs) Free X64.
PROduct: Winnt, Suite: Terminalserver singleuserts personal.
Edition Build lab: 19041.1.AMD64fre. VB_RELEASE. 191206-1406.
Machine name:
Kernel base = 0xfffff802`36200000 psloadedmodulelist = 0xfffff802`36e2a310.
Debug session time: Mon jul 27 16:10:38.123 2020 (utc + 3:00)
System uptime: 0 days 0:38:27.757.
Loading kernel symbols.



Loading user symbols.
Peb is paged out (peb. LDR = 00000070'B32D8018). Type ".Hh dbgerr001" for details.
Loading unloaded module list.

For analysis of this file, run! Analyze -v.
Nt! Kebugcheckex:
Fffff802'365DDB60 48894C2408 mov qword PTR [rsp+8],rcx SS:0018:fffff40D'C54985E0=0000000000000162.
1: Kd>! Analyze -v.
*******************************************************************************
* *
* Bugcheck analysis *
* *
*******************************************************************************

KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE (162)
A lock tracked by autoboost was released by a thread that did not own the lock.
This is typically caused when some thread releases a lock on behalf of another.
Thread (which is not legal with autoboost tracking enabled) or when some thread.
Tries to release a lock it no longer owns.
Arguments:
Arg1: FFFFB4086F2240C0, the address of the thread.
Arg2: FFFFA3807A87C100, the lock address.
Arg3: 00000000FFFFFfff, the session ID of the thread.
Arg4: 0000000000000000, reserved.

Debugging details:
------------------

KEY_VALUES_STRING: 1.

Key: Analysis. CPU. Msec.
Value: 2640.

Key: Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007E on desktop-RP9LE0O.

Key: Analysis. Debugdata.
Value: Createobject.

Key: Analysis. Debugmodel.
Value: Createobject.

Key: Analysis. Elapsed. Msec.
Value: 2659.

Key: Analysis. Memory. Commitpeak. MB.
Value: 78.

Key: Analysis. System.
Value: Createobject.

Key: Wer. OS. Branch.
Value: VB_RELEASE.

Key: Wer. OS. Timestamp.
Value: 2019-12-06T14:06:00Z.

Key: Wer. OS. Version.
Value: 10.0.19041.1.

ADDITIONAL_XML: 1.

OS_BUILD_LAYERS: 1.

BUGCHECK_CODE: 162.

BUGCHECK_P1: FFFFB4086F2240C0.

BUGCHECK_P2: FFFFA3807A87C100.

BUGCHECK_P3: Ffffffff.

BUGCHECK_P4: 0.

Blackboxbsd: 1 (!Blackboxbsd)

Blackboxntfs: 1 (!Blackboxntfs)

Blackboxpnp: 1 (!Blackboxpnp)

Blackboxwınlogon: 1.

PROCESS_NAME: nvcontainer.exe.

STACK_TEXT:
Fffff40D'C54985D8 fffff802'365FAD21: 00000000'00000162 ffffb408'6F2240C0 ffffa380'7A87C100 00000000'ffffffff: Nt! Kebugcheckex.
Fffff40D'C54985E0 fffff802'367F4ABC: Ffffa380'0000003F fffff802'00000000 ffffffff'ffffffff ffffa380'8A7F9310: Nt! Keabpostrelease+0x1D4B01.
Fffff40D'C5498640 fffff802'367FB11C: 00000000'000054C4 00000000'000007FF ffffa380'ffffffff 00000000'00000000: Nt! Obclosehandletableentry+0x19C.
Fffff40D'C5498780 fffff802'365EF478: 00000000'00000000 fffff802'00000000 fffff40D'C5498870 ffffa380'7A000AC0: Nt! Ntclose+0xec.
Fffff40D'C54987F0 fffff802'365E19C0: Fffff802'3689F4B1 00000000'00000000 00000000'00000000 00000000'00000000: Nt! Kisystemservicecopyend+0x28.
Fffff40D'C5498988 fffff802'3689F4B1: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: Nt! Kiservicelinkage.
Fffff40D'C5498990 fffff802'38F192A2: Ffffffff'800054C4 00000000'00000000 ffffb408'64BF18C0 00000000'00000000: Nt! Iogetdeviceobjectpointer+0xe1.
Fffff40D'C5498A20 fffff802'38F190C3: Ffffb408'64BF18C0 ffffb408'6F947BC0 ffffb408'7845C0D0 00000000'00000000: Mountmgr! Mountmgrquerydosvolumepath+0xd2.
Fffff40D'C5498B50 fffff802'36446D45: Fffff40D'C5498CF0 ffffa380'D6BD4540 ffffa380'81DCB5B0 fffff40D'C5498C48: Mountmgr! Mountmgrdevicecontrol+0xb3.
Fffff40D'C5498BB0 fffff802'3689F332: 00000000'00000010 fffff40D'C5498CF0 ffffa380'D6BD4540 00000000'00000000: Nt! Iofcalldriver+0x55.
Fffff40D'C5498BF0 fffff802'3689EB57: B4087601'0050FFFE 00000000'000000C0 ffffa380'D6BD4540 ffffa380'D6BD4540: Nt! Iovolumedevicetodosname+0x232.
Fffff40D'C5498EC0 fffff802'3689EA6E: Ffffb408'7845D200 ffffb408'00000000 fffff40D'C5499001 ffffa380'D6BD4540: Nt! Iopquerynameınternal+0xa3.
Fffff40D'C5498F70 fffff802'3686ECB8: Ffffb408'7845D200 fffff40D'C5499B80 ffffa380'000000D0 0000017E'5F6C9800: Nt! Ioqueryfiledosdevicename+0x5E.
Fffff40D'C5498FC0 fffff802'365EF478: 00000000'00000002 00000000'00000001 00000000'00000000 0000017E'5F5411E4: Nt! Ntqueryınformationprocess+0x968.
Fffff40D'C5499A90 00007FFD'dddeb0b4: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: Nt! Kisystemservicecopyend+0x28.
00000070'B44FF018 00000000'00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000 : 0x00007ffd`dddeb0b4.

SYMBOL_NAME: Mountmgr! Mountmgrquerydosvolumepath+D2.

MODULE_NAME: Mountmgr.

IMAGE_NAME: mountmgr.sys.

STACK_COMMAND:. Thread;. Cxr; KB.

BUCKET_ID_FUNC_OFFSET: D2.

FAILURE_BUCKET_ID: 0x162_mountmgr!MountMgrQueryDosVolumePath.

OS_VERSION: 10.0.19041.1.

BUILDLAB_STR: VB_RELEASE.

OSPLATFORM_TYPE: X64.

Osname: Windows 10.

FAILURE_ID_HASH: {9924CE1C-A12e-8671-635F-ACC1E09BF450}

Followup: Machineowner.
---------
dumpdosyaları
@Recep Baltaş ATTEMPTED_WRITE_TO_READONLY_MEMORY en son bu hata ile karşılaştım ve.
(nvlddmkm.sys, nvlddmkm.sys+12D550) hatası, amdppm.sys hatası ve ntoskrnl.exe hata ayrıntılarını görmüş olmaktayım ben sorunun ekran kartımdan kaynaklandığını düşünüyorum sizin kadar anlamadığım için yine de size sormak istiyorum sizce hata belleklerden mi ekran kartından mı kaynaklanıyor.
ATTEMPTED_WRITE_TO_READONLY_MEMORY bu hatadan önce de DRIVER_IRQL_NOT_LESS_OR_EQUAL hatası aldım zaten dump dosyalarını paylaştım inceleyebilirsiniz bende windbg Preview dosyaları okumuyor önceden okuyor idi ama şimdi AFK bir şekilde bekliyor.
RAM'ler Memtest 86 ile test edildi bellek tanılamayla test edildi sorun çıkmadı zaten son test etmemden sonra resimleri paylaşmıştım.
Genişletmek için tıkla...

Merhabalar, bir gelişme kaydettiniz mi bu konuda? Paylaşırsanız sevinirim.
 
Artı 0 Eksi
Ben de seninle benzer sorunu yaşıyorum ve Memtest defalarca yapmama rağmen sorun gözükmüyor. Ryzen 3600X, ASUS 2060 Super Advanced, B450 MSI Tomahawk Max anakart, Kingston HyperX 16 GB RAM konfigürasyonları mevcut.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Sercan Baydar dedi:
Bende seninle benzer sorunu yaşıyorum ve Memtest defalarca yapmama rağmen sorun gözükmüyor. Ryzen 3600X, ASUS 2060 Super Advanced, B450 MSI Tomahawk Max anakart, Kingston HyperX 16 GB RAM konfigürasyonları mevcut.
Genişletmek için tıkla...

Sende sorun neyde çıktı? Ben tüm donanımları serviste test ettirmiştim bir RAM'ler kaldı.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Alper Gökmen dedi:
Sende sorun neyde çıktı ben tüm donanımları serviste test ettirmiştim bir RAM'ler kaldı.
Genişletmek için tıkla...

Ben hala bulamadım işte sorunu. 3 aydır durum böyle. Son 1 ayda daha nadir mavi ekran alıyorum. Çok araştırıyorum hala bir sonuç yok. Sürekli sürücleri güncelliyorum belki düzelir diye nafile. Ekran kartından şüpheleniyorum ben daha çok fakat oyunda oynayabiliyorum. Anlayamadım hala. Benzer sorun yaşayanlar var yabancı forumlarda dahil olmak üzere ama ya çözüm yok olsa bile bende çözülmüyor :)
 
Artı 0 Eksi
Recep Baltaş dedi:
Adam minidump atmış, daha ne atsın? Açıp oradan öğrenebilirsin kodları. Konusunu okdunuz mu bu cevabı yazmadan önce?
Bellek sorunu gibi.
  • Anakart nedir?
  • XMP açık mı?
  • BIOS güncel mi?
Memtest testi yapıp sonucu paylaşın:

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

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

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

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

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

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.mSec.
Value: 3608.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-1IBQR0U.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.mSec.
Value: 7171.

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

Key : Analysis.System.
Value: CreateObject.

Key : WER.OS.Branch.
Value: vb_release.

Key : WER.OS.Timestamp.
Value: 2019-12-06T14:06:00Z.

Key : WER.OS.Version.
Value: 10.0.19041.1.

ADDITIONAL_XML: 1.

OS_BUILD_LAYERS: 1.

BUGCHECK_CODE: a.

BUGCHECK_P1: ffffe80963ad4460.

BUGCHECK_P2: ff.

BUGCHECK_P3: 9e.

BUGCHECK_P4: fffff8031a6cbd9c.

READ_ADDRESS: fffff8031b0fa388: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
fffff8031b00f2a8: Unable to get Flags value from nt!KdVersionBlock.
fffff8031b00f2a8: Unable to get Flags value from nt!KdVersionBlock.
unable to get nt!MmSpecialPagesInUse.
ffffe80963ad4460.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1.

CUSTOMER_CRASH_COUNT: 1.

PROCESS_NAME: System.

TRAP_FRAME: ffff8a8241629960 -- (.trap 0xffff8a8241629960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000040002000 rbx=0000000000000000 rcx=0000000000000000.
rdx=fffff8031b01ed00 rsi=0000000000000000 rdi=0000000000000000.
rip=fffff8031a6cbd9c rsp=ffff8a8241629af0 rbp=ffff8a8241629bf0.
r8=0000000000002715 r9=ffffe80963ad4438 r10=ffffe70f63304010.
r11=ffffc6fb9ec00000 r12=0000000000000000 r13=0000000000000000.
r14=0000000000000000 r15=0000000000000000.
iopl=0 nv up di ng nz na pe nc.
nt!PoIdle+0xfc:
fffff803`1a6cbd9c 4d014128 add qword ptr [r9+28h],r8 ds:ffffe809`63ad4460=????????????????
Resetting default scope.

STACK_TEXT:
ffff8a82`41629818 fffff803`1a7ef929 : 00000000`0000000a ffffe809`63ad4460 00000000`000000ff 00000000`0000009e : nt!KeBugCheckEx.
ffff8a82`41629820 fffff803`1a7ebc29 : ffffe70f`63304010 ffffffff`ffffffff ffffffff`f75e7aa7 ffffe70f`633041f8 : nt!KiBugCheckDispatch+0x69.
ffff8a82`41629960 fffff803`1a6cbd9c : 00000000`00000000 00001fa0`009e0080 00000000`06320000 00000000`00000004 : nt!KiPageFault+0x469.
ffff8a82`41629af0 fffff803`1a7e1544 : ffffffff`00000000 ffffd700`4d9ed340 ffffe70f`7e210080 00000000`000004ec : nt!PoIdle+0xfc.
ffff8a82`41629c60 00000000`00000000 : ffff8a82`4162a000 ffff8a82`41624000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54.

SYMBOL_NAME: nt!PoIdle+fc.

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe.

IMAGE_VERSION: 10.0.19041.329.

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: fc.

FAILURE_BUCKET_ID: AV_CODE_AV_nt!PoIdle.

OS_VERSION: 10.0.19041.1.

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {e4da1044-dba7-2394-a0c7-af0e27cae716}

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

1: kd> .bugcheck.
Bugcheck code 0000000A.
Arguments ffffe809`63ad4460 00000000`000000ff 00000000`0000009e fffff803`1a6cbd9c.
1: kd> kb.
# RetAddr : Args to Child : Call Site.
00 fffff803`1a7ef929 : 00000000`0000000a ffffe809`63ad4460 00000000`000000ff 00000000`0000009e : nt!KeBugCheckEx.
01 fffff803`1a7ebc29 : ffffe70f`63304010 ffffffff`ffffffff ffffffff`f75e7aa7 ffffe70f`633041f8 : nt!KiBugCheckDispatch+0x69.
02 fffff803`1a6cbd9c : 00000000`00000000 00001fa0`009e0080 00000000`06320000 00000000`00000004 : nt!KiPageFault+0x469.
03 fffff803`1a7e1544 : ffffffff`00000000 ffffd700`4d9ed340 ffffe70f`7e210080 00000000`000004ec : nt!PoIdle+0xfc.
04 00000000`00000000 : ffff8a82`4162a000 ffff8a82`41624000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54.
1: kd> kv.
# Child-SP RetAddr : Args to Child : Call Site.
00 ffff8a82`41629818 fffff803`1a7ef929 : 00000000`0000000a ffffe809`63ad4460 00000000`000000ff 00000000`0000009e : nt!KeBugCheckEx.
01 ffff8a82`41629820 fffff803`1a7ebc29 : ffffe70f`63304010 ffffffff`ffffffff ffffffff`f75e7aa7 ffffe70f`633041f8 : nt!KiBugCheckDispatch+0x69.
02 ffff8a82`41629960 fffff803`1a6cbd9c : 00000000`00000000 00001fa0`009e0080 00000000`06320000 00000000`00000004 : nt!KiPageFault+0x469 (TrapFrame @ ffff8a82`41629960)
03 ffff8a82`41629af0 fffff803`1a7e1544 : ffffffff`00000000 ffffd700`4d9ed340 ffffe70f`7e210080 00000000`000004ec : nt!PoIdle+0xfc.
04 ffff8a82`41629c60 00000000`00000000 : ffff8a82`4162a000 ffff8a82`41624000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54.
1: kd> .trap ffff8a82`41629960.
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000040002000 rbx=0000000000000000 rcx=0000000000000000.
rdx=fffff8031b01ed00 rsi=0000000000000000 rdi=0000000000000000.
rip=fffff8031a6cbd9c rsp=ffff8a8241629af0 rbp=ffff8a8241629bf0.
r8=0000000000002715 r9=ffffe80963ad4438 r10=ffffe70f63304010.
r11=ffffc6fb9ec00000 r12=0000000000000000 r13=0000000000000000.
r14=0000000000000000 r15=0000000000000000.
iopl=0 nv up di ng nz na pe nc.
nt!PoIdle+0xfc:
fffff803`1a6cbd9c 4d014128 add qword ptr [r9+28h],r8 ds:ffffe809`63ad4460=????????????????
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints.
the driver/function that caused the problem. Always note this address.
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled.
Arg2: fffff80330accb61, The address that the exception occurred at.
Arg3: 0000000000000001, Parameter 0 of the exception.
Arg4: 000000000000031c, Parameter 1 of the exception.

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

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

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.mSec.
Value: 6202.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-1IBQR0U.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.mSec.
Value: 9514.

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

Key : Analysis.System.
Value: CreateObject.

Key : WER.OS.Branch.
Value: vb_release.

Key : WER.OS.Timestamp.
Value: 2019-12-06T14:06:00Z.

Key : WER.OS.Version.
Value: 10.0.19041.1.

ADDITIONAL_XML: 1.

OS_BUILD_LAYERS: 1.

BUGCHECK_CODE: 1e.

BUGCHECK_P1: ffffffffc0000005.

BUGCHECK_P2: fffff80330accb61.

BUGCHECK_P3: 1.

BUGCHECK_P4: 31c.

WRITE_ADDRESS: fffff803314fa388: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
fffff8033140f2a8: Unable to get Flags value from nt!KdVersionBlock.
fffff8033140f2a8: Unable to get Flags value from nt!KdVersionBlock.
unable to get nt!MmSpecialPagesInUse.
000000000000031c.

EXCEPTION_PARAMETER1: 0000000000000001.

EXCEPTION_PARAMETER2: 000000000000031c.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1.

CUSTOMER_CRASH_COUNT: 1.

PROCESS_NAME: System.

TRAP_FRAME: fffff8033666b590 -- (.trap 0xfffff8033666b590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80330b84ee0 rbx=0000000000000000 rcx=0000000000000001.
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000.
rip=fffff80330accb61 rsp=fffff8033666b720 rbp=0000000000000000.
r8=0000000000000000 r9=0000000000000001 r10=00000000ffffffff.
r11=ffff917e69c00000 r12=0000000000000000 r13=0000000000000000.
r14=0000000000000000 r15=0000000000000000.
iopl=0 nv up ei pl zr na po nc.
nt!PpmIdleExecuteTransition+0x9d1:
fffff803`30accb61 899e1c030000 mov dword ptr [rsi+31Ch],ebx ds:00000000`0000031c=????????
Resetting default scope.

STACK_TEXT:
fffff803`3666a558 fffff803`30d00c3e : 00000000`0000001e ffffffff`c0000005 fffff803`30accb61 00000000`00000001 : nt!KeBugCheckEx.
fffff803`3666a560 fffff803`30be68e2 : fffff803`30d00c1c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22.
fffff803`3666a5a0 fffff803`30a32fb7 : fffff803`3666ab10 00000000`00000000 fffff803`3666bc60 fffff803`30be1544 : nt!RtlpExecuteHandlerForException+0x12.
fffff803`3666a5d0 fffff803`30a7b226 : fffff803`3666b4e8 fffff803`3666b220 fffff803`3666b4e8 fffff803`2e567180 : nt!RtlDispatchException+0x297.
fffff803`3666acf0 fffff803`30befa6c : fffff803`3666b610 00000000`00001000 fffff803`3666b590 ffff8000`00000000 : nt!KiDispatchException+0x186.
fffff803`3666b3b0 fffff803`30bebc03 : 00000000`00000000 00000000`00000000 464a36ec`a5279b69 e58e5ccf`bce59db2 : nt!KiExceptionDispatch+0x12c.
fffff803`3666b590 fffff803`30accb61 : 00005548`a8ace8e4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x443.
fffff803`3666b720 fffff803`30acc014 : 00000000`00000000 00000000`00000000 00000048`063200e6 00000000`00000004 : nt!PpmIdleExecuteTransition+0x9d1.
fffff803`3666baf0 fffff803`30be1544 : 00000000`00000000 fffff803`31526600 ffffb281`708c8080 00000000`0000021c : nt!PoIdle+0x374.
fffff803`3666bc60 00000000`00000000 : fffff803`3666c000 fffff803`36666000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54.

SYMBOL_NAME: nt!PpmIdleExecuteTransition+9d1.

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe.

IMAGE_VERSION: 10.0.19041.329.

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 9d1.

FAILURE_BUCKET_ID: 0x1E_c0000005_W_nt!PpmIdleExecuteTransition.

OS_VERSION: 10.0.19041.1.

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {33165129-5eba-df70-5004-10486d097d7a}

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

0: kd> kb.
# RetAddr : Args to Child : Call Site.
00 fffff803`30d00c3e : 00000000`0000001e ffffffff`c0000005 fffff803`30accb61 00000000`00000001 : nt!KeBugCheckEx.
01 fffff803`30be68e2 : fffff803`30d00c1c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22.
02 fffff803`30a32fb7 : fffff803`3666ab10 00000000`00000000 fffff803`3666bc60 fffff803`30be1544 : nt!RtlpExecuteHandlerForException+0x12.
03 fffff803`30a7b226 : fffff803`3666b4e8 fffff803`3666b220 fffff803`3666b4e8 fffff803`2e567180 : nt!RtlDispatchException+0x297.
04 fffff803`30befa6c : fffff803`3666b610 00000000`00001000 fffff803`3666b590 ffff8000`00000000 : nt!KiDispatchException+0x186.
05 fffff803`30bebc03 : 00000000`00000000 00000000`00000000 464a36ec`a5279b69 e58e5ccf`bce59db2 : nt!KiExceptionDispatch+0x12c.
06 fffff803`30accb61 : 00005548`a8ace8e4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x443.
07 fffff803`30acc014 : 00000000`00000000 00000000`00000000 00000048`063200e6 00000000`00000004 : nt!PpmIdleExecuteTransition+0x9d1.
08 fffff803`30be1544 : 00000000`00000000 fffff803`31526600 ffffb281`708c8080 00000000`0000021c : nt!PoIdle+0x374.
09 00000000`00000000 : fffff803`3666c000 fffff803`36666000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54.
KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or.
above.
Arguments:
Arg1: ffff9f8625e57080, The address of the thread.
Arg2: ffffce8e811b3b80, The lock address.
Arg3: 0000000000000000, The IRQL at which the lock was acquired.
Arg4: 0000000000000000, Reserved.

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

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.mSec.
Value: 3234.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-1IBQR0U.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.mSec.
Value: 4717.

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

Key : Analysis.System.
Value: CreateObject.

Key : WER.OS.Branch.
Value: vb_release.

Key : WER.OS.Timestamp.
Value: 2019-12-06T14:06:00Z.

Key : WER.OS.Version.
Value: 10.0.19041.1.

ADDITIONAL_XML: 1.

OS_BUILD_LAYERS: 1.

BUGCHECK_CODE: 192.

BUGCHECK_P1: ffff9f8625e57080.

BUGCHECK_P2: ffffce8e811b3b80.

BUGCHECK_P3: 0.

BUGCHECK_P4: 0.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1.

CUSTOMER_CRASH_COUNT: 1.

PROCESS_NAME: nvcontainer.exe.

STACK_TEXT:
ffffc68b`b986f558 fffff807`1f425a7b : 00000000`00000192 ffff9f86`25e57080 ffffce8e`811b3b80 00000000`00000000 : nt!KeBugCheckEx.
ffffc68b`b986f560 fffff807`1f7f35e2 : 00000000`00000000 ffff9f86`25b24230 ffffce8e`00000000 ffff9f86`25b24230 : nt!ExAcquirePushLockExclusiveEx+0x14b.
ffffc68b`b986f5a0 fffff807`1f81350d : ffff9f86`1b010340 ffff9f86`1b012900 ffff9f86`1b015d80 00000000`00000080 : nt!ObpCreateHandle+0x3f2.
ffffc68b`b986f790 fffff807`1f812741 : 00000000`00000001 ffffc68b`b986fb80 00000000`00000001 00000000`00000001 : nt!ObInsertObjectEx+0x13d.
ffffc68b`b986fa20 fffff807`1f5ef478 : ffff9f86`25e57080 000000b6`c2dff978 ffffc68b`b986faa8 00000000`00000000 : nt!NtCreateEvent+0xe1.
ffffc68b`b986fa90 00007ffb`b5eeb694 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28.
000000b6`c2dff958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`b5eeb694.

SYMBOL_NAME: nt!ExAcquirePushLockExclusiveEx+14b.

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe.

IMAGE_VERSION: 10.0.19041.388.

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 14b.

FAILURE_BUCKET_ID: 0x192_nt!ExAcquirePushLockExclusiveEx.

OS_VERSION: 10.0.19041.1.

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {70f07b19-205c-f6b9-7ad5-00ec20680212}

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: 0000000000000001, 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: fffff80676436c74, address which referenced memory.

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

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

KEY_VALUES_STRING: 1.

Key : Analysis.CPU.mSec.
Value: 3624.

Key : Analysis.DebugAnalysisProvider.CPP.
Value: Create: 8007007e on DESKTOP-1IBQR0U.

Key : Analysis.DebugData.
Value: CreateObject.

Key : Analysis.DebugModel.
Value: CreateObject.

Key : Analysis.Elapsed.mSec.
Value: 6228.

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

Key : Analysis.System.
Value: CreateObject.

Key : WER.OS.Branch.
Value: vb_release.

Key : WER.OS.Timestamp.
Value: 2019-12-06T14:06:00Z.

Key : WER.OS.Version.
Value: 10.0.19041.1.

ADDITIONAL_XML: 1.

OS_BUILD_LAYERS: 1.

BUGCHECK_CODE: a.

BUGCHECK_P1: 1.

BUGCHECK_P2: 2.

BUGCHECK_P3: 0.

BUGCHECK_P4: fffff80676436c74.

READ_ADDRESS: fffff80676efa388: Unable to get MiVisibleState.
Unable to get NonPagedPoolStart.
Unable to get NonPagedPoolEnd.
Unable to get PagedPoolStart.
Unable to get PagedPoolEnd.
fffff80676e0f2a8: Unable to get Flags value from nt!KdVersionBlock.
fffff80676e0f2a8: Unable to get Flags value from nt!KdVersionBlock.
unable to get nt!MmSpecialPagesInUse.
0000000000000001.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1.

CUSTOMER_CRASH_COUNT: 1.

PROCESS_NAME: System.

TRAP_FRAME: fffff80679c6b6a0 -- (.trap 0xfffff80679c6b6a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000002.
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000.
rip=fffff80676436c74 rsp=fffff80679c6b830 rbp=0000000000000001.
r8=0000000000000102 r9=0000000000000000 r10=fffff80671b27ac0.
r11=0000000f8dcdabea r12=0000000000000000 r13=0000000000000000.
r14=0000000000000000 r15=0000000000000000.
iopl=0 nv up ei pl zr na po nc.
nt!KiTimerWaitTest+0x1c4:
fffff806`76436c74 4d8b36 mov r14,qword ptr [r14] ds:00000000`00000000=????????????????
Resetting default scope.

STACK_TEXT:
fffff806`79c6b558 fffff806`765ef929 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx.
fffff806`79c6b560 fffff806`765ebc29 : fffff806`79c6b6b8 00000000`00000018 fffff806`76551a00 fffff806`84d41101 : nt!KiBugCheckDispatch+0x69.
fffff806`79c6b6a0 fffff806`76436c74 : ffffc80a`b2b0c408 00000000`00000000 ffffc80a`b2b0c4d0 00000000`00000000 : nt!KiPageFault+0x469.
fffff806`79c6b830 fffff806`7643683c : ffffc80a`b2b0c400 00000000`00000000 fffff806`79c6bb18 00000000`00000000 : nt!KiTimerWaitTest+0x1c4.
fffff806`79c6b8e0 fffff806`7643a169 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`0003e38b : nt!KiProcessExpiredTimerList+0xdc.
fffff806`79c6b9d0 fffff806`765e158e : 00000000`00000000 fffff806`71b24180 fffff806`76f26600 ffffc80a`b6a22080 : nt!KiRetireDpcList+0x9d9.
fffff806`79c6bc60 00000000`00000000 : fffff806`79c6c000 fffff806`79c66000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e.

SYMBOL_NAME: nt!KiTimerWaitTest+1c4.

MODULE_NAME: nt.

IMAGE_NAME: ntkrnlmp.exe.

IMAGE_VERSION: 10.0.19041.329.

STACK_COMMAND: .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET: 1c4.

FAILURE_BUCKET_ID: AV_nt!KiTimerWaitTest.

OS_VERSION: 10.0.19041.1.

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {8c029a8d-9f29-4bde-2664-6010a6365158}

Followup: MachineOwner.
---------
Genişletmek için tıkla...

Mavi ekran hatası hala alıyorum ekran kartını da servise göndertmiştim sorun çıkmadı tek RAM'lar kaldı fakat Memtest86 testindede herhangi bir hata almadım RAM'leri hem Dual Channel olarak hem de Single Channel olarak test ettim.
 
Artı 0 Eksi
Alper Gökmen dedi:
Mavi ekran hatası hala alıyorum ekran kartını da servise göndertmiştim sorun çıkmadı tek RAM'lar kaldı fakat Memtest86 testindede herhangi bir hata almadım RAM'leri hem Dual Channel olarak hem de Single Channel olarak test ettim.
Genişletmek için tıkla...

Sonuç olarak çözüm bulamadınız hala o zaman?
 
Artı 0 Eksi
Sercan Baydar dedi:
Sonuç olarak çözüm bulamadınız hala o zaman?
Genişletmek için tıkla...

Maalesef mavi ekran almam çok sayıda azaldı ama hala alıyorum haftada 3 bazen hiç, bu konuyu açtığım zamanlarda 15 20'şer dakikada 1 hata alıyordum Google'dan YouTube'dan video vs izleyemiyordum.

Sistemi DDR5'e geçirme kararı verdim zaten anakart ve işlemci kaynaklı bir problem olduğunu düşünüyordum ve bu yükseltme sonrası mavi ekran sorunun ortadan kalktı bu tarz sorunu olan bir arkadaş varsa (oyun açıkken mavi ekran yemeyip PC boştayken ya da basit işler için kullanılırken sürekli mavi ekran yiyorsa) bu 2 parçadan birinden şüphelenebilirler.
 
Son düzenleme:
Artı 0 Eksi
Çözüm

Benzer konular

Arashigimo
  • Soru
Ryzen 5 3600 mavi ekran hataları
Mesaj
5
Görüntüleme
414
Persendirian
Persendirian
G
  • Soru
Ryzen 5 3600 sistemde mavi ekran hataları
Mesaj
2
Görüntüleme
356
Görkem Berat Çeker
G
RotasızBey
  • Çözüldü
Çözüldü  Ryzen 5 3600 mavi ekran hataları
Mesaj
6
Görüntüleme
607
RotasızBey
RotasızBey
ygtrcys
  • Soru
R5 3600 sistem mavi ekran hataları
Mesaj
8
Görüntüleme
485
ygtrcys
ygtrcys
TheKill
  • Soru
R5 3600 sistem mavi ekran hataları
Mesaj
1
Görüntüleme
395
Ma'at
Ma'at

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı