Long day's journey...

[[TPG]Grinder]

That's terrific to know, One. I'll look into how I can benchmark CoD2, as it is currently the only application I care about.

Strange thing...

I ran that long Orthos blend last night and when I got up this morning I shut her down and went to work. The wife beat me home and the computer wouldn't recognizing the keyboard when she booted up. I had to use the CMOS jumper on the mobo to get it back to recoginizing the keyboard at boot.

Now, I'll admit I was dinking around in the BIOS a bit last night, but I didn't change any setting related to boot, or the input devices. Could it have been the o.c. run I did last night?

Any thoughts on this one?

[Quakindude]

I'd be very careful about running that Ram above 2.3V. Ideally, 2.2V if you can push the FSB and tighten the timings down. I certainly wouldn't run it at 2.4V as One mentioned.

Using Windows Vista, my Corsair Ram was extremely picky about the FSB. Stability and boot-loops were the norm and I found myself running that kit at 1033FSB and 2.2V just to tone it down a little. I was able to tighten the timings to 4-4-4-14 at 1033FSB. I was able to scale my ram to 1157FSB error free for 8+ hours of Memtest, but anything over that and I'd get errors after 6 hours or so.

Using Windows XP Pro has been largely painless. However, the Memtest errors occurred at the exact same settings.

[[TPG]Grinder]

Thanks for the input, Dude.

I had a weird experience today. After last night's successful run of 6hrs21mins Orthos blend with the FSB at 1420mhz (3.2g), and the RAM at 1066megs (4-5-5-9 2T), I thought I had it licked. Then I boot the system after work and the BIOS has reset itself to 1066fsb and 800megs on the memory.

What might make a BIOS reset itself between boots like that? It's giving me brain damage.
:alberteinstein:
Thanks,
G