Disk - the driver has detected a controller or cable error

 · Hi, we have found out that disk is overloaded in specific periods of time. The latency is higher than 25 ms and this causes the issue. It is a big surprise forme, becuse the VM runs on the fastest possible storage we have. The snapshot creation has failed due to a hardware issue or a conflict with your disk hardware. Windows has reported the following error: 'The driver detected a controller error on Device '. Show. Example of full error log: click to expand. Error code: Explanation This problem is typically caused by a failing cable that connects the drive to the computer. User Action Replace the cable. Please check your even viewer and see if you have this error message. I recently purchased another Inspiron (with warranty) from eBay and it too has a similar www.doorway.ruted Reading Time: 1 min.

3) If errors and bad blocks remain after fixing the disk with Check Disk or hardware manufacturer's tools, consider replacing the faulty hardware.. If the disk shows no errors but the issue persist, please create a system report (see Acronis Cyber Backup Cloud: Collecting System Report, Acronis Cyber Backup and Collecting System Information) of the affected machine and contact Acronis. Here’s a quick guide on running the CHKDSK scan: Open up a Run dialog box by pressing Windows key + R. Next, type ‘cmd’ and press Enter, then press Ctrl + Shift + Enter to open up an elevated Command Prompt. When you see the UAC (User Account Control), click Yes to grant administrative privileges. With this crash on this second brand new mobile workstation z book, I saw controller errors and hard disk info in the report but have not yet identified the source, hardware or software/ driver or possibly all.

If everything looks OK, it might not be the drive, but a faulty SATA port/cable, that's why I'd suggest that you try the HDD with a different. ২৮ মে, ২০২১ 1. Check the hardware cables · You might have a broken USB cable. · Connect the device with a different USB cable. · Try connecting the device to. It could be followed by “DeviceIdeIdeport0 OR”, “on deviceharddisk0dr0”, or “DR3” or the name of the drive or port that's causing the problem. If you are one of.