Protection from blue screens of death. What is written on the Windows blue screen of death? Rollback to a restore point

03.07.2019 news

BSOD (English... Blue Screen Of Death)

BSOD- this is the name of the message that appears in Windows operating system, in case of a critical system error, translated into Russian - blue screen of death. This screen appeared in Windows NT and, since then, is present in all versions of this operating system, and it is so ominously called because after its appearance the OS really "dies" (goes into reboot), dumping the dump and losing all unsaved data ...

What causes BSOD? This error is waiting for you if any the driver will try to perform an illegal operation, and it doesn't matter whether it is a hard disk driver, without which it is really impossible to work, or a network / sound card driver, which does not affect the operation of the main system functionality ... the result is the same: BSOD and an emergency reboot.

Driver problems causing blue screen death, can be conditionally divided into two types:

hardware problems (RAM, motherboard, hard drive, non-standard devices ...),
software driver conflict (antiviruses, emulators, firewalls ...).

There is an indirect sign by which you can determine the cause of the BSOD.

If a blue screen appears with different error codes (on random drivers), it is most likely caused by computer hardware problems. To check this version, you must first examine the equipment for possible overheating: processor, coprocessor, video card, hard disk, etc. The temperature of devices can be viewed in the BIOS or specialized programs that are easy to find on the network. Temperatures above 65-70 ° C are cause for concern.
If overheating is not observed, it is worth visually inspecting the motherboard and power supply for swollen capacitors (leaked electrolyte).
It is also necessary to check the BIOS settings, it is advisable to reset them to the default settings. It will not be superfluous to update the BIOS version from the motherboard manufacturer's website, or at least remove the battery from the motherboard and, after waiting about a minute, insert it back.
Try to conduct various tests on a computer (memory, video card, processor) with special utilities.
If you have several RAM modules installed on your computer, try leaving one of them and check the system operation.
The last way to check is to completely remove all the boards from the connectors, blow out the computer with compressed air, clean the contacts on the boards with cotton wool dipped in an alcohol solution, dry them and put everything back together.

If a critical error occurs constantly with the same error code (driver name), then the problem is more likely with a driver conflict or an incorrectly written driver. In this case, the priority of checking should be given not to system drivers, but software drivers, running in kernel mode.
The first thing to do is to make sure that your operating system stores areas of memory with errors in minidump files. On Windows, such files are saved by default in the% systemroot% \ Minidump folder (C: \ Windows \ Minidump). If there are no files in this directory (there is no directory itself), you must enable this option at the address:
For Windows XP Control Panel - System - Advanced - Startup and Recovery - Options ...
For Windows 7 Control Panel - System and Security - System - Advanced System Settings - Startup and Recovery - Settings ...
Under the heading "Recording debug information" you must set Small memory dump(64 KB for Windows XP, 256 KB for Windows 7).

After that, minidump files will appear in the default folder after every system crash. The file names will indicate the date of saving and the ordinal number of the saved file for this date. You can open such files with special programs that are easy to find on the Internet by a search query. By opening the minidump file for the date you are interested in, you can see which driver caused the abnormal termination, after which you can roll back / update this driver, reinstall conflicting software, and take other actions to restore the computer's performance.
Blue screen of death – this is a critical error message from the operating system. In this way, Windows lets us know that there are serious problems with the computer that require the immediate attention of the user. Let's try to figure out what can cause the blue screen of death, how you can prevent its appearance and how you can deal with it.

What is the Blue Screen of Death?
In order to identify the causes of the appearance of the blue screen of death, it is necessary to understand what it is. Blue Screen of Death or BSoD- this is what the Windows developers themselves call this type of error. Blue - because the message from the system is displayed on a blue background. Death screen - since Windows cannot continue to work after such an error, it is necessary to reboot the operating system, and all unsaved data will be lost. If you see BSoD on your computer 1 or 2 times - do not worry, occasionally everyone has operating system crashes. If the appearance of the blue screen of death has become regular, it is worth thinking about the reasons for its occurrence and how to eliminate it.

The blue screen of death, possible causes of its occurrence.

The main causes of the blue screen of death are:

A software failure in the operation of a device driver. This is the most common cause of BSoD.
A conflict in the operation of applications, as a rule, this happens if you have installed two anti-virus packages or two firewalls on your computer.
Installing drivers from an unknown developer - often third-party drivers may contain errors that can interrupt the operation of the operating system.
Errors in the operation of equipment - overheating of the processor or video card, poor contact in the connectors, defective RAM chips.

As you can see, the list of reasons for the appearance BSoD quite extensive. In order to find out the specific reason, we should take a close look at the blue screen of death itself in Windows XP or another version of Windows. In the Technical Information block, the first line is the error code. It will be difficult for a non-specialist to understand what is hidden behind this sequence of numbers; in the second line of this block, the system tells us exactly in which file a critical failure occurred, which led to the appearance of the blue screen of death. By the name of the file, you can determine in the driver of which particular device an error occurred.

How to deal with the blue screen of death.

At the previous stage, we analyzed the causes of BSoD... Now, based on this data, we will determine why on our computer appeared blue screen of death and what to do in order to eliminate the source of the critical error.

First of all, you need to find out which device driver is the file in which the failure occurred. After that, you need to reinstall this driver, be sure to use the software from the device manufacturer. Now reboot the system and let it run if the error reappears - other reasons for the system crash should be considered. The Blue Screen of Death in Windows 7 often occurs due to hardware malfunction. Try to check, with the computer disconnected from the network, the reliability of installation in the corresponding connectors on the motherboard of the RAM and video card. Often it is a poor-quality installation or the presence of dust on the contacts that can lead to system malfunction.

The most common BSoD. Blue screen of death error codes

KMODE_EXCEPTION_NOT_HANDLED- Causes a blue screen as a result of a kernel-mode process error trying to execute an unknown instruction. May be due to hardware incompatibility or malfunction, or errors in drivers or system services.

NTFS_FILE_SYSTEM- this error appears as a result of a failure to execute the code of the ntfs.sys file system driver. The root cause may be data integrity on disk or memory, or damaged SCSI or IDE drivers.

DATA_BUS_ERROR- the blue screen of death appears as a result of the appearance of a parity error in RAM. The main reason may lie in incompatible or faulty hardware. Also, the problem may be associated with an incorrect driver, as well as a failure that has passed on the disk.

IRQL_NOT_LESS_OR_EQUAL- the blue screen of death in this case appears as a result of the kernel mode process accessing the memory area while using an unacceptably high IRQL level for it. This error can be caused by improper operation of drivers, system services, or incompatible software such as a software emulator or antivirus application.

PAGE_FAULT_IN_NONPAGED_AREA- the error appears as a result of the system not finding the necessary data, for example, when Windows searches for the necessary information in the paging file, but cannot find it. Often, the appearance of a blue screen of death in this case is caused by hardware failures, disruptions in the operation of file systems, or an error in a service or software, such as antivirus.

KERNEL_STACK_INPAGE_ERROR- This error appears as a result of reading errors from the paging file into physical memory. The main reason for the appearance of the blue screen of death is a corrupted sector of the virtual memory file, incorrect operation or failure of the hard disk controller, insufficient free disk space, incorrect connection of the hard drive, conflict in interrupts, defect in RAM, viruses in the operating system.

Basically, the appearance of the blue screen of "death" is caused by: software (drivers), sometimes in the hardware (its failure, conflicts or malfunctioning). In these cases, when a blue screen of "death" appears, you need to remove recently installed programs and drivers, as well as disable and remove recently installed hardware.

You need to uninstall the software in Windows Safe Mode by pressing the F8 key and selecting Safe Mode when loading the operating system.

A common cause of the blue screen of death is overheating of the hardware (computer components). In this regard, the protection is triggered, which is the reason for the emergence of BSoD. To do this, you need to remove the cover of the system unit and determine the source of overheating - very often this source is the central processor, less often the video card and the power supply. If a malfunction is detected, it (malfunction) must be eliminated, then the BSoD problem will be eliminated.

Unfortunately, it happens that over time, Windows XP users have a problem while working on a PC or when loading the OS in the form of a "screen of death". The error is often caused by overheating of the equipment, a conflict between PC components, and infection with malicious applications. This list is endless, since a failure can be caused by a variety of reasons.

Any of the critical errors can become an unpleasant consequence of the "BSOD" display on the monitor, which stands for "Blue Screen Of Death" in English. Below is a guide on how to avoid the appearance of a "blue screen of death" in a computer on Windows XP, and with detailed descriptions of recommendations on what to do if it does happen.

BSOD - what is it?

Despite the formidable name, this screen is intended to help the user, and is a protective feature of Windows XP. It already contains a detailed text with a description and recommendations for solving the problem. The owner of the computer, after carefully studying the error codes displayed on the screen, can already accurately take the necessary measures to eliminate the causes of the failure.

However, sometimes some users mistake other blue-interface programs, such as BIOS, for the "screen of death". Accidentally hitting any key when starting the computer, or in some other way, sometimes the owner of the PC launches the BIOS, which is also blue and newcomers mistake it for the well-known "blue screen of death". If a menu similar to the one below appears on the monitor,

then you just need to click "ESC" or click on the item "Exit Without Saving". After that, the PC will start in the usual mode for the user.

Also, if Windows XP was not shut down correctly, a blue screen may appear when analyzing the disk for the presence of various errors.

You shouldn't be afraid of it either, you just need to wait and let the Chkdsk application perform its functions, after which Windows XP will boot itself.

But if the user sees the following image:

then you will have to follow the steps described below in this manual.

How to decrypt information displayed on BSOD?

A detailed study of the information and codes presented on this screen will allow you to quickly and effectively eliminate the causes of the failure.

Information with a detailed description of the error is available at the top of the screen. Further, recommendations are given on how to eliminate the difficulties that have arisen. After them, specific numerical error codes are indicated. And in the case when a failure occurred due to some file, the name of this file will be shown.

The main causes of BSOD

Knowing the reasons why the problem may arise, you can effectively take preventive measures to prevent the occurrence of failures.

The main reasons are divided into 3 groups:

Computer components;
Hardware software (drivers);
Applications.

PC accessories

These include the most common causes of the screen of death. Therefore, you should first of all pay attention to whether new equipment was installed immediately before the occurrence of the failure. Also, the error is often caused by RAM or hard disk, therefore it is recommended to test the RAM and hard drive of the computer.

It is very rare, but there are problems due to the video card or even due to the central processor. Testing is required too. For this purpose, specialists have developed many applications.

Many users install additional cards to increase the speed of their PC. If there are any, then you should temporarily disable them and work on the PC for a while. In the case when the error does not manifest itself without them, an unambiguous conclusion can be made about the cause of the failure.

When a blue screen appears during operation, very often a weak or outdated power supply is the cause. In this case, it is recommended to install a new PSU - with the best power characteristics.

Hardware software (drivers)

More than half of all cases of the appearance of the "screen of death" are associated with drivers. If you need to reinstall the software, then you must first remove the installed driver and only then install the current version from the official source of the equipment manufacturer.

Applications

Just as with drivers, the issue is solved by reinstalling the application, but with its preliminary complete removal and cleaning the registry from the remnants of the program.

Often, when working on the same computer, 2 antiviruses at once appear errors that cause the appearance of BSOD. Protect one operating system with only one anti-virus utility.

How to troubleshoot a problem in Windows XP

Sometimes Windows XP after a failure in automatic mode restarts or the owner of the PC, by clicking on "RESET", reboots the computer itself, and the system again begins to function normally. However, it is not uncommon for the OS to fail to boot after a crash even in safe mode, and the "screen of death" is again displayed in front of the user's eyes.

In such a situation, you will need to use the external installation media with the Windows XP distribution kit.

You need to do the following:

In the BIOS, set the OS startup priority from external media and, depending on its type, install it into the computer's optical drive (CD-disk) or into a USB-port (flash drive).
Then restart the PC;
The "Install Windows XP" menu will be displayed;
Then activate the "Restore Windows XP" command from the menu - to do this, click the "R" button;
After that, in the next menu that appears, click "1" and click on "Enter";
Type the access code to the PC (if the user set it earlier) and click "Enter" again;
At the prompt, type "fixboot";
The system's recommendation "Do you want to write the new boot sector to the C: directory?" - it is necessary to click on the "Y" button;
Then type "fixmbr" and click on the "Y" button again;
Click "Enter";
Type "exit", close the program, restart the PC;
Open BIOS, where to specify the launch of the OS from the hard disk.

The computer will now work normally again. Despite the fact that the procedure consists of 12 stages, it usually takes no more than five minutes to complete it, and this is guaranteed to eliminate the BSOD problem.

Many of you have probably heard from friends and acquaintances more than once about such a concept as, the Windows 7 blue screen of death, which appeared on their computer, it is also called BSOD ( Blue screen of death).

With the appearance of a blue screen, Windows warns us about what, and it is advisable to eliminate them in a timely manner. On the screen of death, error codes are displayed, by which you can understand why it is happening, and from this you can conclude which component of the computer is failing or is a software problem.

If your computer with Windows 7 began to issue BSOD, then you and I need to understand why it appears, and for this you need to write the error code to yourself in a notepad or take a picture of the monitor screen, and then, filling in these errors, in the search bar or, we are looking for what it means, or we read the entire article, in it you will find codes of the most common errors due to which the blue screen of death appears. But first, we will carry out preparatory work with you.

In order for us to have time to record or photograph the blue screen error code, we need to do some system settings.

You need to turn off restarting the PC when an error occurs, as well as enable writing debug information to the memory dump.

Memory dump- the contents of RAM at a certain point in time, let's say a special image.
Small memory dump - part of the memory that is written to the hard disk during failures, only the most important information remains there.

In order to go to the system settings, open "Start", select the "Computer" item, right-click on it and select "Properties"

A new window will open in which we select the "Advanced" tab and click the "Options" button in the "Startup and Recovery" item

Next, look at the section "Recording debug information" there you need to select "Small memory dump 256 KB"

Now your computer is configured, the next time it crashes, it will not restart, and you can safely write down the error code or take a picture of it.

Blue screen of death, Windows 7 error codes

Let's now take a look at the most common error codes.

KMODE EXCEPTION NOT HANDLED - the computer issues such an error if there is a problem with the hardware (for example, a component of the computer is out of order) or a problem with the drivers.
NTFS FILE SYSTEM - problems with the file system of the hard disk, this problem can occur in several cases:

* presence of viruses in the boot area of the hard disk

* damage to the structure of the file system.

INACCESSIBLE BOOT DEVICE - when this error appears, the Windows operating system says that it could not access the boot partition of the disk. There can be many problems that caused this error. For example, a problem in the PC hardware: the hard drive is damaged, the controller is faulty, individual computer components are faulty, or a software problem: viruses or file system errors.
IRQL NOT LESS OR EQUAL - this error may appear if there is a problem with drivers or any Windows system service

PAGE FAULT IN NONPAGED AREA - a blue screen of death with this code means that the data that the system is looking for is not in memory, respectively, when the operating system accesses, for example, data in the paging file, but there is nothing there, then such an error will appear. The error often appears due to problems with RAM, errors in Windows system services, or due to a damaged file system.

KERNEL DATA INPAGE ERROR - the operating system cannot read data from memory. This error can be caused by faulty RAM, hard drive problems due to unreadable sectors, or a problem with the HDD controller.
KERNEL STACK INPAGE ERROR - OS was unable to read the paging file and write data to the hard disk. The main reasons for this error are a problem with the RAM or hard drive.
UNEXPECTED KERNEL MODE TRAP is an error appearing at the system kernel level. The reasons that caused it can be both hardware and software.
STATUS SYSTEM PROCESS TERMINATED - an error caused by a software failure, problems in the operation of system services, the operation of drivers or applications
DATA BUS ERROR - a blue screen appears when there is a failure in the RAM or when the video adapter malfunctions.

Windows 7 Blue Screen of Death, what to do?

After we have determined what kind of error we are getting, we need to establish the reason due to which our computer began to malfunction. To do this, you need to remember what the last changes took place on your computer. You may have installed a new program or updated drivers for a device. To eliminate the human factor, you need to remove the latest installed programs, as well as roll back the drivers to previous versions. If errors began to appear after installing new hardware in the system unit, then you need to turn it off and observe the operation of the computer.

In order to resolve the error caused by a software glitch, you need to try the following steps.

Roll back installed new drivers to the previous version;
Start Windows with the last known good configuration;
Perform a system restore using a standard Windows function.

I advise you to check the amount of remaining free space on the system partition of the hard disk, as a small amount of memory can cause system malfunctions. Do not forget to check your computer for viruses, for this you can use the free Dr.Web Cureit utility or the KVRT utility from the Kaspersky Lab. If the blue screen of death continues to appear, I recommend installing the latest Windows 7 service pack.

Reset BIOS settings to default, it is possible that the computer components were overclocked incorrectly, due to which the hardware works at the wrong settings that differ from the factory settings, thereby giving malfunctions. To reset the settings, you need to go into the BIOS, press the F5 key and to save the F10 settings. The computer should restart and apply the new settings.

To get information about the error, enter its code in the text field just below in the following format: 7e or 0x0000007e

Go to description

UNEXPECTED_KERNEL_MODE_TRAP

This error means that an unexpected kernel-mode exception, or interrupt, has occurred in which the kernel does not fire.

Also, the cause of the error can be an interrupt, which entailed immediate death in the form of a double fault - a double fault. The first number in the error code is the interrupt number (8 = double fault). To find out more about what this interrupt is, refer to the Intel x86 family manual.

In short, an error occurs when the processor makes an error that the kernel cannot handle. Most often, the error occurs due to bad blocks of RAM, and sometimes due to overclocking the processor.

Try to disable the synchronous data transfer function in the BIOS.

Troubleshooting: If you have new hardware installed in your computer, you will need to disconnect it. If the existing hardware fails, then it is necessary to remove or, if necessary, replace the defective computer components.

Scan your RAM for errors.

Make sure that all of the computer components are installed properly. Clean the contacts of the adapters.

Update BIOS.

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

If a driver is identified in the error message, disable or update that driver. Disable or remove any drivers or services that were recently added. If an error occurs during Windows startup and the system partition is formatted with NTFS, use Safe Mode to reinstall or remove the defective driver. If the driver is used as a system startup process in Safe Mode, start the computer using Recovery Console to access the file.

Restart your computer and press F8 in the text mode menu to display the boot options for the operating system. From this menu, select Load Last Known Good Configuration. This option is most effective when adding only one driver or service to the system at a time.

Overclocking the CPU may cause an error. Return the default CPU clock speed.

Make sure the system is logged into Event Viewer. The error information found there will help identify the device or driver that is causing the 0x0000007F screen of death.

Disable BIOS memory caching.

If the UNEXPECTED_KERNEL_MODE_TRAP error appears when you upgrade to a new version of the Windows operating system, it may be caused by a device driver, system service, antivirus or backup program that is incompatible with the new version. Uninstall all third-party device drivers and system services, disable antivirus software.

Install the latest Windows service pack.

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

SPIN_LOCK_INIT_FAILURE

This validation error appears very rarely.

DFS_FILE_SYSTEM

Distributed file system errors.

Update your OS.

SETUP_FAILURE

A fatal error occurred during installation.

The setup text form no longer uses bugcheck to get out of serious errors. Therefore, you will never encounter 0x85. All bug checks have been replaced with friendlier and (where possible) more informative bug reports. However, some bug writers have simply been replaced by our bugcheck screens, and the code for these error states is the same as it was. They are listed below.)

0: OEM HAL font is not a valid * .fon file format, so the installation was unable to display the text. This means that the vgaxxx.fon on the CD or floppy is corrupted.

1: Video could not be initialized. This error has its own screen and only 2 options are presented to the user.

This means that the vga.sys file (or another driver, depending on the machine) is damaged, or that this hardware is not supported.

The reason for the error:

0: NtCreateFile of devicevideo0

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

2: Out of memory. This error now uses a friendlier screen, depending on how far the installation went.

3: The keyboard has not been initialized. Now 2 different screens are used depending on the errors that might appear here. This may mean that the disk 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 keyboard layout dll cannot be loaded.

The reason for the error:

0: NtCreateFile of deviceKeyboardClass0.

The installation did not detect a keyboard connected to your computer.

1: Unable to load keyboard layout dll.

The installation cannot load the keyboard layout dll.

This means that there is no file on the floppy or CD (kbdus.dll for us or other dlls).

4: The installation could not figure out the path of the device from which the installation started. This is an internal installation error.

5: Partition health check failed. This means a bug in the disk driver. The parameters are only relevant for the installation group.

MBR_CHECKSUM_MISMATCH

This error occurs at boot time when the MBR checksum calculated by the Microsoft Windows operating system does not match the boot loader checksum.

This BSoD indicates the presence of viruses.

It is necessary to scan the operating system for viruses with up-to-date antivirus programs.

PAGE_FAULT_IN_NON_PAGED_AREA

This BSoD is a common error. To interpret it, you need to identify which exception was thrown.

The following exception codes exist:

0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data link;

0x80000003: STATUS_BREAKPOINT. Indicates a situation where the system encounters a checkpoint or ASSERT without a kernel debugger attached;

0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation.

To solve the error, you must:

Make sure that the system disk partition has enough free space;

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

Replace the video card;

Update BIOS;

Disable BIOS caching and shading options.

Parameter 2 (address of the exception) must identify the driver or function that caused the error.

If the reasons for the exception are not clear, consider the following issues:

Hardware incompatibility. Make sure the newly installed hardware is compatible with the installed version of Windows;

A defective device driver or system service may be the cause of the error. Hardware issues such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate blue screens.

If the name of the driver is indicated in the error, it must be removed or disabled. Also remove or disable any recently added drivers and services. If an error occurs during system startup and the system partition is formatted with NTFS, you must use Safe Mode to remove the defective driver. If the driver is used as part of the system's Safe Mode startup process, you will need to start the computer using the Recovery Console to access the file.

If the BSoD points to the Win32k.sys system driver, a third-party remote control program could be the source of the error. If you have such software, you must uninstall it.

Make sure the system is logged into Event Viewer. The error information found there will help you identify the device or driver that is causing Stop 0x0000008E.

Disable BIOS memory caching. Update the BIOS firmware.

You also need to run hardware diagnostics. Scan your RAM for errors.

The KERNEL_MODE_EXCEPTION_NOT_HANDLED blue screen can occur after the first restart during a Windows installation, or after the installation is complete. Possible cause is insufficient disk space for installation. Delete all temporary files, internet cache files, application backup files and .chk files. You can use another hard drive with a larger capacity.

PP1_INITIALIZATION_FAILED

An error occurs during the initialization of the primary phase of the Plug and Play manager in kernel mode. At this point, the system files, drivers and registry have been initialized.

Check your hardware and system drive.

WIN32K_INIT_OR_RIT_FAILURE

UP_DRIVER_ON_MP_SYSTEM

This error only occurs when a uniprocessor driver is loaded on a system where more than one active processor is present.

INVALID_KERNEL_HANDLE

This error appears when some kernel code (such as a server, redirector, or other driver) tried to close an invalid handle or protected handle.

Parameters:

1 - Called handle NtClose

2 - 0 means the protected handle was closed

1 means the wrong handle was closed

Also, the error can be caused by the Novell NetWare Client Service version 3.5b.

PNP_INTERNAL_ERROR

INVALID_WORK_QUEUE_ITEM

This error check indicates that a queue entry was deleted that contained a null pointer.

This message appears when KeRemoveQueue is deleting the data queue while the flink or blink field is 0. This is almost always due to misapplication of the code of the working element of the current object, but misapplication of any queue can also lead to this error. The rule is that data can be entered into the queue only once. When an item is removed from the queue, its flink field is 0. This error occurs when an attempt is made to delete data whose flink or blink fields are 0. In order to resolve this error, you need to find out the queue it refers to. If this queue is one of the EX running queues (ExWorkerQueue), then the object being removed is WORK_QUEUE_ITEM. This error implies that this is the cause. The error parameters can help you identify the driver that is using the queue incorrectly.

BOUND_IMAGE_UNSUPPORTED

MmLoadSystemImage was called to load the bound image. This is not supported by the kernel. Make sure bind.exe has not been run for the picture.

Parameters:

1 - Address of data in the queue, flink / blink field of which is zero.

2 - Address to the referencing queue. This is usually one of the ExWorkerQueues queues.

3 - The starting address of the ExWorkerQueue array. This will help to identify if the queue in question is one of the ExWorkerQueue queues and if so, then offset from this parameter will reveal the queue.

4 - If this is an ExWorkerQueue queue (as is usually the case), this is the address of a running routine that would be called if the running item were valid. This can be used to identify a driver that is misusing the work queue.

The problem is caused by an incorrect hardware driver.

END_OF_NT_EVALUATION_PERIOD

This error check indicates that the trial period for the Microsoft Windows operating system has ended.

INVALID_REGION_OR_SEGMENT

ExInitializeRegion or ExInterlockedExtendRegion were called with the wrong parameter set.

SYSTEM_LICENSE_VIOLATION

The Microsoft Windows operating system has detected a license violation.

BSoD occurs when a user tries to change the offline product type or when the trial period of the Windows Assessment Module is changed.

UDFS_FILE_SYSTEM

One possible cause of a blue screen is a damaged hard drive. Damage to the file system or bad blocks (sectors) on the disk can cause this error. Corrupted SCSI and IDE drivers can also negatively impact the system's ability to read and write to the hard drive, thus causing this error.

Another possible cause is the depletion of the non-paged memory pool. During the indexing process, if the amount of available non-paged memory pool is very small, another driver that requires a non-paged memory pool may trigger an error.

Resolve Disk Corruption: Check Event Viewer for SCSI and FASTFAT (System Log) or Autochk (Application Log) error messages, which can pinpoint the device or driver that is causing the error. Try disabling any antivirus programs, back up programs, or disk defragmenter tools that continuously monitor the system. You should also perform hardware diagnostics on the system.

Run Chkdsk / f / r to detect and repair any structural damage to the file system. You must restart the system before the disk scan starts on the system partition.

You need to solve the problem of depleting the pool of non-paged memory: add new physical memory to the computer. This will increase the amount of non-paged memory pool available to the kernel.

MACHINE_CHECK_EXCEPTION

Fatal error Machine Check Exception.

This is because your computer's processor detects an error and Windows XP reports it. To do this, it uses Machine Check Exception (MCE) for Pentium processors or Machine Check Architecture (MCA) for some Pentium Pro processors. The error can be caused by the following:

System bus errors

Parity problems in memory or Error Correction Code (ECC)

Caching issues in the processor or hardware

Translation Lookaside Buffers (TLB) processor issues

Causes

A blue screen on a laptop with an error message appears when the code is not executed correctly in kernel mode.

Consider what causes the problem leading to the appearance ofBSOD:

hardware malfunction;
conflict or incompatibility of software or hardware;
overheat;
inappropriate drivers or errors in them;
errors in BIOS configuration;
lack of free hard disk space
malware;
incorrect overclocking.

It is easy to see that there are a lot of reasons why the blue screen of death pops up. Based on its own statistics, Microsoft reports that about 70% of BSOD cases are associated with problematic drivers.

A certain percentage of errors are due to applications that execute their own code in kernel mode. If such programs do not work correctly, a blue screen of death also appears.

The main types of applications that need to run their own code in kernel mode are:

antivirus software;
programs for recording information on CD- or DVD-disks;
firewalls;
virtual disks.

Video: Blue Screen of Death: Causes

Trouble-shooting

Very often, the appearance of BSOD indicates serious problems with the laptop hardware or drivers. Therefore, it will not be possible to postpone the decision.

You can try to solve the problem yourself by following these tips:

Carrying out these procedures in most cases will help solve the problem with the emerging blue screens of death. If they continue to appear, then you should pay attention to the error codes. It is they that allow you to determine what it means when a BSOD appears.

Error codes

Each BSOD displays a hexadecimal error code. By remembering it, you can determine the cause of the problems and, if possible, solve it.

Let's consider the most common error codes that appear on a blue background:

There are actually a huge number of error codes. Each of them is described in sufficient detail in specialized documentation. When diagnosing a malfunction, you will have to refer to it in most cases.

The error is not always caused by the problem described. For example, Windows 8 users can very often see error code 0xc0000001. At first glance, this error indicates a problem with the RAM. However, in most cases, you can fix it by running Windows Repair.

You can try to fix the error with code 0xc0000001 in the following way:

when turning on the computer, press the SHIFT + F8 key combination;
in the See advanced repair options section, select Troubleshoot;
go to the Advanced options section and click on the Windows Startup Settings button;
restart the computer using the "Restart" item.

How to view the error message if the system reboots

It is quite common in Windows settings to set the mandatory restart on failure option. In this case, the user usually fails to read the error information.

Resolve an issue with a reboot not allowing the message to be readBSOD can be done in two ways:

A dump is a file that stores information about an error that has occurred. It can be used to diagnose the problem, as it contains information about which driver caused the BSOD.

It is not possible to open dump files and view error codes and drivers that caused them by means of the operating system. This requires installing additional applications such as debugging + kdfe or BlueScreenView.

The debugging + kdfe package runs in console mode. After installing it, run the command: kdfe "% systemroot% Minidump dump file name.dmp". As a result of the command, you can find the driver that caused the error and reinstall or update it.

A program called BlueScreenView has a graphical interface. When you start the application for the first time, you must specify the dump folder. After highlighting the file generated when the error occurred, you can also view the driver that caused the error.

Usually, dumps are stored in the Minidump subfolder of the Windows system directory, but the user can, if desired, change their location in the operating system settings.

It is recommended to disable automatic restart in case of system failure, since the BSOD screen can also provide additional information about the error, which facilitates further diagnostics.

You can disable automatic reboot by referring to the "System Failure" section.

In order to open it to Windows 7 users, you must sequentially open the following items:

start;
control Panel;
system;
additional system parameters;
parameters;
system failure.

Note. The System Failure tab also enables or disables dump recording and specifies the folder for storing them.

In most cases, the user can independently diagnose and fix the error that led to the error message. In addition, regular maintenance of your computer can help reduce its occurrence.