Win8 Can't Boot or Repair

sent, not sure how well it will work but fingers crossed, really want fixed so I don't have to reinstall every game on steam and completely redownload everything on origin
 
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\DUMP\DUMP19a8.tmp]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
Machine Name:
Kernel base = 0xfffff803`9441f000 PsLoadedModuleList = 0xfffff803`946ebb00
Debug session time: Thu May 30 18:58:08.598 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:07.312
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
..
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {fffff8a003a54450, ffffffffc000012f, fffff8a000340b50, 0}

Probably caused by : ntkrnlmp.exe ( nt!NtSetSystemPowerState+878 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff8a003a54450, String that identifies the problem.
Arg2: ffffffffc000012f, Error Code.
Arg3: fffff8a000340b50
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: fffff8a003a54450

EXCEPTION_PARAMETER2: ffffffffc000012f

EXCEPTION_PARAMETER3: fffff8a000340b50

EXCEPTION_PARAMETER4: 0

ADDITIONAL_DEBUG_TEXT: Verification of a KnownDLL failed.

BUGCHECK_STR: 0xc000021a_c000012f

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: smss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8039479032a to fffff80394479240

STACK_TEXT:
fffff880`02b40828 fffff803`9479032a : 00000000`0000004c 00000000`c000021a fffff880`03195540 fffffa80`07bc7420 : nt!KeBugCheckEx
fffff880`02b40830 fffff803`947819e8 : 00000000`00000001 00000000`00000002 ffffffff`80000318 00000000`00000002 : nt!PopGracefulShutdown+0x29a
fffff880`02b40870 fffff803`94478253 : fffffa80`06a15940 00000000`00000000 00000000`c0000004 fffff880`02b40b01 : nt!NtSetSystemPowerState+0x878
fffff880`02b409b0 fffff803`9447d430 : fffff803`94a2132f 00000000`00000001 00000000`00000000 00000000`00000002 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02b40b48 fffff803`94a2132f : 00000000`00000001 00000000`00000000 00000000`00000002 fffff8a0`0464ddb0 : nt!KiServiceLinkage
fffff880`02b40b50 fffff803`948f4bc7 : 00000000`00000087 fffff803`9447d430 00000000`00000000 fffffa80`078ff460 : nt! ?? ::NNGAKEGL::`string'+0x43529
fffff880`02b40c10 fffff803`9444e630 : fffffa80`06a15940 00000000`00000000 00000000`00000002 fffff803`94482aac : nt!PopPolicyWorkerAction+0x63
fffff880`02b40c80 fffff803`944b70d1 : fffff803`00000002 fffff803`9444e570 fffff803`946b8640 fffff803`94694300 : nt!PopPolicyWorkerThread+0xc0
fffff880`02b40cc0 fffff803`9444be45 : 00000000`00000000 00000000`00000080 fffff803`944b6f90 fffffa80`06a15940 : nt!ExpWorkerThread+0x142
fffff880`02b40d50 fffff803`94500676 : fffff803`94717180 fffffa80`06a15940 fffff803`94771880 fffffa80`069ca7c0 : nt!PspSystemThreadStartup+0x59
fffff880`02b40da0 00000000`00000000 : fffff880`02b41000 fffff880`02b3b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!NtSetSystemPowerState+878
fffff803`947819e8 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: 513814ba

BUCKET_ID_FUNC_OFFSET: 878

FAILURE_BUCKET_ID: 0xc000021a_c000012f_nt!NtSetSystemPowerState

BUCKET_ID: 0xc000021a_c000012f_nt!NtSetSystemPowerState

Followup: MachineOwner
---------
Click to expand...

that's the last, here's the first

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\DUMP\DUMP1998.tmp]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
Machine Name:
Kernel base = 0xfffff803`90015000 PsLoadedModuleList = 0xfffff803`902e1b00
Debug session time: Mon May 13 21:27:02.333 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:07.046
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
..
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C000021A, {fffff8a000803cc0, ffffffffc000012f, fffff8a0001e27f0, 0}

Probably caused by : ntkrnlmp.exe ( nt!NtSetSystemPowerState+878 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff8a000803cc0, String that identifies the problem.
Arg2: ffffffffc000012f, Error Code.
Arg3: fffff8a0001e27f0
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: fffff8a000803cc0

EXCEPTION_PARAMETER2: ffffffffc000012f

EXCEPTION_PARAMETER3: fffff8a0001e27f0

EXCEPTION_PARAMETER4: 0

ADDITIONAL_DEBUG_TEXT: Verification of a KnownDLL failed.

BUGCHECK_STR: 0xc000021a_c000012f

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: smss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8039038632a to fffff8039006f240

STACK_TEXT:
fffff880`02b47828 fffff803`9038632a : 00000000`0000004c 00000000`c000021a fffff880`031d4540 fffffa80`07c83dc0 : nt!KeBugCheckEx
fffff880`02b47830 fffff803`903779e8 : 00000000`00000001 00000000`00000002 ffffffff`800003b4 00000000`00000002 : nt!PopGracefulShutdown+0x29a
fffff880`02b47870 fffff803`9006e253 : fffffa80`06a03040 00000000`00000000 00000000`c0000004 fffff880`02b47b01 : nt!NtSetSystemPowerState+0x878
fffff880`02b479b0 fffff803`90073430 : fffff803`9061732f 00000000`00000001 00000000`00000000 fffffa80`00000001 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02b47b48 fffff803`9061732f : 00000000`00000001 00000000`00000000 fffffa80`00000001 000004b0`00000001 : nt!KiServiceLinkage
fffff880`02b47b50 fffff803`904eabc7 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00f5457e : nt! ?? ::NNGAKEGL::`string'+0x43529
fffff880`02b47c10 fffff803`90044630 : fffffa80`06a03040 00000000`00000000 00000000`00000002 fffff803`90078aac : nt!PopPolicyWorkerAction+0x63
fffff880`02b47c80 fffff803`900ad0d1 : fffff803`00000002 fffff803`90044570 fffff803`902ae640 fffff803`9028a300 : nt!PopPolicyWorkerThread+0xc0
fffff880`02b47cc0 fffff803`90041e45 : 00000000`00000000 00000000`00000080 fffff803`900acf90 fffffa80`06a03040 : nt!ExpWorkerThread+0x142
fffff880`02b47d50 fffff803`900f6676 : fffff880`009b8180 fffffa80`06a03040 fffff880`009c3e40 fffffa80`069ca7c0 : nt!PspSystemThreadStartup+0x59
fffff880`02b47da0 00000000`00000000 : fffff880`02b48000 fffff880`02b42000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!NtSetSystemPowerState+878
fffff803`903779e8 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: 513814ba

BUCKET_ID_FUNC_OFFSET: 878

FAILURE_BUCKET_ID: 0xc000021a_c000012f_nt!NtSetSystemPowerState

BUCKET_ID: 0xc000021a_c000012f_nt!NtSetSystemPowerState

Followup: MachineOwner
---------
Click to expand...

skimming them, they look identical

can post more of them if needed
 
Last edited:
my basic ubderstanding from another guide says ntkrnlmp.exe is the issue and possibly has screwed my registry up a little
 
Were you doing any registry tweaking before the problems started? Or did you use a registry cleaner at all?
 
spirit said:
Were you doing any registry tweaking before the problems started? Or did you use a registry cleaner at all?
Click to expand...

Nope and no. There's 10 other dump files i just dont feel like checking when 2 were the same, think i checked a third too and it was the same again
 
Can you do a system restore back to a day before the issue came up? Did you by chance update any drivers that day?
 
Restore doesn't work, tried numerous times. None personally, i think the nvidia updater thing came up with an update but it's not supposed to even download it for me to install.
 
At the beginning of the debug is says "verification of known dll failed" So I'm assuming some driver didn't install properly. Not sure if you have the ability to rollback any drivers, but thats where I would start. Also can you check to see if any windows updates were installed on that day? You should be able to view by install date.
 
Click on windows update and on the left should be like windows 7 and it should say view update history?
 
Nope, only thing i can do on the computer really is wait for it to try to repair itself then go into advanced troubleshooting to get to the command prompt which gives me access to files through notepad and i can use regedit. Other than that it's plugging it into the emachine to edit or open files
 
Ok, well now the problem is that i cant find my windows key. Deleted the email and when i called a ew weeks ago they said it didnt show on any of my emails

I had the preview then upgraded to a full copy when it came out for 40 instead of 100 for an oem copy. All it did was give me a key and download some files. Might have been a cause of this

Edit: found out how to get it from the registry, but cani use that with my friend's oem install disk or what? And could i copy my registry or certain files and put them in with the new install and not get this issue?
 
Last edited:
Nevermind, cant seem to get windows key from registry and not sure how i can reinstall.

Would a boot log help? Enabled it but looking at it, it doesn't have any order to identify what is crashing
 
Wait, found my update log files! And it was updating the day it crashed and the end log is listed at 21:24 which i think is about when it crashed (thought was around 7:30 but 9:30 could be right and most likely is). Do you need me to send you this? Although looking through it now i see no errors
 
You must log in or register to reply here.
Back
Top