| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 98790 | 2009-04-07 06:34:00 | Computer crashing question | Growler (12596) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 762914 | 2009-04-08 02:24:00 | just make sure you have ruled everything else out before laying out for new hardware :) | utopian201 (6245) | ||
| 762915 | 2009-04-08 03:02:00 | Have you tried my solutions yet? | Blam (54) | ||
| 762916 | 2009-04-08 04:18:00 | Have you tried my solutions yet? Not yet. Unfortunately real life gets in the way! I will try tonight. |
Growler (12596) | ||
| 762917 | 2009-04-08 11:16:00 | Have you tried my solutions yet? Ok - I have run the tests on the Harddrives and they all pass. Memtest seems to be OK as well. |
Growler (12596) | ||
| 762918 | 2009-04-08 11:23:00 | Try this - click start/run type in eventvwr <press Enter> When Event Viewer opens have a look through the application and system Logs - look for any errors / Warnings at the time of the crashing. Double click the error message, usually there is some sort of code or actual message that will say what the problem was - Copy/paste back the complete error message. For example if there is any Errors that say DISK ( esp a few one after the other) - that will be a problem with the HDD - usually starting to fail (but not always) |
wainuitech (129) | ||
| 762919 | 2009-04-08 11:39:00 | Try this - click start/run type in eventvwr <press Enter> When Event Viewer opens have a look through the application and system Logs - look for any errors / Warnings at the time of the crashing. Double click the error message, usually there is some sort of code or actual message that will say what the problem was - Copy/paste back the complete error message. For example if there is any Errors that say DISK ( esp a few one after the other) - that will be a problem with the HDD - usually starting to fail (but not always) Ok...the PC seems to be working Ok tonight but looking at the log I had 4 errors within 35 minutes. 3 are for disk (The driver detected a controller error on\Device\Harddisk1\D) and 1 is atapi (The device, \Device\Ide\IdePort1, did not respond within the timeout period. What does this mean? |
Growler (12596) | ||
| 762920 | 2009-04-08 11:52:00 | Is the hdd the bootdisk in the BIOS?? Whats in the case? How many IDE / sata devices?? If youre using IDE, are any hdd/s cd/dvd's on the same IDE connector? Are you using 80 wire IDE cables (If youre using IDE)? If you are, is the blue connector on the mobo IDE connector end? |
Speedy Gonzales (78) | ||
| 762921 | 2009-04-08 12:46:00 | Is the hdd the bootdisk in the BIOS?? Whats in the case? How many IDE / sata devices?? If youre using IDE, are any hdd/s cd/dvd's on the same IDE connector? Are you using 80 wire IDE cables (If youre using IDE)? If you are, is the blue connector on the mobo IDE connector end? What do you mean "is the hdd the bootdisk in the Bios"? If you mean the hdd is the first to load in the bios then yes. Both hdds are SATA2's. The only IDE cable I'm using is for the DVD drive. The "red" end (Gigabyte 80 wire cable) is going into the mobo. |
Growler (12596) | ||
| 762922 | 2009-04-09 23:36:00 | Did anyone else have any ideas on this? | Growler (12596) | ||
| 762923 | 2009-04-10 00:02:00 | Was meant to get back to this yesterday - sorry had work to do. The error message is saying that one of the Disks is losing contact - which more than likely is causing the problem. IF it were the Optical drive, the error would usually be CDROM, not disk. What I suggest is a process of elimination . With the PC turned off, disconnect the second drive - start the PC, and see if it crashes again - if not, look into the event Viewer and make sure there are no more errors. IF it does crash again, do the same to the optical drive. IF its still doing it, then it could be the main drive, try a different SATA port on the board. Once you find which drive is causing the problem/errors, try replacing the cable from the board to the device, if that doesn't work, try a different power plug on your power supply. Sooner or later the errors will stop when a device is disconnected - that will be the problem. |
wainuitech (129) | ||
| 1 2 3 | |||||