System Specs:
Antec Tru430 PSU (about 2 years old)
ECS KT600-A Motherboard (about 4 months old)
AMD Athlon XP 2600, 2.08Ghz (almost 3 years old)
1024GB Crucial PC2700 RAM (2x512) (almost 2 years old)
PowerColor ATI Radeon 9200 (3 years old)
1 Maxtor Diamond Max 10 200GB Harddrive (1 year old)
1 Western Digital WD3200 320GB SATA 150 HDD (2 weeks old) **
** this is the drive causing me problems
Errors, from Event Viewer
Warning:
Source: Ftdisk
Category: Disk
Event ID: 57
The system failed to flush data to the transaction log. Corruption may occur.
Error:
Source: viamraid (I have a VIA raid sata controller on this motherboard)
Category: none
Event ID: 9
The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
Details surrounding the errors:
This SATA drive (plugged into the Via SATA controller on the motherboard) isn't even my system drive. It is only used to store data. I'm not even using data on this drive when these errors occur. I've had it for about 2 weeks, and this has happened at least 3 times. The errors show up in Windows event viewer after I hear the drive click off, and restart. My computer freezes up for a few seconds, but never reboots. This seems to happen when my computer is under some kind of stress.
The first time this happened, I was converting video files (vob to avi). At this time, I had my page file located on the SATA drive (6GB Partition, System Managed Size). I figured that was causing the disk to crash, so I moved the pagefile back to C:, and formatted the SATA drive. There was also a large number of files on the second partition.
This started happening again today, while installing World of Warcraft. The installer was using about 76MB of system resources. I'd hear the drive click then stop spinning. My computer would freeze up completely, mouse and all, for about 20 seconds. I'd restart my computer, try to run the installer, and the drive once again clicked off. This happened a few times. The entries posted above were present in my event viewer after each crash. At the time this started happening, the harddrive was completely empty. In fact, it hasn't even been partitioned yet. It's just "unallocated space". When this began happening, I first tried to disable this drive via the device manager. This didn't help. I had to open my PC and unplug this drive before I was able to install the game without interruption.
I ran the Windows Memory Diagnostic tool, and I passed with flying colors 3 times. I also ran a CHKDSK on both these drives and no problems were found.
What can be causing this? I don't have a problem with viruses, spyware, or system clutter. This is a fairly new windows install, and I am on top of keeping it updated and clean. Why would a drive that isn't even in use, start crashing when I am doing memory intensive work?
Thanks for taking the time to read this.
Antec Tru430 PSU (about 2 years old)
ECS KT600-A Motherboard (about 4 months old)
AMD Athlon XP 2600, 2.08Ghz (almost 3 years old)
1024GB Crucial PC2700 RAM (2x512) (almost 2 years old)
PowerColor ATI Radeon 9200 (3 years old)
1 Maxtor Diamond Max 10 200GB Harddrive (1 year old)
1 Western Digital WD3200 320GB SATA 150 HDD (2 weeks old) **
** this is the drive causing me problems
Errors, from Event Viewer
Warning:
Source: Ftdisk
Category: Disk
Event ID: 57
The system failed to flush data to the transaction log. Corruption may occur.
Error:
Source: viamraid (I have a VIA raid sata controller on this motherboard)
Category: none
Event ID: 9
The device, \Device\Scsi\viamraid1, did not respond within the timeout period.
Details surrounding the errors:
This SATA drive (plugged into the Via SATA controller on the motherboard) isn't even my system drive. It is only used to store data. I'm not even using data on this drive when these errors occur. I've had it for about 2 weeks, and this has happened at least 3 times. The errors show up in Windows event viewer after I hear the drive click off, and restart. My computer freezes up for a few seconds, but never reboots. This seems to happen when my computer is under some kind of stress.
The first time this happened, I was converting video files (vob to avi). At this time, I had my page file located on the SATA drive (6GB Partition, System Managed Size). I figured that was causing the disk to crash, so I moved the pagefile back to C:, and formatted the SATA drive. There was also a large number of files on the second partition.
This started happening again today, while installing World of Warcraft. The installer was using about 76MB of system resources. I'd hear the drive click then stop spinning. My computer would freeze up completely, mouse and all, for about 20 seconds. I'd restart my computer, try to run the installer, and the drive once again clicked off. This happened a few times. The entries posted above were present in my event viewer after each crash. At the time this started happening, the harddrive was completely empty. In fact, it hasn't even been partitioned yet. It's just "unallocated space". When this began happening, I first tried to disable this drive via the device manager. This didn't help. I had to open my PC and unplug this drive before I was able to install the game without interruption.
I ran the Windows Memory Diagnostic tool, and I passed with flying colors 3 times. I also ran a CHKDSK on both these drives and no problems were found.
What can be causing this? I don't have a problem with viruses, spyware, or system clutter. This is a fairly new windows install, and I am on top of keeping it updated and clean. Why would a drive that isn't even in use, start crashing when I am doing memory intensive work?
Thanks for taking the time to read this.
Facebook
Twitter