- Joined
- Apr 29, 2006
- Messages
- 5,105 (0.78/day)
- Location
- Sydney, Australia
| System Name | UltraPC |
|---|---|
| Processor | E8500 Core 2 Duo, 1333Mhz FSB, 3.16Ghz @ 4.5GHz (got into Windows @ 4.75GHz) |
| Motherboard | ASUS P5Q-e |
| Cooling | CPU Cooler - TT V14 Pro, 2x120mm CM Blue LED fans, 1x90mm CM Blue LED fan |
| Memory | G.Skill Pi 4GB (2x2GB) Dual Channel DDR2 PC8000 (1000MHz), 5-5-5-15 |
| Video Card(s) | Sapphire HD4850 512mb with ASUS EAH4850 BIOS |
| Storage | 2x 500GB Seagate 7200.12 Raid 0 |
| Display(s) | Acer AL1912, 19" LCD screen |
| Case | Thermaltake Soprano Black ATX case |
| Audio Device(s) | Onboard 7.1, Speakers - 5 + Sub + Monitor speakers |
| Power Supply | Thermaltake 850W Toughpower Cable Management - Quad (2x18A and 2x30A) 12V rails |
| Software | Win 7 Pro x64, MSN, CS:Source, etc etc |
Over the past few days, my PC has been crashing. Finally today it crashed and Windows woudnt boot back in.
After a LOT of testing/chkdsking/windows repair/system restores/sfc scans, on both my computer and my computers hard drives hooked up to the matx, I had given up. At the end it got to the point where I plugged the HD's back in my PC and it wouldnt recognise windows...the windows CD would give a bsod.
So I backed up whatever data that wasnt already backed up (just a couple of files). I then split the RAID array and was about to rebuild it when I thought I might just run some tests on the HD's.
Just to note, after every chkdsk I would get one of the HD's come up as Error occured in the RAID array. It was still bootable, but had that error. To get around it I would just load matrix storage controller on the matx with the HD's plugged in and mark it as normal. But after every single chkdsk it would come up with that error. I also noticed in one chkdsk it came up: 4KB Bad Sectors or something.
Now anyway I put the split HD's back into the matx to do some diagnostics. So after running the quick test on WD Diagnostics, it ran for around 8-10 seconds on each hard drive and errord. I was like ok lets try an extended test.
Did the extended test and after an hour on each drive they BOTH came up with bad sectors. After trying to "repair" these sectors I just got it couldnt repair them and I need to contact WD support.
Is it something I am doing wrong, or do both drives really need to be RMA'd? Any other programs I can test to see if the HD's are ok?
I still not have figured out why my PC crashed (was targeting power supply) but I was only going to worry about it after a format, to see if the problems were still there.
After a LOT of testing/chkdsking/windows repair/system restores/sfc scans, on both my computer and my computers hard drives hooked up to the matx, I had given up. At the end it got to the point where I plugged the HD's back in my PC and it wouldnt recognise windows...the windows CD would give a bsod.
So I backed up whatever data that wasnt already backed up (just a couple of files). I then split the RAID array and was about to rebuild it when I thought I might just run some tests on the HD's.
Just to note, after every chkdsk I would get one of the HD's come up as Error occured in the RAID array. It was still bootable, but had that error. To get around it I would just load matrix storage controller on the matx with the HD's plugged in and mark it as normal. But after every single chkdsk it would come up with that error. I also noticed in one chkdsk it came up: 4KB Bad Sectors or something.
Now anyway I put the split HD's back into the matx to do some diagnostics. So after running the quick test on WD Diagnostics, it ran for around 8-10 seconds on each hard drive and errord. I was like ok lets try an extended test.
Did the extended test and after an hour on each drive they BOTH came up with bad sectors. After trying to "repair" these sectors I just got it couldnt repair them and I need to contact WD support.
Is it something I am doing wrong, or do both drives really need to be RMA'd? Any other programs I can test to see if the HD's are ok?
I still not have figured out why my PC crashed (was targeting power supply) but I was only going to worry about it after a format, to see if the problems were still there.
