R5 2600 bir şey indirirken mavi ekran hatası

Shinnohana

Femtopat
Katılım
22 Kasım 2022
Mesajlar
3
Daha fazla  
Cinsiyet
Erkek
Bilgisayara bir şey indirirken mavi ekran yiyorum. Özellikler:
  • AMD Ryzen 5 2600 Six-Core Processor 3.40 GHz
  • MSI RTX 2060 Super
  • ASUS B450M-K anakart
  • 16 GB RAM
Minidump: Mavi ekran.rar
 
WINLOGON_FATAL_ERROR (c000021a)
BAD_SYSTEM_CONFIG_INFO (74)
SYSTEM_SERVICE_EXCEPTION (3b)
CRITICAL_PROCESS_DIED (ef)

* Hatalar çeşitli.

* Sebepleri SSD/HDD olabilir, Windows'un bozulmaya başlaması olabilir, RAM veya eskimiş BIOS sürümü de olabilir.

* HDD kullanıyorsanız HD Tune indirip Health sekmesini paylaşır mısınız?
* Ayrıca Error Scan sekmesine gidip "Quick Scan" tikini kaldırıp tarama yapın, sonucu paylaşın.

* SSD kullanıyorsanız CrystalDiskInfo vb. bir araç yardımıyla SSD'nin/SSD'lerin sağlık durumunu ve altındaki değerlerini paylaşın.

* BIOS'unuz eski, 3802 sürümünü kullanıyorsunuz. 4002 sürümüne güncelleyin.

* Ekran kartı sürücünüz eski. Güncelleyin:
* GeForce Game Ready Driver | 535.98 | Windows 10 64-bit, Windows 11 | NVIDIA


* Windows 10 versiyon 2004 kullanıyorsunuz, eski kalmış.
* 22H2'ye güncelleyin.



* Üstteki adımlardan sonra hatalar devam ediyorsa RAM testi yapın. Sonuçları paylaşın.
* Video: Memtest86 ile RAM testi


* Tüm bunlar sonucunda hâlâ mavi ekran almaya devam ederseniz yeni aldığınız mavi ekranların dökümlerini de paylaşın. Duruma bakalım. Aynı hataları alıyorsanız USB'den temiz bir Windows kurulumu gerekecek.


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

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffff910a43cbf8f0, String that identifies the problem.
Arg2: ffffffffc0000006, Error Code.
Arg3: 00007ffa2fb99105
Arg4: 000000d1952be140

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

ETW minidump data unavailable

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2452

    Key  : Analysis.Elapsed.mSec
    Value: 4300

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xc000021a

    Key  : Failure.Bucket
    Value: 0xc000021a_c0000006_csrss.exe_Terminated_nt!PopTransitionSystemPowerStateEx

    Key  : Failure.Hash
    Value: {b3ffc8fa-795c-38e6-3bd9-0b1e1680adf3}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  c000021a

BUGCHECK_P1: ffff910a43cbf8f0

BUGCHECK_P2: ffffffffc0000006

BUGCHECK_P3: 7ffa2fb99105

BUGCHECK_P4: d1952be140

FILE_IN_CAB:  053023-10250-01.dmp

ERROR_CODE: (NTSTATUS) 0xc000021a - { nemli Sistem Hatas }  %hs sistem i lemi, 0x

EXCEPTION_CODE_STR:  c000021a

EXCEPTION_PARAMETER1:  ffff910a43cbf8f0

EXCEPTION_PARAMETER2:  ffffffffc0000006

EXCEPTION_PARAMETER3:  00007ffa2fb99105

EXCEPTION_PARAMETER4: d1952be140

PROCESS_NAME:  csrss.exe

ADDITIONAL_DEBUG_TEXT:  Windows SubSystem

IMAGE_NAME:  ntkrnlmp.exe

MODULE_NAME: nt

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:
fffffc80`30261598 fffff807`793b42fa     : 00000000`0000004c 00000000`c000021a fffffc80`2edf73f0 ffffa60f`bf3f0010 : nt!KeBugCheckEx
fffffc80`302615a0 fffff807`793952d8     : fffffc80`302616c0 fffffc80`30261660 fffffc80`302616c0 fffffc80`30261660 : nt!PopGracefulShutdown+0x29a
fffffc80`302615e0 fffff807`7939bf8c     : 00000000`00000001 fffff807`00000006 00000000`00000005 fffff807`00000000 : nt!PopTransitionSystemPowerStateEx+0x11e4
fffffc80`302616a0 fffff807`78e0f4f8     : fffffc80`30261898 ffffdfad`9dce04a3 00000000`00000000 fffff807`791877c5 : nt!NtSetSystemPowerState+0x4c
fffffc80`30261880 fffff807`78e00880     : fffff807`7924588d 00000000`00000014 ffffffff`ffffff00 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
fffffc80`30261a18 fffff807`7924588d     : 00000000`00000014 ffffffff`ffffff00 00000000`00000000 fffff807`79623ba0 : nt!KiServiceLinkage
fffffc80`30261a20 fffff807`79171939     : 00000000`00000000 ffffa60f`afa906c0 00000000`00000000 00000000`00000000 : nt!PopIssueActionRequest+0xd3e35
fffffc80`30261ac0 fffff807`78d243b4     : 00000000`00000001 00000000`00000000 ffffffff`ffffffff fffff807`79623c00 : nt!PopPolicyWorkerAction+0x79
fffffc80`30261b30 fffff807`78c8e5c5     : ffffa60f`00000001 ffffa60f`bab15040 fffff807`78d24320 ffffa60f`00000000 : nt!PopPolicyWorkerThread+0x94
fffffc80`30261b70 fffff807`78d265f5     : ffffa60f`bab15040 00000000`00000080 ffffa60f`afa94140 000f8067`b4bbbdff : nt!ExpWorkerThread+0x105
fffffc80`30261c10 fffff807`78e048d8     : ffff8000`a3500180 ffffa60f`bab15040 fffff807`78d265a0 000000ae`00000005 : nt!PspSystemThreadStartup+0x55
fffffc80`30261c60 00000000`00000000     : fffffc80`30262000 fffffc80`3025c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!PopTransitionSystemPowerStateEx+11e4

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  11e4

FAILURE_BUCKET_ID:  0xc000021a_c0000006_csrss.exe_Terminated_nt!PopTransitionSystemPowerStateEx

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b3ffc8fa-795c-38e6-3bd9-0b1e1680adf3}

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


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

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
Arg1: 0000000000000002, (reserved)
Arg2: ffffeb091f7afa20, (reserved)
Arg3: 0000000000000002, (reserved)
Arg4: ffffffffc000014d, usually the NT status code.

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x386a7, File: 0x3c50e - C:\ProgramData\Dbg\sym\storahci.sys\6A1B92AB32000\storahci.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1359

    Key  : Analysis.Elapsed.mSec
    Value: 1402

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x74

    Key  : Failure.Bucket
    Value: 0x74_2_c000014d_nt!CmpLoadHiveThread

    Key  : Failure.Hash
    Value: {3438e634-9325-e303-ce4f-669c61a78520}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  74

BUGCHECK_P1: 2

BUGCHECK_P2: ffffeb091f7afa20

BUGCHECK_P3: 2

BUGCHECK_P4: ffffffffc000014d

FILE_IN_CAB:  053023-10937-01.dmp

ERROR_CODE: (NTSTATUS) 0xc000014d - Kay t Defteri taraf ndan ba lat lan bir G/  i lemi kurtar lamaz bi imde ba ar s z oldu. Kay t Defteri, kendi sistem g r nt s n  i eren dosyalardan birini okuyamad , yazamad  veya temizleyemedi.

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

STACK_TEXT:
ffffeb09`1f7af948 fffff801`67394ffc     : 00000000`00000074 00000000`00000002 ffffeb09`1f7afa20 00000000`00000002 : nt!KeBugCheckEx
ffffeb09`1f7af950 fffff801`66f265f5     : ffffc309`4db59080 ffffc309`4db59080 fffff801`67394830 00000000`00000002 : nt!CmpLoadHiveThread+0x7cc
ffffeb09`1f7afc10 fffff801`670048d8     : ffff9e81`73e00180 ffffc309`4db59080 fffff801`66f265a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffeb09`1f7afc60 00000000`00000000     : ffffeb09`1f7b0000 ffffeb09`1f7aa000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!CmpLoadHiveThread+7cc

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  7cc

FAILURE_BUCKET_ID:  0x74_2_c000014d_nt!CmpLoadHiveThread

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3438e634-9325-e303-ce4f-669c61a78520}

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


*******************************************************************************
*                                                                             *
*                        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: fffff80549c9f352, Address of the instruction which caused the BugCheck
Arg3: ffffde893abe1580, 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                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2156

    Key  : Analysis.Elapsed.mSec
    Value: 5444

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

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

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

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

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000006

BUGCHECK_P2: fffff80549c9f352

BUGCHECK_P3: ffffde893abe1580

BUGCHECK_P4: 0

FILE_IN_CAB:  053023-21093-01.dmp

CONTEXT:  ffffde893abe1580 -- (.cxr 0xffffde893abe1580)
rax=0000000000000000 rbx=ffffde893abe1fd0 rcx=0000000000000007
rdx=0000000003e27d58 rsi=ffffde893abe22a0 rdi=ffffba0c0de2e000
rip=fffff80549c9f352 rsp=ffffde893abe1f88 rbp=ffffde893abe2089
 r8=000000000000001c  r9=ffff9183d2c0d080 r10=000001e4d7bb8d58
r11=0000000000000d58 r12=00000000cad3159d r13=ffffde893abe2230
r14=000000000000003e r15=000001e4d7c33024
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!HvpGetCellPaged+0xa2:
fffff805`49c9f352 418b02          mov     eax,dword ptr [r10] ds:002b:000001e4`d7bb8d58=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

STACK_TEXT:
ffffde89`3abe1f88 fffff805`49c71fcf     : 00000000`00000000 ffffba0c`0de2e000 ffffde89`3abe2230 ffffde89`3abe22a0 : nt!HvpGetCellPaged+0xa2
ffffde89`3abe1f90 fffff805`49c79810     : 00000001`ffffffff 00000000`686bb72a 00000000`0000003e 00000000`686bb72a : nt!CmpDoCompareKeyName+0x3f
ffffde89`3abe1fd0 fffff805`49c1a439     : ffffba0c`13855810 00000000`00000001 ffffde89`3abe21d0 ffffde89`3abe2250 : nt!CmpWalkOneLevel+0x700
ffffde89`3abe20d0 fffff805`49c19953     : 00000001`0000001c ffffde89`3abe2420 ffffde89`3abe23d8 ffff9183`d1ad9700 : nt!CmpDoParseKey+0x849
ffffde89`3abe2370 fffff805`49c1501e     : fffff805`49c19601 00000000`00000000 ffff9183`d1ad9700 00000002`07192001 : nt!CmpParseKey+0x2c3
ffffde89`3abe2510 fffff805`49c0ccea     : ffff9183`d1ad9700 ffffde89`3abe2778 00000000`00000040 ffff9183`c8d51da0 : nt!ObpLookupObjectName+0x3fe
ffffde89`3abe26e0 fffff805`49c0cacc     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9183`c8d51da0 : nt!ObOpenObjectByNameEx+0x1fa
ffffde89`3abe2810 fffff805`49c0c5e1     : 0000005d`aad7d4e8 ffffde89`3abe2b80 00000000`00000001 fffff805`498211fe : nt!ObOpenObjectByName+0x5c
ffffde89`3abe2860 fffff805`49c0c30f     : 00000000`00000000 00007ff9`34223750 0000005d`aad7dbe8 00000000`00000000 : nt!CmOpenKey+0x2c1
ffffde89`3abe2ac0 fffff805`49a0f4f8     : ffff9183`d2c0d080 00000000`00000010 ffffde89`00000001 ffff9183`00000000 : nt!NtOpenKeyEx+0xf
ffffde89`3abe2b00 00007ff9`34e0f474     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000005d`aad7d488 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`34e0f474


SYMBOL_NAME:  nt!HvpGetCellPaged+a2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr 0xffffde893abe1580 ; kb

BUCKET_ID_FUNC_OFFSET:  a2

FAILURE_BUCKET_ID:  0x3B_C0000006_nt!HvpGetCellPaged

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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


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

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

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2437

    Key  : Analysis.Elapsed.mSec
    Value: 4232

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xef

    Key  : CriticalProcessDied.ExceptionCode
    Value: 8e3c6080

    Key  : CriticalProcessDied.Process
    Value: csrss.exe

    Key  : Failure.Bucket
    Value: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_8e3c6080_nt!PspCatchCriticalBreak

    Key  : Failure.Hash
    Value: {27aefa90-6255-38b3-9cb2-d4c6815bddd7}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  ef

BUGCHECK_P1: ffffb58c8abd5240

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  053023-10296-01.dmp

PROCESS_NAME:  csrss.exe

CRITICAL_PROCESS:  csrss.exe

EXCEPTION_RECORD:  ffffb58c8abd5980 -- (.exr 0xffffb58c8abd5980)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

EXCEPTION_STR:  0x0

STACK_TEXT:
ffffad0a`72a59d88 fffff801`0870d842     : 00000000`000000ef ffffb58c`8abd5240 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffad0a`72a59d90 fffff801`0860cbb7     : 00000000`00000001 fffff801`08113a19 00000000`00000002 fffff801`080eb06b : nt!PspCatchCriticalBreak+0x10e
ffffad0a`72a59e30 fffff801`08499698     : ffffb58c`00000000 00000000`00000000 ffffb58c`8abd5240 ffffb58c`8abd5678 : nt!PspTerminateAllThreads+0x17291b
ffffad0a`72a59ea0 fffff801`0849926c     : ffffb58c`8abd5240 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffffad0a`72a59ee0 fffff801`0820f4f8     : ffffb58c`8abd5240 ffffb58c`8e3c6080 ffffad0a`72a59fd0 fffff801`0852e042 : nt!NtTerminateProcess+0x9c
ffffad0a`72a59f50 fffff801`08200880     : fffff801`08260d4d ffffad0a`72a5aa58 ffffad0a`72a5aa58 ffffffff`ffffffff : nt!KiSystemServiceCopyEnd+0x28
ffffad0a`72a5a0e8 fffff801`08260d4d     : ffffad0a`72a5aa58 ffffad0a`72a5aa58 ffffffff`ffffffff 00007ff8`62bbf000 : nt!KiServiceLinkage
ffffad0a`72a5a0f0 fffff801`0820fe6c     : ffffb58c`8abd5980 fffff801`08070b16 00000000`00000800 ffffad0a`72a5ab00 : nt!KiDispatchException+0x17963d
ffffad0a`72a5a920 fffff801`0820b8bd     : 00000000`000513bc 000001d6`97e278e0 ffffad0a`72a5ab80 ffffb58c`8e3c6001 : nt!KiExceptionDispatch+0x12c
ffffad0a`72a5ab00 00007ff8`65582c62     : 00000000`00000000 0000003a`00000000 0000003a`69d01640 00007ff8`655f23df : nt!KiPageFault+0x43d
0000003a`69d01620 00000000`00000000     : 0000003a`00000000 0000003a`69d01640 00007ff8`655f23df 00007ff8`62bbf000 : 0x00007ff8`65582c62


SYMBOL_NAME:  nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  10e

FAILURE_BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_8e3c6080_nt!PspCatchCriticalBreak

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {27aefa90-6255-38b3-9cb2-d4c6815bddd7}

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


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

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

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2905

    Key  : Analysis.Elapsed.mSec
    Value: 7746

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xef

    Key  : CriticalProcessDied.ExceptionCode
    Value: 524e6080

    Key  : CriticalProcessDied.Process
    Value: services.exe

    Key  : Failure.Bucket
    Value: 0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_524e6080_nt!PspCatchCriticalBreak

    Key  : Failure.Hash
    Value: {8c867024-b7c2-66fb-8966-e5bb75be8a2b}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  ef

BUGCHECK_P1: ffffce0a4d62b280

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  053023-41578-01.dmp

PROCESS_NAME:  services.exe

CRITICAL_PROCESS:  services.exe

EXCEPTION_RECORD:  0000000000001000 -- (.exr 0x1000)
Cannot read Exception record @ 0000000000001000

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffff8608`2a42ed88 fffff800`5db0d842     : 00000000`000000ef ffffce0a`4d62b280 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8608`2a42ed90 fffff800`5da0cbb7     : 00000000`00000001 fffff800`5d513a19 00000000`00000002 fffff800`5d4eb06b : nt!PspCatchCriticalBreak+0x10e
ffff8608`2a42ee30 fffff800`5d899698     : ffffce0a`00000000 00000000`00000000 ffffce0a`4d62b280 ffffce0a`4d62b6b8 : nt!PspTerminateAllThreads+0x17291b
ffff8608`2a42eea0 fffff800`5d89926c     : ffffce0a`4d62b280 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!PspTerminateProcess+0xe0
ffff8608`2a42eee0 fffff800`5d60f4f8     : ffffce0a`4d62b280 ffffce0a`524e6080 ffff8608`2a42efd0 fffff800`5d92e042 : nt!NtTerminateProcess+0x9c
ffff8608`2a42ef50 fffff800`5d600880     : fffff800`5d660d4d ffff8608`2a42fa58 ffff8608`2a42fa58 ffffffff`ffffffff : nt!KiSystemServiceCopyEnd+0x28
ffff8608`2a42f0e8 fffff800`5d660d4d     : ffff8608`2a42fa58 ffff8608`2a42fa58 ffffffff`ffffffff 00007ff7`08111000 : nt!KiServiceLinkage
ffff8608`2a42f0f0 fffff800`5d60fe6c     : 00000000`00001000 ffff8608`2a42fb00 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x17963d
ffff8608`2a42f920 fffff800`5d60b8bd     : 00000000`00000001 00000000`00000000 ffffce0a`4a9dfc30 ffffce0a`00000000 : nt!KiExceptionDispatch+0x12c
ffff8608`2a42fb00 00007ffc`9862129e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x43d
00000009`41680ef0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`9862129e


SYMBOL_NAME:  nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  10e

FAILURE_BUCKET_ID:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_524e6080_nt!PspCatchCriticalBreak

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8c867024-b7c2-66fb-8966-e5bb75be8a2b}

Followup:     MachineOwner
---------
 
BIOS Güncellemesi yaptığımda sorunum düzeldi. En azından şu anda öyle gözüküyor Başka bir gelişme olursa Yeniden konu oluştururum teşekkürler
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…