· Windows Event viewer says errors are occurring on \Device\Harddisk2\DR76 and \Device\Harddisk3\DR So, at least in this case, the disk number in the logs (Harddisk2 and Harddisk3) and the disk number in Disk Management (0 and1) have nothing to do with each other. · from the error message 'device/Harddisc2/DR2' the Harddisc2 corresponds to DISK2 attached to your computer/server however, DR2 in the error message, i think it corresponds to the desk sector number 2 or partition number 2. · Error is: Log Name: System. Source: Disk. Date: Event ID: Task Category: None. Level: Error. Keywords: Classic. User: N/A. Computer: Name. Description: The driver detected a controller error on \Device\Harddisk2\DR7. Event Xml.
In recent years the error “The driver detected a controller error on \Device\Harddisk2\DR2” is covering up a severe disk defect within RAID systems on some servers. It’s quite peculiar because the RAID utility that ships with the RAID controller fails to realize a disk is bad until the disk generally fails completely. Every time you connect a new storage device Windows will install a driver for it. This 'driver' essentially identifies the unique device and tells the controller how to communicate with it. If the device does not behave exactly as the controller expects, or vice versa, then it gets chalked up as an error. Vista Ultimate is reporting in the Event Log that the driver has detected a controller error on \Device\Harddisk2\DR2. Disk 0 is a WDBEKT formated into 2 partitions C: D: Disk 1 is a WDBEVS formated into 1 partition E.
22 черв. р. logged: “The driver detected a controller error on \Device\Harddisk2\DR2. log errors and figured I'd try to get to the bottom of it. 6 січ. р. "The driver detected a controller error on \Device\Harddisk0\D." All this with eventID: Everything works fine; checkdisk does not find. 22 серп. р. then i found with clean install, the laptop will go bsod continuously The driver detected a controller error on \Device\Harddisk2\DR2.
0コメント