HAY GUYS

^-^ · Local time: Jul 3, 2007, 04:40 PM

hey guys. Lately my computer had been making some clicking sounds, so I decided to check it out. Unfortunetly, I can't really pinpoint it down to one problem. I thought it was a harddrive issue (if it was....), but this afternoon, I think it may be something else. As per Zerg's request, I'll post my system log up here. It's in txt format.

Jam it back in, in the dark.

LiquidAcid · Local time: Jul 3, 2007, 10:49 PM

its the harddrive

There's nowhere I can't reach.

^-^ · Local time: Jul 3, 2007, 05:31 PM

which one?

This thing is sticky, and I don't like it. I don't appreciate it.

Excrono · Local time: Jul 3, 2007, 05:44 PM

Its hard to tell without knowing your setup, but the logs would seem to indicate that drive D:\ (an 80GB Seagate disk) and another drive was removed suddenly from the system after Windows was unable to write to it. As a precaution, I would run the chkdsk command ("chkdsk /f") on all disks to verify there are no issues. Once you do that, press "Y" and then reboot so Windows can examine the disks before startup. An event will then be entered into the Application Log with the results of the scan. At that point, you should backup any important documents to removable storage and look into getting a replacement. If the errors go away after doing that, you may be good for a little while (as any bad sectors will be marked off limits by Windows), however it is still best to get a replacement in asap.

I am a dolphin, do you want me on your body?

Zergrinch · Local time: Jul 4, 2007, 09:04 AM

I don't think it's Drive D. Windows can be a tad misleading on that account, calling it "HardDisk0\D".

Look for the drive with "ST380013A" serial number. The system calls it "HardDisk0", which generally corresponds to Drive C.

Your log also indicates the IDE port conked out before the drive did. Try replacing the IDE cables first, and delete all drivers from Device Manager. If symptoms persist, replace the hard disk. If symptoms still persist, replace the motherboard. If symptoms persist, replace the memory. If symptoms persist, replace the power supply unit

Get going!

I was speaking idiomatically.

^-^ · Local time: Jul 3, 2007, 09:57 PM

yes sir! thanks for helping me out, folks!

What kind of toxic man-thing is happening now?

LiquidAcid · Local time: Jul 4, 2007, 11:23 PM

I wouldn't run chkdsk on that drive if I was in your situation. chkdsk does put a lot stress on the drive and might trigger something more serious. If that happens you know that the drive is indeed faulty, BUT you don't have any access to your data.
So FIRST try to backup your data and then check with something like chkdsk, or maybe also the tools from your harddrive vendor.

FELIPE NO

^-^ · Local time: Jul 5, 2007, 10:52 AM

Thanks for all of the replies, guys. I did take advice, backed up and bought a new drive. I then took that old drive, hooked it up via USB, and ran chkdsk on it anyway (just to see) and chkdsk (both, not running the /f and running the /f flag) gave positives. I don't know what's going on with this drive ._.

What, you don't want my bikini-clad body?

mortis · Jul 5, 2007, 06:31 PM

Maybe it is the IDE cable? If it's working fine with USB, maybe then the cable needs to be replaced?

It could also, MAYBE be a fluke that it worked out this time...

Jam it back in, in the dark.