- Aug 25, 2001
- 56,587
- 10,227
- 126
second Q9300 rig in sig.
Last night, installed F@H single-threaded client, when it downloaded and decompressed the computational core, it crashed. Running it again succeeded.
So I reformatted, and after the first pass of the Win7 install, it went fine, no problems. But when I stuck the 64-bit install DVD back in, at the windows desktop, it prompted me to run SETUP.EXE (or view files), I clicked to run SETUP.EXE, then it said something about an error loading autorun.dll. I tried it again, and it succeeded.
Does this sound like RAM? Or an unstable overclock?
When I installed my 8GB of DDR2-800 RAM, I did so with the 3.0Ghz OC, and I ran Memtest86+ overnight, with no issues.
I also did an hour test with OCCT, a few days after I overclocked, and also, no issues. I'm overclocking on stock volts.
The other desktop, an identical rig, did not pass OCCT, I had to bump up the vcore a tiny bit.
Also, I noticed when I took the computer apart, the northbridge heatsink was too hot to touch, and the HD's SATA connector on the drive was slightly loose.
I'm going to run another Memtest86+, and some overnight Prime95.
This rig has been running F@H 24/7 on the GPU without errors, and during the winter, it was running F@H 24/7 on the CPU, OC to 3.0, without errors too.
It just seems strange that it would be so uber-stable, and now, two strange app errors in the span of two days.
I hope that the computer hasn't slowly been cooking itself. The PSU was really hot too, along with the northbridge. The GPU gets up to 74C, and the CPU (almost idle, 6% CPU usage for F@H GPU), is 60C. It gets up to 85C or beyond, when running both F@H on the GPU and CPU. That's why I stopped running it on the CPU.
I do have A/C in my room, I keep it at 70F.
Last night, installed F@H single-threaded client, when it downloaded and decompressed the computational core, it crashed. Running it again succeeded.
So I reformatted, and after the first pass of the Win7 install, it went fine, no problems. But when I stuck the 64-bit install DVD back in, at the windows desktop, it prompted me to run SETUP.EXE (or view files), I clicked to run SETUP.EXE, then it said something about an error loading autorun.dll. I tried it again, and it succeeded.
Does this sound like RAM? Or an unstable overclock?
When I installed my 8GB of DDR2-800 RAM, I did so with the 3.0Ghz OC, and I ran Memtest86+ overnight, with no issues.
I also did an hour test with OCCT, a few days after I overclocked, and also, no issues. I'm overclocking on stock volts.
The other desktop, an identical rig, did not pass OCCT, I had to bump up the vcore a tiny bit.
Also, I noticed when I took the computer apart, the northbridge heatsink was too hot to touch, and the HD's SATA connector on the drive was slightly loose.
I'm going to run another Memtest86+, and some overnight Prime95.
This rig has been running F@H 24/7 on the GPU without errors, and during the winter, it was running F@H 24/7 on the CPU, OC to 3.0, without errors too.
It just seems strange that it would be so uber-stable, and now, two strange app errors in the span of two days.
I hope that the computer hasn't slowly been cooking itself. The PSU was really hot too, along with the northbridge. The GPU gets up to 74C, and the CPU (almost idle, 6% CPU usage for F@H GPU), is 60C. It gets up to 85C or beyond, when running both F@H on the GPU and CPU. That's why I stopped running it on the CPU.
I do have A/C in my room, I keep it at 70F.
Facebook
Twitter