calmloki
Give me a museum and I'll fill it. (Picasso) Give me a forum ...
2 year old Gateway decides to go down after 5 minutes or so - was random, then 5 or 10, now predictably within 5. This is without running anything other than normal startup programs, and from a cold start. All fans running including power supply and chip fan. Decided it seemed like a heat related failure of some component. Have 2 different Ram chip pairs in the Gateway, pulled each pair and ran them 2 chips only in each of the two Ram banks. Same failure each time. Bought a new power supply and installed. Same failure.
Bought a new Emachine yesterday and, after running the Emachine for a while without issue, plugged in the Gateway's SATA drive as a secondary drive, thinking maybe it was a Gateway operating system problem. Thought we would use the Gateway Sata drive as loaded program and data storage. The Emachine started failing over and over just like the Gateway had - without even accessing the secondary drive's programs or data!
Now the weird stuff: ran a power cord from the Gateway to the Gateway SATA drive installed in the Emachine and ran the data cable from the Gateway drive to the Emachine motherboard and we were able to download the pictures and data from the Gateway drive to the Emachine drive without issue. Over 15 minutes without problem. Ok good. Thought I would try the reverse and plugged the Gateway data cable into 2 different ports on the Gateway motherboard, powering the Gateway SATA drive with the Emachine powercable and booted up and ...it went down after bootup both times!
We run AVG virus scan on all machines and have a router and hub - not really thinking virus - it acts more like a power failure to my mind. When transferring the data if there was a power failure would data transfer pick back up at the drop point or would it just report a failure? Would really like to use the Gateway box for my machine as it has working USB2.0 ports that my older machine doesn't have - of course that means getting an IDE to SATA converter so my old drives can swap in. Also wouldn't mind using that Gateway 320 GB drive if it's not the problem - not looking forward to program and operating system tweaking - even if she's the one doing it the air gets a bit of a charge in it....
Any ideas? What am I missing in the hardware trouble shooting and what fits the observed results?
Bought a new Emachine yesterday and, after running the Emachine for a while without issue, plugged in the Gateway's SATA drive as a secondary drive, thinking maybe it was a Gateway operating system problem. Thought we would use the Gateway Sata drive as loaded program and data storage. The Emachine started failing over and over just like the Gateway had - without even accessing the secondary drive's programs or data!
Now the weird stuff: ran a power cord from the Gateway to the Gateway SATA drive installed in the Emachine and ran the data cable from the Gateway drive to the Emachine motherboard and we were able to download the pictures and data from the Gateway drive to the Emachine drive without issue. Over 15 minutes without problem. Ok good. Thought I would try the reverse and plugged the Gateway data cable into 2 different ports on the Gateway motherboard, powering the Gateway SATA drive with the Emachine powercable and booted up and ...it went down after bootup both times!
We run AVG virus scan on all machines and have a router and hub - not really thinking virus - it acts more like a power failure to my mind. When transferring the data if there was a power failure would data transfer pick back up at the drop point or would it just report a failure? Would really like to use the Gateway box for my machine as it has working USB2.0 ports that my older machine doesn't have - of course that means getting an IDE to SATA converter so my old drives can swap in. Also wouldn't mind using that Gateway 320 GB drive if it's not the problem - not looking forward to program and operating system tweaking - even if she's the one doing it the air gets a bit of a charge in it....
Any ideas? What am I missing in the hardware trouble shooting and what fits the observed results?