Çözüldü Windows 8.1 0xc000021a Hatası

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

Blackankas

Hectopat
Katılım
8 Ocak 2020
Mesajlar
422
Çözümler
2
Yer
\Evren\Samanyolu Galaksisi\Dünya\Türkiye\
Daha fazla  
Cinsiyet
Erkek
Windows 8.1 Embedded Industry Pro kullanıyorum ve sorun şu ki bugün Steam i açınca Yazma korumalı diye bir hata verdi (0x13) ondan sonra UI buglanmaya başlayıp sistem 0xc000021a mavi ekran hatası verdi.

Sorunun GPU driverlarında olduğunu düşünüyorum ama tam emin değilim o yüzden minidump dosyalarımı paylaşmaya karar verdim.


Sistemi başlattıktan birkaç dakika sonra sürekli aynı mavi ekranı veriyor. Durum güvenli modda aynı

Sistem
  • i5-3210M
  • AMD Radeon HD 7670M
  • KIOXIA Exceria 240GB SSD
  • 8GB DDR3L 1600Mhz RAM
 
Çözüm
Sorun GPU sürücüsüyle alakalı olsa güvenli modda hata almazdınız, bu yüzden bunu direkt kafanızdan elemeliydiniz. :)

Sorunun çözümüne gelecek olursak, o da çok zor değil. Yapmanız gereken bir Windows 8.1 flashlanmış USB'yi sisteme takıp boot etmek ve gelişmiş seçenekler kısmından otomatik onarmayı başlatmak. Ardından sorununuz çözülmeli. Yine çözülmezse ya da çözülürse belirtmeyi unutmayınız. İyi akşamlar, kolay gelsin.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffffc000f1065520, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

ETW minidump data unavailable

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6046

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 27455

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

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

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

Key : WER.OS.Branch
Value: winblue_gdr

Key : WER.OS.Timestamp
Value: 2014-02-21T19:52:00Z

Key : WER.OS.Version
Value: 8.1.9600.17031


FILE_IN_CAB: 020822-6687-01.dmp

ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x

EXCEPTION_CODE_STR: c000021a

EXCEPTION_PARAMETER1: ffffc000f1065520

EXCEPTION_PARAMETER2: 0000000000000000

EXCEPTION_PARAMETER3: 0000000000000000

EXCEPTION_PARAMETER4: 0

BUGCHECK_CODE: c000021a

BUGCHECK_P1: ffffc000f1065520

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: services.exe

ADDITIONAL_DEBUG_TEXT: Güç hizmeti beklenmedik biçimde sonlandýrýldýðýndan, Windows þimdi yeniden baþlatýlmalýdýr

TAG_NOT_DEFINED_1004c:
This is a STATUS_SYSTEM_PROCESS_TERMINATED bugcheck.
It signals that the system is rebooting due to a critical service termination.
The bugcheck is not very useful for debugging. To investigate the root cause
find the related svchost.exe crashes that happened on the same machine
around the time of this dump.

IMAGE_NAME: ntkrnlmp.exe

MODULE_NAME: nt

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffd001`bf9d0658 fffff801`07ff4779 : 00000000`0000004c 00000000`c000021a ffffd000`207ff3f8 ffffe001`6835a160 : nt!KeBugCheckEx
ffffd001`bf9d0660 fffff801`07fec909 : ffffe001`662ea400 ffffd001`bf9d07a0 00000000`00000000 00000000`00000002 : nt!PopGracefulShutdown+0x2c9
ffffd001`bf9d06a0 fffff801`07dd67b3 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`662ea040 : nt! ?? ::OKHAJAOM::`string'+0xb69
ffffd001`bf9d0840 fffff801`07dcec00 : fffff801`082067d1 00000000`00000001 ffffd001`bf9d0a58 00000000`c0000004 : nt!KiSystemServiceCopyEnd+0x13
ffffd001`bf9d09d8 fffff801`082067d1 : 00000000`00000001 ffffd001`bf9d0a58 00000000`c0000004 ffffd001`beb78180 : nt!KiServiceLinkage
ffffd001`bf9d09e0 fffff801`0813c843 : 00000000`00000000 00000000`00000000 ffffd001`beb78180 ffffe001`662ea180 : nt! ?? ::NNGAKEGL::`string'+0x65101
ffffd001`bf9d0aa0 fffff801`07cbefee : fffff801`07cbef34 00000000`00000000 00000000`00000002 ffffe001`662ea040 : nt!PopPolicyWorkerAction+0x63
ffffd001`bf9d0b10 fffff801`07ccaadb : fffff800`00000002 ffffd001`bf9d0bd0 00000000`80000000 fffff801`07f504c0 : nt!PopPolicyWorkerThread+0xba
ffffd001`bf9d0b50 fffff801`07d46794 : fffff801`07fc4a00 ffffe001`662ea040 ffffe001`662ea040 ffffe001`648f3900 : nt!ExpWorkerThread+0x293
ffffd001`bf9d0c00 fffff801`07dd15c6 : fffff801`07f5d180 ffffe001`662ea040 fffff801`07fc4a00 ffffc000`e4e743e0 : nt!PspSystemThreadStartup+0x58
ffffd001`bf9d0c60 00000000`00000000 : ffffd001`bf9d1000 ffffd001`bf9cb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME: nt! ?? ::OKHAJAOM::`string'+b69

IMAGE_VERSION: 6.3.9600.17031

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: b69

FAILURE_BUCKET_ID: 0xc000021a_unknown_Critical_Service_Terminated_nt!_??_::OKHAJAOM::_string_

OS_VERSION: 8.1.9600.17031

BUILDLAB_STR: winblue_gdr

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

FAILURE_ID_HASH: {d39e45bf-ceb1-a708-52c5-8a807fdcbd24}

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


This is a STATUS_SYSTEM_PROCESS_TERMINATED bugcheck.
It signals that the system is rebooting due to a critical service termination.
The bugcheck is not very useful for debugging. To investigate the root cause
find the related svchost.exe crashes that happened on the same machine
around the time of this dump.
[/CODE]
Sorun GPU sürücüsüyle alakalı olsa güvenli modda hata almazdınız, bu yüzden bunu direkt kafanızdan elemeliydiniz. :)

Sorunun çözümüne gelecek olursak, o da çok zor değil. Yapmanız gereken bir Windows 8.1 flashlanmış USB'yi sisteme takıp boot etmek ve gelişmiş seçenekler kısmından otomatik onarmayı başlatmak. Ardından sorununuz çözülmeli. Yine çözülmezse ya da çözülürse belirtmeyi unutmayınız. İyi akşamlar, kolay gelsin.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffffc000f1065520, String that identifies the problem.
Arg2: 0000000000000000, Error Code.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

ETW minidump data unavailable

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6046

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 27455

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

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

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

Key : WER.OS.Branch
Value: winblue_gdr

Key : WER.OS.Timestamp
Value: 2014-02-21T19:52:00Z

Key : WER.OS.Version
Value: 8.1.9600.17031


FILE_IN_CAB: 020822-6687-01.dmp

ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x

EXCEPTION_CODE_STR: c000021a

EXCEPTION_PARAMETER1: ffffc000f1065520

EXCEPTION_PARAMETER2: 0000000000000000

EXCEPTION_PARAMETER3: 0000000000000000

EXCEPTION_PARAMETER4: 0

BUGCHECK_CODE: c000021a

BUGCHECK_P1: ffffc000f1065520

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: services.exe

ADDITIONAL_DEBUG_TEXT: Güç hizmeti beklenmedik biçimde sonlandýrýldýðýndan, Windows þimdi yeniden baþlatýlmalýdýr

TAG_NOT_DEFINED_1004c:
This is a STATUS_SYSTEM_PROCESS_TERMINATED bugcheck.
It signals that the system is rebooting due to a critical service termination.
The bugcheck is not very useful for debugging. To investigate the root cause
find the related svchost.exe crashes that happened on the same machine
around the time of this dump.

IMAGE_NAME: ntkrnlmp.exe

MODULE_NAME: nt

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffd001`bf9d0658 fffff801`07ff4779 : 00000000`0000004c 00000000`c000021a ffffd000`207ff3f8 ffffe001`6835a160 : nt!KeBugCheckEx
ffffd001`bf9d0660 fffff801`07fec909 : ffffe001`662ea400 ffffd001`bf9d07a0 00000000`00000000 00000000`00000002 : nt!PopGracefulShutdown+0x2c9
ffffd001`bf9d06a0 fffff801`07dd67b3 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`662ea040 : nt! ?? ::OKHAJAOM::`string'+0xb69
ffffd001`bf9d0840 fffff801`07dcec00 : fffff801`082067d1 00000000`00000001 ffffd001`bf9d0a58 00000000`c0000004 : nt!KiSystemServiceCopyEnd+0x13
ffffd001`bf9d09d8 fffff801`082067d1 : 00000000`00000001 ffffd001`bf9d0a58 00000000`c0000004 ffffd001`beb78180 : nt!KiServiceLinkage
ffffd001`bf9d09e0 fffff801`0813c843 : 00000000`00000000 00000000`00000000 ffffd001`beb78180 ffffe001`662ea180 : nt! ?? ::NNGAKEGL::`string'+0x65101
ffffd001`bf9d0aa0 fffff801`07cbefee : fffff801`07cbef34 00000000`00000000 00000000`00000002 ffffe001`662ea040 : nt!PopPolicyWorkerAction+0x63
ffffd001`bf9d0b10 fffff801`07ccaadb : fffff800`00000002 ffffd001`bf9d0bd0 00000000`80000000 fffff801`07f504c0 : nt!PopPolicyWorkerThread+0xba
ffffd001`bf9d0b50 fffff801`07d46794 : fffff801`07fc4a00 ffffe001`662ea040 ffffe001`662ea040 ffffe001`648f3900 : nt!ExpWorkerThread+0x293
ffffd001`bf9d0c00 fffff801`07dd15c6 : fffff801`07f5d180 ffffe001`662ea040 fffff801`07fc4a00 ffffc000`e4e743e0 : nt!PspSystemThreadStartup+0x58
ffffd001`bf9d0c60 00000000`00000000 : ffffd001`bf9d1000 ffffd001`bf9cb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME: nt! ?? ::OKHAJAOM::`string'+b69

IMAGE_VERSION: 6.3.9600.17031

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: b69

FAILURE_BUCKET_ID: 0xc000021a_unknown_Critical_Service_Terminated_nt!_??_::OKHAJAOM::_string_

OS_VERSION: 8.1.9600.17031

BUILDLAB_STR: winblue_gdr

OSPLATFORM_TYPE: x64

OSNAME: Windows 8.1

FAILURE_ID_HASH: {d39e45bf-ceb1-a708-52c5-8a807fdcbd24}

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


This is a STATUS_SYSTEM_PROCESS_TERMINATED bugcheck.
It signals that the system is rebooting due to a critical service termination.
The bugcheck is not very useful for debugging. To investigate the root cause
find the related svchost.exe crashes that happened on the same machine
around the time of this dump.
[/CODE]
 
Çözüm

Geri
Yukarı