[Autogenerated] The infamous blue screen.
Is probably one of the most recognizable aspects of Windows
This is also called as a system _____, the screen turns blue.
However, in some cases might be green.
In fact, if using one of the insider preview bills.
That Microsoft provides for insiders, and anyone,
can be insider, then If that machine crashes,
the screen has the green call to Give you a quick note,
that this is In fact, a preview build rather than an official build.
And then there, are several names, that the blue screen,
is referred, to in Microsoft documentation,
and tools.
Such as bug, check stop, error system failure.
These all mean the same thing.
Why does the blue screen occur?
This occurs when an exception.
Is happening in kernel mode and is unhanded or perhaps the kernel or
some driver decides that Some inconsistency exists.
And its better off crashing the system.
The blue screen might seem like a sort of punishment.
But in fact, we can think of that as a protection mechanism.
Because if you allow the system, to continue running.
You might cause ec recoverable damage, to the system,
in the sense, that You might call some critical data to be deleted,
and Windows might not even boot again.
This could be something.
That is simply irrevocable.
So everything stops because kernel code is supposed,
to be trusted So it shouldn't really cause any unhanded exceptions.
To occur.
However, this does happen.
So what should we do Next, we have a blue screen on our hands.
What's our options?
So obviously we have to Restart the system.
That's the only thing.
To get back.
To normally functioning.
Windows But since we are in the Windows internals course,
we want to dig, a little bit deeper.
If there's a current debugger attached, to the system,
the debugger will be broken into and We see where that blue screen,
is happening or at least very close to that This allows us to examine the
state of the system just before the system crashes.
We can't really prevent the system from crashing,
but at least we have the most amount of detail as to
What is going on when the system, is about to _____.
If we don't have a co debugger attached,
then our best option, is to write, a crush,
dump,
file which essentially is writing the state of memory into a file which you can.
Let later open with the win debug debugger and examine.
So at that point, once we have a DOM file assuming that we do manage,
to get one and We'll see.
In the Next couple of videos, what we need.
To do in order to get that we can Restart the system,
and then analyze the damp file with the debugger to try to
get a Sense of why this system crashed.
Let's start by looking at how to configure information
related to that dump or to crashing in general.