- Aug 28, 2006
- 6
- 0
- 0
Before anyone asks: Yes, I've trolled the forum for answers. Yes, I read the FAQ's. No, this is not my first system to build, nor my first to overclock. Yes, it's the first where I'm *really* paying attention to temperatures and stability.
E6600 (stock speed at the moment)
3GB (Would be 4GB, but Windows 32-bit apparently can't handle it!) Corsair TWINX2048-6400 (1GB DIMMS, DDR800) in asynchronus dual-channel mode (Didn't even know you could DO that, but apparently the P5W can..)
2 x Seagate Barracuda 7200.10 ST3320620AS (Perpendicular Recording Technology) 320GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM (Set up in RAID 0)
Sapphire X1900XTX 512MB
Memory is set to DDR-800 in BIOS, other than that, all "overclocking" options are untouched for the moment. I'm using the stock HSF, with AS5. It wasn't lapped or anything, I just scraped the crap TIM off and used the AS5.
Okay, so here's the temps (CoreTemp for CPU):
Ambient Room Temp - Around 75F, 24C
Idle 35C-39C The low end temps here are with my floor fan blowing.
Load 51C-54C
Orthos fails after about 2.5 minutes with the following:
1:FATAL ERROR: Rounding was 0.5, expected less than 0.4
1:Hardware failure detected, consult stress.txt file.
WTF, so there's something wrong with my system, right? Well, not so fast there..
This system was sitting at 2.9GHz for days, no problem. Been playing EQ2, encoding videos, and doing other various stuff, no problem. Runs 32M SuperPi (two instances, of course) and finishes no problem. Haven't tried MemTest yet, have to burn the CD, which is a PITA.
Keep in mind that every other program I run does fine at the overclocked speed, much less stock, but Orthos fails. Anyone got an explanation for this? A bug in Orthos, mabye? Oh, and there *is no stress.txt file anywhere on my computer, I looked for it*.
Any help would be much appreciated, thanks in advance,
You local n00b, CountryEvil.
E6600 (stock speed at the moment)
3GB (Would be 4GB, but Windows 32-bit apparently can't handle it!) Corsair TWINX2048-6400 (1GB DIMMS, DDR800) in asynchronus dual-channel mode (Didn't even know you could DO that, but apparently the P5W can..)
2 x Seagate Barracuda 7200.10 ST3320620AS (Perpendicular Recording Technology) 320GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM (Set up in RAID 0)
Sapphire X1900XTX 512MB
Memory is set to DDR-800 in BIOS, other than that, all "overclocking" options are untouched for the moment. I'm using the stock HSF, with AS5. It wasn't lapped or anything, I just scraped the crap TIM off and used the AS5.
Okay, so here's the temps (CoreTemp for CPU):
Ambient Room Temp - Around 75F, 24C
Idle 35C-39C The low end temps here are with my floor fan blowing.
Load 51C-54C
Orthos fails after about 2.5 minutes with the following:
1:FATAL ERROR: Rounding was 0.5, expected less than 0.4
1:Hardware failure detected, consult stress.txt file.
WTF, so there's something wrong with my system, right? Well, not so fast there..
This system was sitting at 2.9GHz for days, no problem. Been playing EQ2, encoding videos, and doing other various stuff, no problem. Runs 32M SuperPi (two instances, of course) and finishes no problem. Haven't tried MemTest yet, have to burn the CD, which is a PITA.
Keep in mind that every other program I run does fine at the overclocked speed, much less stock, but Orthos fails. Anyone got an explanation for this? A bug in Orthos, mabye? Oh, and there *is no stress.txt file anywhere on my computer, I looked for it*.
Any help would be much appreciated, thanks in advance,
You local n00b, CountryEvil.