For more information, see Open Event Viewer. The event properties for the bug check will list the four stop code parameters. There are multiple ways to gather the four stop code parameters.Įxamine the Windows system log in the Event Viewer. The parameters are described in Bug check code reference for each stop code. Gather the stop code parametersĮach bug check code has four associated parameters that provide information. There's a stop code hex value associated with each stop code as listed in Bug check code reference. If a kernel-mode dump file has been written, it's indicated with a percentage complete count down as the dump is being written. When it's available, the module name of the code that was being executed is also displayed, such as AcmeVideo.sys. The stop code is displayed, such as PAGE_FAULT_IN_NONPAGED_AREA. The following example shows a possible blue screen: The exact appearance of the blue screen depends on the cause of the error. If you're using an insider build of Windows, the text is displayed on a green background. This screen is called a blue screen, a bug check screen, or a stop screen. If no debugger is attached, a blue text screen appears with information about the error. If a kernel debugger is attached and active, the system causes a break so that the debugger can be used to investigate the crash. If crash dumps are enabled on the system, a crash dump file is created. If the OS is allowed to continue to run after the operating system integrity is compromised, it could corrupt data or compromise the security of the system. It's also referred to as a system crash, a kernel error, or a stop error.Įxamples of situations that could occur are: When Microsoft Windows encounters a condition that compromises safe system operation, the system halts. If you're an IT professional or support agent, see Advanced troubleshooting for stop or blue screen errors for more information.
0 Comments
Leave a Reply. |