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

Chaintech vnf3-250 bios 3/21/2005 no cpu volt adjust?

jazzisjazz

Senior member
I don't see the cpu voltage adjustment.

this is a vnf3-250 "zenith value edition" . Should it be there?

I am trying to clock a sempron 2800 256k palermo core.

The bios is dated 3/21/2005 and I know there is a later one.

I see the adj for chipset , agp and memory.

I just want to be sure that I'm not missing something.

.

jazzisjazz
 
Hmm, Chaintechs are usually good overclockers... The regular VNF3-250 has an option to select up to 1.7V in the BIOS...

This review shows you the screen... It would however seem strange to me if the newer BIOSes lacked the CPU Voltage Regulator option...

Fiddle with BIOSes maybe, the review takes on 1.0, and this one has the option...
 
I'm pretty sure I updated to latest BIOS on my VNF3-250 and still had vcore, but I was using a Newcastle chip. I'm wondering, perhaps vcore is disabled if you have a 90nm chip installed. I recall some P4 motherboards being that way initially, with vcore for Northwoods but not for Prescotts.

EDIT: I have a Semrpon 2600+, will put that in my Chaintech and see... when I get a chance.
 
zap

Let me know if it's there when you do.

Everything i've seen so far tells me that at least with this cpu,
i'll need to go back to an older bios to get vcore adj
unless i finds a modded one.

I'll keep looking.

 
A pic of my board is at this link. I've already pulled the board to upgrade my wife's computer to a socket 939/PCIe setup so the board is free for my pleasure. :evil: I just have to switch back to the standard HSF mounting... will report back.
 
My BIOS is dated 09/16/2005
VN61C120C-00

WTF!!!! No VCORE.

With "Voltage Fine Tune" enabled, I get AGP, DIMM, CHIPSET.

The reported CPU VCore in PC Heath Status is 1.40-1.42v so it may be overvolting a hair. My default is 1.40v D0 stepping.

Another thing interesting is that the system will POST easily enough at 300MHz bus, but won't POST at 301MHz. One time at 300MHz I got BIOS corruption, so may have to increase chipset voltage or something. I have RAM set to 133, so it is running at default DDR400 with default latencies, except had to manually set 1T timing. HT set to 3X. Will do some memtest/Prime at 2.4GHz/300MHz and see how stable it is.

My CPU is the top one listed.

BAH, as I'm typing this, got massive BIOS screen corruption, so 300MHz is a no go. It also won't boot off IDE devices at that speed, locks at Verifying DMO Pool Data and can't even CTRL-ALT-DEL. I really should try this CPU in my Epox board, but will be a pain to remove that Tt Silent Tower HSF...

At 295/2368MHz, fails Prime immediately (running off UBCD).

At 290/2328MHz, fails Prime immediately.

BAH#2, now my oolong tea has gotten cold messing with stuff.

At 285/2280MHz, fails Prime immediately.

At 280/2248MHz, fails Prime immediately. This is with CHIPSET voltage set to maximum 1.9v. This also is getting old.

At 275/2208MHz, does NOT fail Prime immediately, but did afer a few seconds. We're getting close!!!

At 270/2168MHz, passes first test in Prime... so far. My gawd, watching Prime is like watching water boil with the exception that water eventually boils if you remember to turn on the proper burner.

I'm wondering, does the CPU need more vcore? Is it just a limitation of the motherboard? If I continue to be bored I'll dust off that Epox board... otherwise I'm gonna go play some Enemy Territory now.
 
Just set all voltages to default and started Prime again, still passing... either the CPU needs more volts or this board just doesn't like above 270MHz system bus. I'm wanting to believe the latter because at higher speeds I get BIOS corruption, but won't know until I can test this CPU on the other board.
 
Sounds familiar. I followed an overclocking guide for this board and began by setting HTT multiplier at 3x , selecting 100 for memory and raising HTTbase frequency to 260 fine, 270 booted but with incorrect memory freq display same way up to 300

tried 310 and board would lock and no ctrl/alt/del had to shut down and reset with bios jumper.

I am supposed to search for max memory speed next but wanted to have voltage bumped to make sure I would have seen the max on the cpu frequency first and to have other settings in the ball park of their final values.

I noticed that the chipset gets rather warm so I put a 40x10mm fan which keeps it very cool. I'm using a Hyper 6 original on the cpu and temp have never been above 45C so far.
 
EDITED: January 9, 2005 to correct statements that were, bluntly, wrong.

I also noticed, with no modicum of chagrin, the lack of Vcore adjustments in the BIOS and think we ought to bombard Chaintech with highly indignant emails (I am however aware of the Clockgen utility for non-BIOS overclocking). Maybe if we started a "Boo Chaintech Wimps" thread it might get their attention. I personally would be satisfied if they re-instated Vcore adjustments but limited them to, say, 10-15% over stock for the E6 core. It would also be nice to be able to turn off the on-board LAN in the BIOS.

I'm running a recently-acquired "pre-owned" VNF3-250 (using it for this reply). Processor is a 1.4GHz Sempy 2500+ (remember "Celery" and BH6?), Palermo E6 core. Memory is a single 512MB stick of inexpensive Nanya PC3200 rated at 3-3-3-8 @400MHz DDR. Like "jazzisjazz" above, I installed a fan (about a 45 x 45 x 10MM) on what I call the "onebridge" (the nVidia nForce 3 chip) - think this is a "must" addition, ESPECIALLY if stability testing with PRIME95.

However, while closely reading an xBit Labs writeup (Another Gift to Overclockers: AMD Sempron 3100+ on E Core Revision) on the 3100+ Sempron (Palermo E3 core), I noticed that 88% of the frequency delta they obtained by overclocking was achieved at ==>default<== Vcore. But regrettably, the xBit Labs article did not report stability testing results for the portion of the overclock that was achieved using default Vcore.

My observations so far:

(1) DON'T USE THE 1T MEMORY SETTING ON THIS BOARD. From other threads I've read on AnandTech, it doesn't buy you much in terms of performance and from personal experience I think it could cause grief. The first of two lockups I've had (during about 24 hours of running) came at a mild overclock frequency of 1680MHz (240/166) and "stock" 400MHz memory timings, with the 1T setting on. That lockup came while I was installing Adobe Reader with several copies of the IE browser running at the time (admittedly not best software installation practice). After that lockup, Win2K/Scandisk had to repair some files during the boot (running FAT32 for reasons too lengthy to elaborate). If memory serves, the second lockup came shortly after while simply surfing @ stock frequency and memory settings, again with 1T on. I can't rigorously prove that the 1T setting caused the problem but my gut feeling is that the 1T setting is essentially a needless risk that common sense dictates should be avoided. So call me a 2T convert.

(2) When overclocking, set Tras to 10 or so - at least for memory like mine, and as suggested by AnandTech articles/reviews. Edit: March 10, 2006. For about 3 weeks I've been running at Tras = 8 (default for my memory stick at 200MHz), at memory frequency, after divider, of 200MHz / 400MHz DDR. No adverse consequences to date...

So far I have booted, surfed the net, and run SiSoft Sandra 2005 Lite at 2.1GHz, @ default Vcore of 1.4V (300MHz processor / [133MHz-->200/400MHzDDR memory] / 7x multi). The Sandra FPU score blew my mind at 4280 MFLOPS - beating a $230 P4 550 and also beating an OC'd Tbred "B" I own clocked at 2.3GHz (DLT3C JIUHB 0320: 11.5 x 200MHz @ 1.65Vcore) which scored 3635 MFLOPS on the same bench.

I plan to run PRIME95 @ highest heat settings at some point but first want to give the AS Ceramique thermal compound I'm using some time to cure. BTW, I'm using a stock HS/fan - have read about other Sempies at or above 2400+MHz using the same retail cooling.

Will post stability testing results if others are interested.....
 
I'd like to echo some of Edzard's statements. For reference, you CAN use an earlier bios...that doesn't properly recognize the 90nm semprons but will allow you to adjust the vcore. When initially overclocking my sempron 2800+ vnf3-250 combo with 2x512CVR I had this bios installed. I had a speed goal of 2.2ghz. After surpassing it on stock vcore, I installed the latest bios. I settled at 2320 (290 x 8, default vcore) with my ram running at 193mhz (2.5-3-3-10, 1T, 2.7v) HTT bus 3x290=870 and stress tested it. Prime blend 20hrs, 12hrs small FFTs. I was pretty happy with these results...but became a bit greedy last night and tried to even things out a 2.4 200memory.

I walked away while priming and found the system stuck in standby when I came back a little while later, so just reverted to earlier settings. However, that doesn't mean I met the top end of the cpu at 1.4v. I'm running 1.7 chipset voltage at 290, and the hyper transport bus was already overclocked at that speed. Dropping the Hypertransport bus multiplier down to 2x instead of 3x or increasing the chipset voltage could both solve the problem. Since I saw no indication of having hit the cpus limit in testing I think those things are more likely culprits. The only time I had ANY stress test failure during the overclocking phase was when the bios automatically set aggressive ram timings in response to me using a lower divider setting. Its also possible that 1t operation causes problems on this board like Edzard suggested and that the reason my ram is stable is that its running slightly underclocked with a bit of a voltage boost. Of note is that in earlier bios revisions 1t was standard, but in later revisions chaintech saw fit to change 2t to the default.

I haven't decided if I want to try again for 2400 in a more serious manner. I *did* meet my goal and stability testing is done. Plus, the temp readings on this board seem unchanging even with the latest bios so I don't feel like I really know how hot things are running on stock cooling with AS5. I may just wait until summer when I plan to run an additional stability test. Its pretty cool here now so its hard to tell if its REALLY stable in the worst conditions.

It DOES seem stupid they don't have vcore for the new semprons. And I REALLY hate that there's no way to disable onboard LAN in the bios, as I prefer to use a 3com NIC for my lan and was forced to disable the other NIC in device manager. But as Edzard pointed out you can get quite a bit out of these sempron chips most of the time at stock vcore anyway.
 
Originally posted by: Zap
I'll dust off that Epox board...

Running the Sempron on the Epox 8KDA3I board now. The board recognizes the CPU as a 64 bit Sempron. WTF? CPU is a SDA2600BABOX, supposedly 32 bit only. My BIOS is dated 08/15/05 but looking at Epox site and don't see it. Epox USA site is down or something so I was looking at the international English site. The BIOS allows for vcore up to +.30v over. Set to "default" of +0.00v gives me 1.48-1.49v, so this board overvolts. Currently it is idling at 300MHz bus - 2.4GHz at 35ºC. All I did was drop the memory and HT, raise the system bus MHz to 300. No sweat. The Chaintech board would not POST at that speed. Don't know if it was because of CPU voltage so I'm gonna go run Prime... no go, didn't even start but immediately gave a "kernel panic." Raising chipset voltage gives me another error. Raising CPU voltage +0.10v... it is passing Prime. Time to lower chipset voltage... seems okay. Alright, seems like my particular CPU needs voltage and the Epox board will give it but the Chaintech won't.

Perhaps the Chaintech is good at higher bus speeds as well, but since my particular CPU needs the volts to hit 2.4GHz I won't know. My Newcastle 130nm 2800+ A64 can run stable at 2.4GHz on default 1.5v. What's up with this Sempron 90nm needing more voltage to hit the same speed? Perhaps board is detecting it wrong...
 
Zap -

With regard to your comment "The board recognizes the CPU as a 64 bit Sempron. WTF?"

Refer to the link you posted earlier for your proceesor specs. That link appears in your post above bearing the date/time stamp of 12/31/2005 11:24 AM. You stated in that post that your processor is "the top one listed" and indeed that is consistent with the PIB code of SDA2600BABOX you posted on 01/16/2006 03:50 PM.

But note that (1) the processor described in the BOTTOM of the two processor descriptions shown at your link states "32/64" and (2) the Ordering P/N (Tray) number, SDA2600AIO2BA is the SAME for both processors, and THAT is the code that is printed, during manufacturing, on the PROCESSOR itself. So unless there is some other code on the processor that differentiates between the two, it would be darn difficult to sort them for boxing.....

Here's what I think based on what you've said. (1) The tables are wrong and the "64/32" belongs in the SDA2600BABOX description of the processor or (2) you somehow goofed and reported the wrong box code or (3) there was a boxing error at the factory and your processor should have come in a box bearing a box code of SDA2600CVBOX [assuming no error in the AMD table] or (4) there was a boxing error at the factory and you actually have an E3 or E6 core [well-documented as supporting both SSE3 and 64-bit] - in which case the box code should have been SDA2600BOBOX or SDA2600BXBOX or (5) the EPOX BIOS is wrong or (6) something else [when conjecturing, I always include "something else"]

To shed more light on the enigma, I suggest you download and run CPU-Z (Version 1.31 or higher). Look for "x86-64" in the "Instructions" line CPU-Z reports under the CPU tab. If you see "x86-64" (64-bit support) in the "Instructions" line, I think you'll see SSE3 support there as well since support for SSE3 allegedly preceded support for 64-bit. It would also be extremely illuminating to look at what CPU-Z reports for the "Revision", which is the stepping. Theoretically, the "Revision" for your chip, according to the info you supplied, should be D0 (as per AMD's table). But heck, based on what I've read at xBitlabs.com, if the core is indeed D0 it "shouldn't" have support for either SSE3 or 64-bit. So in this particular case, (specifically the XP2600+ processor with D0 revision/stepping), xBitlabs and AMD are at odds regarding what D0 supports.

Given the 08/15/2005 date of your BIOS and the "October 2005" date appearing at the top of the pictures of your system, and assuming your system was built between those two dates, and assuming you bought the processor new, my best guess is that your core is either E3 or E6, both of which support 64-bit computing (if I can believe AMD).

My guess is actually most heavily supported by the 08/15/05 date of your BIOS. I think it is correctly identifying your processor. AMD was making 64-bit Semprons at least as early as week 19 (May) of 2005. I know that with certainty because I have two E6 Sempron 2500+ processor that each bear a manufacturing date code of "0519" (week 19 of 2005). The Ordering P/N (Tray) number is SDA2500AIO3BX on both processors, which indicates the E6 core. And CPU-Z reports both processors as having the E6 core. That implies that, if AMD gave the motherboard makers a "heads up" on the introduction of the new cores, EPOX and the other board makers had at least two months of time in which to have new BIOS versions ready by August 2005.

PLEASE report what CPU-Z shows for your "Revision" code.

With regard to your comment

"Set to "default" of +0.00v gives me 1.48-1.49v, so this board overvolts",

how do you know the board "overvolts."? Is that "1.48-1.49v" a BIOS readout, which may or may not be correct, or did you read the voltage independently with a meter?

Re your Chaintech VNF3-250, I noticed you had set memory timing to 1T. Highly recommend 2T - read my earlier post for why. Also suggest you read the last sentence in the second paragraph of PingSpike's post. If you have consistently used 1T timings that may be the reason you are not having great success OCing the VNF3-250.

Two days ago, with the following settings, I hit 2296MHz (7 x 328) on my VNF3-250, at default Vcore, using one of my Sempron 2500+ processors, E6 core, one 512MB stick of budget Nanya PC3200 memory (stock 3-3-3-8 at 200MHz and set at 3-3-3-10 for the overclock).

CPU: 328MHz
Memory: 133MHz
HT: 3
Mem timing: 2 <====

At 2296MHz I booted Win2K, ran CPU-Z, SiSandra 2005 Lite, but no PRIME95. A bit too scary to run PRIME95, especially given the questionable BIOS temperature readouts. This is, after all, my primary PC and I've probably taken too many chances already.....


 
Apologies for getting back to this at such a late date. Was busy (starting classes, etc) and just got time to mess with stuff. The setup is just a pile of parts so I have to get it put together enough to run. Using UBCD for Prime and WUBCD to get into a Windows environment to run CPU-Z

Originally posted by: Edzard
PLEASE report what CPU-Z shows for your "Revision" code.
SSE3 - no
x86-64 - YES
Revision D0

Bonus! Not that I have any need for 64 bit at this time... Don't know about SSE3, but it makes sense that 64 bit is supported because both CPUs listed at AMD's site (in the link above) are the same tray P/N, meaning they are the same CPU. I guess in the retail box they initially didn't publicise it as having 64 bit to further distinguish it from the Athlon 64, but then after Intel Celerons started to support 64 bit, these Palermo Semprons "magically" became 64 bit capable just by some new printing on the box. Indeed the tray P/N SDA2600AIO2BA is on my CPU core, just as it should. That's probably also why AMD lists both retail boxes under the same page (other ones for 2600+ are distinctly one listing per page).

Are the E3/E6 cores newer/better? Mine being D0 could be why I'm not getting any huge clocks out of it.

Originally posted by: Edzard
how do you know the board "overvolts."? Is that "1.48-1.49v" a BIOS readout, which may or may not be correct, or did you read the voltage independently with a meter?
This is from BIOS. I do have a multimeter but don?t know where to check on the board, plus the tips aren?t very fine so I would be concerned with shorting something out. At this point it isn't too important to me.

Originally posted by: Edzard
Re your Chaintech VNF3-250, I noticed you had set memory timing to 1T. Highly recommend 2T
Just tried it (even down to using one stick of RAM like you are) and didn?t get any higher overclock. At 280Mhz bus still fails Prime immediately. Used one stick of Corsair ValueRAM 1GB at CAS 3, command rate 2T, 133MHz (2/3) so it was even underclocked.
 
I just tried my A64 2800+ in the Chaintech board and it also won't OC as high as my Epox board. On my Epox board the CPU will POST at 2.7GHz while it won't on the Chaintech. However, I'm able to lower the CPU multiplier to 5X (default 1000MHz) and it seems to run fine set to 300MHz (1500MHz) so both Chaintech and Epox boards seem reasonably happy at that bus speed. For my particular two CPUs (A64 2800+ Newcastle and Sempron 2600+ Palermo) I'm able to hit a higher overclock (both suicide POST and stable Prime) with the Epox board. I chalk up the variance as just "one of those things" with overclocking.
 
Zap -

Here are the facts regarding your Sempy 2600+ as you have reported them in this thread:
Box code: SDA2600BABOX
Tray code printed on processor: SDA2600AIO2BA
Stepping code: D0
64-bit capable: Yes

Between your observations of your Sempy 2600+ and from AMD via your earlier link:

http://www.amdcompare.com/us-en/desktop/details.aspx?opn=SDA2600AIO2BA

we know that processors bearing the tray code of SDA2600AIO2BA may or may not support 64-bit.

And now we know from your observations that processors that came in a box having a PIB code of SDA2600BABOX MAY support 64-bit. From doing a bit of surfing, I have found that others have made that same discovery. Your case is not unique. See:

http://forums.amd.com/lofiversion/index.php/t55733.html

With respect to:

Originally posted by: Zap
these Palermo Semprons "magically" became 64 bit capable just by some new printing on the box.
Here's my own guess as to what happened.

A manufacturing change was indeed necessary to implement 64 bit support. It was made in the fab during the period of the D0 stepping, which preceded E3 and E6. It is very possible, even likely that 64 support was available but had to be essentially unlocked. The change was made perhaps by discontinuing the cutting of a bridge or bridges by a laser? Pure speculation (with regard to bridges) on my part, but it has the implication that it might be possible to rejoin those (hypothetical) bridges on older non-64 bit Semprons to obtain 64-bit capable Semprons. But I digress - the point is that a manufacturing change of some kind was likely made at some point in time to implement 64-bit support and that transition was made during the reign of the D0 stepping.

BUT the inventory of BOXES bearing the code of SDA2600BABOX probably hadn't been exhausted at the point in time when the manufacturing change to 64-bit was made. The change was made on short notice in a scramble to react to Intel's 64-bit Celeron. Rather than discarding usable boxes, AMD just went ahead and depleted that box inventory by using them to box the 64-bit capable processors. As that supply of boxes was being exhausted, the new boxes bearing the box code of SDA2600CVBOX were being made and AMD began using them when all the "old" boxes had been used.

Or perhaps there was just a foul-up at the factory due to the fact the tray code of SDA2600AIO2BA is the same for both variants of the processor, as I mentioned in an earlier post.

My "box inventory" theory gains somewhat firmer ground if indeed the box code is printed directly on the box itself, and NOT on a label that is AFFIXED to the box. You can shed some light on that.

With regard to:

Originally posted by: Zap
Are the E3/E6 cores newer/better?
The E3/E6 cores are for sure newer and allegedly better, at least according to the following statement:

"E core revision supports SSE3 instructions and boasts slightly upgraded memory controller compared with the memory controller used in D core revision."

that appears on the following page:

http://www.xbitlabs.com/articles/cpu/display/sempron-3100e_3.html

But if AMD's processor tables can be believed, the following XbitLabs statement made on that same page,

"As for the AMD64 technology support, Sempron processors based on the E revision of Palermo core do not have it, either."

is absolutely wrong. According to the table at:

http://www.amdcompare.com/us-en/desktop/default.aspx

EVERY Sempron E core, be it E3 or E6 supports 64 bit. And I think both cores support SSE3 as well. So the E6 core may just contain bug fixes, when compared to E3.

Finally, FYI, there were actually THREE "D0" revisions/steppings (and that lends further credence to my "manufacturing change" theory):

SH-D0
DH-D0
CH-D0

and D0 appears to be unique in that multiplicity. See page 13 of:

http://www.amd.com/us-en/assets/content...e/white_papers_and_tech_docs/25759.pdf






 
This is an interesting thread. So, mine is Winchester based - explains lack of SSE3.

BTW, the OP of that thread also got to 270MHz bus - dunno what mobo he's using but that's the same as I got on my Chaintech board.

Originally posted by: Edzard
My "box inventory" theory gains somewhat firmer ground if indeed the box code is printed directly on the box itself, and NOT on a label that is AFFIXED to the box. You can shed some light on that.
Yes, the codes are on a sticker. The box also does NOT have that "64" on the lower right corner like the ones that "officially" support 64 bit.

Originally posted by: Edzard
The E3/E6 cores are for sure newer and allegedly better, at least according to the following statement:

"E core revision supports SSE3 instructions and boasts slightly upgraded memory controller compared with the memory controller used in D core revision."
*SIGH* ahh well, it was über cheap - guess I shouldn't complain. 😛
 
Zap -

The originator of that thread was using an ASUS K8N motherboard - that's buried in the interior of the thread (someone asked her/him).

If you are running at 8 x 270 = 2160MHz you can console yourself with the knowledge that you can easily beat a stock $120 Sempron 3400+, and you have the 64-bit support to boot which could come in very handy later on.

And according to what I've read, SSE3 support buys one very little. No great loss.
 
Zap-

Something just occurred to me. The ==>slightly upgraded memory controller<== in the E stepping relative to the D0 stepping, in a quote above, repeated here in its entirety:

"E core revision supports SSE3 instructions and boasts slightly upgraded memory controller compared with the memory controller used in D core revision."

You've got the D0 stepping - what if your overclocking hurdles are originating from memory settings? Admittedly a long shot, but one avenue I don't think you've investigated.

I remember that you varied the voltage to the nVidia chip, and I recall that you did try the 2T timing, but I don't recall your having tried to up the voltage to memory or loosening the timings (such as CAS, Tras etc.) on the memory, which can be done on the VNF3-250.

You might try setting Tras to 10 (it probably defaults at 7 or 8), leave CAS at 3, use 2T timing, and bump your memory voltage by .1V (and see what the BIOS says is the actual memory voltage after rebooting to instate the new settings). Try that first. If that doesn't work, leave CAS at 3 and Tras at 10 and bump each of the other memory timings up by one. If that doesn't work, as a last resort, bump CAS to 4. These experiments should, at the very least, eliminate memory as a hurdle.

You can use CPUID's "Memory" button to double-check your BIOS memory settings and CPUID's "SPD" button to see the default timings for the memory in detail.

If the above doesn't work and if you are really serious about OCing above 270MHz, then why not get one of the early BIOSes to obtain Vcore adjustments? If you do that, be extremely careful when you do the flash - VNF3-250 boards seem to like to eat CMOS. I actually corrupted my BIOS's CMOS by turning off my board right after a change (but not a flash) to the BIOS. I thought I had given it plenty of time to reset - it had completed the display of my video card's BIOS and was finishing the memory count for the mainboard when I turned it off (I've done this dozens of times on other boards), but that did it. Luckily I had a spare dead Chaintech VNF3-250 board with a still-intact BIOS so I used that intact BIOS to replace the one I had nailed and "got back up." So be extremely careful if you do the BIOS flash and I recommend you turn off BIOS cacheing (and of course enable BIOS flashes in the BIOS setup) before that flash.

If you try the above, please let us know.....

 
Originally posted by: Edzard
You've got the D0 stepping - what if your overclocking hurdles are originating from memory settings? Admittedly a long shot, but one avenue I don't think you've investigated.

I've already ruled out memory and even the board's ability to run at high speeds. I did this by installing my A64, lowering the mutliplier to 5X and raising the bus speed to 300MHz for a resulting underclock of the CPU at 1.5GHz and the RAM running at default of DDR400 (at the 133MHz 2/3 setting) using all standard latencies. All voltages were default. When I'm running at between 270MHz and 300MHz, the memory is actually underclocked as well.

Again, I'm just gonna chalk it up as "one of those things" when overclocking. With two otherwise identical CPUs, one may clock higher than the other. Same goes for motherboards.

BTW, I'm "solving" the voltage problem by pairing the Sempron with the Epox board and the A64 with the Chaintech.
 
Back
Top