When the computer is shut down, "Shutdown in progress" is displayed for a long time, and a blue screen appears for about 15 minutes. The error is DRIVER_POWER_STATE_FAILURE

During the use of computers, blue screens are often encountered. For beginners, it seems like a computer disaster and they are at a loss. In fact, as long as you understand the reason, you don’t need to be afraid. There are many reasons for computer blue screen. The hardware reasons can be summarized as follows:

Fault problems of WIN9X, Me and other versions below NT4.0

1. Screen It shows that the system is busy, please press any key to continue...

1. Insufficient virtual memory causes system multi-tasking errors

Virtual memory is a unique method of Windows system to solve the problem of insufficient system resources. This method generally requires that the remaining space of the hard disk in the main boot area is 2-3 times its physical memory. In order to make full use of the space, some enthusiasts fill their hard drives to capacity and keep in mind the demanding requirements of WINDOWS. As a result, the virtual memory has an operation error due to insufficient hard disk space, so a blue screen appears. To solve this problem is very simple, try not to fill up the hard disk, and frequently delete some temporary files and swap files generated by the system to free up space. Or you can manually configure the virtual memory, select Advanced, and transfer the default address of the virtual memory to another logical disk. This avoids blue screens caused by insufficient virtual memory.

2. CPU overclocking leads to calculation errors

Overclocking is a common thing for enthusiasts, so various failures caused by overclocking are inevitable. Overclocking itself is to achieve higher performance on the original basis, but due to overloading operations, too many internal operations are caused, causing the CPU to overheat, resulting in system operation errors. Some CPUs have better overclocking performance, such as INTEL's Celeron processor and AMD-K6-2 processor, which are relatively good, but sometimes some inexplicable errors may occur. (For example: I once tried to overclock the INTEL Celeron 300A to 450, and the floppy drive read the disk without accepting the command). The overclocking capabilities of INTEL's sub-200 CPUs and AMD-K5 are not that good. It is recommended that when a high-end CPU is overclocked, the heat dissipation work must be done well. It is best to install a large fan and some heat dissipation materials such as silica gel. As for some low-end CPUs, I suggest you not to overclock, otherwise the overclocking will not achieve the expected effect but will often cause blue screens and affect the normal speed of the computer.

2. Computational errors caused by mutual incompatibility or damage of memory modules

This is the most intuitive phenomenon, because this phenomenon can often be seen when the computer is turned on. The computer cannot be started, and the screen prompts that there is a problem with the memory, asking you if you want to continue. This error is caused by physical damage to the memory or incompatibility between the memory and other hardware. At this time, the only option is to replace another memory.

3. The optical drive is opened abnormally when reading a disk.

This phenomenon is caused by a blue screen being opened due to a mistaken operation when the optical drive is reading data. This problem does not affect the normal operation of the system, just eject the CD or press the ESC key.

The above are several reasons that caused the blue screen that I encountered during computer maintenance. There may be other inexplicable problems that cause the computer to have a blue screen. In any case, when encountering this kind of problem, you should carefully analyze the cause of the problem before starting to solve it.

4. The remaining space of the hardware is too small or there are too many fragments

Since Win9X needs to use the hard disk as virtual memory when running, this requires that the hard disk must retain a certain amount of free space to ensure the program's performance. normal operation. Generally speaking, the minimum space should be more than 100MB. Otherwise, the "blue screen" may be related to the remaining space of the hard disk being too small. In addition, too many hard disk fragments can easily lead to the appearance of a "blue screen". Therefore, defragmentation every once in a while is necessary.

5. System hardware conflict

This phenomenon leads to "blue screen" which is also common. What is often encountered in practice is the setting conflict of the sound card or display card.

Check whether there is a device with a yellow question mark or exclamation mark in "Control Panel" → "System" → "Device Management". If it exists, try to delete it first and restart the computer. Win9X will automatically adjust it, which can generally solve the problem. question. If it still doesn't work, you can manually adjust or upgrade the corresponding driver.

　　　　　 XP Blue Screen Solution Tips

Although the stability of the Windows 2000/XP system based on the NT architecture has been greatly enhanced, and even Windows XP is known as "never crashes", we still see it from time to time. When you see a blue alert message, this is commonly known as a "blue screen". What exactly is going on?

1. The reason for the blue alert in Windows 2000/XP

Windows 2000/XP adopts a layered structure. Its two layers are also called modes, which are user mode ( User Mode) and Kernel Mode (Kernel Mode), applications cannot directly access hardware devices, and can only access them directly with the help of drivers.

However, no matter how stable the NT architecture is, there will be problems due to certain reasons, such as hardware conflicts, hardware problems, registry errors, insufficient virtual memory, dynamic link library file loss, resource exhaustion, etc. Sometimes it may cause errors in drivers or applications, and in severe cases it may even affect the kernel layer. In this case, Windows will stop the system and start a function called KeBugCheck. By checking all interrupted processing processes and comparing them with the preset stop codes and parameters, the screen will turn blue and display the corresponding Error messages and fault prompts are often called "Blue Screen of Death" (BSOD), also known as "STOP message" or "Stop message", because this phenomenon actually means a crash.

2. Understand the information hidden in the blue alert

There is a big difference between the BSOD window of Windows 2000/XP and the BOSD window before Windows NT4. The biggest difference is that of NT The BSOD window only includes a general stop message code, but the BSOD of Windows 2000/XP includes two types of stop messages and hardware messages. The former is an error message generated when an unrecoverable software error is found, and the latter is when a serious software error is found. Error message generated when there is a hardware error.

Although the information in the error window looks complicated, it generally consists of the following three parts:

1. Error message

The content between "*** Stop:" and "****** wdmaud.sys" is the so-called error message, which consists of error code, custom parameters, error Symbols and other three parts, the meaning of each part is as follows:

Error code: the hexadecimal number after STOP;

Custom parameters: the composition of error code characters, determined by the programmer Definition, it is difficult for ordinary users to understand;

Error symbol: KMODE_EXCEPTION_NOT_HANDLED

After the error symbol, a memory location and file name are also displayed here, so that you can understand the memory when the error occurs location and source files. For us, the most useful thing is actually the previous error code information, which will be used when searching the Microsoft Knowledge Base

2. Recommended actions

Here are the actions and steps recommended by the system for users to take, such as uninstalling programs in safe mode, rolling back drivers, updating BIOS, installing patches, etc. However, in most cases, they need to be reinstalled. No further operations can be considered until the system is started.

3. Debug port information

Here will display information on how to set up the kernel debugger, including whether the memory dump image has been written to disk and what port to use to complete this debugging.

In fact, according to the author's experience, except for the error code in the blue alert, which is more useful, most of the other information in the blue alert has little practical significance for ordinary users and is for reference only.

For the purpose of debugging the system, after a BSOP error occurs in the Windows system, KeBugCheck will automatically generate a debugging file named Memory.dmp. This file is located in the C:WindowsMinidump folder. Under the default settings, The size of the file is consistent with the system's physical memory capacity. We can compress the file and send it to Microsoft's technical support department to obtain the corresponding solution, but the capacity of the file is so huge that how to send it is a big problem, so Very few users actually do this.

Tip: Open the "System Properties → Advanced → Startup and Recovery" window, where you can see the generation method of "Write debugging information": small memory dump, core memory dump, full memory Dump, None. Based on the above analysis, it is recommended to select "None" here.

3. Dealing with the Blue Alert Trilogy

Although the information displayed in the Blue Alert window of Windows 2000/XP may be different, it may be due to hardware reasons or drivers. Issues with system compatibility, or simply some bugs in the application. Of course, the first thing to do is to eliminate the cause of the virus, and then we can handle it according to the following steps:

Step 1: Restart the system

When a blue alert window appears, the first thing we should consider is Restart the system. In most cases, the problem can be solved after restarting the system. However, generally at this time, it is no longer possible to hot-start through "Ctrl+Alt+Del", but can only be cold-started by pressing the reset button, or simply turning off the power and restarting.

When entering the system, enter the event viewer interface from "Control Panel→Administrative Tools→Event Viewer", or type the "eventvwr.msc" command in the "Start→Run" box, where according to the date and time focus on checking events in "System" and "Application" with the type flag "Error", such as errors reporting a service startup failure.

Step 2: Restore to the last correct configuration

The blue alert in Windows 2000/XP does not come for no reason, and the NT-based operating system will not issue it randomly. Temper temper is usually caused by updating device drivers or installing certain software. Sometimes it is even caused by users optimizing the system or deleting some important system files. At this time, you can restart the system and quickly press F8 key and select "Last Known Good Configuration". This will restore the valid registry information of the HKEY_LOCAL_MACHINESystemCurrentControlSet item in the registry, but it will not solve errors caused by driver or file corruption.

Alternatively, you can also try pressing the F8 key to choose to boot into safe mode. If you can enter safe mode normally, it may be a problem with the driver or system service.

Step 3: Query the error code

Write down the English information in the window, especially the error code "0x0000001E", and then access it from another computer; 314062 View Hardware Compatibility List (HCL), and then you can consider re-plugging and unplugging the memory, graphics card, and network card, or trying to replace them one by one using the replacement method. The more common ones are memory problems or power supply problems. If this method does not work, I am afraid you can only consider Reinstall the system or format the hard drive.

Attached:

Code prompts when a blue screen appears on the computer!

Your error is the following error number 0030: The system cannot read the specified device. It is very likely that one of your processes illegally writes memory.

Or there is simply a problem with the memory. Check if it works in safe mode. If it works, then it's a problem with a certain process.

0000 The operation completed successfully.

0001 Bad function.

0002 The system cannot find the specified file.

0003 The system cannot find the specified path.

0004 The system cannot open the file.

0005 Access denied.

0006 The handle is invalid.

0007 The storage area control block is damaged.

0008 Insufficient storage area is available to execute the command.

0009 The storage area control block address is invalid.

0010 Environment error.