ARGH!! My stupid new comp can't handle default clo

[prometheusdt]

it's with newegg's Adata 512mb pc3200 memory, biostar m7ncd (already flashed to latest bios), barton 2800 with <A HREF="http://www.supergooddeal.net/ebay/products/RW-2000-Black/pic07_l.jpg" target="_new"> this power supply </A>. it also has a 9800pro (cat 4.6), 160gig maxtor, floppy, and cdrw. it boots up fine and everything under 166fsb but it reboots by itself when i try to run 3dmark2003. i tried running sisoft sandra burn in test with the cpu but that failed after a few tries also. the cpu temperature though is low at about 45 C load with an alx800 and an 80mm case fan. weird thing is that it works at 165fsb but at 166 or above, it crashes. when i put on my vantec tornado that pushes 84cfm, it still crashes at 166 or above. so it seems like my cpu shouldn't be a problem. or can it? my agp is locked at 66. memory timing is at 7-3-3-2.5 and frequency is at 100%. does anyone know what's going on? btw, would it matter if my 512 (one stick) is on the first slot or the 2nd slot? also, why is it that when i set my fsb at 166, the POST screen reads the memory at 366. but when i set it to 165, 167 or 168, POST screen says DDR400? thanks for all of the help in advance.

 

[rook]

I would set the FSB to 166 and try <A HREF="http://www.memtest86.com/" target="_new">memtest86</A>.

<A HREF="http://www.anandtech.com/mysystemrig.html?id=23900" target="_new">System</A>
<A HREF="http://service.futuremark.com/compare?2k3=2072215" target="_new">3DMark03</A>

 

[prometheusdt]

it's at 166 and i ran memtest. ran it for an hour and had 3 pass and 0 errors. any other ideas?

 

[Crashman]

Try motherboard monitor 5, set it to record values to a text dolog every second for 60 records (1 minute's worth), then when it crashes check the log to see what voltage fluctuations were present.

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>

 

[prometheusdt]

do i do the interval log or the syslog? so i just enable one of these two and then run 3dmark?

 

[prometheusdt]

well, i switched the ps with the one in my current computer which i use to o/c a thoroughbred 2100 to 2.1ghz with a r9700pro and epox 8rda+. the same problem is still occurring. so that means the ram and the ps shouldn't be a problem. blah