• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Barton Weirdness

Elfear

Elfear

Diamond Member
A buddy of mine has been attempting to oc his 2500+ Barton chip (early unlocked multi version) and came up with some weird results. He has the following setup:

Shuttle AN35N-Ultra
2500+ chip
Geil PC3200 2x512MB

If he drops the multi to x10 and bumps fsb to 200MHz than the board is semi stable, meaning Prime fails at random times and memtest gets a dozen errors or so after running overnight. It boots into Windows just fine but every few days he gets a bsod.

Well he tried just raising the multi to x12 and keeping the fsb at default and it's rock solid. So basically he's running the chip at 2GHz in both situations but with different results. The board and ram are rated to run at 200MHz stock so I'm not sure why one method would work and the other fail 😕. Any ideas?
 
I have that same board and mine will do 200 fsb no problem. I think it is likely he has a stick of defective RAM. Try running just a single stick to see if it will take it. The fact that PC3200 RAM fails memtest at 200 mhz makes me wonder.
 
The problem is not board specific, but chipset specific. Early revisions of the nForce 2 chips were simply not capable at running at 200MHz FSB. As newer revisions of the nForce2 chipset were rolled out the problem simply went away.

But yes, it could also be your RAM.
 
I thought the same thing but he said when he bumps the multi to x12 he runs the ram asynchronously and clocks it up to 200MHz. I guess that board has the option of actually increasing ram speed vs. fsb (?)
 
async+AXP=teh oh noes! Not a good idea to run async with a barton. The performance hit is def. not worth the pride. could try overvolting the ram or just the proc can't take it. IDK.
 
Well if the proc can't take it wouldn't it poop out when running 12x166 (~=10x200)? If the ram is running at 200MHz in both cases I don't see how it could be the ram. Maybe like WobbleWobble said, probably just an early board that can't handle a 200MHz fsb.
 
The problem is likely in the interaction of the mobo and ram. I had the same issue with my barton setup, unstable beyond 175mhz fsb on my asus A7N8X rev2.0 (which is supposed to run at 200mhz). I thought my PC3200 ram (rated for that board) was fine too, because it would run async at 200mhz without memtest errors. Turns out switching to Corsair LL PC3200 solved all the problems (well, sort of - stable to 198mhz 🙂. Strange I know, but some of those mobo/chipsets were fussy with ram.
 
You must log in or register to reply here.
Back
Top