Error message 0xc000021a - every day after a boot of notebook W8

Question

Hi,
I have the following issue. I have a Windows 8 notebook from MSI. Since the last couple of days, I'm facing an issue when I try to boot the notenbook. It returns with a 0c000021A error. When I open SrtTrail.txt, I see the following message:
Test Performed:
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
Test Performed:
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
Test Performed:
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 172 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
Test Performed:
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 641 ms
Test Performed:
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 281 ms
Test Performed:
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
Test Performed:
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
Test Performed:
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms
Test Performed:
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms
Test Performed:
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
Test Performed:
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 188 ms
Test Performed:
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 1828 ms
Test Performed:
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms
Test Performed:
Name: Bugcheck analysis
Result: Completed successfully. Error code =  0x0
Time taken = 516 ms
Root cause found:
Bugcheck c000021a. Parameters = 0xfffff8a003f9b850, 0xffffffffc0000428, 0xfffff8a0003bb610, 0x0.
Boot critical file  is corrupt.
I have been looking for a long time to find a proper solution, but from what I found on the internet, there are so many different approaches and I don't know whether the provided solutions have worked or not. I did a disk clean up, I have no other log files
present. If you need more details for further analysis, please let me know. Currently, I'm using the DISM utility to get the notebook booted, but I prefer a proper start up from my notebook.
Any help is really appreciated.

Answer 1

* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck C000021A, {fffff8a003e1cda0, ffffffffc0000428, fffff8a00017dbb0, 0}
----- ETW minidump data unavailable-----
Probably caused by : ntkrnlmp.exe ( nt!NtSetSystemPowerState+878 )
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff8a003e1cda0, String that identifies the problem.
Arg2: ffffffffc0000428, Error Code.
Arg3: fffff8a00017dbb0
Arg4: 0000000000000000
Debugging Details:
ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
EXCEPTION_PARAMETER1: fffff8a003e1cda0
EXCEPTION_PARAMETER2: ffffffffc0000428
EXCEPTION_PARAMETER3: fffff8a00017dbb0
EXCEPTION_PARAMETER4: 0
ADDITIONAL_DEBUG_TEXT: Verification of a KnownDLL failed.
BUGCHECK_STR: 0xc000021a_c0000428_user32.dll_HASH_INVALID
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: smss.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff8030a39048e to fffff8030a079540
STACK_TEXT:
fffff880`039436e8 fffff803`0a39048e : 00000000`0000004c 00000000`c000021a fffff880`0120d400 fffffa80`0dd1d130 : nt!KeBugCheckEx
fffff880`039436f0 fffff803`0a381aec : 00000000`00000001 00000000`00000002 ffffffff`80000110 00000000`00000002 : nt!PopGracefulShutdown+0x29a
fffff880`03943730 fffff803`0a078553 : fffffa80`06bf5900 00000000`00000000 00000000`c0000004 fffff880`03943901 : nt!NtSetSystemPowerState+0x878
fffff880`03943870 fffff803`0a07d730 : fffff803`0a626fcf 00000000`00000001 00000000`00000000 fffffa80`00000004 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03943a08 fffff803`0a626fcf : 00000000`00000001 00000000`00000000 fffffa80`00000004 fffffa80`0bf07ce0 : nt!KiServiceLinkage
fffff880`03943a10 fffff803`0a4fb833 : fffff8a0`00027010 fffff803`0a45f2bc 00000000`00000000 fffff8a0`000604a8 : nt! ?? ::NNGAKEGL::`string'+0x41aa9
fffff880`03943ad0 fffff803`0a04e860 : fffffa80`06bf5900 00000000`00000000 00000000`00000002 fffff803`0a082dbc : nt!PopPolicyWorkerAction+0x63
fffff880`03943b40 fffff803`0a0b7411 : fffff803`00000002 fffff803`0a04e7a0 fffff803`0a2b8620 fffff803`0a082d00 : nt!PopPolicyWorkerThread+0xc0
fffff880`03943b80 fffff803`0a04c075 : 00000000`10000000 00000000`00000080 fffff803`0a0b72d0 fffffa80`06bf5900 : nt!ExpWorkerThread+0x142
fffff880`03943c10 fffff803`0a1003b6 : fffff803`0a317180 fffffa80`06bf5900 fffff803`0a371880 fffffa80`06996040 : nt!PspSystemThreadStartup+0x59
fffff880`03943c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtSetSystemPowerState+878
fffff803`0a381aec cc int 3
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!NtSetSystemPowerState+878
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 536464f4
IMAGE_VERSION: 6.2.9200.16912
BUCKET_ID_FUNC_OFFSET: 878
FAILURE_BUCKET_ID: 0xc000021a_c0000428_user32.dll_HASH_INVALID_nt!NtSetSystemPowerState
BUCKET_ID: 0xc000021a_c0000428_user32.dll_HASH_INVALID_nt!NtSetSystemPowerState
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc000021a_c0000428_user32.dll_hash_invalid_nt!ntsetsystempowerstate
FAILURE_ID_HASH: {4c1cb833-8749-f823-0b1e-7f7a668864ad}
Followup: MachineOwner
adn this shows 6: kd> db fffff8a003e1cda0
fffff8a0`03e1cda0 56 65 72 69 66 69 63 61-74 69 6f 6e 20 6f 66 20 Verification of
fffff8a0`03e1cdb0 61 20 4b 6e 6f 77 6e 44-4c 4c 20 66 61 69 6c 65 a KnownDLL faile
fffff8a0`03e1cdc0 64 2e 00 00 20 02 00 00-01 01 00 00 00 00 00 05 d... ...........
fffff8a0`03e1cdd0 04 01 04 03 4e 74 46 73-02 00 00 00 00 00 14 00 ....NtFs........
fffff8a0`03e1cde0 20 ea d1 03 a0 f8 ff ff-00 00 00 00 00 00 00 00 ...............
fffff8a0`03e1cdf0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
fffff8a0`03e1ce00 38 ce 00 00 00 00 02 00-20 9b e3 03 a0 f8 ff ff 8....... .......
fffff8a0`03e1ce10 04 01 0c 03 46 49 63 73-30 00 43 00 30 00 34 00 ....FIcs0.C.0.4.
6: kd> da fffff8a00017dbb0
fffff8a0`0017dbb0 "user32.dll"
Hi, the dump analysis indicates that this issue is probably caused by ntkrnlmp.exe a NT Kernel & System file, and deep analysis shows that the error is related with user32.dll file, invalid hash, this file must be corrupted, or might be placed with
other files due to some 3 rd part software installation, or even virus infection, I suggest you refer to this link to fix the dll file, replace the file with a right copy (this is an old link, but some solutions are also useful in Windows 8.1)
http://support.microsoft.com/kb/142676
Yolanda Zhu
TechNet Community Support