5000 B.E. on M2N32-SLI Dlx Overclocked

[ghot]

ok 1st here is screen of current OC....
SYSTEM:

Windows XP Pro w/SP2......1603 Motherboard BIOS
ASUS M2N32-SLI Deluxe Wireless Edition AM2 NVIDIA nForce 590 SLI MCP ATX AMD Motherboard NEW version 1.04g
AMD Athlon 64 X2 5000+ Brisbane 2.6GHz Socket AM2 65W Dual-Core Black Edition Processor NEW
ZALMAN 9500A 92mm 2 Ball CPU Cooler 45 CFM at 27db (full speed) NEW
CORSAIR XMS2 (2 x 1GB) 240-Pin DDR2 1066 (PC2 8500) Dual Channel Memory Model TWIN2X2048-8500C5D NEW version 4.1
EVGA 256-P2-N758-TR GeForce 8600GT SSC 256MB 128-bit GDDR3 PCI Express x16 SLI Supported Video Card NEW
WD 36GB 10,000rpm Raptor SATA
Seagate 80GB 7200rpm SATA
Lite-On LTR-52246S CD/RW
Lite-On LH-18A1P CD/DVD Burner
PC Power & Cooling Silencer 750 Quad (Black) EPS12V 750W
ViewSonic G90FB Black 19" CRT Monitor
Generic Mid Tower case w/ 5x 80mm case fans [ 2x front intake, 2x rear exhaust, 1x left side exhaust]





SETTINGS YOU CAN'T SEE:

CPU vcore=1.5v, PCI-E bus (locked @ 100MHZ), Mem Clock Freq = (DDR2 800Mhz), NB to SB HT Freq. = (auto), CPU<> NB HT = 4x, SLI Ready Memory = (enabled / optimal / Max OC), trc = 3, Max Async = 8ns, Mem 2.1v

Idle temps: MB=27C, CPU = 30C
100&#37; Load temps: MB= 29C, CPU = 55C

I want to keep the CPU vcore at 1.5v but I also want to get 24Hr stable on Orthos Beta v0.41.110.18....As I ran Orthos I noticed this:

2hrs Core 2 leads Core 1 by 25s
3hrs Core 2 leads Core 1 by 47s
4hrs Core 2 leads Core 1 by 60s
5hrs Core 2 leads Core 1 by 75s
6hrs Core 2 leads Core 1 by 95s
7hrs Core 2 leads Core 1 by 130s
8hrs Core 2 leads Core 1 by 152s
9hrs Core 2 leads Core 1 by 166s

10hrs Core 2 leads Core 1 by 54s
11hrs Core 2 leads Core 1 by 60s
12hrs Core 2 leads Core 1 by 90s
13hrs Core 2 leads Core 1 by 100s
14hrs Core 2 leads Core 1 by 120s
15hrs Core 2 leads Core 1 by 135s

15:50 Illegal Sumout

Questions:
1. Why are the cores getting out of sync like this?
2. Why didnt the Cores come nearer together as they did at 10hrs, and instead give an Illegal Sumout at 15:50?
3. What can I adjust in the BIOS (1603) to fix this?
4. I know I got a sloppy CPU....but i do NOT want to raise the vcore!
5. Even at 1.55vcore it wont even post at 13x267 or 3.4ghz

Things I dont want to change:
CPU freq @ 267
CPU vcore @ 1.5v
CPU<>NB HT multi @ 4x
Mem Clock freq @ DDR2 800Mhz

I know this is a sloppy CPU (in this case) but is there ANY way to ...well....sync the Cores of the CPU without changing any of the settings I listed just above? I am convinced that the Cores being so far out of sync as the stress times increase...is causing the Illegal Sumout.

I've also noticed that, rounding errors are solved by memory settings and the errors that show large exponetial numbers are solved with a little CPU vcore.

The illegal sumout errors, however seems to be caused by a combination of CPU settings and memory settings. I know I could raise the CPU vcore and get a 24hr Orthos stable....but on air cooling I want to keep the CPU at 100% load at 55C.

Is there any OTHER settings that anyone could think of that would get me 24hr Orthos stable?

[ghot]

any ideas at all?

[Rammsteiner]

Cores, as far as I know, always run out of sync. One core handles background processes and the other one nothing. When you Prime it one core still puts a little bit of processing power into the little background applications so it can't put the full 100% on Prime. That's why after a while one core looks like 'faster'.

No idea what Illegal Sumout is. As it ran 15:50 hours Im pretty sure it's just because the delta became too high rather the PC is unstable.

Try to see how far your memory could go with 4-4-4 timings. Maybe it would work with DDR1066

[ghot]

It wont work on 1066 in BIOS because the motherboard is an 800mhz board...
If you notice in the screenie it IS running at 1066 (534 double pumped) on the 800Mhz setting. On this motherboard with this ram...it seems the only settings i can get and still keep the RAM at 534 is 12x267 for the CPU....13x267 wont post.

I agree that its a stable OC but I'd really like to get 13x267 which would give me 3471Ghz. If I use any other CPU freq besides 267mhz...things get really weird....aka.. Everest and CPU-Z don't report the same divider etc.

267Mhz IS my magic CPU number. 267x2=534x2=1066
...............................................267 x4=1068 HT speed

I get best memory bench from Everest at 267Mhz CPU freq. If i run at less than 534...memory bench suffers dramatically.....like 54.x ns latency etc.

Im a memory noob and this is my 1st OC ever! Well this is the result of 3 weeks of tweaking, posting, testing etc, on about 9 different OCing forums.
I wasted 2 weeks with a really sickly 5000 B.E. which really screwed up my understanding of OCing in general. I DID learn one very useful piece of information: For a dual core CPU from AMD....use Everest 4.20 Ultimate and note the individual core temps BEFORE you overclock....if the core temps differ by more than 1C-5C...just RMA them immediately. The 1st 5000 had core temp difference of 10C-15C and was really unstable when overclocked.

By checking the two core temps BEFORE you OC you wont void the warranty and will still be able to RMA the CPU.

Anyways...back to my problem.....how can I get this CPU to post and boot etc at 13x267?

[ghot]

Here maybe this will help you, help me......