|Without even managing to fix my last issues with my graphics card, I encounter a new but maybe related issue with my hard drives. To prevent possible confusion and to make myself easier to understand, I'll try and categorize a few things about my problems to make things easier.|
Primary Master: ExcelStor Technology (82GB)
Primary Slave: WDC WD800BB-00JHC0
Secondary Master: CDDVDW SH-S202
PMaster - 2 Partitions (C: & E:)
PSlave - 1 Partition (D:)
PMaster was given to me with the computer. As far as I can remember, this drive was working fine when I got it, but considering who I got it from, I'm not quite sure.
After months (maybe a year or so) of regular use, I noticed that the hard drive had began ticking. I thought nothing of it.
Months later, my computer started to have a 'breakdown' and started throwing diskcheck prompts at me, although nothing too dramatic happened and after a while, the chkdsk thing went away, so I figured it must have solved any problems. It was at that period that I noticed the ticking to be a possible threat, as it would tick more frequently during chkdsk.
After time, my copy of windows decided to die and I couldn't even boot into Safe Mode as it would just freeze. Having lost the disc for windows, I sent it to someone who said he could fix it. Now this guy aint nothing new to computing, but as I soon figured out he isn't that good either... After months I got my computer back. My copy of windows was somewhat fixed (but slow as hell) and a new copy of windows had been put onto the computer using a new partition... E: - which totaled to 6GB... Told you he wasn't that clever...
The ticking seemed to dissapear for a while, but then came back again... But only when I was doing alot of stuff with my PC. I had finally got internet by then and decided to Google my ticking HD thing... Discovering that aparently, this is the sign of a dying hard drive.
So I got a new hard drive. Unfortunately the only one available for me at the time was another 80GB one (grr) which I figured would do as long as I got rid of un-needed stuff. I put my new HD in as the PSlave and everything worked great...
... So great that the ticking stopped completely. I installed another copy of XP onto the PSlave (so now I have 3 XP's, 1 half-broken) just so I had something to boot if things got nasty with my PMaster.
I backed up some stuff, but the sudden stop in ticking for my PMaster and the fact that I've had the thing ticking for almost 2 years got me thinking that maybe my PMasters ticking wasn't the same type of ticking that other people have been getting. After all, this isn't the only kind of tick a hard drive can make... As I find out later...
Okay, so now I'm using both drives equally. Everything with my computer works great. The backups I made are useless now since all backed up files are either obsolete or updated since the backup. But after time, I encounter another batch of problems...
... My videocard!
I even tried a brand new copy of XP to test my card on... Now this is kinda my fault, but I've ended up with 4 XP's on these 3 partitions. Little did I know that on the XP install dialog's, where it originally says "choose install path" IS the place it installs XP to, not the place it puts temp install files. I seemed to remember typing the install path in the BIOS part of the installation... So I put these files in C:/windows/install (attempting to overwrite my old, broken XP).
So after having those problems (which never got fixed, btw) and trying a new, 16MB card w/ drivers that never works either... I start to get deeper problems. This is somewhat a crossfade between GFX problems and HD problems... I start to get these reboots and crashes. Now previously these came from the GFX card... But I got some new errors.
I started to run low on disk-space for my 6GB E: drive (that guys fault, lol) and really couldn't find much that I could safely delete. Maybe that's the explanation to some of the bluescreens I started having on that drive. After all, it did say something about checking disk space on the screen, as well as displaying a system file. All this is on the windows installed on E:
Meanwhile, on my D: drive O/S (PSlave), it seemed that problems with booting were caused by my videocard errors... See, something called "Windows Updates" ensured the auto-install of GFX Drivers and since GFX Drives = crash... Well... This also seemed to occur on my newest XP install in C:/windows/install
All this is going on at the same time... Really stressful.
Until eventually... I can no longer even boot up any OS. I tried safe mode, vga mode... All of my XP's. I figured they wouldn't boot up for different reasons... Most because of my gfx card and one because of the low disk space...
After a while of trying, the bios would no longer even detect my HD's... And then it would detect one (PSlave)... Then none. I thought my PMaster was broken.
I reset my BIOS, unplugged my CD Drive, changed BIOS settings etc.
Now, remember my GFX troubles? There was a sound that seemed to occur whenever my PC crashed from the drivers... A sound that I thought was coming from my motherboard since my GFX cards are surely incapable of making this sound. It sounds like something loosing power, a slight click (not a sharp one, though) and a winding-down sound. Maybe the sound of my HD disks stopping briefly?
This seemed to happen after a while of my PC being on, preventing the BIOS from detecting the HD's. This is the thing that makes me think that maybe the HD and GFX problems are in some weird way related...
(I'm as bored of typing as you are of reading, sorry)
Eventually, I got one drive working... After lot's of testing, I came to the conclusion that my newer drive was the problem... Which really confused me. My BIOS seemed to be fine without it. And no more of that noise...
But I was determined to get to the bottom of it... I plugged the D: drive (PSlave) back in as well as reordering all drives numerous times. Eventually, they both seemed to work, so I put them back in their usual positions.
When D: is the PMaster, a NTLDR message appears (I assume it's the file that tells the BIOS of the installed OS's) stopping me from booting any of my XP's... So using just that drive was out of the question.
I tried all OS's and they wouldn't load. I came to the conclusion that disabling the D: drive (PSlave) in the BIOS would work, it did. Which made me believe more that it is the problem drive.
I've currently only been able to get 2 OS's working. Both of which are those C: drive installs. E: crashes during loading and D: cannot be loaded as it is not officially installed...
C:\Windows - works, but is still broken.
C:\Windows\Install - works great.
D:\Windows - unbootable.
E:\Windows - stalls after booting (before the blue logon screen)
When I first got these working, I had to go thru a heck of alot of chkdsks... With my old drive ticking again, but still less frequently. Also, less problems appear in chkdsk.
So I'm using the 2nd one listed. Things seem to be better, have just finished backing up critical things from C: onto D: since I am unsure of which has the problems... The one that I can't install in the BIOS or the one that needs chkdsk.. Maybe both.
According to a drive-checking program, both disks are "OK"... I started a scan with it. So far I'm up to my old drive, PSlave (C: and E:). And things seem okay. So far only 0.2% of it has errors...
I deleted a heck of allota files from all partitions. Kinda solved the disk space issue on E: (500MB left, not great, but..). I figured that since I HD's biggest task was storing files, if I deleted some, there's less room for error. Less bad files, etc.
Oh, yeah... One extra thing that may be of importance... While the space issue with E: still existed, I compressed a fair load of files on it... Well, disk cleaner did it... This same thing happened before chkdsk's started occurring last time... Although I can't really say it's the direct cause, I've never thought compression is a good idea. Maybe this is a contribution to the errors?
D: drive is fully browse-able from windows without having installed it in the BIOS. Although I hear that sound quite a few times and it seems to slow down my PC when using both drives. I also encountered a load of un-deletable files due to either errors or permission denial (grr).
Since I'm using my new C:/Windows/Install OS, not much is installed or fiddled. Nor have I got internet access.
Lastly, GFX problems seem to have stopped (even with drivers installed) since I got my XP loading again although I'm really unsure.
Which drive is most likely broken? PMaster, PSlave or both?
Can compression lead to these issues?
What is the cause?
Which HD is safest?
Could the GFX card problems be a result of HD failures?
Sorry to make you read all that (unless you skipped it), but I consider most of it relevant. I am working on gettin a new PC, but buying new HD's seems unnecessary since if I'm getting a new PC, it's probably gunna use SATA HD's (they are the latest, aren't they?).