Error codes on a windows 7 computer. Windows error codes

0x00000001: APC_INDЕX_MISMATCH - Error related to the operating system kernel, check installed drivers, they may not work, or they need to be replaced. random access memory.
0x0000000A: IRQL_NOT_LESS_OR_EQUAL - Errors when working with virtual memory, usually associated with an interrupt. Try to update the drivers, one of them probably hides this problem... It is also possible that the equipment itself, which is connected to your computer, is not working properly, although this is extremely rare.
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED - This is quite common.
The error code may indicate a driver that caused the computer to crash into a blue screen. Therefore, pay attention to the address after the error. For example:
0x80000002- May indicate hardware incompatibility, memory conflict, or interrupts. There may also be a problem with a driver or service.
0x80000003- The breakpoint was damaged and the system started with / NODEBUG
0x00000020: KERNEL_APC_PЕNDING_DURING_EXIT - Problem with APC counter. Check the file system. Also check the IRQL, it should be zero. Remember what you installed the last time. You may have installed a problematic or incorrect driver.
0x00000023: FAT_FILE_SYSTEM - FAT format failure on hard disk. Perhaps you have different formats of partitions on the disk, or the disk is already "crumbling".
0x00000024: NTFS_FILE_SYSTEM - Failed NTFS format on hard disk. It is also possible that you have different formats of partitions on the disk, or the disk is already "crumbling".
0x0000002A: INCONSISTENT_IRP - Failure in IRP (I / O Request Packet). This is possible, for example, when the IRP is turned off, at the moment when a command from the driver is expected.
0x0000002B: PANIC_STACK_SWITCH - Kernel stack full. The core may even be damaged.
0x0000002E: DATA_BUS_ERROR - The driver accessed the RAM at the address of which is not present.
0x00000032: PHASE1_INITIALIZATION_FAILED - The system was not initialized successfully. The error has two parameters: the first is the reason for the incomplete initialization, the second is the point where the INIT.C error occurred.
0x00000035: NO_MORE_IRP_STACK_LOCATIONS - When calling low-level or high-level driver, no free space stack. Possible stack or memory corruption. We need to check the drivers and memory.
0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO - If the driver is trying to remove its device and the hit counter has not yet been cleared.
0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED - The system is not symmetrical, due to the fact that they are installed different types, parameters, or processor level.
0x0000003F: NO_MORE_SYSTEM_PTES - The swap file lacks access points. The driver does not clear its data and overflows the swap file, or the Swap partition is fragmented.
0x00000040: TARGET_MDL_TOO_SMALL - Insufficient size of MDL area. Driver problem.
0x00000041: MUST_SUCCEED_POOL_EMPTY - The function called by the driver associated with the Must Succeed Pool is not being executed.
0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS - The IRP has completed and the driver is trying to complete it again. There may be two drivers in the system.
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP - The package is frozen on cancellation, but it is no longer part of the driver.
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF - Error working with memory, IRQ interrupts disabled.
0x0000004C: FATAL_UNHANDLED_HARD_ERROR - Unknown error. And the reasons for the occurrence can be like 0x0000022A, 0xC0000218 or 0xC0000221.
0x0000004D: NO_PAGES_AVAILABLE - insufficient memory space. Try reinstalling the driver.
0x0000004E: PFN_LIST_CORRUPT - Driver I / O failure.
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA - The requested data was not found, or the paging file was not allowed to write.
0x00000051: REGISTRY_ERROR - A system or hardware failure caused the registry to fail to read. The Account Security library may be full.
0x00000058: FTDISK_INTERNAL_ERROR - Failure to boot the system from the restored array and the function reports a broken mirror, although it is with an error. You need to boot from shadow copies.
0x00000067: CONFIG_INITIALIZATION_FAILED Out of memory for the registry to work.
0x00000069: IO1_INITIALIZATION_FAILED - Failed to start the input or output device. The equipment is not correctly identified, or it is not correctly configured.
0x0000006B: PROCESS1_INITIALIZATION_FAILED - Processor startup error.
0x0000006D: SESSION1_INITIALIZATION_FAILED 0x0000006E - System startup error. Shows to NTOS \ INIT \ INIT.C where the error occurred.
0x00000073: CONFIG_LIST_FAILED - Corrupted registry. There may be insufficient free space on the system drive or RAM.
0x00000074: BAD_SYSTEM_CONFIG_INFO - Corrupted SYSTEM registry key. Some keys or registry settings might be missing. You will most likely need to rearrange the system.
0x00000075: CANNOT_WRITE_CONFIGURATION - An error occurred writing to System. Possibly out of disk space.
0x00000076: PROCESS_HAS_LOCKED_PAGES - incomplete unloading of the driver.
0x00000077: KERNEL_STACK_INPAGE_ERROR - Virtual memory block failure or disk controller error.
c0000009a- there are not enough system resources.
c000009c, c000016al - damaged memory block.
c0000185- SCSI health failure
0x00000079: MISMATCHED_HAL - HAL does not match kernel or hardware. Possibly the problem is NTOSKRNL.EXE or HAL.DLL
0x0000007A: KERNEL_DATA_INPAGE_ERROR - Kernel read error. The memory may be defective.
0x0000007B: INACCESSIBLE_BOOT_DEVICE - Boot device failure. Perhaps there is no SCSI or disk support.
0x0000007D: INSTALL_MORE_MEMORY - memory failure. It lacks its size.
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - Driver or hardware failure. Out of disk space, or update the driver.
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP - The kernel does not start. The problem is in memory or with an overclocked processor.
0x00000080: NMI_HARDWARE_FAILURE - Hardware problem.
0x00000085: SETUP_FAILURE - Problem in the installer loader on the first Windows
0x0000008B: MBR_CHECKSUM_MISMATCH - MBR and bootloader checksums do not match. Boot from the LIVE-CD and check the disc for viruses.
0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA - Incompatible or corrupted memory.
0x0000008F: PP0_INITIALIZATION_FAILED - Hardware problem
0x00000090: PP1_INITIALIZATION_FAILED - Problem with one of the processors
0x00000093: INVALID_KERNEL_HANDLE - Descriptor problem
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT - Locked stack. Hardware driver problem.
0x00000096: INVALID_WORK_QUEUE_ITEM - Hardware driver problem
0x00000098: END_OF_NT_EVALUATION_PERIOD - Windows period has ended
0x00000099: INVALID_REGION_OR_SEGMENT - Error ExInitializeRegion, or ExInterlockedExtendRegion. Perhaps there is an error in the parameters.
0x0000009A: SYSTEM_LICENSE_VIOLATION - License agreement violation
0x0000009B: UDFS_FILE_SYSTEM - Error writing / reading UDFS
0x0000009C: MACHINE_CHECK_EXCEPTION - Problems with computer components. It can be a power supply, overclocking the processor, overheating.
0x0000009F: DRIVER_POWER_STATE_FAILURE - Power driver failed. Update your driver.
0x000000A5: ACPI_BIOS_ERROR - BIOS error.
0x000000B4: VIDEO_DRIVER_INIT_FAILURE - Video card driver error. Try reinstalling or updating the driver
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY - Problem with ROM write driver
0x000000C2: BAD_POOL_CALLER - Error accessing memory due to driver or program
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION - Error in the driver, in the STOP module
0x000000C5: DRIVER_CORRUPTED_EXPOOL - Access from invalid memory. Driver problem
0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL - Access to free POOL memory. The problem is in the driver
0x000000C7: TIMER_OR_DPC_INVALID - The driver did not complete unloading the kernel timer before unloading. You need to reinstall the driver
0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS - The driver cannot cancel hung Windows components. Possibly bad drivers or hardware.
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL - The swap file or RAM may be corrupted
0x000000D8: DRIVER_USED_EXCESSIVE_PTES - The device driver is not allocating memory correctly, the system is processing a lot of I / O, or the program is allocating too much memory in the address space. The driver needs to be replaced
0x000000E3: RESOURCE_NOT_OWNED - Failure file system
0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER - The driver caused the system to hang. Often the cause of the error is in the video card or its driver
0x000000F2: HARDWARE_INTERRUPT_STORM - Cannot set interrupt. The driver may need to be reinstalled
0x000000F3: DISORDERLY_SHUTDOWN - Unable to shutdown system due to insufficient memory. Define a program that "crawls" out of memory
0x000000FA: HTTP_DRIVER_CORRUPTED - http.sys failed - replace with a new one
0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY - an attempt to start a process in non-executable memory area
0x000000FD: DIRTY_NOWRITE_PAGES_CONGESTION - out of page memory
0x000000FE: BUGCODE_USB_DRIVER - error of the USB controller or devices connected to it
0x00000101: CLOCK_WATCHDOG_TIMEOUT - problem with one of the processors
0x00000104: AGP_INVALID_ACCESS - an attempt to write to the wrong section of memory by the video processor. Problem with driver or BIOS version (no support)
0x00000105: AGP_GART_CORRUPTION - driver problem direct access to memory by the video processor. Replace the driver
0x00000106: AGP_ILLEGALLY_REPROGRAMME - failure of the signature or the GPU driver itself
0x00000108: THIRD_PARTY_FILE_SYSTEM_FAILURE - crash caused by third-party programs. Increase memory or paging file. You can also uninstall the program
0x00000109: CRITICAL_STRUCTURE_CORRUPTION - data integrity failure, possibly a problem in third-party drivers, RAM
0x0000010E: VIDEO_MEMORY_MANAGEMENT_INTERNAL - problem in the video driver
0x0000010F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED - error in kernel mode
0x00000112: MSRPC_STATE_VIOLATION Failed to execute msrpc.sys
0x00000113: VIDEO_DXGKRNL_FATAL_ERROR - error in DirectX
0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR - crash in the shadow video driver
0x00000115: AGP_INTERNAL - crash in AGP driver
0x00000116: VIDEO_TDR_ERROR - error in resetting the video driver
0x0000011C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE - attempt to write to protected area
0x00000121: DRIVER_VIOLATION - failure to access memory area
0x00000122: WHEA_INTERNAL_ERROR - A problem with the hardware of the computer itself
0x00000127: PAGE_NOT_ZERO - A problem with the hardware of the computer itself
0x0000012B: FAULTY_HARDWARE_CORRUPTED_PAGE - error reading exFAT. The disk or file system may be damaged
0xC000009A: STATUS_INSUFFICIENT_RESOURCES - Windows has taken up all the resources of the computer and cannot continue. Check HDD and RAM
0xC0000135: UNABLE TO LOCATE DLL - problem with DLL library, registry may be corrupted
0xC0000142: DLL_INITIALIZATION_FAILURE - DLL library problem
0xC0000218: UNKNOWN_HARD_ERROR - unable to load the registry file. Check memory, hard drive and file itself
0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED - problem in user32.dll, sys system drivers
0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH - problem in drivers or system library
0xDEADDEAD: MANUALLY_INITIATED_CRASH1 - system crash caused by user

0xC000026C- problem with device drivers
80070005 access denied - Failed to update or Windows activation, is solved by the subinacl.exe utility which can be downloaded from the Microsoft website. Or, the permissions for the files where the Windows applications are stored are not correct.
80070490 - Error when Windows update... This means that the CBS Manifest, which is needed to install updates, is corrupted.
800b0001- One of the Update Centers cannot determine the CSP, or one of the Centers files is damaged.
800c0019- Date or time is not set correctly

An article about what types of system errors exist and how you can fix them without having to reinstall the system.

If we compare popular operating systems with people, then we can say something like the following. Mac OS is such a rich macho who has everything. Android is a trendy hipster teenager. Linux is a harsh bearded man from Chelyabinsk. And Windows is a beautiful but very capricious woman :)

Everybody knows firsthand about constant crashes and errors of Windows. Jokes and even songs are made about them! However, not everyone knows what to do with these errors. We will try to fill the knowledge gap with the help of today's article.

Types of errors

It is possible to characterize errors that may occur when working with Windows based on different approaches... However, one of the most important for the user, in my opinion, is the degree of criticality. That is, the degree of its importance, which is expressed on a scale from "a fig with her" to "everything - it's time to reinstall" :)

Many may argue that it is more important to characterize errors by reason of their occurrence. However, it happens that the same error can be caused by completely various breakdowns, ranging from a simple software failure and ending with the failure of one of the parts of the PC.

Considering that our classification can be quite extensive, I think it would be logical to divide it into several subgroups. The first will include errors, such as system messages, which are usually one of the most innocuous. Secondly, errors of the so-called " blue screen death. "And thirdly, errors at the bootloader level. With the necessary knowledge (which can be gleaned from the Internet by the error code) and a simple set of tools, in many cases it is really possible to prevent the reinstallation of the system while preserving its operability and all data!

System recovery tools

As one of the main characters of the movie "Spy Children" said: "The coolness of the agent in his gadgets!" In our case, various disks (or flash drives) with the necessary programs act as "lotions".

The arsenal of every more or less advanced user should have the following tools:

1. A disk with your operating system in case you reinstall or restore damaged files.
2. Disk with antivirus scanner. I recommend getting a DVD-RW or USB flash drive for this and updating it periodically. As the scanner itself, it is not bad, which is also a bootable disk.
3. Boot disk with Windows PE. Many errors are easiest to fix in virtual Windows environment, which can be obtained by writing the so-called "reanimator" to a disk or USB flash drive. One of the best in this business is the Alkid Live CD / DVD / USB assembly, which can be found and downloaded quite easily on the Internet.
4. Boot disks with partition management programs hard disk... Since the most valuable thing on a computer is our data, if it is impossible to restore the system, you need to at least save it by copying it from Disk C (on which Windows is usually installed) to Disk D or a USB flash drive. A boot disk (or program) works well for these operations. For creating and managing backups, I recommend the tool.
5. Disks with native drivers for motherboard and other PC hardware components. You can also use various collections of drivers with auto-installation (such as DriverPack Solution). However, you should work with them carefully and do not put everything that you are offered, so as not to disrupt the normal operation of well-functioning components.

Naturally, the above are mainly listed free tools(except Windows, of course). They may not be as convenient as the popular products from Acronis or Paragon, but they do their job nonetheless. Therefore, if there is no extra money to buy expensive system tools, and you don't really want to pirate, then they are quite suitable :).

So, having at your disposal all of the above, you can start trying to fix the arising system errors.

System messages

The first (and most common) form Windows errors- system notifications.

Visually, they are a small window with a picture in the form of a red cross on the left, information about the error, about the program in which this error occurred, and the "Ok" button (sometimes they also contain the "Cancel" or "Help" buttons). Let's look at one of the typical problems (in the screenshot above) when memory cannot be read (read) or written (written).

This error occurs quite often and serves as an indicator that the program or service (indicated in the window title) cannot work correctly with the RAM (read or write data). There may be several reasons for this error:

• incorrect operation of the program as a result of exposure to a virus or patch (a stone in the garden for fans of hacking games and software;));
• the presence of faulty blocks in RAM;
• overzealousness of PC protection systems;
• conflict of drivers or software;
• malfunctions in the computer's power supply system.

To find out the real reason, we use the principle of Occam's razor (by the way, the stress in the surname of the creator of the principle falls on the first letter "O") and discard all obviously inappropriate possible problems.

The first step is to answer the question whether the program worked for you before or whether it began to give an error immediately after installation. If it has never started normally, then most likely the reason is in the program itself. Either it is a hacked version of paid software, or it requires some system libraries and drivers for its work, or it is simply written for newer / older versions of Windows.

In the latter case, if you are running Windows 7 or 8 Ultimate (Professional), you can try to run the non-launching program in compatibility mode with Windows XP. To do this, call the properties executable file program, go to the "Compatibility" tab and run the "Compatibility troubleshooter" using the button of the same name, or select the manual emulation mode:

Antiviruses can also block programs. To eliminate this variant of the problem, try running the problematic program with the antivirus turned off. However, this can be done only when the antivirus does not swear at the program itself. Pre-scan the entire folder with it and only if no viruses are found, try this solution.

The last common option for an error to appear is incompatibility between programs and their components. If before that the application you need was working properly, but suddenly started giving errors, remember if you have installed any software or drivers recently. If installed, try uninstalling them and running the program again.

For correct deletion programs, it is better to use special uninstallers, which, after removal, scan the registry for residual "garbage" (there is one on our site that is suitable for this purpose). It is better to remove drivers using standard system tools.

If none of the methods helped to solve the problem, it may well be that the cause is a malfunction of the computer itself. Open up system unit immediately after turning off the system and gently touch the RAM bar. If it is very hot, then there is a short circuit.

Before you write off such a memory card, try removing it and reinserting it into the adjacent slot. Sometimes the normal contact of the memory stick with the connector is simply disrupted, which can lead to errors.

However, in addition to read / write errors, many other failures can occur in Windows. Most often, the text in such system messages will be in English, which can make it difficult to understand the reason for their appearance. But it is not all that bad. Usually, the text mentions an error code that looks like a number in hexadecimal notation (for example, as in the screenshot below - 0xc000007b). Using this code, you can find a solution to the problem on the Internet!

If the code is not given in the text (it also happens), you can try to find a solution by entering a fragment of the received message into the search engine. Often when you start typing search system She will tell you the continuation of the error text herself and offer you to look at the issue for it.

Blue screen of death errors

It's good if Windows starts up. We can search the Internet for a solution to the errors we receive, or simply ignore the system notifications using other working programs. However, it also happens that the system will not boot, producing a bunch of white text written over a blue background instead. This is the "blue screen of death".

Despite such an ominous name, this type of error does not mean the final crash of the system! Often with a blue screen Windows death you can still save by understanding what she wants from us :) And to do it, as in the case with system notifications, you can by looking at the error code, which is usually indicated after the word "STOP" at the very bottom of the error text. For this, by the way, this type of failure is also called "stop errors" (since they interrupt the normal loading of the OS).

There are quite a few blue screen of death codes, so it makes no sense to list them all in the article. If you want to get acquainted with one of the most complete lists of mistakes in Russian, you can visit the website mistakes.ru, where an entire article is devoted to them!

In addition to the error code itself, the blue screen of death may also display the name of the system module that caused the failure (usually indicated immediately below the stop code) and the type of problem (look at the top of the description). For example, let's analyze the message shown in the screenshot above.

At the top we see a separate line that says "DRIVER_IRQL_NOT_LESS_OR_EQUAL". This "incantation" indicates that the cause of the failure is in the driver, which did not share system interrupts (IRQL) with some other module. Below we see a whole chain of stop codes that arose as a result of a failure, and even lower - the name of the hero of the "celebration". It turns out to be the TCP / IP driver tcpip.sys.

You can solve this problem by reinstalling the driver for the network card of your PC. In general, the algorithm of actions for BSOD should be something like this:

1. The first step is to try rebooting. If access to Windows appears, then there may be a temporary random crash. At the same time, no additional actions are required on our part.
2. If a blue screen appears, then no, most likely we are dealing with the unstable operation of some driver or other system component. The solution is to roll back the driver to more old version(if errors began to appear after the update), or, conversely, installing a more recent version of the driver.
3. If a blue screen appears every time the system is restarted, there is a permanent malfunction. In this case, the boot disks will come in handy, with the help of which you can restore many system components. Read on the Internet descriptions of your particular failure by code or error description and proceed according to the instructions for restoring the system after the problem you have encountered.

In the latter case, in my practice, I often encounter errors related to the failure of the file system. This type of error can be solved quite simply. Loading with boot disk with Windows PE (for example, Alkid LiveCD), run command line(Start - Run - CMD command) and there we enter the command "chkdsk C: / f" without quotes. This command will scan the file system of the C drive for errors and, thanks to the "/ f" flag, will automatically fix them!

Naturally, checking the file system is not a panacea for all system failures, but it often helps to fix them. Therefore, if you encounter an unknown type of error, try scanning the system disk. It definitely won't hurt, but it might help :)

Errors before the system starts booting

The last and most severe type of Windows errors are errors that appear not on the blue screen of death, but on the black one. Such errors usually signal a serious system failure and are not always amenable to correction. However, there are exceptions here too :)

The most "funny" variant of "error" can be an inscription containing the phrase "Press Any Key":

In fact, this is not an error at all, but simply the computer's offer to confirm the boot by pressing any key. However, this can confuse a person who is unaware of the possibility of such messages appearing.

However, not everything is so simple. Quite often it happens that Windows does not boot due to corrupted system files... The files hal.dll, ntldr and / or ntdetect.com most often suffer, about which we receive a message like this:

This kind of error can be solved, but it will require us to either have backup system, made in advance, or the disk from which your Windows was installed, or dancing with a tambourine :). There are many ways to recover corrupted system files on the Internet, so proceed based on which one is listed in the error message.

Alas, it is impossible to give any universal advice on such failures, but I will say that a certain number of them can be solved, as well as errors of the blue screen of death, by fixing the file system with the CHKDSK command! At least don't neglect it;)

conclusions

As we could see, there can be quite a few reasons for errors in Windows, but all of them are somehow related to the following problems:

• the consequences of a virus attack;
• crashes of programs and drivers;
• failures in the hardware of the computer.

These three root causes are at the root of absolutely all the troubles in your system. However, their external manifestations can be so varied that it can be difficult even for a technically savvy person to pinpoint exactly what is wrong! That's why, The best way figuring out what's what is a banal exception. If initially you do not have any suspicions about the cause of the error, try first to check the system for viruses, then check what you installed recently, and if nothing, then look towards hardware faults.

And, of course, do not forget to consult with Google :) Over the long existence of computers in general and Windows in particular, other people have probably had problems like yours more than once. All you need to do is find a description of their solution and successfully apply it in practice.

P.S. It is allowed to freely copy and quote this article, provided that an open active link to the source is indicated and the authorship of Ruslan Tertyshny is preserved.

Nothing is perfect, and this famous saying fully applies to software products... Even the most reliable and proven program can fail due to internal or external errors. This also applies to the Windows operating system, which is installed on the computers of the vast majority of users.

In this chapter, we will analyze the main errors and malfunctions specific to Windows 7, as well as possible reasons their occurrence.

Many novice users who have had an operating system crash ask their more advanced computer acquaintances: why did my computer freeze (does not boot, the screen went out, works slowly, etc.)? At the same time, they do not even suspect that there can be a huge number of reasons for the failure: viruses, hardware problems, software incompatibility, excessive resource utilization, etc. Let's analyze some of them.

Windows 7 operating system does not load

Each windows user sooner or later comes across the fact that the system refuses to boot. Let's consider how you can try to "revive" the system.

At the very beginning of the computer boot, you should call the menu to select the boot mode of the operating system. Sometimes this simple method allows, if not completely restore Windows to work, then at least force it to boot, which, in turn, will save the data by rewriting it to external media. After saving and writing down the information, you can reinstall Windows, format the disk, or take other steps to restore your computer to work.

To call the menu for selecting Windows boot modes, you need to turn on the computer, press the F8 key and hold it until the corresponding menu appears.

If you want to try to "reanimate" the system and you know how to do it, choose one of the three safe modes(in most cases, the most optimal first of them).

Why Windows 7 computer freezes

One of the most frustrating situations is that operating system hangs, that is, does not respond to user actions and calls (mouse clicks and keyboard button presses remain unanswered, moreover, sometimes the mouse pointer itself disappears). In other words, the computer does not show signs of life (the screen displays only a frozen image corresponding to the last session of work). In this case, we mean the freezing of the system, and not of any separate application.

The system freezes can be caused by both software and hardware problems. Hardware issues were discussed in the chapter