How to read blue screen
How to read blue screen
![]()
The dreaded blue screen is the mask that gets Windows to tell us that something is wrong. Seemingly incomprehensible, these messages contain information useful for solving hardware and software conflicts that plague the system.
In this article we explain how to read a blue screen with the help of special tools. Having identified the problem, you can put to work to resolve it. So the next time you see a blue screen, and you will not feel as helpless as before.
Anatomy of a blue screen
Read the blue screen is only possible if the system automatically restarts after a failure, to prevent this, you need to disable the automatic restart . Go to Control Panel > System > Advanced and click the button configuration of paragraph Startup and Recovery . Uncheck the "Automatically restart" and accepted.
Propiedades avanzadas del sistema
The blue screen (hereafter, PA) always have the same structure is reported the occurrence of a problem, the file concerned, the error message or stop and, after some generic recommendations, it shows some technical information difficult to decipher. In the picture we have outlined the position of each element:
Anatomía de un pantallazo azul
The really interesting data are the first two: the file and the error. In most cases this is hardware drivers or conflicts between programs. The codes that follow the word STOP is also useful. Here are some of the most common:
DRIVER_IRQ_NOT_LESS_THAN_OR_EQUAL_TO : a classic. It refers to a conflict caused by hardware devices such as graphics or sound cards. A faulty driver or a device failure are two of the most common causes. The quickest solution is to boot in safe mode and change the driver.
UNMOUNTABLE_BOOT_DEVICE: indicates an error in the file system hard drive or by corrupted system files, either by a physical error. Can be solved by running chkdsk and fixmbr utilities included in all versions of Windows.
PAGE_FAULT_IN_NON_PAGE_AREA: when Windows can not find the information sought in memory, this error appears inexorably. Incompatibilities between programs (eg antivirus) and bad memory modules can also cause this stop.
CRITICAL_OBJECT_TERMINATION: some important processes have terminated unexpectedly or have been closed. It’s the closest thing to take two legs to a table. It is best to restart in safe mode and investigate what service has failed or if there is malware acting freely.
Check out this exhaustive list of STOP codes to find yours. In most cases, a combined search of both strings can put you on the trail of what happened. For example, a file error with nv4_disp.dll DRIVER_IRQL-owned Nvidia drivers, indicates a failure of the graphics card or its driver.
Utilities for interpreting the blue screen
There are a couple of forensic tools that are helpful to find out what is behind the PA: BlueScreenView and WhoCrashed . Both analyze the C: \ Windows \ minidump in search of memory dumps, traces left by serious errors. For BlueScreenView, even recreates the appearance of the original screenshot:
BlueScreenView
Besides pointing out the date and time of the error, BlueScreenView summarizes all the important values in a table export, memory addresses, modules and drivers involved, as well as data on the same (version, description, etc.). WhoCrashed does the same, but also offers an interpretation of what happened:
WhoCrashed
A click on Analyze and WhoCrashed process all dumps of memory. The report generated much more legible, contain all crashes in chronological order and a final interpretation (not always successfully). Certainly better than reading a screen shot just appeared.
What to do to solve a blue screen
Ready to save the world? Sign in safe mode (or safe) by pressing F8 during boot. If you use XP, the tool BootSafe save you this step. In Safe Mode, the vast majority of programs and services are disabled, including possible cause of the PA.
Modo Seguro If you could not boot into safe mode, choose Last Known Good Configuration
The phrase "if it works, do not touch" aptly describes the search for the perpetrators of the system error. Your Memory: installed a conflicting program? Do we update a driver? Slinks Maybe a virus? Any recent changes may be the prime suspect. Here is a set of desirable actions:
* System Restore is the solution to the conflicts caused by newly installed software and drivers
* Scan hard disk for errors is also a good idea. Use the command chkdsk and fixmbr
* Should check the integrity of system files. Run the command SFC / scannow
* Use a bootable CD antivirus to clean any infections (eg, G-Data Boot CD )
* Defective RAM modules are an endless source of bugs. Look for them with Memtest86 +
These five steps should help to solve most problems. In some cases, verify the correct connection of the components (eg hard drives) or the temperature of the system is also useful. More specific issues related to the BIOS if you change the factory defaults, return them to their original state.
Have you ever encountered a blue screen? Tell us your story!
Other Electronics News:
- lenovo thinkpad t60 battery
- lenovo thinkpad x200 battery
- acer laptop batteries
- sony battery
- laptop batteries






