PRIME B450M-K II mavi ekran hatası

İşletim sistemi
Windows 11
Tarihe göre sırala Puana göre sırala
EgeN7 dedi:
Hyper-V'ye ihtiyacınız olduğu için şimdilik açık kalabilir. Önceki mesajımda da dediğim gibi, aslında problem depolamadaysa suçu Hyper-V'ye atıyor olabilir, bundan emin olamayabiliriz hemen. Sorun Hyper-V'den de kaynaklanıyor olabilir tabii orası ayrı konu.

Health sekmesinin neden açılmadığını tam kestiremiyorum. Markasını bilmediğiniz bir SSD demiştiniz, bundan dolayı olabilir.

Niye sadece Edge'de olduğuna pek anlam veremedim açıkçası.
Genişletmek için tıkla...
Selam. Bugün yine Call of Duty oynarken mavi ekran yedim. Arkada ise Edge uygulaması olan YouTube Music açıktı. DMP dosyasını bırakıyorum.
 
Artı 0 Eksi
Selam,

- Öncekilerle benzer sayılır, sistem dosyalarında bir hata görünüyor.
- İlk etapta Corsair araçlarını ve Malwarebytes'ı kaldırır mısınız?
- Arka planda çok fazla üçüncü parti program çalıştırmamaya çalışın.
- Bir de tekrardan CMD'yi yönetici olarak çalıştırıp sfc /scannow girer misiniz?


Yine aynı veya benzer bir mavi ekran alırsanız artık temiz kurulum veya RAM testi yapılacak.

- Bu hata için genelde USB'den temiz kurulum önerilmiş.
- Ancak donanımsal bir problem de olabilir.
- Markası belli olmayan SSD'den şüphelenmiyor değilim.

Temiz kurulum sizin için sıkıntı olmayacaksa direkt USB'den temiz kurulum öneririm.

Ama bundan önce bir RAM testi de yapabilirsiniz. Bu hatada RAM kontrolü de tavsiye edilmiş geçmişte.

Daha önce Memtest86 ile RAM testi yapıp RAM'lerde bir problem var mı diye kontrol ettiniz mi?

www.technopat.net

Memtest86 ile Bozuk RAM Testi

Bu rehberimizde Memtes86 ile RAM testi yaparak bozuk RAM modüllerini nasıl tespit edeceğinize bakıyoruz. Bilgisayarda karşılaşılan mavi ekran hataları
www.technopat.net www.technopat.net

* Memtest güncel sürüm:

https://www.memtest86.com/downloads/memtest86-usb.zip



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

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffe78456e9e140, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: ffffe78456e9e140, The process object that initiated the termination.
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2640

    Key  : Analysis.Elapsed.mSec
    Value: 9161

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xef

    Key  : CriticalProcessDied.ExceptionCode
    Value: 68fd8080

    Key  : CriticalProcessDied.Process
    Value: csrss.exe

    Key  : Failure.Bucket
    Value: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_68fd8080_ntdll!RtlpCallVectoredHandlers

    Key  : Failure.Hash
    Value: {aadee5fa-7243-6ff6-d420-10beafe5c5ed}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  ef

BUGCHECK_P1: ffffe78456e9e140

BUGCHECK_P2: 0

BUGCHECK_P3: ffffe78456e9e140

BUGCHECK_P4: 0

FILE_IN_CAB:  070423-11687-01.dmp

PROCESS_NAME:  csrss.exe

CRITICAL_PROCESS:  csrss.exe

EXCEPTION_RECORD:  ffffe78456e9e7c0 -- (.exr 0xffffe78456e9e7c0)
ExceptionAddress: ffffe78456270d50
   ExceptionCode: 000085eb
  ExceptionFlags: 000010f9
NumberParameters: 1516952840
   Parameter[0]: ffffe7845c525718
   Parameter[1]: 0000000000000098
   Parameter[2]: 00000000000000a8
   Parameter[3]: 0000000000000002
   Parameter[4]: 0000000000000000
   Parameter[5]: 00000000000000e1
   Parameter[6]: 0000000000000040
   Parameter[7]: 00000000000003e1
   Parameter[8]: 0000000000000000
   Parameter[9]: 0000000000000000
   Parameter[10]: 0000000000000032
   Parameter[11]: 0000000000000159
   Parameter[12]: 0000000000000602
   Parameter[13]: 00000000000000e2
   Parameter[14]: 0000000000000644

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

EXCEPTION_CODE_STR:  85eb

EXCEPTION_PARAMETER1:  ffffe7845c525718

EXCEPTION_PARAMETER2:  0000000000000098

EXCEPTION_PARAMETER3:  00000000000000a8

EXCEPTION_PARAMETER4: 0

EXCEPTION_STR:  0x85eb

STACK_TEXT:
ffffd68d`88347d48 fffff801`547b7afb     : 00000000`000000ef ffffe784`56e9e140 00000000`00000000 ffffe784`56e9e140 : nt!KeBugCheckEx
ffffd68d`88347d50 fffff801`546d5659     : ffffe784`56e9e140 fffff801`541381c1 00000000`00000000 fffff801`54137a4b : nt!PspCatchCriticalBreak+0x11b
ffffd68d`88347de0 fffff801`545a7657     : ffffe784`56e9e140 00000000`c0000005 ffffe784`56e9e140 00000000`00000001 : nt!PspTerminateAllThreads+0x1d16f1
ffffd68d`88347e50 fffff801`545a7431     : ffffffff`ffffffff ffffe784`56e9e140 ffffe784`68fd8080 ffffe784`56e9e140 : nt!PspTerminateProcess+0xe3
ffffd68d`88347e90 fffff801`54240fe8     : 00000008`00000314 ffffe784`68fd8080 ffffe784`56e9e140 fffff801`5474f2e7 : nt!NtTerminateProcess+0xb1
ffffd68d`88347f10 fffff801`54231b10     : fffff801`542ced79 ffffffff`ffffffff 00000008`c95b0df0 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x28
ffffd68d`883480a8 fffff801`542ced79     : ffffffff`ffffffff 00000008`c95b0df0 00000000`00000001 ffffd68d`883480e0 : nt!KiServiceLinkage
ffffd68d`883480b0 fffff801`542419fc     : ffffe784`56e9e7c0 fffff801`54039dd9 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1bb029
ffffd68d`88348900 fffff801`5423cf0e     : 00000000`000a2cee ffffb300`f6d5da00 00000008`c95b1a50 ffffe784`00000000 : nt!KiExceptionDispatch+0x13c
ffffd68d`88348ae0 00007ffe`79687928     : 00007ffe`7698a8ec 00007ffe`769a1000 00000008`c95b1770 00000008`c95b1090 : nt!KiPageFault+0x44e
00000008`c95b1000 00007ffe`7962e232     : 00000008`c95b1770 00000008`c95b1280 00000000`00000000 00000000`00000000 : ntdll!RtlpCallVectoredHandlers+0x10
00000008`c95b1030 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlDispatchException+0x62


SYMBOL_NAME:  ntdll!RtlpCallVectoredHandlers+10

MODULE_NAME: ntdll

IMAGE_NAME:  ntdll.dll

IMAGE_VERSION:  10.0.22621.1844

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  10

FAILURE_BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_68fd8080_ntdll!RtlpCallVectoredHandlers

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {aadee5fa-7243-6ff6-d420-10beafe5c5ed}

Followup:     MachineOwner
--------


ntdll.dll + Edge çökmesi ile alakalı bir konu:
answers.microsoft.com

Chromium Edge Browser Keeps Crashing!!! - Microsoft Q&A

In the Event Viewer, it says the failed module is "ntdll.dll". Even with Administrator mode I cannot replace the dll with an older version. The browser always crashes almost 1 hour after I lock my computer. How can I fix that? The Event Viewer…
answers.microsoft.com
 
Son düzenleme:
Artı 0 Eksi
EgeN7 dedi:
Selam,

- Öncekilerle benzer sayılır, sistem dosyalarında bir hata görünüyor.
- İlk etapta Corsair araçlarını ve Malwarebytes'ı kaldırır mısınız?
- Arka planda çok fazla üçüncü parti program çalıştırmamaya çalışın.
- Bir de tekrardan CMD'yi yönetici olarak çalıştırıp sfc /scannow girer misiniz?


Yine aynı veya benzer bir mavi ekran alırsanız artık temiz kurulum veya RAM testi yapılacak.

- Bu hata için genelde USB'den temiz kurulum önerilmiş.
- Ancak donanımsal bir problem de olabilir.
- Markası belli olmayan SSD'den şüphelenmiyor değilim.

Temiz kurulum sizin için sıkıntı olmayacaksa direkt USB'den temiz kurulum öneririm.

Ama bundan önce bir RAM testi de yapabilirsiniz. Bu hatada RAM kontrolü de tavsiye edilmiş geçmişte.

Daha önce Memtest86 ile RAM testi yapıp RAM'lerde bir problem var mı diye kontrol ettiniz mi?

www.technopat.net

Memtest86 ile Bozuk RAM Testi

Bu rehberimizde Memtes86 ile RAM testi yaparak bozuk RAM modüllerini nasıl tespit edeceğinize bakıyoruz. Bilgisayarda karşılaşılan mavi ekran hataları
www.technopat.net www.technopat.net

* Memtest güncel sürüm:

https://www.memtest86.com/downloads/memtest86-usb.zip



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

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffe78456e9e140, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: ffffe78456e9e140, The process object that initiated the termination.
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2640

    Key  : Analysis.Elapsed.mSec
    Value: 9161

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xef

    Key  : CriticalProcessDied.ExceptionCode
    Value: 68fd8080

    Key  : CriticalProcessDied.Process
    Value: csrss.exe

    Key  : Failure.Bucket
    Value: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_68fd8080_ntdll!RtlpCallVectoredHandlers

    Key  : Failure.Hash
    Value: {aadee5fa-7243-6ff6-d420-10beafe5c5ed}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  ef

BUGCHECK_P1: ffffe78456e9e140

BUGCHECK_P2: 0

BUGCHECK_P3: ffffe78456e9e140

BUGCHECK_P4: 0

FILE_IN_CAB:  070423-11687-01.dmp

PROCESS_NAME:  csrss.exe

CRITICAL_PROCESS:  csrss.exe

EXCEPTION_RECORD:  ffffe78456e9e7c0 -- (.exr 0xffffe78456e9e7c0)
ExceptionAddress: ffffe78456270d50
   ExceptionCode: 000085eb
  ExceptionFlags: 000010f9
NumberParameters: 1516952840
   Parameter[0]: ffffe7845c525718
   Parameter[1]: 0000000000000098
   Parameter[2]: 00000000000000a8
   Parameter[3]: 0000000000000002
   Parameter[4]: 0000000000000000
   Parameter[5]: 00000000000000e1
   Parameter[6]: 0000000000000040
   Parameter[7]: 00000000000003e1
   Parameter[8]: 0000000000000000
   Parameter[9]: 0000000000000000
   Parameter[10]: 0000000000000032
   Parameter[11]: 0000000000000159
   Parameter[12]: 0000000000000602
   Parameter[13]: 00000000000000e2
   Parameter[14]: 0000000000000644

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

EXCEPTION_CODE_STR:  85eb

EXCEPTION_PARAMETER1:  ffffe7845c525718

EXCEPTION_PARAMETER2:  0000000000000098

EXCEPTION_PARAMETER3:  00000000000000a8

EXCEPTION_PARAMETER4: 0

EXCEPTION_STR:  0x85eb

STACK_TEXT:
ffffd68d`88347d48 fffff801`547b7afb     : 00000000`000000ef ffffe784`56e9e140 00000000`00000000 ffffe784`56e9e140 : nt!KeBugCheckEx
ffffd68d`88347d50 fffff801`546d5659     : ffffe784`56e9e140 fffff801`541381c1 00000000`00000000 fffff801`54137a4b : nt!PspCatchCriticalBreak+0x11b
ffffd68d`88347de0 fffff801`545a7657     : ffffe784`56e9e140 00000000`c0000005 ffffe784`56e9e140 00000000`00000001 : nt!PspTerminateAllThreads+0x1d16f1
ffffd68d`88347e50 fffff801`545a7431     : ffffffff`ffffffff ffffe784`56e9e140 ffffe784`68fd8080 ffffe784`56e9e140 : nt!PspTerminateProcess+0xe3
ffffd68d`88347e90 fffff801`54240fe8     : 00000008`00000314 ffffe784`68fd8080 ffffe784`56e9e140 fffff801`5474f2e7 : nt!NtTerminateProcess+0xb1
ffffd68d`88347f10 fffff801`54231b10     : fffff801`542ced79 ffffffff`ffffffff 00000008`c95b0df0 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x28
ffffd68d`883480a8 fffff801`542ced79     : ffffffff`ffffffff 00000008`c95b0df0 00000000`00000001 ffffd68d`883480e0 : nt!KiServiceLinkage
ffffd68d`883480b0 fffff801`542419fc     : ffffe784`56e9e7c0 fffff801`54039dd9 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1bb029
ffffd68d`88348900 fffff801`5423cf0e     : 00000000`000a2cee ffffb300`f6d5da00 00000008`c95b1a50 ffffe784`00000000 : nt!KiExceptionDispatch+0x13c
ffffd68d`88348ae0 00007ffe`79687928     : 00007ffe`7698a8ec 00007ffe`769a1000 00000008`c95b1770 00000008`c95b1090 : nt!KiPageFault+0x44e
00000008`c95b1000 00007ffe`7962e232     : 00000008`c95b1770 00000008`c95b1280 00000000`00000000 00000000`00000000 : ntdll!RtlpCallVectoredHandlers+0x10
00000008`c95b1030 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlDispatchException+0x62


SYMBOL_NAME:  ntdll!RtlpCallVectoredHandlers+10

MODULE_NAME: ntdll

IMAGE_NAME:  ntdll.dll

IMAGE_VERSION:  10.0.22621.1844

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  10

FAILURE_BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_68fd8080_ntdll!RtlpCallVectoredHandlers

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {aadee5fa-7243-6ff6-d420-10beafe5c5ed}

Followup:     MachineOwner
--------


ntdll.dll + Edge çökmesi ile alakalı bir konu:
answers.microsoft.com

Chromium Edge Browser Keeps Crashing!!! - Microsoft Q&A

In the Event Viewer, it says the failed module is "ntdll.dll". Even with Administrator mode I cannot replace the dll with an older version. The browser always crashes almost 1 hour after I lock my computer. How can I fix that? The Event Viewer…
answers.microsoft.com
Genişletmek için tıkla...
Tekrardan selam hocam. RPCS3 ile God of War 3 oynarken aldım bu sefer de hatayı. Tekrardan dmp dosyasını bırakıyorum. Memtest86 testini de yaptım ve sorun çıkmadı. Sonucunu bırakıyorum. Şimdiden teşekkürler.
 
Artı 0 Eksi
RPCS3'ten kaynaklanması çok zor denilmiş.
Blue screens after using RPCS3

Mavi ekrana yazılımın değil donanımdaki bir problemin sebebiyet vereceği belirtilmiş.

Örnek olarak daha önceden ortaya çıkmayan bir arızanın/stabilite probleminin herhangi bir oyunda, yazılımda vb. ortaya çıkabileceğinden bahsetmiş birçok kişi.

Mesela Reddit'teki postta undervolt yapıldığı için problem yaşanmış gibi görünüyor.

Genel olarak işlemci ve RAM üzerinde odaklanılmış.

  • Benim fikrim işlemci veya RAM'lerde bir stabilite sorunu olması.
  • Veya Windows dosya sisteminin bozulması / SSD'deki bir arıza.

Herhangi bir undervolt / overclock var mı işlemcide?

Gerçi yok gibi görünüyor ama yine de sorayım.
Rich (BB code): 
  Processor Version             AMD Ryzen 5 3500X 6-Core Processor          
  Processor Voltage             8bh - 1.1V
  External Clock                100MHz
  Max Speed                     4100MHz
  Current Speed                 3600MHz


XMP kapalı bir şekilde oynayıp benzer senaryolarda mavi ekran alıyor musunuz diye kontrol eder misiniz?

Bu arada chipset sürücülerini sormuş muydum hatırlayamadım.
Güncel değilse AMD sitesinden güncelleyebilirsiniz.


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

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

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x1c9f3, File: 0x20c4a - C:\ProgramData\Dbg\sym\bfs.sys\D0FEE6E614000\bfs.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2906

    Key  : Analysis.Elapsed.mSec
    Value: 2959

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: 0x3B_C0000006_nt!HvpGetCellPaged

    Key  : Failure.Hash
    Value: {68f3db38-ae8e-4bae-c37a-85819946495f}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000006

BUGCHECK_P2: fffff80450aad88c

BUGCHECK_P3: fffff4002fbe1390

BUGCHECK_P4: 0

FILE_IN_CAB:  071023-12343-01.dmp

CONTEXT:  fffff4002fbe1390 -- (.cxr 0xfffff4002fbe1390)
rax=0000029acd881000 rbx=0000000003cc0b78 rcx=0000029acd881b78
rdx=ffff9f057767f200 rsi=fffff4002fbe1e80 rdi=00000000a88ef046
rip=fffff80450aad88c rsp=fffff4002fbe1db0 rbp=fffff4002fbe1ee0
 r8=fffff4002fbe1e84  r9=00000000000000c0 r10=ffff9f0574446000
r11=0000000004853ff0 r12=00000000a88ef046 r13=fffff4002fbe2250
r14=0000029ace41ab1c r15=0000029ace41a024
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!HvpGetCellPaged+0x7c:
fffff804`50aad88c 8b01            mov     eax,dword ptr [rcx] ds:002b:0000029a`cd881b78=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

STACK_TEXT:
fffff400`2fbe1db0 fffff804`50aac73e     : 00000000`a88ef046 00000000`e9c5e935 fffff400`2fbe2250 00000000`00000000 : nt!HvpGetCellPaged+0x7c
fffff400`2fbe1de0 fffff804`50aae577     : ffff9f05`7d473990 fffff400`2fbe2160 fffff400`2fbe2060 fffff400`2fbe2180 : nt!CmpWalkOneLevel+0x73e
fffff400`2fbe1f40 fffff804`50ab3435     : 00000000`0000001c fffff400`2fbe2470 fffff400`2fbe23f8 00000000`00000000 : nt!CmpDoParseKey+0x867
fffff400`2fbe2380 fffff804`50ab79db     : fffff804`50ab3101 ffffe403`00000000 ffffe403`67a2cae0 00000000`00000001 : nt!CmpParseKey+0x2e5
fffff400`2fbe2570 fffff804`50ab6e52     : ffffe403`67a2cae0 fffff400`2fbe27a0 00000000`00000040 ffffe403`55f6a900 : nt!ObpLookupObjectName+0x63b
fffff400`2fbe2710 fffff804`50aba184     : 00000000`00000000 ffffe403`55f6a900 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
fffff400`2fbe2840 fffff804`50abab48     : 000000ca`c8a7d6e8 00000000`00000000 fffff400`2fbe2b60 fffff804`50b49d99 : nt!CmOpenKey+0x2c4
fffff400`2fbe2a90 fffff804`50840fe8     : ffffe403`5e21d080 ffff8d81`00000000 00000237`3a8322d8 ffffe403`00000000 : nt!NtOpenKeyEx+0x48
fffff400`2fbe2ae0 00007ff8`22bd1164     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000ca`c8a7d6c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`22bd1164


SYMBOL_NAME:  nt!HvpGetCellPaged+7c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1848

STACK_COMMAND:  .cxr 0xfffff4002fbe1390 ; kb

BUCKET_ID_FUNC_OFFSET:  7c

FAILURE_BUCKET_ID:  0x3B_C0000006_nt!HvpGetCellPaged

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {68f3db38-ae8e-4bae-c37a-85819946495f}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
EgeN7 dedi:
RPCS3'ten kaynaklanması çok zor denilmiş.
Blue screens after using RPCS3

Mavi ekrana yazılımın değil donanımdaki bir problemin sebebiyet vereceği belirtilmiş.

Örnek olarak daha önceden ortaya çıkmayan bir arızanın/stabilite probleminin herhangi bir oyunda, yazılımda vb. ortaya çıkabileceğinden bahsetmiş birçok kişi.

Mesela Reddit'teki postta undervolt yapıldığı için problem yaşanmış gibi görünüyor.

Genel olarak işlemci ve RAM üzerinde odaklanılmış.

  • Benim fikrim işlemci veya RAM'lerde bir stabilite sorunu olması.
  • Veya Windows dosya sisteminin bozulması / SSD'deki bir arıza.

Herhangi bir undervolt / overclock var mı işlemcide?

Gerçi yok gibi görünüyor ama yine de sorayım.
Rich (BB code): 
  Processor Version             AMD Ryzen 5 3500X 6-Core Processor         
  Processor Voltage             8bh - 1.1V
  External Clock                100MHz
  Max Speed                     4100MHz
  Current Speed                 3600MHz


XMP kapalı bir şekilde oynayıp benzer senaryolarda mavi ekran alıyor musunuz diye kontrol eder misiniz?

Bu arada chipset sürücülerini sormuş muydum hatırlayamadım.
Güncel değilse AMD sitesinden güncelleyebilirsiniz.


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

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

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x1c9f3, File: 0x20c4a - C:\ProgramData\Dbg\sym\bfs.sys\D0FEE6E614000\bfs.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2906

    Key  : Analysis.Elapsed.mSec
    Value: 2959

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: 0x3B_C0000006_nt!HvpGetCellPaged

    Key  : Failure.Hash
    Value: {68f3db38-ae8e-4bae-c37a-85819946495f}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000006

BUGCHECK_P2: fffff80450aad88c

BUGCHECK_P3: fffff4002fbe1390

BUGCHECK_P4: 0

FILE_IN_CAB:  071023-12343-01.dmp

CONTEXT:  fffff4002fbe1390 -- (.cxr 0xfffff4002fbe1390)
rax=0000029acd881000 rbx=0000000003cc0b78 rcx=0000029acd881b78
rdx=ffff9f057767f200 rsi=fffff4002fbe1e80 rdi=00000000a88ef046
rip=fffff80450aad88c rsp=fffff4002fbe1db0 rbp=fffff4002fbe1ee0
 r8=fffff4002fbe1e84  r9=00000000000000c0 r10=ffff9f0574446000
r11=0000000004853ff0 r12=00000000a88ef046 r13=fffff4002fbe2250
r14=0000029ace41ab1c r15=0000029ace41a024
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!HvpGetCellPaged+0x7c:
fffff804`50aad88c 8b01            mov     eax,dword ptr [rcx] ds:002b:0000029a`cd881b78=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

STACK_TEXT:
fffff400`2fbe1db0 fffff804`50aac73e     : 00000000`a88ef046 00000000`e9c5e935 fffff400`2fbe2250 00000000`00000000 : nt!HvpGetCellPaged+0x7c
fffff400`2fbe1de0 fffff804`50aae577     : ffff9f05`7d473990 fffff400`2fbe2160 fffff400`2fbe2060 fffff400`2fbe2180 : nt!CmpWalkOneLevel+0x73e
fffff400`2fbe1f40 fffff804`50ab3435     : 00000000`0000001c fffff400`2fbe2470 fffff400`2fbe23f8 00000000`00000000 : nt!CmpDoParseKey+0x867
fffff400`2fbe2380 fffff804`50ab79db     : fffff804`50ab3101 ffffe403`00000000 ffffe403`67a2cae0 00000000`00000001 : nt!CmpParseKey+0x2e5
fffff400`2fbe2570 fffff804`50ab6e52     : ffffe403`67a2cae0 fffff400`2fbe27a0 00000000`00000040 ffffe403`55f6a900 : nt!ObpLookupObjectName+0x63b
fffff400`2fbe2710 fffff804`50aba184     : 00000000`00000000 ffffe403`55f6a900 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
fffff400`2fbe2840 fffff804`50abab48     : 000000ca`c8a7d6e8 00000000`00000000 fffff400`2fbe2b60 fffff804`50b49d99 : nt!CmOpenKey+0x2c4
fffff400`2fbe2a90 fffff804`50840fe8     : ffffe403`5e21d080 ffff8d81`00000000 00000237`3a8322d8 ffffe403`00000000 : nt!NtOpenKeyEx+0x48
fffff400`2fbe2ae0 00007ff8`22bd1164     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000ca`c8a7d6c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`22bd1164


SYMBOL_NAME:  nt!HvpGetCellPaged+7c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1848

STACK_COMMAND:  .cxr 0xfffff4002fbe1390 ; kb

BUCKET_ID_FUNC_OFFSET:  7c

FAILURE_BUCKET_ID:  0x3B_C0000006_nt!HvpGetCellPaged

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {68f3db38-ae8e-4bae-c37a-85819946495f}

Followup:     MachineOwner
---------
Genişletmek için tıkla...
İşlemcimde bir şey yok. Chipset sürücüleri de güncel. XMP'yi kapatırsam performansım azalmaz mı? RAM testinde sorun çıkmadı zaten. İstiyorsanız termal macun yenileyeyim.
 
Artı 0 Eksi
Aeronight dedi:
XMP'yi kapatırsam performansım azalmaz mı?
Genişletmek için tıkla...
- Deneme amaçlı. Sonsuza dek kapalı kalmayacak tabii ki. 😀

Aeronight dedi:
RAM testinde sorun çıkmadı zaten.
Genişletmek için tıkla...
- Bazen Memtest86 bile sorun yakalayamıyor.
- Burada önerim 2 RAM'i birlikte XMP kapalı şekilde mavi ekran aldığınız senaryoda test etmeniz.
- Mavi ekran aldırmaya çalışın, bir süre deneyin sistemi.

- Yine hata alırsanız tek RAM ile ama XMP açık şekilde deneyin.
- Yine alırsanız takılı olanı sökün, diğer RAM'i takın, XMP açın ve yine deneyin.
- Yani RAM'leri tek tek denemiş olacaksınız.

Aeronight dedi:
İstiyorsanız termal macun yenileyeyim.
Genişletmek için tıkla...
- Sıcaklıklarda bir problem yoksa o kadar önemli değil.
 
Artı 0 Eksi
Hocam dediklerinizi yaptım. Oyunlarda sıkıntı çıkarmıyor ama bu sefer de ne zaman bilgisayardan bir video açsam mavi ekran yiyorum. YouTube'da vs. sorun yok. Video editlerken vs. sorun oluyor. Videoyu açmak istiyorum ve ileri sarıyorum acaba oldu mu diye ama sardıktan 5-10 saniye sonra mavi ekran yiyorum. Muhtemelen sorun SSD'de gibi.

Ne önerirsiniz hocam? SSD mi değişeyim? Sadece video izlerken oluyor çünkü. Edge vs. değil şuan.

Bir şey daha fark ettim. Şuan video playerımı değiştirdim ve mavi ekran almıyorum ama fotoğraflarda gezinirken de oldu bu sorun. SFC komutunu girdim sorun bulmadı.
 
Son düzenleme:
Artı 0 Eksi

Benzer konular

Grimnir
  • Soru
Ryzen 5 5600G - Prime B450M K II mavi ekran hatası
Mesaj
2
Görüntüleme
391
Grimnir
Grimnir
H
  • Çözüldü
Çözüldü  ASUS Prime B450 M k II "attempted wrıtereadonly Memory "mavi ekran hatası
Mesaj
4
Görüntüleme
868
hsnglc
H
mrtckr05
  • Soru
B450M-K sistemde mavi ekran hatası
Mesaj
2
Görüntüleme
557
mrtckr05
mrtckr05
U
  • Soru
ASUS Prime B450 m k II RAM mavi ekran veriyor
Mesaj
1
Görüntüleme
407
xxMFIxx
xxMFIxx
Ducuk
  • Soru
ASUS Prime B450M-K BIOS güncellemesinden sonra mavi ekran hataları
2 3
Mesaj
27
Görüntüleme
2.719
darthmotun
darthmotun

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı