Model Name : GA-X58A-UD5(rev. 2.0)
BIOS Ver : FC2 (Beta version supplied direct by Gigabyte)
CPU : Intel i7-960
Memory : Kingston 6 x 4GB DDR3 x 1333 (Kingston KVR1333D3N9K3)
Power Supply : 1000W Coolermaster Silent Pro Gold PSU
Video card : Asus model ENGT240
Hard Drive (Main): Intel X25-M SATA 160GB solid state hard drive
DVD : Sony DRU-870S DVD/CD rewritable drive
Screen : Iiyama ProLite E2200WS
Other kit : USB mouse, USB keyboard,
Operating System : Windows 7 (64-bit )
I have successfully built my computer and installed Windows 7 (64 bit). I had a little bit of a problem with the original PSU (covered under another thread), but my system is now up and running like a rocket.
That is until I add a Western Digital 2TB hard drive (WD20EARS). [Not brand new but bought a few months ago and used as an external SATA drive on my old system].
Connections :
Intel SSD is attached to SATA2_0 (Identified at IDE channel 0 master)
Sony DVD is attached to SATA2_1 (Identified at IDE channel 0 slave)
WD drive is attached to SATA2_2 (Identified at IDE channel 1 master)
BIOS FC2 is set to defaults except as follows :
Advanced Frequency Settings - SPD set to 10.0 to increase memory frequency from identified 1066MHz to 1333MHz.
Advanced BIOS Features - Full Screen LOGO Show - Disabled.
Problem :
The WD hard drive is identified and can be used by Windows (set to drive I:).
I have installed and checked the disk using the WD Disk Align utility. I have deleted the partition and recreated with the Windows Disk Management several times. [Identified as a healthy primary partition 1863.01GB NTFS].
However, copying from drive I: to drive C: initially is acceptable, but rapidly reduces transfer rates to a painfully slow rate (KB/second and not MB/second).
Use of file managers (Explorer or PowerDesk) is initially OK, but then the system virtually seizes up with no visible progress and a ‘Not Responding’ message from Windows.
Using Task Manager to shut down programs that have apparently stopped takes an age.
Shutting Windows down can take 15 minutes or more.
Windows is also identifying problems with the disk on bootup, insists on checking the disk and then usually finding problems.
And this is all on an almost empty hard drive.
I would like to know if this is likely to be a faulty WD drive, a SATA set up problem or other BIOS issue. Can anyone advise me on how to proceed from here?
Regards
Chris