Support Forums

Full Version: Windows 8 BSOD - Forced
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
I forced a Windows 8 BSOD today, and this is what came up. In my opinion it looks a little silly, but I guess for the average computer user seeing a keyboard frowning face is supposed to lighten your mood after seeing this BSOD? haha even all of the stop error codes were removed... What a bad idea. If you can't access your computer, then you'll never be able to get to your crash dump if you have them enabled, and without any hint of the error, other than a little tiny description. That only just makes things harder to troubleshoot in my opinion.

[Image: bsod.png]
I just realized that a crash dump should have been made at the time of the fault. So I found it lol Smile

It's pointing towards the NT boot initialization as it's reference in the stack trace to the NT symbol. Highly unlikely for a cause, it's only blaming that because the boot initialization was forwarded bad data from a bad config in the registry, which gets checked ON boot.

lol, it works, relatively the exact same format too, nothing changed, that's good. Here's the output it gave me:

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 74, {2, fffff880022dcb30, 2, ffffffffc000014c}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+26af )

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

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff880022dcb30, (reserved)
Arg3: 0000000000000002, (reserved)
Arg4: ffffffffc000014c, usually the NT status code.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x74

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800014328a5 to fffff80000f3d9c0

STACK_TEXT:  
fffff880`022dca78 fffff800`014328a5 : 00000000`00000074 00000000`00000002 fffff880`022dcb30 00000000`00000002 : nt!KeBugCheckEx
fffff880`022dca80 fffff800`0127dfa8 : fffff880`022dcdd0 fffffa80`0495f3c0 00000000`00000002 fffffa80`04a7e5c0 : nt! ?? ::NNGAKEGL::`string'+0x26af
fffff880`022dcd50 fffff800`00f0bce6 : fffff800`01177180 fffffa80`0495f3c0 fffffa80`04a7e5c0 fffffa80`036622c0 : nt!PspSystemThreadStartup+0x58
fffff880`022dcda0 00000000`00000000 : fffff880`022dd000 fffff880`022d7000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+26af
fffff800`014328a5 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+26af

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e5dc748

FAILURE_BUCKET_ID:  X64_0x74_nt!_??_::NNGAKEGL::_string_+26af

BUCKET_ID:  X64_0x74_nt!_??_::NNGAKEGL::_string_+26af

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

BAD_SYSTEM_CONFIG_INFO (0x74)

I did some careless registry editing on purpose to get this to come up, probably put a lot of invalidity on one of the system hives lol. Windows 8 is working again, I just wanted to test this out...
Did you download a corrupt version? That may be the problem. Or your computer cannot support it which I doubt.


(09-20-2011, 08:31 AM)Grin Wrote: [ -> ]Did you download a corrupt version? That may be the problem. Or your computer cannot support it which I doubt.

No, try reading my thread. I Forced the BSOD to see what it would look like...
It looks a bit silly indeed. I like the old BSOD, where you actually can see what the problem is...

I don't like anything with w8 that I've seen so far...
So do I, imho it sucks on Windows8.
(09-20-2011, 04:00 PM)яeborn Wrote: [ -> ]It looks a bit silly indeed. I like the old BSOD, where you actually can see what the problem is...

I don't like anything with w8 that I've seen so far...

True, it was designed mainly for visuals, and touchscreen from what I can see. Not necessarily for ease of use on the average desktop user. I really dislike the metro UI they've put in place, so with a registry edit i've gotten rid of it and back to the start menu and Windows 7 visuals we go!

So basically if you don't like that tile-layout, no point in upgrading to Windows 8. Because if you get rid of that, it's pretty much just like Windows 7 again. The fancy taskmanager goes away when you disable the metro too.
(09-20-2011, 04:50 PM)Ace Wrote: [ -> ]True, it was designed mainly for visuals, and touchscreen from what I can see. Not necessarily for ease of use on the average desktop user. I really dislike the metro UI they've put in place, so with a registry edit i've gotten rid of it and back to the start menu and Windows 7 visuals we go!

So basically if you don't like that tile-layout, no point in upgrading to Windows 8. Because if you get rid of that, it's pretty much just like Windows 7 again. The fancy taskmanager goes away when you disable the metro too.

Lol, so it's basicly that Microsoft are in need of money, and selling a stupid OS?

I'll stay with Windows 7, like I said before, windows 8 looks terrible. And I wont buy a touchscreen or w/e to use it, lol. I like my 120hz screen :3
(09-22-2011, 05:40 AM)яeborn Wrote: [ -> ]Lol, so it's basicly that Microsoft are in need of money, and selling a stupid OS?

I'll stay with Windows 7, like I said before, windows 8 looks terrible. And I wont buy a touchscreen or w/e to use it, lol. I like my 120hz screen :3

Microsoft in need of money? lol are you kidding? They are greedy, but they don't need the money. Their employees sleep on a pile of money almost.
When did windows 8 get release? crap i didn't even know.
Pages: 1 2