Classpnp. sys (with: blue screen when installing the system; 0x0000007b) is a headache in win7 ).

Preface:

1.

From today to the organization, open the notebook and find that the program reports an appcrash error after startup.

So restart and use safe mode to enter.
On classpnp. sys,

Then the program will no longer go down.

Security mode cannot access the system. I encountered it for the first time !! Windows 7.

Bytes -----------------------------------------------------------------------------------------------------------

2.

So, reinstall the system ~

If you use an XP installation disk, you cannot install it. (Blue screen)

 

Error code: 0xc000007b

The system can be reinstalled with a blue screen, and I have a long experience!

Bytes --------------------------------------------------------------------------------------------------------------------

Solution:

1. classpnp. sys can only redo the system.

2. For 0x0000007b, the operating system is not compatible with the machine hardware (first time I heard about it !?).

Cause (Source: Baidu Road)

This code is related to the hard disk, but you don't have to worry about it. It's not a bad track,

It is a hard disk boot partition error caused by a setup problem or a virus.

If this problem occurs when you use the original system disk to install the system,

It means that your machine configuration is still relatively new, as an old system disk,

If you do not recognize such a new hard disk interface, you must enter the BIOS to change the hard disk mode to the IDE compatibility mode. When

Now, people use ghostos,

This problem does not exist when comparing new ghost disks. Regarding the issue that people cannot find the IDE,

Because many boards indicate that the wording is not the same

Some write ahci and compatibility, and the ahci is equal to the SATA mode,

Compatibility is equivalent to the IDE mode.

If your operating system has been in use for a while and suddenly this problem occurs one day,
Sorry, the virus is caused. Press F8 at startup and select the last correct configuration,
If the normal mode is not restored, try again. [Baidu Knows ctangel]

Bytes ----------------------------------------------------------------------------------------------------------------------------

Source: http://zhidao.baidu.com/question/212010623.html? An = 0 & Si = 1

More extensions:

The following content is Baidu's personal summary of ctangel, which is not about network replication. It is all about why I encountered in my daily work and clearly identified. If you need to copy the file, specify the source.
Here are several typical causes and solutions for blue screen failures.
1. 0x0000000a
This blue screen code has nothing to do with hardware, and is caused by a conflict between the driver and the software, this code was first found because of conflicts between the USB keyboard of the company's Dell machine and the qq2007 keyboard encryption program. Driver errors have also occurred in ibm t series laptops.
If your machine has a blue screen and this code is used every time, consider whether the software or driver has been updated recently. uninstall it and check again. In general, it can be solved. If you can't remember it very often, you can't do it again.
Ii. 0x0000007b
This code is related to the hard disk, but you don't have to worry about it. It's not a bad track. It's a hard disk boot partition error caused by a setup problem or a virus.
If this problem occurs when you use the original system disk to install the system, it means that your machine configuration is still relatively new. As an old system disk, you do not recognize this new hard disk interface, therefore, you must change the hard disk mode to the IDE compatibility mode in BIOS. Of course, people now use the ghostversion of the operating system, the newer ghost disk does not have this problem.
If your operating system has been in use for a while and suddenly this problem occurs one day, I'm sorry, the virus caused it. Press F8 at startup and select the last correct configuration, if the normal mode is not restored, try again.
Iii. 0x000000ed
This fault is related to the hard disk. The probability of a system failure is relatively high, and the probability of a hard disk failure is relatively small. I have no more than 20 blue-screen machines with this code, and only one of them has a bad track on the hard disk. The rest are problems that have been rolled out and fixed. This is also one of the few blue screen codes that can be fixed.
The solution is to find the original system installation disk (or use the console to fix it on the PE startup interface of golden finger V6 ). Here we will use the system disk method to put the system disk into the optical drive, start to the installation interface, and choose to press R to enter the console for repair. after entering the console, the prompt C: \ enter chkdsk-r here, and then it will automatically detect and fix the problem. After the fix is complete, restart the computer to enter the system. After entering the system, it is best to take the virus first, restart and try again. If it is normal, it will be okay. If the code is still available, it indicates that the hard disk is faulty and needs to be changed, or separate the problematic areas into hidden partitions and use the following space to install the system.
Iv. 0x0000007e and 0x0000008e
These two codes are mostly caused by viruses. They can be used as viruses. If you cannot enter the normal mode, press F8 to enter the safe mode. Of course, it may also be caused by memory. You can try to re-plug the memory. Generally, this code has a low probability of memory corruption.
V. 0x00000050
Hardware faults are highly probable for hard disks. If this code is generated every time, first try another hard disk to check whether the machine can be started normally. If the hard disk test is OK, try again memory, and if the memory is also tested, change the CPU, in short, this must be a hardware fault.
6. coooo21a
The fault at the beginning of C is very evil and unknown hardware fault is reported. However, the code at the beginning of C is mostly irrelevant to hardware. Basically, some drivers started with the system at the same time! Or a service problem. For example, once I changed the f disk Of a notebook to an E disk, the code starting with C is displayed after I start it. Finally, I found that I can start it normally by inserting a USB flash disk, because I inserted the USB flash drive into the system, I found that the hidden file was written by the system at startup. I unplugged the USB flash drive, and the problem occurred again. Then I changed the e-drive back to the F-drive. I thought it would be necessary to leave the software started with the system to some files on the F-drive, if you do not have a blue screen, you can create it by yourself. If you do not have a drive, you can only report an error.
7. The code for each blue screen is different
This problem is basically caused by hardware, especially the memory is the first object to be suspected, and the attempt to replace the memory is the second possibility that the CPU is not bad, however, from to now, I have met both of them. Other hardware will basically not cause random changes to the blue screen code.
8. Occasional blue screen and code restarting
There are two possibilities.
1. Take XP as an example. Right-click on my computer and select Properties, find the Advanced tab, find the startup and troubleshooting items below, and click Settings. In the pop-up window, there are three options in the middle 'System failed'. The third option is automatically restarted, and this option is checked and then the blue screen stops when a problem occurs.
2. I have already done the above settings, but it will still flash and restart, that is, the graphics card or CPU is overheated. Open the chassis and check the cooling fan and radiator status.
In addition, when the screen is turned on, the code will not flash and restart itself. At this time, it is no longer possible to set the first step in the system. Press F8 when the machine is started, and select disable restart after startup failure. After selection, the startup fails, the system will stop at the blue screen code so that you can view the problem according to the blue screen code.
9. Other blue screen Codes
Refer to the seventh item. Generally, first check whether the system is a system problem, and then test the hardware in the following order. First, check whether the memory is the most likely, then the CPU, the hard disk, and the video card, the motherboard basically does not have a blue screen.


--------------------------------------------------------------------------------

Postscript:

After the system is reinstalled today, the checkpoint (an encryption program) is installed again. After the system is reinstalled, The classpnp problem occurs again,

Call the technical department again and tell me that the driver of the program is not safe.

Comments:

Classpnp. sys

Windows 7, you are too tough!

Classpnp. sys