Never mind. I moved the hard disk to another drive bay away from the fans, and the problem vanished (perhaps it didn't like having its cable stretched out, or being situated next to those fans).

can i just say that i used to have a geforce fx5600 256mb and my half life 2, cs source and many other high gfx games used to crash while playing. i now have a xfx geforce 6600gt 128mb card which has resolved those problems. im not sayin this is ur problem, i thought u might want to know that.

Phalanx-Imawano, I found this to be very interesting, after reading your post I took my 3 xtra fans I had lying around and installed it into my box, I've got a Chieftec Midi Mesh case, it has the easy clips for the hard drives in the front side of the box but with the hard drive going in from the side, 90° to the norm. I have a S-ATA 160 Gig and the 3 fans I installed fit on the side panel right next to the hard drive. Now, here comes the interesting part, in the couple of months that I've had this PC I've never had any problems with my PC at all, but within the first 10 minutes of runing the new fans my PC just restarted, twice, then the third time it said I must install a proper boot device (and my hard drive made funny sounds, like a faulty one) and it would not boot up no matter what I did, as soon as I just unplugged the power to the fans my PC was back to normal and has been running 100% for the past 6 hours.
 
I honestly do not understand why the fans would infuence the hard drive, HUH?

there is a common thing with sata disk cables...
DONT BEND THE CABLE!
if you have to bend the end of the SATA cable you have to buy special cables for it.
otherwise it wont read successfully and use several tried to some binary strings.
which could result in a CRC error when reading and then have to read
again.
not many people know this and thinks there is a problem with their drive which they have put in a bay so far up and in in their full tower that they have to bend their cable like this [ which isnt really good for a standard S-ata cable.
im not sure if thats your problem, but now you know anyways

firechimp:
 
That so? I'll keep that in mind in my next upgrade.
 
 
Wicked101:
 
Yeah that's really fishy. And I wonder why Hard Drive coolers are available in the market (in fact, that SATA hard disk of mine was sitting on top of such Hard Disk cooler while it had those problems).
 
 
janfebmar:
 
Really? Then that must have been the main problem. That SATA hard disk was in fact situated on the topmost drive bay at the time, thus the cable was indeed stretched out (the controller port was at the bottom of the case). So I guess moving that HD to one of the lower bays did it. By the way is there anything wrong with coiling the SATA cable (say about 2.5" diameter) so it won't clutter the inside of the PC case (it's set up that way right now, so far no problems)?
 

as long as you dont like "break". sata cables are kinda stiff.
i bought some i could bend like "<" that. because i have some vertical HD bays with watercooling. if it works i guess there is no problems at all

Originally posted by janfebmar:

Quote:there is a common thing with sata disk cables...DONT BEND THE CABLE!
if you have to bend the end of the SATA cable you have to buy special cables for it.
otherwise it wont read successfully and use several tried to some binary strings.
which could result in a CRC error when reading and then have to read
again.
not many people know this and thinks there is a problem with their drive which they have put in a bay so far up and in in their full tower that they have to bend their cable like this [ which isnt really good for a standard S-ata cable.
im not sure if thats your problem, but now you know anyways
 
I have the flexible S-ATA cables, thats not my problem and I never had any problems with it, I just found it strange that my hard drive stopped working as soon as I added the 3 fans, I did not touch the hard drive, the fans has its own housing that you remove, add the fans and replace the housing, no problem there. Its just strange that the hard drive stopped working and when I remove the power to the fans everything goes back to normal.

Ugh, it's happening again. I'm getting a sinking feeling it's the hard disk itself, because it doesn't happen to any of my other hard disks.
 
What exactly is happenning is that if a major Write operation is applied to the hard disk (i.e. copying a large file or a batch of files totalling say over 500MB to the hard disk from another hard disk) one of these happens:
 
1. It goes PIO Mode (rebooting restores it to UDMA 5)
2. Windows XP Freezes, requiring a hard reset (the hard drive also goes back to UDMA 5 upon bootup)
 
 
I can reduce the chances of those two happening if I do these:
 
1. Disable Write Caching on the said Hard Drive (which reduces Write performance by 50%)
2. Limit write operations (eg copying) to less than 500MB in one sitting (apparently anything over 500MB for the HD means biting off more than it can chew).
 
The problem does not happen during Read operations, Defragging, Formatting, or a Scandisk check. Heck even a Zero Fill didn't seem to result in errors.
 
At least if there's any consolation, thanks to the Prescott's Hyperthreading, PIO Mode doesn't load the CPU as much as it would an older processor (the "Logical CPU" isn't loaded at all, so total CPU load doesn't go over 50%).
 
 
[Edited by Phalanx-Imawano on 2005-02-20 04:47:58]
 

Update:
 
I found this in the Event Viewer:
 

Quote:Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 02/20/2005
Time: 19:31:03
User: N/A
Computer: MYCOMPUTER
Description:
The driver detected a controller error on \Device\Harddisk2\D.
 
 
Clicking on the link pointed me to this:
 

Quote:Details Product: Windows Operating System
ID: 11
Source: Disk
Version: 5.2
Symbolic Name: IO_ERR_CONTROLLER_ERROR
Message: The driver detected a controller error on %1.
 
Explanation
This problem is typically caused by a failing cable that connects the drive to the computer.
 
 
User Action
Replace the cable.
 
I did as suggested, but the error message in Event Viewer still comes in. I even switched cables with the good SATA Hard Disk and it still reports the error (while that other SATA Hard Disk is reporting no errors). This to me means that the Hard Disk concerned is itself for some reason generating those controller errors (perhaps something in it is busted).
 
 
 
Addendum:
 
That error appears several times until this one does:
 

Quote:Event Type: ErrorEvent Source: atapi
Event Category: None
Event ID: 5
Date: 02/20/2005
Time: 20:00:08
User: N/A
Computer: MYCOMPUTER
Description:
A parity error was detected on \Device\Ide\IdePort2.
 
By the time that message appears, the Hard Disk goes into PIO Mode, and the previous error no longer appears.

Tried Swapping cable?

 
Do not know if this works for SATA disk, but you can try:

Quote: http://support.microsoft.com/default.aspx?scid=kb;en-us;817472
 
WARNING:
If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
 
Follow these steps, and then quit Registry Editor:
1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001
3.On the Edit menu, point to New, and then click DWORD Value.
4.Type ResetErrorCountersOnSuccess, and then press ENTER.
5.On the Edit menu, click Modify.
6.Type 1, and then click OK.
 
Follow these steps, and then quit Registry Editor:
1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002
3.On the Edit menu, point to New, and then click DWORD Value.
4.Type ResetErrorCountersOnSuccess, and then press ENTER.
5.On the Edit menu, click Modify.
6.Type 1, and then click OK.
 
Note The numbered subkeys that are listed earlier correspond to the primary and secondary IDE channels on a computer that contains a single IDE controller.
If your computer contains two IDE controllers, the numbered subkeys for the primary and secondary IDE channels for each of the two controllers may be:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0003
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0004
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0005
 
To verify that you have located the correct subkey, verify that the DriverDesc value for the subkey contains the string value "Primary IDE Channel" or the string value "Secondary IDE Channel."

thats just seems wierd.
how can it be a controller error when he has lots of other S-ata disks?
maybe he got that Hard-Drive on a seperate add-on S-ata extension card. PCI or some sort.
maybe its that seperate controllers fault.
he had alot of sata disks too. might just be that.

but it fixed the problem when he placed it further down. so i still go for the theory that he bended the sata kable right at the end so it got a really shart bend "<" like that. because i know standard kables dont handle that.
but i dont understand wicked101's situation..
that just seems to ulogical.
it might be the drive got to hot. and then read wrong.
 
Best Regards
E.S

ive also heard that about sata cables, i think i read it in my motherboards guide book, a little wanring box in it says do not bend the sata cables! not standard 1s any way.

Originally posted by janfebmar:

Quote:but it fixed the problem when he placed it further down. so i still go for the theory that he bended the sata kable right at the end so it got a really shart bend "<" like that. because i know standard kables dont handle that.but i dont understand wicked101's situation..
that just seems to ulogical.
it might be the drive got to hot. and then read wrong.
 
Best Regards
E.S
 
It's not the cable at all, because when I swapped the cables between the 2 SATA drives (after moving that hard drive down, which later I found out did not solve the problem at all), the same hard drive still had problems (the other Drive which now had the previous one's cable reported no problems). Later, I tried swapping the drives' controller ports (they're built-in to the motherboard) to see if the controller was the problem. Instead the other controller (where the problematic hard drive is now connected) reported the error. My theory now stands that it's the Hard Drive.
 

Originally posted by Wilhelmus:

Quote:Do not know if this works for SATA disk, but you can try:
http://support.microsoft.com/default.aspx?scid=kb;en-us;817472
 
WARNING:
If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
 
Follow these steps, and then quit Registry Editor:
1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001
3.On the Edit menu, point to New, and then click DWORD Value.
4.Type ResetErrorCountersOnSuccess, and then press ENTER.
5.On the Edit menu, click Modify.
6.Type 1, and then click OK.
 
Follow these steps, and then quit Registry Editor:
1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002
3.On the Edit menu, point to New, and then click DWORD Value.
4.Type ResetErrorCountersOnSuccess, and then press ENTER.
5.On the Edit menu, click Modify.
6.Type 1, and then click OK.
 
Note The numbered subkeys that are listed earlier correspond to the primary and secondary IDE channels on a computer that contains a single IDE controller.
If your computer contains two IDE controllers, the numbered subkeys for the primary and secondary IDE channels for each of the two controllers may be:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0003
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0004
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0005
 
To verify that you have located the correct subkey, verify that the DriverDesc value for the subkey contains the string value "Primary IDE Channel" or the string value "Secondary IDE Channel."

 
Tried that already. Instead of the Hard Drive going PIO, Windows XP Freezes.
 

but didnt you find a workaround already?
so why try to fix something thats not broken anymore?
heh
i know the cables cant be bended with too much,
and that was my guess. but if your disk is working properly now, there is no point in trying to fix it, ;P

Originally posted by janfebmar:

Quote:but didnt you find a workaround already?so why try to fix something thats not broken anymore?
heh
i know the cables cant be bended with too much,
and that was my guess. but if your disk is working properly now, there is no point in trying to fix it, ;P
 
I though it was fixed. I was wrong. It's still acting up.

did you scan your HD for damaged sectors?

well.. the its most likely your disk thats gone FUBAR.