This WB 1TB Black Caviar (WD1001FALS) drive I got 40 days ago has been running fine except a few problems. After some weeks of usage, Windows 7 beta would crash due to system files corruption. I suspected of bad HDD but someone else mentioned how that version of Windows 7 beta corrupts system files itself. I thought that was the case.
However, the exact same problem occured a few weeks later again. This time, I was running Windows RTM and it didn't seem right. I ran chkdsk and HDTune to see if the drive is fine. The result: No problem detected.
Again, same problem occured and this time, BIOS doesn't even pick up the drive.
(I'm using Gigabyte P35C-DS3R and it uses this "Serial ATA AHCI BIOS version...by Intel" when AHCI is enabled in BIOS. That's where the system gets stuck. Unlike before, the drive is NOT detected by that AHCI BIOS. It just hangs there.)
Changing it to IDE mode shows the HDD being detected by BIOS but it wouldn't boot.
I tried changing SATA ports, cables, power cables to see if this problem is caused by other factors but the problem is within HDD itself.
I tried it on my friend's Asus board and it worked!
Finally, I tried it on my Gigabyte board's Marvell IDE controller(set as AHCI mode) and it just works and that's where I am now.
1. This problem is very strange and I don't know what to make out of it. What would be the possible cause of this problem?
2. One more question: From what I gathered, Marvell IDE controller just sucks compared to the original Intel one. Is that really the case?
p.s: I have 3 other HDDs: 2 from Hitachi and 1 from Samsung. All works fine.
However, the exact same problem occured a few weeks later again. This time, I was running Windows RTM and it didn't seem right. I ran chkdsk and HDTune to see if the drive is fine. The result: No problem detected.
Again, same problem occured and this time, BIOS doesn't even pick up the drive.
(I'm using Gigabyte P35C-DS3R and it uses this "Serial ATA AHCI BIOS version...by Intel" when AHCI is enabled in BIOS. That's where the system gets stuck. Unlike before, the drive is NOT detected by that AHCI BIOS. It just hangs there.)
Changing it to IDE mode shows the HDD being detected by BIOS but it wouldn't boot.
I tried changing SATA ports, cables, power cables to see if this problem is caused by other factors but the problem is within HDD itself.
I tried it on my friend's Asus board and it worked!
Finally, I tried it on my Gigabyte board's Marvell IDE controller(set as AHCI mode) and it just works and that's where I am now.
1. This problem is very strange and I don't know what to make out of it. What would be the possible cause of this problem?
2. One more question: From what I gathered, Marvell IDE controller just sucks compared to the original Intel one. Is that really the case?
p.s: I have 3 other HDDs: 2 from Hitachi and 1 from Samsung. All works fine.
Facebook
Twitter