The driver detects a controller error on/device/harddisk0/d.

During the past few days when the project is to be completed, the implementation of the system suddenly becomes unstable, and the inexplicable problem arises one by one. It has been running stably until now .....

 

Therefore, the cause of troubleshooting in one place and one place should first check whether there are any vulnerabilities in the code, and add a series of operations such as conditional judgment and log addition. However, there is still a frequent phenomenon of network latency, and the on-site PC running program is particularly slow, and the CPU often jumps to 100. It takes about 15-20 minutes to restart the PC. The self-check before the start takes more than 40 times, and the fault persists after the restart.

 

I suddenly thought of looking at the system log and found the problem. In the system log, I recorded a large number of "drivers detected controller errors on/device/harddisk0/D". error Log of "parity error detected on/device/IDE/ideport0. The original system was slow because of the hard disk.

 

Find the cause and search for the solution on Google as follows:

Fault symptom:

The Event Viewer displays the following information:
1. The driver detects a controller error on/device/harddisk0/d.
2. the parity error is detected on/device/IDE/ideport0.
"The Driver detected a controller error on/device ." There are roughly the following reasons:
Solution: Check whether the data cable or power cord has poor contact with the disk first, and then use the disk repair software to detect and fix the problem or try to update the driver or return the driver.

Perform the following checks in sequence:
1. Make sure that you have used an 80-core hard disk cable. Make sure that the hard disk data cable is in normal contact;
2. The data cable or power cord connecting to the disk is loose, leading to poor contact. (Unplug and re-plug the data cable or power cord)
3. The disk itself has hardware problems, such as bad channels. (Use disk repair software to detect and repair)
4. The disk driver is incorrect or the driver of the IDE controller is faulty. Make sure that the driver of the motherboard has been correctly installed (you can try to update the driver or return the driver)
5. Whether the DMA mode is disabled by the system. Check the ide ata/atapi controller in the Device Manager and double-click "primary ide channel" and "secondary ide channel" to check whether the current transmission mode has changed to Pio mode in advanced settings?

If yes, follow these steps:
1. Click Device Manager ";
. Expand the "Ide ATA/atapi controller" node;
Double-click the Controller for which you want to restore the typical DMA transfer mode;
Click the drivers tab;
Click Uninstall ".
2. After this process is completed, restart your computer. After windows restarts, the hard disk controller is reenumerated and the transfer mode of each device connected to the Controller is reset to the default value.
However, this only resets the transmission mode of the hard disk device to the default value. When the system is suspended, the system will disable the DMA mode on its own! Therefore, we need to do the following:
A. Click Start, click Run, type regedit, and click OK ".
B. Locate and click the following items in the registry:
HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/class/{4d36e96a-e325-11ce-bfc1-08002be10318}/0001 and
HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/class/{4d36e96a-e325-11ce-bfc1-08002be10318}/0002
C. On the "edit" menu, point to "new" and click "DWORD Value ".
D. Type reseterrorcountersonsuccess and press Enter.
E. on the "edit" menu, click "modify ".
F. Type L and click OK ".
G. Follow these steps to exit the Registry Editor:
Note:
The subkeys listed in the last entry "" in the Registry above with the "0001" number correspond to the Primary and Secondary ide channels of a computer with only one ide controller. If your computer has two ide controllers, the numbered sub-items of the primary ide channel and secondary ide channel for each controller are: "0001, 0002, 0003, 0004, 0005, 0006 ......".
To check whether the correct subitem is found, check whether the driverdesc value of the subitem contains the string value "Main ide channel" or the string value "secondary ide channel ".

 

As a result, we processed the problem according to the above method, shut down the system, and re-plugged the hard disk, and restarted the problem. "When the total number of times of time-out errors or CRC errors occurring during hard disk read/write accumulation reaches 6 times, the IDE/atapi port driver (atapi. sys) will reduce the transmission mode.
"

 

I learned about the DMA transfer mode and PIO transfer mode through this question.

DMA mode: http://baike.baidu.com/view/196502.htm

Pio mode: http://baike.baidu.com/view/196507.htm

 

It is said that if Windows XP encounters multiple access errors (for example, it fails to shut down normally after a crash), it will automatically downgrade the hard disk to a lower speed DMA mode or a slower Pio mode.