· Ensure the Drivers and Firmware on the controller are up-to-date. If the error repeats with lastest Drivers/FW then consider opening a call with hardware support, or replace the controller. HTH, edwin. Proposed as answer byEdwin vMierloSaturday, . Harassment is any behavior intended to disturb or upset a person or group of people. Threats include any threat of suicide, violence, or harm to another. · The PIO Only Transfer mode for IDE ATA/ATAPI Controller (Primary IDE channel) as suggested in Microsoft technote seemed to fix the issue with "The driver detected a controller error on \Device\Harddisk0\D" and "A parity error was detected on \Device\Ide\IdePort0" errors in the System Event Log. However, it is not conclusive because I have used the PC in this mode only for one day.
Harassment is any behavior intended to disturb or upset a person or group of people. Threats include any threat of suicide, violence, or harm to another. So the disk numbers shown in the Disk Management console (Disk 1, Disk 2, Disk 3, etc) correspond to the \Device\Harddisk# in those Event Log errors. For instance, in the following error, the matching disk to look for in Disk Management is "Disk 5". The driver detected a controller error on \Device\Harddisk5\DR6. Edited May 8, at UTC. Please restart your computer when encountering the driver detected a controller error. Then, open the event log to check the error messages. If you see The driver detected a controller error on \Device\Harddisk2\DR2, it means there’s a serious disk defect in the RAID systems on some servers. However, the RAID utility can’t detect the error until the disk is failed completely.
Error: The driver detected a controller error on \device\harddisk0\DR0. In SQL log: The operating system returned error (the request. 13 de mai. de Help identifying source of repeated "The driver detected a controller error on \Device\Harddisk#\DR#" error. We have a clustered HV Log Name: System Source: LSI_SAS Date: 12/10/ PM Event ID: 11 Description: The driver detected a controller error on.
0コメント