RUnning the memory and fsb asynchronously doesnt do you any good. Your memory is puking out info at 166, but is returning to the CPU 133mhz...
Read over at anandtech, poke around the web... from what I have read, unless you get the fsb to 166, running the memory at 166 is pointless.
Benchmarks are like sex, everybody loves doing it, everybody thinks they are good at it.
Got my 7VRXP board w/XP1800+ yesterday, configured it and installed Windows XP with only one hitch (some rather poorly worded instructions for creating the driver diskette needed to install Raid 0 - my first RAID experience). When I get back home tonight and have access to my driver disk again, I'll post the right way to do it in case anyone else is having this problem.
Right now, I'm running the RAM and CPU synchronously at 133 Mhz (Ram at CL2.5), as I am still using my 2x256 MB Crucial PC2100. If others get better results as high quality CL2.0 PC2700 or PC3000 DIMMS become more plentiful and maybe come down in price, I'll consider upgrading the RAM. For now, however, it doesn't seem to me worth another $150 to $160 squeeze out less than a 5% performance gain. Heck, I wouldn't even have purchased the new board and CPI if I wasn't getting flakey performance out of my old MSI KT266/T-Bird 1.33 (if anyone wants this stuff cheap, let me know - otherwise it's off to EBay).
Will try more agressive memory timings and run some benchies after a burn-in period. So far, all looks good.