While the PC was frozen and accessing my 250 GB drive, I powered the system off and back on. That 'experiment' proved fatal as the same damn problem returned, but with a nasty twist this time. When that was done I removed the 200 GB, stuck it into my older PC, closed my PC's case up, removed the SATA PCI card (I wanted to experiment without that card for a bit) and powered it on. Following that I proceeded to transfer the data from my 200 GB drive to my new 500 GB drive. I got a 500 GB SATA drive (WD5000AAKS) and proceeded to do some serious rearrangement of all those wires coming out of my PSU. Anyways, after I installed the card, everything was fine again. I also had a 200 GB WD IDE drive (WD2000JB) connected via an IDE cable which may have contributed to the problem. The problem, according to the solution I read on Hardware Analysis (link: Hardware Analysis - Forum - Event ID - 51 - An error was detected on device DeviceHarddisk0D during a paging operation) was probably because of the nForce4 chipset being incapable of handling that much data flowing through it.
I searched up for solutions to this problem and found one: buy a SATA PCI card and connect my hard drive's SATA cable to it. This problem escalated to the point where it corrupted part of my games partition on my main hard drive, a 250 GB WD SATA drive (model number WD2500KS). It was random and the only errors that indicated something was acting up were a bunch of Event ID 51 errors in the Event Log. Here goes:īack in April 2006 I experienced problems where my computer will grind to a heavy halt. I guess I'll use this post to share a simplified version of my experiences with two particular parts of my computer: my hard drive and my motherboard's chipset.
0 kommentar(er)
