- Jun 30, 2004
- 16,593
- 2,002
- 126
First -- I completely agree that my rig is at least a generation old. It's Intel. It's a single-core Prescott. But the board is a good over-clocker, and the memory modules are rated at DDR500 with very competitive latencies -- for those speeds anyway.
It's been a great video processing system, and I occasionally play some games with it. And until the income from my rental property has resumed flowing again, I'll be hard-pressed to shell out for an SLI-based system -- or the Athlon 64 X2 it will use.
Meanwhile --
I was experimenting with over-clock settings, VCORE settings and MEMTEST86. I had been too cautious previously in setting the VCORE, and have now discovered that I can run the VCORE up to as much as 1.42V on my P4P800 SE mobo without much risk to the processor.
So I decided to disable the ASUS "Lock-Free" mobo feature, over-clock the FSB without underclocking the CPU multiplier, and found a nice, stable setting of about 3.74 Ghz (with a 3.2E Prescott) where the memory runs at DDR468, or an FSB of 936 Mhz. I figured that the L2 cache-size of 1MB would probably compensate for a slightly slower memory setting.
I ran MEMTEST86 all freakin' night without errors. Something like 20 iterations on the tests, and with the VCORE set only to about 1.4125V .
So I try to boot into Windows. Error messages post about the Winlogon.Exe program failing to recognize hardware -- unable to validate activation -- and the system either crashes or makes it impossible to logon.
I tried dropping the external frequency to 230, lowering the CPU speed to around 3.6 Ghz, and the system actually boots, but my AV software reports a failure to load some DLLs, and refers -- again -- to "an activation" problem.
Anyone have any suggestions? I KNOW I've seen people discussing this issue before . . . . .
It's been a great video processing system, and I occasionally play some games with it. And until the income from my rental property has resumed flowing again, I'll be hard-pressed to shell out for an SLI-based system -- or the Athlon 64 X2 it will use.
Meanwhile --
I was experimenting with over-clock settings, VCORE settings and MEMTEST86. I had been too cautious previously in setting the VCORE, and have now discovered that I can run the VCORE up to as much as 1.42V on my P4P800 SE mobo without much risk to the processor.
So I decided to disable the ASUS "Lock-Free" mobo feature, over-clock the FSB without underclocking the CPU multiplier, and found a nice, stable setting of about 3.74 Ghz (with a 3.2E Prescott) where the memory runs at DDR468, or an FSB of 936 Mhz. I figured that the L2 cache-size of 1MB would probably compensate for a slightly slower memory setting.
I ran MEMTEST86 all freakin' night without errors. Something like 20 iterations on the tests, and with the VCORE set only to about 1.4125V .
So I try to boot into Windows. Error messages post about the Winlogon.Exe program failing to recognize hardware -- unable to validate activation -- and the system either crashes or makes it impossible to logon.
I tried dropping the external frequency to 230, lowering the CPU speed to around 3.6 Ghz, and the system actually boots, but my AV software reports a failure to load some DLLs, and refers -- again -- to "an activation" problem.
Anyone have any suggestions? I KNOW I've seen people discussing this issue before . . . . .