What if the blue screen of Windows death. Damaged RAM

Blue screen death sign to everyone windows user 7, because it is a built-in functionality. If you saw a blue screen, it is important to remember the error code, and after the system is restored, solve all problems. In this article we will talk in more detail what to do in the event of a blue screen of death.

What is the blue screen of death in Windows 7

Blue Death Screen is a BSOD, or Blue Screen of Death, a system function that displays an error code. In practice, it looks like this - at any time the system can switch from the actual interface to the blue screen. Thanks to this, the user can learn the cause of the system failure. The reason is encrypted as a code, in addition, additional system information is displayed on the screen.

Causes of the blue screen of death

The reasons for the occurrence of the blue screen of death are many, but they all are reduced to one - something is wrong with your computer. This may be not only a systemic (software) error, but also problems with iron. 6 main reasons can be distinguished:

• Flew the driver;
• Ended free space on system disk;
• Registry problems;
• System files are damaged;
• Virus;
• Problems with "iron";

The remaining reasons why the blue screen of death on Windows 7 falls into one of these categories.

What to do

If you saw a blue screen of death, then the first thing to write down the error code. Alternatively, make a screen photo using the phone. Standard "Printscreen" in the case of the blue screen of death will not work. In addition to the error code, the screen, as a rule, contains recommendations that the user can do to eliminate the problem. You do not need to hurry to take actions, you need to give a little time to try to find solutions on your own. If the blue screen of death does not disappear and the system does not automatically reboot, then it is necessary to take action.

If the OS could not eliminate the problem on their own, then it is necessary to help her. Consider all typical cases.

1. If the problem is with the drivers, then you need to boot into safe mode and reinstall required drivers. If the blue screen of death did not suggest a problem driver, then reinstall completely all drivers. They can be taken on the system disk that walked along with the computer or you can use the program.
2. Free space on a C (or any other system disk), it is vital for the correct operation of the OS. If the place ends completely, the blue screen of death appears. Solutions two - download the OS and until I left the track on the disk and did not score all the memory, delete some big files. By this you will free the place. If the place is over and the options to free it is not, it will help only the replacement of HDD.
3. Registry problems are perfectly solved by rollback OS to the previous recovery point. Or use specialized software, for example, to check and clean the registry.
4. Problems with system files, i.e. The files of the OS itself is one of the most frequent causes of the blue screen of death. The elimination of such problems is usually not difficult for the OS itself in automatic mode. If the system was not able to eliminate the problems itself, then the solution is one thing - download the OS in safe mode and restore at the last recovery point. If it did not help and the system is not loaded, it will help to reinstall the OS.
5. Viruses - themselves are not the cause of the blue screen, but their activities can disturb the integrity of the OS and interfere with the system. In this case, you need to boot without supporting network connections and check the computer or laptop for viruses. Check the best special antivirus solutions other than the built-in. For example, you can use Kaspersky Anti-Virus.
6. Problems with iron include all components of your device. Problems can be as global - burned chip, broke mother card Etc., so small - the power loop departed. You will not be able to eliminate such problems in automatic mode. However, in the event of problems with iron, the blue screen of death always suggests what cause. Elimination of such a problem is better to entrust professionals.

As you understand, the blue screen of death is your friend and a good assistant. The main purpose of the appearance of such an error is to protect your device. Moreover, the blue screen itself suggests solving the problem. For those who want to get even deeper into this question, we recommend to see a small video about the causes of the blue screen of death, and the ways to troubleshoot problems:

To get error information Enter its code into a text box just below in the following format: 7E or 0x0000007E

Go to description

UNEXPECTED_KERNEL_MODE_TRAP

This error means that an unexpected exception occurred in the kernel mode, or interrupt, at which the kernel does not work.

Also, the cause of the error can be an interrupt, which entailed immediate death in the form of a double error - double fault. The first number in the error code is the number of interrupts (8 \u003d Double Fault). To learn more, what is the interrupt, refer to the Intel X86 Manual.

In short, the error appears when the processor allows an error with which the kernel cannot cope. Most often, the error occurs due to bad RAM blocks, and sometimes due to the acceleration of the processor.

Try to cancel the synchronous data transmission feature in the BIOS.

Troubleshooting: If new hardware installed in the computer, you must disconnect them. If existing hardware has led to a failure, you need to remove or replace the package components of the computer if necessary.

Schedule RAM for errors.

Make sure all computer components are set properly. Clean adapter contacts.

Update BIOS.

All hard drives, controllers hard disks and SCSI adapters must be compatible with installed version Windows.

If the driver is identified in the error message, disconnect or update this driver. Disable or delete any drivers or services that have been recently added. If the error occurs during windows downloads, and the system partition is formatted with the NTFS file system, use the secure mode to reinstall or delete a defective driver. If the driver is used as a system startup process in safe mode, start the computer using the Recovery Console to access the file.

Restart the computer and press F8 in the text mode menu, to display the download options operating system. In this menu, select "Load the latest successful configuration". This option is the most efficient, when adding only one driver or service to the system at a time.

Acceleration central processor may cause an error. Return the value clock frequency The default CPU.

Make sure the system enters the Event Viewer system. The error information there will help identify the device or driver that causes the Death screen 0x0000007F.

Disable BIOS memory caching.

If the error is unexpected_kernel_mode_trap appeared when updating to the new version of the Windows operating system, it can be caused by the device driver, system service, antivirus program or backup program that are incompatible with new version. Delete all third-party device drivers and system services, disconnect antivirus programs.

Set the latest Windows Update Package.

If the previous steps did not help solve the problem, take motherboard In the repair shop for diagnosis. Cracks, scratches or defective components on system board Can cause this error.

Spin_lock_init_failure

This check error appears very rarely.

DFS_FILE_SYSTEM.

Distributed errors file System (Distributed File System).

Update the OS.

Setup_failure

A fatal error occurred during installation.

The SETUPDA text form no longer uses bug check (BugCheck) to exit serious errors. Therefore, you will never encounter 0x85. All bug checks were replaced with more friendly and (where possible) more informative error messages. However, some error compilers were simply replaced by our BugCheck screens, and the code for these states of errors is the same as it was. They are shown below.)

0: OEM HAL Font is an invalid file format * .fon, so the installation could not display the text. This means that VGAXXX.FON on CD or floppy is damaged.

1: Unable to initialize the video. This error has its own screen and only 2 options are provided to the user.

This means that the VGA.SYS file (or another driver, depending on the machine) is damaged, or the fact that this equipment is not supported.

Cause of the error:

0: NtCreateFile of DeviceVideo0

3: The desired video mode is not supported. This means an internal installation error.

2: Lack of memory. Now this error uses a more friendly screen, depending on how the installation has entered.

3: The keyboard was not initialized. Now 2 different screens are used depending on the errors that could appear here. This may mean that the drive containing the keyboard drivers (I8042PRT.SYS or KBDCLASS.SYS) is damaged or the machine has a keyboard that is not supported.

It may also mean that the DLL keyboard layout cannot be loaded.

Cause of the error:

0: Ntcreatefile of DeviceKeyboardClass0.

Installation did not detect the keyboard connected to your computer.

1: Unable to Load Keyboard Layout DLL.

Installation cannot load the DLL keyboard layout.

This means that on floppy or CD there is no file (kbdus.dll for US or other DLL).

4: Installation could not find out the device path from which the installation began. This is an internal installation error.

5: Did not check the performance of the partitions. This means the bug in the disk driver. Parameters are valid only for installation group.

MBR_CHECKSUM_MISMATCH

This error occurs during the boot of the operating system when check sum MBR, which calculates the operating system Microsoft Windows., does not correspond to the checksum of the system loader.

This BSOD indicates the presence of viruses.

It is necessary to scan the operating system for viruses with current antivirus programs.

Page_fault_in_non_paged_area.

This bsod is overall error. To interpret it, it is necessary to identify which exception was generated.

There are the following exception codes:

0x80000002: STATUS_DATATYPE_MISALIGNMENT Indicates a non-aligned data link;

0x80000003: Status_BreakPoint. Indicates a situation where the system is faced with a control point or ASSERT without an attached kernel debugger;

0xc0000005: Status_Access_Violation Indicates Disruption of Memory Access.

To solve the error you need:

Make sure the system section of the disk has enough free space;

If the error message is identified by the driver, disable or update it;

Replace the video card;

Update BIOS;

Disconnect the caching options and BIOS memory shades.

2 The parameter (exception address) must identify the driver or a function that caused an error.

If the reasons for exception are not defined, consider the following problems:

Hardware incompatibility. Make sure that new hardware installed are compatible with the installed version of Windows;

Defective Device Driver or System Service may be causes of error. Hardware problems such as BIOS incompatibility, memory conflicts and IRQ conflicts can also generate a blue screen.

If the error specifies the driver name it must be removed or disabled. Also delete or disable all recently added drivers and services. If the error occurs during the system launch, and the system partition is formatted by the NTFS file system, you must use a secure mode to remove the defective driver. If the driver is used as a part of the system process of running a secure mode, then to access the file, you will need to start a computer using the recovery console.

If BSOD indicates a Win32K.sys system driver, an error source may be a third-party program remote control. If there is such software, it must be deleted.

Make sure the system enters the Event Viewer system. There are error information there will help identify the device or driver that calls STOP 0x0000008E.

Disable BIOS memory caching. Update the BIOS firmware.

You must also perform hardware diagnostics. Schedule RAM for errors.

Blue screen kernel_mode_exception_not_handled can occur after the first restart during windows installations, or after the installation is completed. Possible cause - lack of disk space for installation. Delete all temporal files, Internet cache files, files backups Applications I.Chk files. You can use another hDD with large volume.

PP1_INITIALIZATION_FAILED

An error occurs during the initialization of the primary phase of the Plug and Play Manager in the kernel mode. By this time, system files, drivers and registry are initialized.

Check the equipment and system disk.

Win32k_init_or_rit_failure

Up_driver_on_mp_system

This error occurs only when the single-processor driver is loaded in the system where more than one active processor is present.

Invalid_kernel_handle

This error appears when some kernel code (for example, server, redirector, or other driver) tried to close an unacceptable handle or protected descriptor.

Parameters:

1 - called a descriptor ntclose

2 - 0 means that the protected handle was closed

1 means that the wrong descriptor is closed

Also, the error can call the NOVELL NetWare version 3.5B client service.

PNP_INTERNAL_ERROR.

Invalid_work_queuee_item.

This error check indicates that the queue record has been deleted, which contained a zero pointer.

This message appears when Keremovequeue deletes the data queue, while Flink or Blink field is 0. This is almost always due to improper use of the working element code of the current object, but incorrect use of any queue can also lead to this error. Rule - data entry in the queue can only be produced once. When the item is removed from the queue, its flink field is 0. This error occurs when an attempt is to delete data, FLINK or BLINK fields of which are equal to 0. In order to allow this error, you need to find out the queue on which it refers. If this queue is one of the running queues (ExWorkerQueue), then the object that is deleted - work_queue_item. This error implies that this is the reason. Error settings help reveal the driver that incorrectly uses the queue.

Bound_image_unsupported

MMLoadSystemImage was called to download Bound Image. This is not supported by the kernel. Make sure that bind.exe was not running for the picture.

Parameters:

1 - data address in the queue, FLINK / BLINK field of which zero.

2 - Address on the referring queue. This is usually one of the exverkerqueues queues.

3 - Initial addressee EXWORKERQUEUE array. This will help to identify if the queue on the question is one of the exverkerqueue queues and if so, then the offset from this parameter will reveal the queue.

4 - If this is ExWorkerQueue queue (as it is usually), it is an address of a working routine that would be called if the working element would be valid. It can be used to reveal a driver that incorrectly uses the working queue.

The problem is caused by an incorrect hardware driver.

END_OF_NT_EVALUATION_PERIOD.

This error check shows that the probation period for the Microsoft Windows operating system is over.

Invalid_region_or_segment

EXINITIALIZEREGION or EXINTERLOCKEDEXTENDREGION has been called with an incorrect set of parameters.

System_license_violation

Microsoft Windows operating system has discovered a violation of the license agreement.

BSOD occurs when you try to change the type of product of the offline system or when the test life of the Windows estimate module is changed.

UDFS_FILE_SYSTEM.

One of the possible causes of blue screen appearance is damage hard disk. Damage to the file system or failure blocks (sectors) on disk can cause this error. Damaged drivers SCSI and IDE can also have a negative impact on the ability to read and write to the hard disk, thus causing this error.

Other possible reason - Exhaustion of the pool of non-accepted memory. During the indexing process, if the amount of the available pool of the non-accepted memory is very small, the other driver requires the pool of non-accepted memory, can initiate an error.

Solve the problem of disk damage: Check Event Viewer on SCSI and FastFat error messages or AUTOCHK (application log), which can accurately define a device or driver that causes an error. Try to disable any antivirus programs, make a copy of the programs, or disk defragment tools that continuously control the system. You should also perform hardware diagnostics of the system.

Run the chkdsk / f / r command to detect and correct any structural damage to the file system. You must restart the system before the disk scan will begin on the system section.

It is necessary to solve the problem of exhaustion of the pool of the non-memory pool: add new physical memory to the computer. This will increase the number of the pool of non-driven memory available to the kernel.

Machine_Check_Exception

Fatal error Machine Check Exception.

This is due to the fact that the processor of your computer detects an error and reports Windows XP. To do this, it uses Machine Check Exception (MCE) for Pentium or Machine Check Architecture (MCA) processors for some Pentium Pro processors. An error can be called as follows:

Errors of the system tire

Contact problems or ERROR CORRECTION CODE (ECC)

Caching problems in a processor or in equipment

Translation Lookaside Buffers (TLB) Processor Problems

Other Processor Problems

Other equipment with equipment

An error may occur if:

1. You dispersed (overclocking) processor or tire. In this case, set the work parameters recommended by the manufacturer.

2. Not a stable power supply. Make sure your BP works correctly.

3. Overheating. Overheating of any components can lead to this error. Make sure all ventilators work properly.

4. Damaged memory or memory is not suitable for your computer. Make sure the memory works properly and the model is compatible with your configuration.

Adding:

This error may also occur if:

1. You have changed the parameters in the BIOS, affecting the system kernel configuration

2. You installed XP with an image of someone else's system

3. You are not correctly connected to some kind of equipment.

This is due to the fact that the machine check does not correspond to the already installed kernel configuration.

In Windows Vista and later operating systems, the blue screen 0x0000009C occurs only under the following circumstances:

WHEA is not fully initialized;

All processors that come closer do not have errors in registers.

Under other circumstances, this error was replaced by BSOD 0x00000124: Whea_uncorRectable_error.

User_Mode_Health_Monitor

This problem occurs due to the competition between the threads, which frees the stack of the kernel and another stream, which is highlighting the memory .. This problem occurs if the attempts of memory is attempting occurs before the workflow clears the kernel memory stack.

Hardware mechanisms detected kernel mode services that are not performed. However, the problems of resource exhaustion (including memory leaks, blocking competition) can block the critical components of the user mode, without blocking the deferred procedure calls (DPCS) or the depletion of the non-memory pool.

In operating rooms microsoft systems Windows Server 2003, Enterprise Edition, Windows Server 2003, Datacenter Edition, and Windows 2000 with Service Pack 4 (SP4) BSOD can be called by the user mode. Blue screen 0x0000009E occurs only if the user installed HangrecoveryAction to 3.

Also, an error may appear when adding additional disk drives for fault tolerant clusters in Windows Server 2008 R2

Driver_power_state_failure

The driver is in an incompatible or confusing state of the power supply. In most cases, due to nutrition failures, while the computer is turned off or out of the standby mode (Hibernate).

Windows XP and above

The reason for this foot is the device driver that has not stood the call to the transition to another power state.

You must update or remove an inoperable device driver or file system driver (File System Filter Driver), which may have been installed by antivirus, program remote access or by CDW / CDRW.

To detect the driver, apply the following:

1. Use% Systemroot% System32Sigverif.exe to check for drivers that did not pass Microsoft tests (Unsigned Drivers).

2. Check the driver updates from your system supplier.

3. Update the software that can have a file system filter driver (File System Filter Drivers).

4. Remove equipment components, as well as software that is not required.

5. Install another Windows to another partition. And install the software, immediately checking until I detect a vulnerable program.

Internal_power_error

Indicates the fatabal error of the power management manager.

PRI attempted to translate a computer under windows control Vista or Windows Server 2008 in sleep mode appears a message about an unreasonable error.

This problem occurs due to an error in the ATAPI.SYS file. Before Windows Vista goes into sleep mode, Windows Vista has a memory entry file of the sleep mode on the disk. However, in some cases, the disk may not return the correct value when you try to initialize the corresponding stack of the system's repositories. When the storage disk returns incorrect valueWindows Vista stops responding to requests.

Update your OS

Pci_bus_driver_internal

0x000000A1 appears when inconsistencies are detected in its internal structure of the PCI bus driver and can not continue to work.

Memory_image_Currupt.

0x000000A2 indicates damage to the image of an executable file in memory.

The memory checksum (CRC) ceased to work.

Check the memory for errors.

Acpi_driver_internal

0x000000A3 Indicates that the ACPI driver discovered internal inconsistency.

The inconsistency in the ACPI driver is so serious that the continuation of the work would cause serious problems.

A possible source of this problem is a BIOS error.

CNSS_FILE_SYSTEM_Filter.

0x000000A4 Indicates an error in the CNSS File System Filter.

BSOD CNSS_FILE_SYSTEM_FILTER can occur due to the overflow of the pool of non-accepted memory. If the pool is not permanent memory absolutely full, this error can stop the system. If during the indexing process, the number of available pool of non-memoryable memory is very small, another driver that requires a pool of not driven memory also, can initiate this error.

Solve the problem of depletion of the pool of non-switched memory: Add new physical memory to the computer. This will increase the number of the pool of non-driven memory available to the kernel.

ACPI_BIOS_ERROR.

The reason for this message is the constant failures in ACPI BIOS. At the operating system level, this problem cannot be solved. A detailed analysis is required.

This may occur if it is found that BIOS Computer Not fully compatible with configuration and power (ACPI).

To resolve this problem, contact your computer manufacturer to get a BIOS update, which is completely ACPI-compatible.

To temporarily solve this problem, you must manually install the standard computer (HAL) abstraction layer:

Restart your computer and re-run the installation program.

After re-starting the installer, press the F7 key (not F6) when you appear on the "Press F6, if you need to install a special SCSI or RAID driver."

Windows automatically disables the installation of ACPI HAL and sets the standard HAL PC.

Bad_exhandle

This error means that checking in kernel mode, the descriptor tables are detected incompatible entry in the status table.

Session_has_valid_pool_on_exit.

This error means that the verification of the unloading session occurred while the driver session was still kept in memory.

An error occurs because the session driver does not release its pool selection before the session is unloaded. This error check indicates an error in win32k.sys, atmfd.dll, rdpddd.dll, or video driver.

Blue Death Screen (Blue Screen of Death, BSOD) is a critical system error In Microsoft Operating Systems Windows. When this malfunction occurs, the system hangs and the data that has been changed during operation is not saved. It is one of the most common windows 7 in the operating system. To eliminate this problem, you must first figure it out for the reasons for its appearance.

The reasons due to which the BSOD error appears, can be divided into 2 generalized groups: hardware and software. Hardware problems are problems with the "hardware" in system block and various components. Most often, malfunctions arise with RAM and hard disk. But still, malfunctions and other devices are possible. BSOD may arise due to the following hardware problems:

• Incompatibility of installed equipment (for example, installation of an additional plank "RAM");
• Breakdown of components (most often fail or RAM);
• Incorrect acceleration of the processor or video card.

The program reasons for the appearance of a problem much more extensive. Failure may arise in system services, incorrectly installed drivers or due to action malicious programs.

• Unsuitable drivers or conflict of some drivers (incompatibility with the operating system);
• Activities of viral software;
• Coes in the application of applications (most often, in such faults, the culprits are viruses or software solutions that produce an application emulation).

Cause 1: Installing a new program or equipment

If you install a new software solution, it can lead to the appearance of a blue screen of death. The error could arise because of software update. Provided that you conducted similar actions, you need to return everything to your previous condition. To do this, you need to roll back the system by the time when the errors were not seen.

There will be launch of the Windows Recovery Process 7, after which your PC will restart and the malfunction must disappear.

Cause 2: Lack of free space

You must make sure that on the disk where Windows files are located, there is a necessary free space. The blue screen of death and various major malfunctions occur if the disk space is overflowing. Clean the disk with system files.

Microsoft advises to leave free minimum 100 MB, but as practice shows, it is better to leave 15% of the system partition.

Cause 3: System Update

Try updating windows 7 to latest version Service Pak. Microsoft stably produces new patches and packages with updates for its product. Often, they contain fixes that help eliminate BSOD fault.

Cause 4: Drivers

Procedure to update your system drivers. The overwhelming majority of BSOD errors are associated with incorrectly installed drivers that cause a similar malfunction.

Cause 5: System Errors

Check the event log on the presence of warnings and faults that can be associated with the appearance of a blue screen.

Cause 6: BIOS

Incorrect bIOS settings May lead to the appearance of BSOD error. After throwing these parameters, you can fix BSOD problem. How to do it, told in a separate material.

Reason 7: Hardware component

It is necessary to check for the correct connection of all internal cables, cards and other components of your PC. Elements that are poorly connected can cause the blue screen appearance.

Error codes

Consider the most common error codes and their interpretation. It can help troubleshoot.

• Inaccessible Boot Device. – this code means that there is no access to the download section. The download disk has a defect, a controller malfunction, also incompatible system components can cause a problem;
• KMODE EXCEPTION NOT HANDLED - The problem most likely arose due to problems with hardware components of PCs. Incorrectly installed drivers or physical equipment breakdown. It is necessary to conduct an alternate check of all components;
• NTFS File System - The problem is caused by the failures of the system window files 7. Such a situation arises due to mechanical damage In the hard disk. Viruses recorded in the hard drive area causes this malfunction. Damaged logic structures system files Also are able to cause malfunction;
• IRQL NOT LESS OR EQUAL - Such code means that BSOD faults appeared due to errors in service data or Windows 7 drivers;
• Page FAULT IN NONPAGED AREA - Parameters that are requested cannot be found in memory cells. Most often, the reason lies in the defects of RAM or incorrect operation of antivirus software;
• Kernel Data Inpage Error - The system failed to read the data that were requested from the memory partition. The reasons here are: Failures in the Winchester sectors, problem points in the HDD controller, malfunction in the "RAM";
• Kernel Stack Inpage Error - OS is not able to read data from the paging file to the hard drive. Causes of such a situation - damage in the HDD device or RAM memory;
• UNEXPECTED KERNEL MODE TRAP - the problem is associated with the system core, it happens both software and hardware;
• Status System Process Terminated - A logical fault that is directly related to drivers or with incorrectly working applications.

So, to recover the correct operation of Windows 7 and get rid of BSOD error, first of all, you need to roll back the system at the time of stable operation. If there is no such possibility, then you should install the latest updates for your system, check the installed drivers, test the health of the PC. Error troubleshooting is also present in the fault code. Taking advantage of the methods that are given above, you can get rid of the blue screen of death.

Blue Screen of Death or BSOD (The Blue Screen of Death) is always a very disturbing symptom of computer problems. This screen appears when Windows detects a critical error that the system is unable to fix independently. As a result, a reboot of a computer is requested, and very often it leads to the loss of all unsaved changes.

The blue screen of death is the worst error with which the computer user may encounter. Unlike application failures, a critical fall with BSOD disrupts the efficiency of the entire system. Usually the blue screen of death appears as a result of low-level software failures or problems of computer hardware components.

Causes of BSOD appearance

Usually, blue death screens are caused by a computer malfunction or drivers. Conventional applications should not cause BSOD. In cases of fall third-party programs Do not cause violation of the operating system. The most frequent causes of BSOD - hardware failures or problems with software Windows kernel level. There are drops associated with updates of antiviruses.

Blue screen usually appears when Windows detects a "Stop error". This critical fall leads to stopping the Windows system. In this case, it remains only forced to turn off the computer and restart it. This procedure can lead to loss of unsaved data, because applications actually do not have a chance to save changes. In the perfect program scenario, regularly keeping the progress of work so that BSOD or other errors have not led to data loss.

When blue screen appears windows death Automatically creates and saves the "minidump" dump file, which contains information about the critical failure. Users can view information in dumps - it can help identify the cause of falling with BSOD.

By default, Windows automatically restarts the computer when the blue death screen appears. If your computer reboots without a visible reason, it is possible that it is related to the blue screen.

If you want to see detailed information when the blue screen appears, you should disable the automatic reboot in the Windows control panel.

1. Click on My Computer icon.
2. Right-click and select the "Properties" item.
3. In the left navigation menu, select the option " Extra options Systems.
4. Go to the "Advanced" tab and in the "Download and Recovery" section, click the "Parameters" button.
5. In the "System Failure" section, remove the checkbox from the "Automatic Reload" option.

The BlueScreenView application offers an easy way to view BSOD information. The program automatically scans all the memory dump files and displays the failures.

Similar information can be viewed using the embedded classic application "View Events". True, in this case, the BSOD messages will be displayed in one list with application drops and other messages of the system log.

For developers or advanced users, a powerful Ledbg dump debugger from Microsoft will be suitable.

Search and eliminate vulnerabilities

In Windows 7 and more new windows versionsBSOD information is also displayed in the center of action. If you encountered a BSOD error, you can open the Actions Center and check the available solutions. Windows will analyze BSOD and other types of errors on the computer and provide recommendations to eliminate the problem.

Often you can get additional information About the blue screen error, when searching for a specific error message - for example, "Driver_irql_not_less_or_equal". New BSOD screens in windows systems You yourself encourage users to search the Internet to familiarize yourself with possible problems.

• Use the system recovery wizard. If the system recently started testing failures with BSOD, use the system recovery function to return the system to the previous stable state. If this helps, it is likely that the problem was caused by software errors.
• Check the system for malicious programs. Threats that penetrate deeply in Windows kernel can cause system stability problems. Scan your computer for malicious programs to ensure that the system failure is not caused by cunning malware.
• Install driver updates. An incorrectly installed or defective driver can lead to drops. Download and install the latest drivers for computer components from the manufacturer's official website - it can help cope with BSOD.
• Perform download in safe mode. If your computer constantly issues failures with BSOD, try to boot in safe mode. In safe windows mode Loads only the most basic drivers. If the blue screen of death appears due to installed Driver, There will be no critical error in the safe mode, and you can correct the problem.
• Diagnosing hardware components. Blue screens can be caused by faulty equipment. Try performing memory testing for errors and check the temperature individual elements PC to make sure that it does not overheat.
• Reinstall Windows. Pure installation Systems is a radical action, but it will allow you to get rid of possible problems installed programs. If, after reinstalling the system, BSOD errors continue, which is most likely they are associated with equipment.

Even, an absolutely serviceable computer in rare cases may experience falling with BSOD without a visible cause - due to driver errors, installed applications or hardware components.

If you are very rarely encountered with BSOD (let's say, every two years), then there is no reason for anxiety. If BSOD errors pop up regularly, then you need to look for the cause and eliminate the problem.

Found a typo? Highlight and press Ctrl + Enter