Orthos - Hardware Failure Detected

[Matt18]

I just OC'd my c2d e6600 to 3.0ghz. Orthos ran for about 2 minutes and it said Hardware Failure detected but it gave me no further details.
The bios settings I was unsure of I left at Auto. Is there something I am overlooking. I am thinking my vcore might be to low for this chip...
A few other things I have noticed that have been weird:
Bios and ASUS probe report a much higher CPU temp then coretemp does. Coretemp is reporting a 32-33 idle while bios/asus probe is reporting 47. I think I read this is normal and I should truse Coretemp?

CPUZ is report a multiplier of 6, but once I start running orthos it changes to 9. Everything else is still showing the CPU at 3.0ghz(system info and coretemp)

Please let me know if you need any further info. I just did a bunch of cooling updates(Thermaltake big typhoon and lots of case fans) and I really want to start pushing this chip.

Here are my BIOS settings:
Jumperfreee config:
cpu freq - 333
dram DDR2 - 833mhz
PCI-E - 100
PCI Clock Sync 33.33mhz
Spread Spectrum - Disabled
Mem volt - 1.8v
CPU Vcore 1.25
FSB Termination Volt - Auto
NB Vcore - Auto
SB Vcore - Auto
ICH Chipset Voltage -Auto

CPU CONFIG:
cpu ratio setting - Auto
C1E Support - Auto
Max CPUID Value Limit - Disabled
Vaderpool - Disabled
CPU TM Function - Enabled
Execute Disable Bit - Disabled
Speedstep - Disabled

CPUZ:

Processor 1 (ID = 0)
Number of cores 2
Number of threads 2 (max 2)
Name Intel Core 2 Duo E6600
Codename Conroe
Specification Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
Package Socket 775 LGA (platform ID = 0h)
CPUID 6.F.6
Extended CPUID 6.F
Core Stepping B2
Technology 65 nm
Core Speed 1996.8 MHz (6.0 x 332.8 MHz)
Rated Bus speed 1331.2 MHz
Stock frequency 2400 MHz
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T
L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 4096 KBytes, 16-way set associative, 64-byte line size
FID/VID Control yes
FID range 6.0x - 9.0x
max VID 1.213V

[Kursah]

Increase Vcore, what is the stock rated vcore for that proc? My e6300 is 1.32v @ 1.86 (good for up to 3.36 though).

That's the primary reason for Orthos failure in my experience.

Also I would disable TM and C1E unless you like power saving features...you should be okay...that could also be leading to issues though. I would also start with setting your MB voltages to their minimal ratings.

My P5B Dlx is great to OC with...I leave ICH voltage on Auto, but that's it.

[Kursah]

As-far-as temps are concnerned, depending on your bios (if not newer than 1216 in my findings), enable PECI under CPU properties for more accurate TCase and Core readings from CPU.

Also, I have a demo of settings I was using for my OC when I created my guide, take a look at them. (Link in sig...OC is Easy!....), that may give you an idea of how I oc'd my rig. I have a slightly different strategy to keep my 6300 solid at 3.5, but nothing really major.

:toast:

[Matt18]

Thanks Kursah, Your the reason I wanted to start OC'n this bad boy to begin with.

I think the stock vcore is 1.3-1.35.

"I would also start with setting your MB voltages to their minimal ratings."
- I was having trouble finding these settings which is why I left that at auto. Should I just select the lowest voltage option it offers in bios?

I already read most of your guide - excellent btw.

[Kursah]

:D

That's how I started, the only thing I raised was the FSB Termination V, set to 1.300v, the rest are at minimal. If unstable, take NB up from 1.25 to 1.45v first. But really, my rig is stable up to 500fsb with mostly minimal voltages, results may vary though.

And if you get in a no boot situation, just turn off the PSU for 30 seconds, turn it on, push the power button, and you should be able to press F1 at POST screen (should have a message) to re-enter your settings.

:toast:

[Matt18]

Thanks, You da man! I just got everything changed so I will see what happens. Is orthos still the best for stressing the CPU? Should I use TAT?

[niko084]

Orthos is the best for testing to see if your processor is performing perfectly.

I had my e6750 clocked to 3600 at stock voltages would seem fine for me for hours running things, but after 5 minutes of orthos you would see an error.

It's great! Odd's are a little voltage or a little knock back in the clock should fix it.

[Kursah]

I use Orthos for CPU stress testing, TAT for max temp findings that nothing else can match...so TAT's more of a gimmick thing imo. Where Orthos like Prime95 analyzes your CPU's results to verify it's working correctly.

Good job Matt18, I might have made some suggestions, but you had to make it happen!

I also agree with Niko, but I'm too picky...I had a P4 rig that would fail Orthos after a few minutes yet was stable in everything else...eventually I downclocked till I was Orthos stable with the P4 rig. My C2D will be Orthos stable, it's a personal preference. My rig is over 24 hours Orthos and Memtest stable...which makes me feel better about my overclock.

Everyone has their own preferences though. :toast:

[Matt18]

Well what suggestions would you have made?

[Kursah]

I use Speedfan/Everest for my temps, ATI Tool for Vid Card duties and monitoring.

Orthos Prime, Small FFT's, Priority 9 for CPU Stress and Stability Verifacation, If it can pass overnight (6-8hrs), you're good to go, I let it run over 24hrs just for my own preferences.

I use Memtest for Windows as my up-front Memory tester authorization, if it fails, then I'll use the boot Memtest. If you have 2 gigs, you'll have to run two instances, which the program is able to do by just double clicking the icon again. It'll tell you how much to type in for testing. It can't test what's loaded, ie windows, services, etc, but I can test about 860mb per Memtest Instance, also let it run overnight, it'll keep making passes (read in %), will show # of errors found, just ensure it's 0 after an overnight pass and you're okay.

Aside from that, then once I decied I was at a prime OC, I would see how low I could run the fan speeds and still be 55C or less on CPU load.

Any other questions?

Also, feel free to e-mail me, Kursah@yahoo.com with any questions you may have. I'm off to bed here shortly...but I will try to check back tomorrow!

:toast:

[niko084]

My only issue I would have on my system when it was clocked and failing on orthos was after about 2 hours of a game of Supreme Commander, the game would just lock up and close.

Only issue I actually had, but IMO any error is too much, never know when something might go wrong outside of a silly game and cause you to lose like 4 hours of homework you forgot to save.

[Matt18]

Well, Orthos ran smooth for about an hour(I know its not long enough). But I keep getting a "burned failed" error about 3/4 of the way through the burning process of copying a dvd. I lowered the bus back down and everything went smooth. I guess I need to up the voltage to the cpu or memory. Thanks for your help guys.

Is there any problem w/ having my burner and harddrive on the same power cable? They are both sata.

[Kursah]

The power shouldn't be an issue really, neither should draw a significant ammount.

You may try increasing your SB voltage when you overclock as that controls PCI-E, PCI, SATA, etc...

Also, ensure you run a memtest to verify your memory is stable, like I recommended earlier...trust me, it's worth it.

Glad to see you are successfully overclocking man, good job! It takes practice and every system will react differently, you just gotta learn what your system is willing to give for certain settings, it takes time, but you'll get there.

[Dr. Spankenstein]

His G-Skill is overclocked by 33MHz @ 1.8v. Maybe that could use a bump. Have you tested it w/Memtest?
Is this perhaps the ZX kit?

[Matt18]

This is the ram: http://www.newegg.com/Product/Product.asp?Item=N82E16820231098

I bumped it up to 1.85v, but when I lowered the bus I switched the memory back to 900mhz. It was stable at that for a long time (prior to the recent overclock).

My thoughts were memory as well since copying a dvd doesn't use much of the cpu.

[Dr. Spankenstein]

Yeah, that kit is labeled 800MHz 5-5-5-12 @ 1.8-2.0v. You are running it @ 900MHz now...is there is future instability, you are going to want to give it the full 2.0v.

I still would suggest booting to Memtest and letting it run a few passes to make sure it's stable.

Glad to hear you got it working again!:toast: