• 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.

My Overclocking the T-bred 1700+ thread :)

Frosty3799

Diamond Member
Ok, I just got my CPU yesterday, and have been doing some overclocking.

MY components are:
AMD XP 1700+ Thoroughbred core
Epox 8K5A3+
Mushkin high performance cas 2-2-2 pc2700 DDR

Throughout all of these overclocks, I have the DDR Ram on TURBO timings with everything at the fastest command rate, and also the Ram and CPU are running in sync (i.e. both at the same fsb speed)

Here are some WCPUID screen shots I have taken:
So far, my highest OC I managed was this: Highest OC

It failed the first test in Prime95, but ran easy stuff like internet explorer and trillian AOK

The speed I am at now, and burned-in overnight w/ no errors is this: Current OC

That's not too bad if you ask me 🙂

The system will run with the FSB up to 210, but 3DMark doesn't run successfully... If I had another divider for the AGP/PCI then I would be able to squeeze a little more out of this setup... Anyone know if there is a way to lock the ZGP/PCI clocks with this Epox board?

thanks
Josh
 
Throughout all of these overclocks, I have the DDR Ram on TURBO timings with everything at the fastest command rate, and also the Ram and CPU are running in sync (i.e. both at the same fsb speed)

There is your first mistake!!! Run memory at conservative timings at first so you can truly isolate the cpu to determine its true limit...I am starting to sound like a broken record....hmmm 3dmark fails!!!!😉
 
Originally posted by: Duvie
Throughout all of these overclocks, I have the DDR Ram on TURBO timings with everything at the fastest command rate, and also the Ram and CPU are running in sync (i.e. both at the same fsb speed)

There is your first mistake!!! Run memory at conservative timings at first so you can truly isolate the cpu to determine its true limit...I am starting to sound like a broken record....hmmm 3dmark fails!!!!😉

Duvie, 3DMark doent fail until 210 fsb, at 200, my current settings, it runs grrreat.

The thing is, I would drop the ram timings down, but I don't need to 🙂 I am hitting the roof of my video card speed/ OC by bus before I am hitting the roof of my ram.

I need a AGP/PCI lock
 
Back
Top