- Jan 12, 2001
- 1,405
- 7
- 81
Title sez all. Wondering if you guys think the WD is bad or if this is a Chaintech problem.
The WD runs slow, crashes the system when defragged, crashes the system when you copy more than one file to it at a time, crashes as a boot drive (if you install an OS on it) and when I mean crash, I mean lockup mouse cursor crash, not a BSOD. I've tried all SATA ports, and again, in any combination the Seagate works great, and the WD does not. However, the WD works flawlessly in another PC by itself!?
Neither drive has bad sectors, runs hot (they're cooled) or make weird noises. I will note that I have owned this system since February and recently (30 days ago) added the WD as a slave (D) drive for additional storage. This is by far the STRANGEST problem I've run into with SATA yet.
Note that the system is overclocked, but behavior is identical when running all stock.
By a stretch, is this a firmware incompatibility with Seagate's and WD's on the same bus (are these companies out to get eachother with hashing firmwares?)
-Tim
The WD runs slow, crashes the system when defragged, crashes the system when you copy more than one file to it at a time, crashes as a boot drive (if you install an OS on it) and when I mean crash, I mean lockup mouse cursor crash, not a BSOD. I've tried all SATA ports, and again, in any combination the Seagate works great, and the WD does not. However, the WD works flawlessly in another PC by itself!?
Neither drive has bad sectors, runs hot (they're cooled) or make weird noises. I will note that I have owned this system since February and recently (30 days ago) added the WD as a slave (D) drive for additional storage. This is by far the STRANGEST problem I've run into with SATA yet.
Note that the system is overclocked, but behavior is identical when running all stock.
By a stretch, is this a firmware incompatibility with Seagate's and WD's on the same bus (are these companies out to get eachother with hashing firmwares?)
-Tim
Facebook
Twitter