"The device can't start code 10" How to solve the network card failure

“Selected cylinder exceeds maximum supported by BIOS”

Translated into Chinese means: The number of selected cylinders exceeds the maximum supported by the BIOS. Is my disk broken? The cursor has been stopped here, the XP system can't get in, and it's the same as the Ubuntu system (I installed XP and Ubuntu dual systems). Intuitively, when you encounter such a problem, the first thing is to restart.

……

Restarted N times, still like this. . . After shutting down. . . Restart again, no!

Then look at the disk, unpack, re-plug the hard drive data cable. Sure enough, this time started normally. Maybe the data cable is loose. . .

However, the situation is far more than that simple.

After entering the system, the blue screen has been repeated many times, depressed. Then “local connection” is missing! Go to “Device Manager Check the network card, the expected yellow exclamation mark appears, check the properties----the device can't start. Code 10.

Encounter such a problem, intuition, uninstall the network card, and then reinstall, update the driver. . . The yellow exclamation mark is still there to demonstrate! !

Google. . . Baidu. . . Execution of all the methods that can be searched, the yellow exclamation mark is still there to demonstrate!

It’s really depressed, it’s so sudden, I don’t even give it a snack. Simply shut down, leaving. . .

Of course, people still have to come back, the problem still has to face. It is impossible not to go online from now!

Entering the cute Ubuntu, you can't detect the network card. It’s weird! It stands to reason that if it is the NIC driver problem of XP system, it will not affect the Ubuntu system. It can be concluded that there is a problem with the NIC hardware. However, the network card is generally not so easy to break, and it was still good yesterday. Is it a hardware conflict? It has been added a note recently. Hold the attitude of trying, wash your hands (release static electricity!), open the case, unplug all the strips (hehe, the strips are quite a lot, there are three) and re-plug, short the two poles of the BIOS battery, so that the BIOS is set to &ldquo Factory setting ”.

Power on, prompt B IOS error, press Del to reset it, and enter XP system normally. Haha, discover new hardware! ! ! Dear & ldquo;Local Connections & rdquo; Come back! ! !

Summary of the problem:

(1) encountered disk problems, may be caused by loose disk data cable (SATA data interface is very small, it is easy to loose, must be fixed) .

(2) If there is a problem with the hardware, first uninstall the driver and reload it. If it doesn't work, uninstall the hardware, then reinstall the hardware in the “Add Hardware” wizard and reinstall the driver. If it doesn't work, it may be a BIOS setup problem. The solution is to short the BIOS jumper. If there is no jumper, remove the battery and short the contact point of the battery positive and negative boards in the motherboard. If it is a new hardware installed recently, there may be a hardware conflict. If the above methods are not working, you should remove the newly installed hardware and try again.

Phenomenon: After the ThinkPad T61 notebook turns off the power outlet switch (the system enters the standby state) and then turns it on, “local connection” is disconnected, and after rebooting, “local connection” disappears in the device. In the manager, there is a yellow exclamation mark in front of the network card. When it is disabled and then enabled, it cannot be enabled. The prompt “ld”; the device cannot be started. (Code 10) & rdquo;. Uninstall and reinstall the NIC driver that comes with the system, it is invalid; download the latest version of the NIC from the ThinkPad official website, invalid

Reason: Unknown

Search to the registry before installation " Local Connect & rdquo; (without the quotation marks), delete the related items found, such as: {09ED733F- 9951-4567-88C9-8EB24973B707}, etc. (the characters in this item may be different). The purpose of the deletion is to not appear such as "local connection 2" or "local connection 3" or "local connection 4", etc.

The hidden network card here does not mean true hiding. The problem is this happening. Sometimes after a network card is set once, the second time you need to change the settings, it always prompts that the network card is occupied. Then we delete the network card and reinstall it. After installation, we find that every time the local connection is added, it will increase by 1. For example, if it is a local connection, you will change to re-install once and become local connection 2, and then change to local connection 3. The virtual, non-existent NIC connection in front is the hidden NIC. In fact, it is just the information recorded in the registry. At this time, the memory IP can be deleted by searching the registry, and the corresponding local connection information is also deleted, and the local connection is finally restored.

Widows2000 can be removed by adding hidden devices inside the hardware. Because Windows
2003 &Windows
XP does not need to be installed to install new hardware devices, so when there is hardware update, the original hardware information of the system will still exist, we must modify the registration The table manually clears the hardware information.

Method:

To delete a hidden network card in the system, we run regedit to open the registry editor and find

HKEY_LOCAL_MCHINE\\SYSTEM \\CurrentControlSet\\Control\\Network\\{4D36E972 -E325-11CE- BFC1-08002BE10318}”Key value. Information about the local connection is saved under this subkey. There are one or more subkeys, where the first subkey corresponds to “local connection", the second subkey corresponds to “local connection 2” and so on, we can also expand the subkey, and then Select the “Connection” subkey below, and you will see which connection corresponds to the corresponding window in the right window, and delete the entire subkey corresponding to the previous old connection. After modifying the registry, you can set the network card correctly by restarting the computer.