March 25th, 2023, 4:09
March 25th, 2023, 4:17
March 25th, 2023, 7:47
March 25th, 2023, 13:33
michael chiklis wrote:MRT has a bug which sometimes doesn't load properly WD configuration ID in the utility on ATA0 channel.
Try to attach the drive on ATA1 to see if does the same, if is still the same then it is hard drive issue.
I've see this bug only for WD drives, it can be solved by repowering pc (turn off it completely from grid) and discharging motherboard caps (you can do that by pressing few times the power on switch of your pc while it is unplugged from grid).
Once you boot again in windows, disinstall and reinstall MRT and its drivers.
March 25th, 2023, 14:24
Spildit wrote:michael chiklis wrote:(...)
I've see this bug only for WD drives, it can be solved by repowering pc (turn off it completely from grid) and discharging motherboard caps (you can do that by pressing few times the power on switch of your pc while it is unplugged from grid).
Once you boot again in windows, disinstall and reinstall MRT and its drivers.
Interesting bug that would require a full discharge of the motherboard + re-install MRT to "fix" something that looks simple like the lack of capability to read a single module ...![]()
![]()
![]()
March 25th, 2023, 14:35
reliableservice wrote:michael chiklis wrote:MRT has a bug which sometimes doesn't load properly WD configuration ID in the utility on ATA0 channel.
Try to attach the drive on ATA1 to see if does the same, if is still the same then it is hard drive issue.
I've see this bug only for WD drives, it can be solved by repowering pc (turn off it completely from grid) and discharging motherboard caps (you can do that by pressing few times the power on switch of your pc while it is unplugged from grid).
Once you boot again in windows, disinstall and reinstall MRT and its drivers.
Problem Remain Same - even Changing to ATA1, ATA2
Powered by phpBB © phpBB Group.