Bought around March 2005-
Pentium 4 3.0Ghz 530J
Prescott, 3.0 GHz, LGA 775, 800 MHz FSB, L2 Cache 1MB, 90nm, Hyper Threading
-80 GB SATA Seagate hard drive
-LG GSA-4120B optical drive
12 March 2005 order placed from Dabs.com:
- Thermaltake Tsunami Black case with side window
- Gigabyte GA-8I915P Duo Pro Motherboard
-1GB DDR PC3200 (333Mhz) – (Not sure about speed check my signature please) Corsair Valueselect RAM CAS 2.5 (2x 512MB RAM Modules)
Antec Trueblue 480W PSU
12th March 2005 – Order placed from overclockers.co.uk
- Powercolor X800XL 256MB PCI-E
23rd March 2005 – Order placed from dabs.com
-Iiyama Prolite E435S-B 17 inch LCD and a Belkin DVI cable
Computer was then built during around March 2005
Worked fine until I bought the following:
2nd June 2006 – Order placed form overclockers.co.uk
-Zalman Aero Flower (Socket 775) Heatsink and fan
-Arctic Silver 5 Thermal Compound (3.5g)
-Akasa AK-178-BL 12 inch Cold Cathode
-Logitech G5 Gaming Grade Laser Mouse
-Akasa AL-171 Copper RAM Heatsink (only 1) (I thought 2 came in the pack but only 1 comes)
The above components were installed on the 6th June 2006 (before the components listed below)
12th June 2006 - Order placed from overclockers.co.uk
-Powercolor X1900XT 512MB GDDR3 AVIVO PCI-E
13th June 2006 - Order placed from Scan.co.uk
-Akasa AK171 Copper RAM heatsink (only 1) (Because I thought 2 would come in the previous order)
-Zalman Northbridge Heatsink - Which I did not install because it was not an improvement over the one which is in the system - however when I pulled off the Northbridge heatsink it was stuck like glue so I yanked it off. I later found out it would have come off easier if I had used a hairdryer on it for a minute or so. I then replaced the Northbridge heatsink (it’s passively cooled). However I doubt I damaged the Northbridge, and even if I did this couldn’t explain the SATA HDD's failing could it? And the result of damage would be immediate however there was nothing to suggest there was a problem immediately afterwards nor a week afterwards.
-Silverstone ST60F PSU 600W
Items bought above were assembled on 16th June 2006
18th August bought S-Video cable (50 ft) and tried to record TV via S-Video however only black and white appeared (Rewired a SCART adapter as a website informed me this is why I was getting Black and White). Again I doubt this caused the problem- it is important to mention around September the main power box blew. The people from EDF energy came and repaired it for free as it was below the black box thing which the company EDF are responsible for (we own a business a shop which is located under the house it is my fathers just to let you know).
Also I cannot remember when this was, but some time back before the S-Video cable was bought and before the power blew I had to test a Hard drive that was in the shops security system. It is not a pc it is a box with record buttons and stuff that records off the cameras. Well whilst that was in the security box thing it was making beeping noises (yes I know hard drives don't normally emit noises that sound like beeps). So I disconnected the IDE hard drive in my system and connected the security hdd as I will now call it. It did not show up in My Computer on the desktop link so I disconnected it (of course after powering down the system etc) and carried on as normal. And low and behold a couple of days later my HDD started beeping (the SATA one). That is when the first 80GB Seagate Hard drive broke. It is important that you understand that the IDE hard drive was bought before this system was even built and I removed it from the other Intel Celeron Dell PC (I had bought this hard drive from dabs as the PC only had a 'Fireball' (or something like that) 8Gb HDD! This IDE hard drive still runs fine! I have always used it to backup the important files.
On 2nd September 2006 (Exactly 2 months and 16 days after components were assembled) Tomb Raider Legend crashed came up with some error regarding 'Microsoft C++ Fatal error please refer to readme' or something along those lines.
Then the PC went into endless reboot. After this I reformatted and reinstalled. (This was when I still had the SATA Seagate 80Gb HDD).
On September 30th 2006 (Roughly 3 Months after assembling components) HDD Health reported that the Hard drive was going to fail on the 21/01/07. A couple of days before this the hard drive was making beeping noises (yes the hard drive).
Did not allow HDD to fail instead bought: - > 20th October 2006- Order placed from Komplett.co.uk (Notice that the HDD managed to survive from 30th Sep till the 20th October although I cannot remember if it was alive or what or if I left the PC off or whatever I simply cannot remember).
Seagate Barracuda 7200.10 320GB SATA 16MB cache 7200Rpm (20th October 2006 - Komplett)
Hard drive failed around 12th November 2006, so RMA'd it and got refund for the HDD.
So bought new HDD.
23 November 2006- Order placed from Scan.co.uk
Western Digital 320Gb WD3200YS
This hard drive failed around 19th January 2007 so got replacement (5 year warranty)
31 January 2007- Scan.co.uk - HDD failed again so sent PSU (as I suspected it) and HDD to Scan.co.uk
The PSU was found as not faulty and sent back on the 2nd of February along with the replacement HDD; I then found that the connections on the PSU were loose. So I sent it back on the 23rd February 2007 for free as Scan realised that I was NOT going to pay for something their engineers failed to spot.
Replacement PSU arrived on the 1st March 2007. Installed PSU on the 3rd March 2007 (Saturday). Installed OS on the 4th March 2007 (Sunday). Uninstalled SP2 on 6th March 2007 (Tuesday). This caused BSOD so repaired OS using the recovery tool on the original OS installation disk. After it had finished repairing and had rebooted, the hdd made a clunk slowing down noise and BSOD 'Winsrv is missing' or something along those lines (BSOD) and a STOP:0xc0000135
Clunk noise indicates HDD failure. So installed OS the same night and turned it off.
7th March 2007 (Wednesday) Installed SP 1a and motherboard drivers. Then installed HDD health. Continued installing drivers and software as I was doing so the program reported HDD failures as follows - ID - 3 - Spin Up Time - TEC - 13/03/2007 - Value 188 - Threshold 21 - Worst 188 - INC -5. Now the official Western Digital Diagnostics tool says that all S.M.A.R.T info is fine and there is nothing wrong with it.
Then again that's what it said for the other 2 drives. Ok and then it says there is something wrong with the temperature of the hdd and it says unknown attribute ID - BE which I know is the airflow temperature because of the Western Digital Diagnostics software which says ID - BE - Air flow temperature. When I first start the PC HDD health gives the Airflow temperature and the HDD temperature +4 and +6 respectively and highlights it blue whilst spin up time remains the same although the T.E.C date changes with time as it gathers more info.
However as I use the PC or leave it on the numbers decline and eventually it goes red and bases the T.E.C date on the temperatures. This is utterly ridiculous because the same HDD health tells me that the HDD temperature (in the brief info tab) is 37C MAX at any one point although it usually runs at 35-36C and my IDE one operates at 34 constant as it is not in use only for backup purposes. There is a 120mm fan DIRECTLY behind the drives so this is DEFINTLEY not an overheating issue and the other things such as Everest home edition says the temperatures and EVERYTHING are fine just as Western Digital's Diagnostics does. So lets kick temperature in the butt and say forget it cus it aint the problem!
The spinuptime cannot cause a HDD to fail and is apparently its normal for the spinuptime to be slightly slow during the first X amount of hours of a HDD's life.
Ok now when I installed everything on Sunday I did notice some strange sounds which sounded like the HDD would fail although they were very brief and not that often.
However yesterday 8th March 2007 when I installed sound drivers, graphics drivers etc and some programs, there were no sounds. I had turned the Cold Cathode off (it has a switch) as I thought it could be causing the problems.
However after installing drivers and some programs such as Everest Home edition and leaving it running idle for 1 and a half hours I decided it probably wasnt the cathode but I left it off. I hit upoun the idea that it might be the raphics card as I had been experiencing low FPS in Far Cry and Tomb Raider Legend when I last played (around 12-18 FPS on average) and there were new graphical glitches in COD2 tried using older drivers (ATI) etc made no difference. And sine around July I noticed there is a thin border on the left hand side of the screen and the top of the screen which only appear when I play a game and the line remains a set colour dependong on the game played. For example in Far Cry it remains Blue in TRL it remains White. And during playing TRL (the card is not overclocked or overdrived using the ATI overdirve tool although I used it once for like 1 minute in TRL) the card runs at 90C during playing TRL. All the game related information is not recent data as you know that I have not used my HDD for those purposes yet. It was when I had the other HDD's.
Also notice that the Seagate HDD lasted the shortest and thats the HDD that I played the most games on so I thought a strong link huh?
So I thought given my theory turning the Cold cathode on should make no diffrence. So I turned it on; whilst I was formatting the second half of the WD HDD (my copy of XP does not have any service packs so XP recognises only half the disk; the other half must be formatted (of course forst service pack 1a msut be installed for xp to recognise the other half, then after installing SP 1 a I install SP2), Whilst all of this was going on I thought I would put some stress on the HDD to see if that affects it and run HD video clips to check if the graphics card was causing the problem, which I downloaded from a variety of sites - Microsoft and some game HD trailers. During all this I was playing the Alexander Trailer and found I lost sound form the rear speakers and the center speaker. During this time the hard drive started making those noises again, so I now think its due to partitioning it or it could be the graphics card or the cathode . (Pulls hair out in frustration) (Screams aghhhh)(Thumps the table with energy remaining)
Dam who on earth or mars can figure this amazingly complex problem out? Quantam physics and molecular reengineering and rocket science are easier then this (Not really derr!)
Please help me Please Please!!!!!
Edited by Mitesh, 09 March 2007 - 07:05 AM.