Twinmos timing settings

Hi,
today i bought my new hardware (look down for specs).
Evrything goes fine but i have one question, thats the only
point where i am very nubish, its about the ram timings.
I know that the auto spe settings just suck because
they are incorrect or to slow. So i want to turn it to manual
and set it more agressiv but i dont know which values i
should set. Can you please help me and tell me whats the
best? Thank you!
my specs:
MSI-k7n2 ILSR-Delta
barton 2500 running at 200 fsb
2 x 512 twinmos rams, Cl 2,5 (DDR 400)
i hope thats enuff.
-little

If you're talking about the memmory speed setting in the BIOS, if I'm not mistaken it should be set for 200Mhz if you are running twinX 400DDR. I know it sounds funny, but it's 400Mhz, but through twin banks of 200Mhz apiece.
Hope that helps.

Similar Messages

TEB Timing Settings Not Working Correctly

I'm having further problems with my TEBs. I posted last week about having issues with multiple on a slide, so I have solved those problems by having multiple slides with just one TEB on them. But now as I keep working on the project and editing, I'm noticing that on some slides it won't let me edit the Timing Settings of when a box appears and pauses. On some slides I have a text caption box or two and then a TEB, I'm not sure if in that case you need to stagger when they appear, but I was trying to set a delay on the TEB, sometimes it won't let me, and for some slides it went screwy where the pause time is earlier than the appear time which makes no sense and it won't let me change the number. If I do, when I hit enter it reverts back. Does anyone know how that happens and how to fix it? Should I delete the TEB and do another one? Thanks so much in advance for any help.

It's Adobe Captivate 7 that I'm using. Don't know how it would get corrupted, but it does keep acting weird. It's my first time using the program, so I have no point of reference, but it seems like things are harder than they should be. Like I have 3 projects I'm working on, that are similar, but have some different slides targeted at a different audiences, but most of it has overlap. I was recording the audio yesterday and wanted to just copy the audio files for the duplicate slides onto the other 2 projects. I figured out I needed to export them to a folder and then add audio and pull them from that folder. But when I did and listened back a bunch were corrupted at the end, like it repeated the last word or words I said or had a weird noise, but it was fine in the original recording in the first project. And for some reason some of them were .wav files and some .mp3 even though I never saw a place to choose. But I ended up fixing them and making them .wav files which seemed to work better, although some of them that never had problems are still .mp3 files. Don't know if it matters that some are different.
And when I try to edit a slide it keeps not being synced to the PP presentation that I imported into Captivate. So I keep editing in PP and then having to import a slide in and then delete the old one. It worked at some point in an earlier draft to edit a slide, but now it never works.
Now, my projects are pretty much done, the audio seems good for everything, but I have some glitches on some of my interactive stuff, like TEB issues, where what is typed isn't being validated. And I created a button so they can click OK, but use the Enter key as a shortcut, but Enter isn't working and clicking OK it will advance even if the right thing isn't typed. I swear stuff will work when I first put it there and then eventually it glitches on me. So I'm at a loss. Like I create settings and then they just change on me. Very frustrating. And no one else in the office seems to know how it works, I was supposed to figure it all out. So I don't know if it really is corrupted, or I just don't know what I'm doing. I was there really late last night and won't be back until Monday morning. It just got to a point where it was too late to keep looking at it. So I have no idea how to fix the glitches and I'm supposed to show the finished product on Monday.

Using signal express with NI9227 timing settings

I have Signal Express LE and using modual NI 9227, I am trying to measure input current draw AAC. What should my timing setting be for "Acquisition Mode," "Samples to Read", and "Rate (Hz)" be if I want to read every .5 seconds and every 1 seconds? Can someone explain to me what the Time Settings mentioned above mean. I am a Lab Technician learning as I go. My EE's are very busy and want me to do as much as I can on my own, please help.
Thanks
DustDevil

DustDevil,
First, welcome to our forums!
Second, we have a great KnowledgeBase article here that talks about the various timing settings you have available and what they each will mean for the timing of your measurements. In that article, "number of samples per channel" corresponds to the "samples to read" you have available in SignalExpress.
Also, the 9227 is one of our modules that uses Delta-Sigma modulation to get a higher resolution, which has some caveats as far as sampling rate is concerned. There is a minimum data rate (about 1600 samples per second) that you cannot sample below. If you set a rate lower than 1600 you'll still be getting data back at 1600 S/s. This help file describes the "Subset and Resample" step you can use in SignalExpress so you can acquire data at the minimum rate of the device and then resample the result to end up with data at the "rate" you actually want.
Give those a look and re-post if you have any follow-up questions or need clarification.
Best,
National Instruments

645-Ultra Timing Settings (MS-6547)

I just finished building my new PC. I've been exploring and found in the bios timing setting modes. My mode is currently set to normal. When trying to advance the settings to fast, turbo, or ultra the PC won't boot or post until I clear CMOS.
Any idea why the faster settings won't work?
Also I have installed Fuzzy Logic 4. When trying to manipulate any of the overclock
settings, the system locks and I can't reboot until I unplug the system. Any idea why Fuzzy Logic freezes the sysem?
The system is stable and runs good wiyh no other known issues.
MSI 645 Ultra (MS-6547 bios ver. 1.0)
Channel Watt Tech. 350w Power Supply
P4 Northwood 2.4
1 Stick 512MB Kingston 2-3-3-6 1T
Western Digital 80GB 7200 RPM 8MB Cache
Sony CD/RW 52X
Samsung CD ROM 40X
Sound Blaster PCI512
GeForce MX/MX 400 (PCI Slot)
Yahama YST-MS50 (Powered Multi Media Speakers)
HP Deskjet 656C
Windows XP Pro SP-1

Here is What CPUZ spit out.
CPU-Z version 1.22
Memory Modules Serial Presence Detect (SPD)
Module #1
General
Memory type      DDR-SDRAM
Manufacturer (ID)   Kingston (7F98000000000000)
Size         512 MBytes
Max bandwidth      PC2700 (166 MHz)
Part number      K
Attributes
Number of banks      2
Data width      64 bits
Correction      None
Registered      no
Buffered      no
Timings table
Frequency (MHz)      133   166
CAS#         2.0   2.5
RAS# to CAS# delay   3   3
RAS# Precharge      3   3
TRAS#         6   7
I'm currently set at 133MHz 2 3 3 6

Timing Settings in LabView

We have a LabView Program that is set up to start our pump motor and then read data from a pressure transducer. We also have a program timer to stop the test after 5 seconds. The program writes to a file what the pressure was at a specific time. I want to set of the DAQ timer settings for the pressure transducer so it samples/reads what the pressure is every .01 seconds. This way I'll have only 500 data point for every 5 second test.
Right now I can select the acquisition mode to run continuous and get way more data than needed or if I change to "N Samples" The samples to read box and Rate (Hz) box are unclear as to what values to put in. What values and acquisition mode do I need to be in to get a sample read every .01 seconds.

I did this and tha data that gets recorded is not what is asked for. I have attached a screen shot of the program and the data recorded (one can open with the Windows notepad). Looking at the recorded data it takes readings ~ .00062 seconds for 500 samples, then the time skips ahead from .3 seconds to 1.2 seconds. It seems as if it will start and take 500 sample readings and then skip over time until 1.2 seconds is reached, then take another 500 samples .00062 seconds aparts from eachother.
Please look at this and suggest a countermeasure so that I can get what I want. Thanks.
Attachments:
wescor vi.doc ‏115 KB
test.txt ‏77 KB

Can wrong memory timing settings cause RAM damage?

Yesterday, I tried some more aggressive memory timings than I have previously been using. The system wouldn't even POST, so I obviously picked settings that were too aggressive. However, it did power up, and it beeped -- continuously.
I used the JBAT jumper to reset the BIOS but it still wouldn't boot.
I even removed the battery for a few minutes, and that didn't help, either.
Finally, a friend suggested pulling the RAM and seeing what happened. Sure enough, when I pulled the RAM stick from slot 2, the system booted just fine.
If I put it back, it won't POST and it beeps.
If I put it in slot 3, the system will POST but Windows won't start.
Did this stick of RAM get damaged, or is the problem with slots 2 and 3 on the motherboard?
(I did power the system off when I used the JBAT jumper.)
Mitch
K8N Neo Platinum
2x512 Crucial DDR400
WD 120 SATA HD
Liteon DVDRW
Liteon CDRW
Gigabyte Radeon 9200 video card (I'm not into gaming)

Well, I'm totally screwed.
My new RAM arrived today. I put it into Slot 1. The computer wouldn't POST. I moved the stick to Slot 3. The computer turned on briefly, then I heard a pop, and it died. The Power LED on the front remained on.
I think I fried the mobo.
Now I have a couple of important questions for you guys:
1. How can I make sure it's the mobo rather than some other component (I want to replace the right component)?
2. Since the K8N Neo Platinum is essentially unavailable, I thought I'd upgrade to a Socket 939 board and a faster CPU. But if I swap in a Socket 939 board with nForce 4 chipset, will my PC boot, or will it be useless because the drivers on my system are for nForce 3? Will I have to reinstall Windows to get the system working again?
3. Any secret sources of K8N Neo Platinum mobos? That would make my life a lot easier.
Your expertise and advice is very sorely needed!!
(I'm typing this at the new Apple store in midtown Manhattan, open 24 hours a day.)
Mitch

How to set a value of delay in Timing settings

Hi all,
I am trying to set value for delay in TimingSetting but not able to set it.
please suggest me any solution
Thanks In advance,

Hi Pooja,
try the below method.
$.sleep(1000);
thx,
csm_phil

No Bios Update for Satellite: L755D-S5204 / Inability to change Memory Settings in Bios

Ok so I bought two new 8GB of BLUE Kingston Hyperx 1600 MHZ Memory Modules with heat spreaders recently from newegg.
I installed them, and my system recognizes the full 8 GB, but when running CPU-Z the memory MHZ is registering in at 665.5 MHZ.
I want to be able to run my Memory at least the STANDARD minimum 1333 MHZ if not be able to change the MHZ if possible to 1600 MHZ. I CANNOT DO THIS WITH THE BIOS THAT CAME WITH MY SYSTEM, AND I CANNOT FIND A BIOS UPDATE ANYWHERE ON THE TOSHIBA SITE THAT WILL LET ME DO THIS.
My system Laptop Satellite L755D-S5204 has the basic Bios that came with the system. However I do not know or CAN NOT FIND any flash updates to update the bios so I can change these setting.
My question to Toshiba Tech support is it possible to clock my system memory higher, and how do I do this with a BIOS that doesn't let me make any changes to my Voltage to my Memory, and doesn't let me make any changes to system memory or memory timing settings??
When you figure that out and if you could possibly help me resolve this problem, please email me because as a computer technician I am really intrigued as to the reason why Toshiba doesn't have a FLASH BIOS UPDATE that will let you change the Memory settings, and Memory Timings!!
Thanks,
Michael Richins
Comptia A+ Computer Technician

BIOS does not provide such option!
I have no idea what graphic card you have but for example the Sat P850-138 was equipped with an NVIDIA GeForce GT 630M graphic card.
This GPU supports dedicated VRAM (default 2048MB)
The available graphics memory can be expanded using system memory, through TurboCache
In case the system memory would be expanded to 6GB RAM, the TurboCache technology could use up to 4,095 MB VRAM

Media Manager slide show timing help

Hi,
Not sure which forum this belongs but I have built multiple slideshows on my vista 32 machine using media manager. I added music in the back. When shown on my pc the slide show takes the timing settings I gave and runs perfect. However when I go to the tv, the timing is fixed at 5 sec. What can I do to adjust the timing? Also, is there a means to play in a loop? I have a music file with slide show I want to use on my large video wall during a party and want it to set to loop (100+ slides). Thanks for any help!

Open your project. Hover your mouse over the music track in the timeline and when it changes to a hand symbol, click once to highlight the track you want to remove. Then hit delete.

Problem with memory settings

Hello,
i got a brand new PC4000 PRO from corsair and i got problem setting timings with this motherboard (neo2 PFISR - bios v3.9).
I can't set CAS timing nor to 3 neither to 2, it automatically turns it back to 2.5.
It seems that there is a lot of users having the same issues with this motherboard all over the net, but they told me to post here.
Has anybody an idea why this happen and how i can fix it ?
Thanks,
Fab

Hi there,
For some reason the BIOS settings have a rather confusion relation.
This is what my experiences have been, please try them and report your findings:
- MAT is enabled (and overrules SPD or manual memory timings) if:
Memory clock is set to "auto" within the frequency menu AND you set your perfomance above FAST.
To get a stable system, I'd advice the following:
- Go back to default BIOS settings.
- Disable D.O.T.
- Disable Spread Spectrum
- Fix your memory frequency to what it should be (e.g. 400Mhz), and not AUTO.
- Choose SPD timings for your memory (or set them below SPD timing manually).
- Start with performance settings to SLOW.
Check memory timing settings (chipset) with AIDA or CPU-z.
Check stability with Prime95 & torture test on maximum RAM.
Once the system is table, try upping the speed setting, check the actual timings and see what happens. If you still have problems, take out one memory stick and try with just one (maybe one is faulty).
Once you got it stable, continue from here.
Keep in mind: in my experience, if you set your memory frequency at a fixed frequency and use SPD settings, you will find that upping the performance settings, changes the memory timings! However as long as the frequency is not AUTO, MAT is not enabled, whatever the performance setting.
It really confused me at first, as I could not get the system running with MAT enabled, whatever memory time I entered. But with fix memory frequency, I got the system stable with 2,2,2,5 timing!
If anyone has techdoc on these matters, I'd appreciate an URL.
Bios 2.3 on 865PE neo2-LS
Twin Kingston ValueRam Cl2.5 (winbond)

MSI Neo4-F & Athlon64 3700+ E6 1T/2T Memory Timing missing in BIOS

Hi. This is my first post. I need help with my new MSI Neo4-F motherboard. The problem is that 1T/2T Memory Timing is not present in the latest BIOS v.1D. MSI website says that my CPU (San Diego 3700+ E6) is supported by the motherboard but there is no way to control the command rate of the memory thru the BIOS. So far I've been using A64 Tweaker to change command rate to 1T from Windows. Previously I used this CPU with the same memory Kingston KHX3200AK2/1G for another motherboard (MSI Diamond Plus) and I didn't have any problems being able to change the 1T/2T memory timing settings thru the BIOS. I wrote couple of e-mails to MSI TEchnical support but i didn't get a response. Does anyone have any ideas that would help me resolve this issue? Any suggestions will be appreciated. Thanks a lot in advance!

Quote from: BG84 on 05-July-06, 02:57:00
its supposed to be there, i have a 3500+ and a 3800+ and its there, but why does it depend on the cpu if the 1t is there anyway, ?, its there with the 1a 1b 1c and 1d, in dram configuration, second auto put it to manual and 1t, youre supposed to gain a 4% performance, which youre not going to see at all.
Sorry to disagree with your 4% figure but using the 1T setting on the A64s makes a huge difference.
I did a quick check on my current rig using 3dmark 03 and the difference in CPU score was 485 vice 554 making an improvement of over 12%!
I know it's not the best of tests to use for this, but it was quick and points to the "noticable" improvement I've found while doing OC benchmarking with a variety of programs.
Not trying to be argumentative, but I didn't want anybody reading this thread in the future to dismiss the "1T" option as being unimportant.

6585 with ddr400 problems

My MSI board wont boot with TwinMos 3200 DDR 400 Cas 2.5 RAM. I can however underclock the RAM to about 350MHz and get the system to boot. I've been reading posts similar to this and people came to the same kind of conclusion.
Will MSI/Can MSI do something about this incompatabililty problem? Please. ;(
Anyone?
Lee
computer
monitor
keyboard
mouse

I tried putting the voltage up to 2.7v, again no boot. The Ram timing settings(in advanced chipset i think) are VERY sensitive. I underclocked my 400Mhz ram to 266Mhz and even then the system wont boot. Timings set to "fast", forget the fabled "ultra" setting
Thanks for the idea though...
Lee

Memory upgrade on Satellite A300D-15B

Hi all,
I am having upgrading the ram on my laptop from 4gb to 8gb. First I will post the full details of my laptop then explain the problem.
(Original Configuration)
Satellite A300D-15B
Model : PSAKCE
Bios Ver: 3.30
AMD Turion X2 Ultra Dual-Core Mobile Processor ZM-86 (Upgraded from ZM-80)
Genuine Windows Vista Home Premium 32bit
4096 MB (2048 +2048) PC2-6400 DDR RAM (800MHZ)
Right then, I installed Windows 7 32bit on it ages ago and upgraded the CPU and have never had any issues as i work with computers.
I did some checking and found out my Motherboard supports uo to 8gb of ram and decided to buy two 4gb ram modules. I made sure I got the correct ram for my laptop.
I upgraded the ram and it recognised it without any issue and even stated that 8gb of ram was installed under 'System'in contol panel and in the bios. As it was a 32bit OS it only utilised 3gb of the ram. I then decided to upgrade my OS to Windows 7 Ultimate 64bit and thats when the fun began.
Basically my laptop will not boot if I have more than 4gb of ram installed (In any configuration) and get a BSOD. I have had a few different Stop Error codes but I cant seem to find a solution. Also there arent any/many options to change in the bios so Im stumped.
I have tested the ram modules with Memtest several times without error and have also tried them in different laptops without issue. I know my laptop suppors the 8gb as I had no issues running the 32bit OS.
All my drivers and other software are to date and work fine and have installed all windows updates to date.
Has anyone else had this issue and is there a patch/fix available?
Any help, ideas or suggestions are welcome and hopefully I can sort this problem out. Many thanks in advance.
Melchius

Hi there,
The Ram I bought is the correct to the letter and is as follows:
Komputerbay DDR2 PC2-6400 @ 800Mhz - 2 x4gb modules.
It has exactly the same Cas latency and timing settings aswell.
You mentioned that it booted fine in 32bit as it didnt address the full 8gb but now on the 64bit OS I have 1 x 4gb module installed and it is recognised without any issues,.
If the ram wasnt compatible in any way then I should be getting some errors or something to indicate a problem.
It also wouldnt boot/run properly with just 1 of the 4gb modules installed on either 32/64bit OS's, which isnt the case at all. I am certain that the ram itself isnt the issue.
I also tried installing 1 x 2gb and 1 x 4gb module for a total of 6gb and I managed to get windows to load (once) but it then stopped responding. Im not very keen on spending loads of money on another 8gb of ram from Kingston or Crucial if the same thing is going to happen, which I fully expect it will.
Thanks for the suggestions though, any other ideas?
Melchius
Also worth mentioning that the ram that came with the laptop wasnt even Toshiba brand, it is Samsung ram so maybe they should make a list of all the compatible makes for their laptops or maybe not lock their bios's to the point that the end user is so limited.
+Message was edited by: Melchius+

MSI K7N2 Delta ILSR Memory problems

I'm trying to burn in a system in a 50 deg C (122 deg F) room for a minimum of 12 hours. The main system components are as follows:
Motherboard: MSI K7N2 Delta ILSR
CPU: AMD Athlon XP 2800+
Memory: 2x512 OCZ PC3200 EL
My problem is that the burn-in software continues to freeze up during the memory test. I've already contacted the software manufacturers and the software is stable. It's a problem with the way the motherboard handles the memory. I've tried putting the memory in dual channel configuration and changing the timing settings in the BIOS. The SPD settings are 2.5-3-3-7. Right now I have them at 3-4-3-8. It's a lot more stable than it was under the default settings but it still freezes up sometime after 7 hours. Unfortunately, I wasn't around when it froze so I don't know exactly how long it lasted. I can say that after 7 hours, it wasn't showing any slowdown in performance. If anyone could think of anything else I might be able to do to get the system stable, I would greatly appreciate it.

Thanks for the suggestions. The CPU FSB is 200, so it's already matched up there. And we have a ton of fans already. There are two in the front, 4 inside and 1 on the back. It's a custom case, 2u high. The power supply is oversized and more than adequate to provide the required power. I have four of these units running right now. Two with 2x512 sticks and two with 1x1024 sticks. For each combination, the memory clock speed for one is 166 and 200 for the other. I have been loosening up the memory timings trying to get the system stable, but it still isn't. If the power supply is good, and I'm unable to cool the system anymore due to limititions within the case, is there anything you can think of to stabilize the system. Maybe other settings in the BIOS or suggestions on how to go about getting good timings for the memory. Thanks.

Neo4 Overclocking Guide

This guide is intended to help those people who have K8N Neo4 (nforce 4 based) boards. It will provide some general background information, but a lot of things will be specific to this particular series of motherboards, and in general it is assumed that the user is at least moderately familiar with the basic concepts of computer hardware and the concepts and risks associated with overclocking. As usual, I am in no way responsible for any losses/damages resulting in whole or in part from the use or misuse of this information, or in short, "overclock at your own risk". It should also be noted that I have the Neo4 Platinum, so things might be slightly different for those of you with the SLI or other variants of this board, though I would strongly suspect that most of the overclocking features will be pretty much the same. Anyways:
The Basics:
Okay, for those of you who are new to the overclocking crowd, here is a quick overview of some of the essential bits of knowledge. A very complete and thorough introduction and general overclocking guide is also available at https://forum-en.msi.com/index.php?topic=40413.0 for those of you who need extra help.
CPU Speed - If you don't know what this is, then I wonder what you were hoping to attain by accessing an article about "overclocking". The main aim of overclocking is to increase the CPU speed beyond what it is originally specified to run at. The CPU speed is equivalent to the product of your FSB speed and the CPU multiplier.
FSB - FSB is short for "frontside bus". Historically the FSB essentially controls the speed at which the CPU is able to communicate with the rest of the system, and this is pretty much still true for the Athlon64, although the impact of higher FSB speeds is somewhat diminished, as we will see later. On the Neo4 (and most any other board) the FSB and various multipliers/dividers are responsible for determining the core CPU speed, the memory speed, and the HTT speed. You PCI-E bus is locked, so raising the FSB will not cause your video card and other devices to become unstable. Additionally, there is no need to worry about an overclocked FSB screwing up the built-in SATA/IDE controller (the nforce one at least, I haven't tested the SiL, although it should be fine as well).
HTT - HTT (or sometimes just HT) is short for "HyperTransport Technology". Not to be confused with the HyperThreading feature on Intel's P4 processors, this is the communication link between an Athlon64 processor and the PCI-E bus, as well as everything that hangs off this bus, including the SATA/IDE controllers and so on. Basically, everything except for the RAM talks to the CPU via the HTT bus. The speed of the HTT bus is determined by taking the product of the FSB speed and the HyperTransport multiplier, and it provides an extremely large amount of potential throughput, so much so that once its speed is above about 800 MHz, there's very little to be gained by pushing the HTT speed higher.
Memory Clock - The memory clock refers to the speed at which the RAM modules are operated. The memory clock is determined by taking the FSB and applying a ratio to it. Generally speaking, a higher memory clock is better, although there are tradeoffs in terms of latency if memory timings (CAS latency, etc.) have to be loosened in order to get the memory clock higher, or if a ratio other than 1:1 is used (which will be necessary for high overclocks unless the RAM you are using is of extremely high quality).
PCI-E - The PCI-Express bus. This provides connectivity for your graphics card(s) and other add-in cards. The default PCI-E speed is 100 MHz, and this is locked on the Neo4 so that increasing the FSB does not increase the PCI-E speed. You may manually increase the PCI-E speed if you wish, although this is not at all recommended.
vcore - This is an abbreviated way of referring to the voltage that is applied to the CPU. Generally speaking, a higher vcore will provide stability at higher clock speeds, the tradeoff being additional heat, which may or may not require a more robust cooling solution, depending on how high the vcore is being pushed, the quality of your thermal interface compound, and the thermal characteristics of your individual CPU (some just overclock better than others). For the 90 nm Athlon64, the default vcore is 1.40V. The default is slightly higher for the 130 nm variants.
vmem - Similar to "vcore", this is a shorthand way of referring to the voltage that is currently being applied to the RAM modules. Again, an elevated vmem will generally give you improved stability at higher memory clock speeds. Memory specifications vary from manufacturer to manufacturer in terms of what voltages are supported (for instance, my RAM supports from 2.55V to 2.95V), though the default voltage is usually 2.65V. Vmem, vdimm, and vram all refer to the same thing.
Purchasing:
For anyone who happens to stumble across this guide while in the process of looking for some new hardware, I thought I'd list some of the things that are important considerations when you are buying a system with the intent of overclocking it.
The CPU - For most people, the main point behind their desire to overclock is that they want to be able to get a cheap CPU, and then run it at the same speed (or faster than) of a CPU that costs much more (possibly one for which the price premium has not come down on yet). When choosing which CPU to purchase, there are a few aspects that are especially relevant to overclocking (I'm going to assume that you've already decided to use an AMD CPU, due to the reduced overclockability, thermal problems, and generally poorer performance in most areas despite having higher raw clock speeds that all of Intel's current P4 models offer). Arguably the most important feature (when looking at the current Athlon64's anyways, which are very good CPU's and which you have to use if you want the Neo4) is the manufacturing process used. This denotes the size of the smallest individual feature on the chip (smaller is better). Your two choices right now are 90 nm and 130 nm. The 90 nm carries a fairly small price premium (about $10 for the 3000+/3200+ models), but is *much* more overclockable due to the fact that it operates at a lower voltage (and thus generates less heat), and also uses a more "mature" revision than the 130 nm parts. It is *strongly* recommended that you make sure to get a 90 nm CPU if you are in the market for a new socket 939 Athlon64. The next thing to consider is the default CPU multiplier. This is the one reason why it might be preferable to get a 3200+ over a 3000+ chip (generally speaking, all the 90 nm Athlon64's have about the same upper limit on their overclocked core speeds, until you hit the still very expensive 3800+ and FX variants, so it doesn't make sense to buy a more expensive CPU when you're not getting any extra overclockability out of it). The multipliers on the Athlon64 CPU's are "half-locked", meaning that you can run at the default multiplier (9x for the 3000+, 10x for the 3200+), or any multiplier that is smaller than the default, but you cannot select a multiplier that is higher than your default multiplier. Thus, getting the 3200+ over the 3000+ gives you two extra multipliers (10x and 9.5x) and, all things being equal, will let you achieve a higher clock speed before you are forced to run your RAM asynchronously and pay the latency penalty for doing so, although your max clock speed will likely be about the same as it would if you had gotten the 3000+ instead (so if you have cheap RAM that's not giong to overclock well at all, there's very little reason to go with the 3200+ unless a RAM upgrade is planned in the near future). So, for overclocking purposes my recommendation is a 90 nm Socket 939 Athlon64 3000+, or if you have high performance memory and want to get the most out of it, the 3200+. Both chips are competitively priced and should overclock at least to 2.4 GHz, if not higher, on stock cooling (spend the extra $10 for the non-OEM variant and get the HSF that comes with the chip, it works as well as many more expensive third-party air-based systems and is well worth the extra $10), and of course both offer the attractive feature-set of a socket 939 Athlon64 (dual integrated memory controllers, 64-bit support, dual-core processors on the future upgrade path, etc.).
The Motherboard - The motherboard is an important part of overclocking as well. There's not much point in getting a highly overclockable CPU and then pairing it with a mainboard that was not designed with overclocking in mind, and this is one area where the Neo4 really shines...it has superb overclocking support. Probably the most important feature to have if you indend to overclock your CPU by 20%+ (which should be easily attainable on either of the recommended CPU's above) is that the board have locks that prevent the overclocked FSB from overclocking parts of the system that can't handle the extra speed (like the PCI/PCI-E bus, for example), and long story short, the Neo4 has these (unlike the Via-based K8T Neo, which had no locks and which limited SATA users to overclocks of no more than about 225 MHz because any high than that and the SATA controllers would start to become unstable and kill your HDD data...working locks are a very good and important thing if you are overclocking). The next important feature is to choose a board whose BIOS lets you control the options that are important for overclocking. Again, the Neo4 does excellent here, letting you pick your memory divider, memory timings (and some very obscure ones at that), CPU multiplier, FSB speed, HTT multiplier, CPU voltage, chipset voltage, RAM voltage, and so on without complaint. The MB also has a handly little button on it that will clear the CMOS with a single press (no more screwing around with those annoying jumpers) in case you screw up and the system won't POST. The board also has some extra cooling hardware installed in the form of a passive heatsink near the rear I/O panel, but mostly it's the presence of functional locks and the wide range over overclocking related BIOS features that make it attractive from an overclocking perspective. Aside from this, it has a very nice feature set in general, including 8 SATA ports and 2 IDE channels (for a total of up to 12 drives), two gigabit ethernet adapters, firewire, 7.1 channel audio, and the additional selling point that nvidia's unified drivers tend to be much easier to install than most companies' drivers.
Cooling:
Okay, one last thing to consider before the overclocking starts. Cooling is important in general and especially if you are going to be overclocking. While a 90 nm Athlon64 performs rather admirably from a thermal perspective even when only stock cooling components are used, some simple modifications can drop your idle/load temps by 5+ degrees, which can give you a bit more overclocking headroom and which in any event will make your CPU happier.
Case Fans - The first thing you want to do is make sure your case is adequately ventilated...in general a single 120 mm exhaust fan will do the job just fine. If your case does not support fans this large, use at least two 80 mm fans, either both as exhaust, or one as exhaust and one as intake (if they perform differently, use the more powerful one as the exhaust fan to avoid overpressuring your case). If noise is a concern, the Vantec Stealth (http://www.newegg.com/app/ViewProductDesc.asp?description=11-999-614&depa=1) series of case fans are affordable, come in a variety of sizes, perform quite well, and do not make much noise at all (though you might want to consider doubling up on the 120 mm's just to be on the safe side). This can lower your CPU temp by about 2 to 5 degrees over a poorly ventilated case configuration using the same CPU fan.
CPU Fan - As I mentioned earlier, the default CPU fan that comes packaged with the retail Athlon64 chips is perfectly acceptable for overclocking use in my opinion. The only complaint I have is that the thermal compound that comes preapplied to the HSF is fairly cheap and does not perform that well. I *very strongly* recommend replacing it with Arctic Silver (http://www.arcticsilver.com/as5.htm) before ever installing it on your CPU. To remove the default thermal pad, you can use a razor blade to get most of it off, and then hot soapy water (or denatured alcohol I've heard) to remove any remaining reside. Be sure that the HSF is free of any cleaning residue and also of any moisture before going to install it on the CPU, and then just apply the Arctic Silver and then complete the HSF installation, and you're good to go. Arctic Silver is relatively cheap (the tube you'll get will do several CPU's, and it doesn't go bad), and by replacing the thermal pad that comes on the stock HSF with it, you should be able to reduce your idle/load times by at least 5 degrees, and with this plus the added reduction you get from having a well ventilated case, you should have enough headroom to pull off some pretty aggressive overclocks.
Overclocking:
Finally, on to the good (and Neo4 specific) stuff. Hopefully at this point you have a freshly built Neo4 based system with an Athlon64 CPU that provides a large headroom for overclocking.
Initial Setup - Okay, the first thing you're going to want to do once the system is built and powered on for the first time is enter the BIOS and configure everything to run at its *default* settings. It's not quite time to overclock yet. First, you want to install Windows, patch it to SP2 if necessary, and then install some benchmarking, stress testing, and monitoring software. SiSoft Sandra is a good benchmark suite, as are FutureMark's PCMark and 3dMark lines of software. For stress testing you can use SuperPi and Prime95 (and Memtest86 if you don't mind the tedium of having to reboot in order to use it, which I do so I don't bother with it). For monitoring you can use SpeedFan or Motherboard Monitor 5. At the very least you should install one application from each category, and configure your monitoring software to launch when Windows loads. One you have all this configured and working right, it's time to start overclocking (don't install too much else, in case of the worst case scenario in which an instability causes your HDD to become corrupted, requiring a reinstall of Windows and all the software, which is admittedly very unlikely, but unfortunately possible if you're unlucky enough). For comparison purposes you may want to run some benchmarks and record the results before you start. Additionally, you may want to install something like ClockGen, which will let you tweak your FSB/CPU coltage on the fly and which can make it easier to zero in on a stable configuration without having to reboot every time an instability is found.
BIOS Layout - Just to save some time, I'll describe where BIOS options that we'll be using are all in one place, so that when I reference something you can just look up here and figure out how to find the appropriate setting in the BIOS. Basically, there are two pages that we're interested in for overclocking (note that the Neo4 manual is actually extremely well done, and describes pretty much all of the BIOS options, so you can use it as well). The first is the "Advanced Chipset Features" page. Going "Advanced Chipset Features" -> "DRAM Configuration" brings up pretty much all of your memory related options (divider, timings, etc.), *except* for the RAM voltage. The RAM voltage option is on the "Cell Menu" page, which happens to also contain all the other settings we are interested in, including FSB speed, HTT multiplier, CPU multiplier, vcore, vmem, chipset voltage, etc.. Basically, if it's not memory related, it's on the "Cell Menu" page.
HTT Speed - As mentioned earlier, your HTT speed pretty much has no performance impact on the system once it gets to 800+ MHz, so the very first thing you can do is select the 4x HTT multiplier in the BIOS. Note that as the HTT speed gets above about 1100 MHz, it will probably start to make the system unstable. Therefore, you should keep track of the product of your FSB setting and your HTT multiplier, and whenever it gets to be above 1100, decrement the HTT multiplier to the next lowest setting. at a 4x multiplier, you should be good up to about 275 MHz on your FSB. Because the HTT's impact on performance is negligible, you do not need to worry about trying to maximize its value during overclocking.
CPU speed - Onve you've reduced your HTT multiplier, it's time to find your max stable core speed. To do this first go to the memory page and select a memclock index of 100 MHz. This will run your RAM it half the FSB speed, and the reason for doing this is to ensure that as we raise the FSB, any instability the occurs is a result of the overclocked CPU and not a result of overclocked RAM, so that we can be sure that we have indeed found the maximum stable CPU speed when we are done. Leave your other RAM settings at their defaults, we'll come back and tweak these later. Now go to the CPU page and select "Manual" for the "High Performance Mode" option if necessary to enable editing of the settings. You should disable Dynamic Overclocking (since you are doing this manually) and I recommend disabling Cool'n'Quiet, though you don't have to if you really don't want to. Disable all the "... Spectrum" settings (what these do is kind of complicated, but the manual plainly states that they should be disabled if you are overclocking, so heed its advice). Also disable "Aggressive Timing", as this will decrease your RAM overclockability substantially without providing any real benefit (and may make it unstable even at its rated settings). Now, what you want to do is, leaving the other CPU settings (i.e. vcore and multiplier) the same, start raising your FSB Frequency in 10 to 12 MHz increments, depending on your multiplier (basically you want to raise it about 100 MHz at a time). Some people feel this is a fairly large jump to do at a time, but I've found that the Athlon64 handles it just fine. If you get up above about 2.4 GHz, then you might want to only go by half of this at a time though. Remember to decrement your HTT multiplier as necessary. Basically, every time you raise the FSB, test for stability by letting the system try to boot to Windows. If it is successful, return to BIOS and raise the core speed some more. Once the system fails to boot, you have two options, either raise the CPU voltage (use the "CPU VID" setting in the BIOS to adjust the voltage directly, or the "CPU Voltage" setting to specify how much over the specified amount of voltage to apply...personally I prefer the "CPU VID" route, but it's really a matter of personal preference, and yes, both can be manipulated in unison...one thing I've noticed here is that the "CPU Voltage" settings seem to allow for less variance in the final vcore setting, keeping it very close to the specified voltage at all times, whereas increasing via the "CPU VID" option lets the voltage decrease a bit from the specified value when the system is not under load) and try again (and keep repeating until you have given the CPU as much voltage as you are comfortable with and the system can no longer be made stable), or return to you last stable setting and let it boot. Once you have done this, use your benchmarking and stress testing software to make sure you really are stable at your settings. If the system crashes or the test reports errors, you will either need to raise the voltage a little, or lower the FSB a little (this is where ClockGen can be a big timesaver). While some people swear by Prime95, my opinion is that if you can get through the largest SuperPi test without any errors, your overclock is stable. Monitor your temps while you do this. If you notice that the CPU temperature is getting above 60 degrees, you are running a bit too hot. Generally speaking, about 55 should be considered the threshold of safety here. If you're running hot, you can either decrease the voltage and FSB settings, or get a better cooling solution. Once you have determined that your setting is stable and not overheating your CPU, record your core speed (not your FSB speed, the total CPU speed) and voltage settings for later. You should probably be shooting for a target clock speed of around 2.4 GHz, or more if you have good cooling, or if you are interested in doing a "safe" overclock, just shoot for as high as you can get without raising the voltage.
Memory Speed - Now that you know your CPU's limits, it's time to work on the RAM. First restore your FSB to 200 MHz and your CPU voltage to its default, and specify a CPU multiplier of 6x to make sure that the CPU will not be stressed as your raise the FSB. Go to your RAM page, and manually specify whatever timings are appropriate to your RAM modules. Also be sure to set "1T/2T Memory Timing" to 1T (set the "... Mode" setting to Manual to make the RAM settings editable). Leave the rest of the settings alone, except for the "Memclock Index Value". Here, you have a choice to make. If you have high quality RAM, or your target CPU speed is not too high (like < 2.3 GHz), you can try to run your RAM synchronously, which will give you somewhat better latency. If this is the case, select an index value of 200 MHz (note that on the Neo4, when you select a memclock index what you are really specifying in the ratio at which the RAM operates relative to the FSB...the memclock index option is basically just obscuring this setting. To calculate your ratio, divide whatever the index value is by 200, so an index of 200 MHz is a 1:1 ratio, an index of 150 MHz is a 3:4 ratio, and so on). If your RAM is not of very high quality (for example, it's only rated as PC3200), or your target CPU speed is high, you will likely need to run the RAM asynchronously, so select the next highest index value of 180 MHz. This will let you get slightly higher RAM clock speeds, at the cost of a little bit of added latency (the performance hit isn't much...you'll be much faster running asynch at 2.4 GHz than synch at 2.2 GHz). Now you do the same thing that you did with the CPU, gradually increasing the FSB (you might want to use smaller increments this time though) until the system will no longer boot (remember again to decrease the HTT multiplier if necessary), and then returning to your last stable setting (or increasing the voltage and repeating) and booting to Windows and running stability tests. You do not need to monitor your temps while doing the RAM tests (unless you want to). Generally I find that Sandra's "Cache and Memory..." benchmark works well for detecting memory instability, and you can also use SuperPi, Prime95, or Memtest86 as well. Once you have tested stable, record your memory clock speed (use the formula: memory speed = FSB speed * memclock index value / 200) and voltage and reboot to the BIOS settings menu. Note that while you may be able to attain a higher memory clock speed by selecting a higher CAS latency, it is not generally advisible to do so, as from what I've seen, although memory bandwidth remains about the same as CAS increases (as far as Sandra is concerned anyways), the lower latency provided by CAS2 improves the system score by 5% in PCMark 04, and given that RAM performance scales pretty much linearly relative to the clock speed, unless running at CL2.5 lets you get *at least* 10 to 15 MHz higher than at CL2, it is not worth it overall.
Run the Numbers - Believe it or not the performance of the Neo4 system is dictacted pretty much entirely by the core and memory clock speeds (given identical memory timing settings). The only other real factor is whether the RAM is run synchronously or not, which you just decided in the above step, so all that's left to do now is find the combination of memclock index, FSB, and CPU multiplier that allow you to get as clost to both your target core and memory speeds as possible. If you are running synchronously, your task is simple, just keep your memclock index of 200 MHz, specify your target FSB speed, and your default CPU multiplier (unless your RAM is so good that the CPU is not stable at the default multiplier and the RAM's top FSB speed, in which case drop the multiplier accordingly). If running the RAM asynchronously your task is a bit more difficult (having a calculator for this part will help), basically you have to go through the list of memory dividers (memclock indexes), and for each one calculate the ratio of memclock index / 200, and then divide your target memory clock speed by that ratio to get the FSB needed to attain your target memory speed (for example, if the target is 230 MHz, for a memclock index of 150 we get a ratio of 0.75, and 230 / 0.75 = 307 MHz, so running the RAM at 230 MHz with an index of 150 MHz requires a FSB setting of 307 MHz...pretty good if your target clockspeed is 2.45 GHz, as selecting an 8x multiplier will pretty much hit this exactly), and then go through the available *whole* CPU multipliers (I've heard that the half-multipliers should be avoided, as they cause the memory to get clocked incorrectly) and see if any multiplier times the FSB you calculated hits (or comes reasonably close to hitting) your target CPU speed. Go through all of them until you get an exact (or very close) match, and pick whichever one ends up matching most closely. Note that there is no benefit in this case to a higher FSB speed configuration over a lower FSB speed configuration, provided that both produce the same core and memory clock values, so you should not favor configurations with needlessly high FSB settings unless they produce a better fit than the others. Apply whichever settings are closest, and then apply the appropriate CPU and memory voltage settings that you got from the previous steps. Also apply whichever HTT multiplier will put you closest to 1000 MHz without going over 1100 MHz. After this, your system should be ready to boot, overclocked and stable. Be sure to do additional benchmarking and stress testing to make sure that you really are stable (if you saved your scores at the beginning, compare them to your scores now and marvel at the improvement...and post the results for people to see), and be sure to monitor your temps for a bit to make sure your cooling is working adequately.
Post Overclock Overclocking:
There's not a whole lot to do now, but if you want to try to tweak your memory timings to get a little bit of extra performance, now is the time to do it...just remember to record your stable overclock settings somewhere (*not* on the computer) in case the tweaking forces a CMOS reset and you lose all your settings, and enjoy. Also you can overclock whatever video card you have, a process that's much easier and faster than overclocking your CPU/RAM/FSB.
In Closing:
I hope someone out there finds this useful, given how long it took to write up. Maybe I'll get lucky and this will end up as a sticky...we'll see. And just to start things off, here are my benchmark scores, at stock and at the overclock described in my sig:
Stock:
3dMark05 = 3141
PCMark04 = 3589
Overclocked:
3dMark05 = 3704
PCMark = 4805

Just started ocing the system, I'm new at this so these are where my system stands and the results
--------[ EVEREST Home Edition (c) 2003-2005 Lavalys, Inc. ]------------------------------------------------------------
Version EVEREST v2.20.405
Homepage http://www.lavalys.com/
Report Type Report Wizard
Computer HOWARD-4B304E62
Generator Howard
Operating System Microsoft Windows XP Home Edition 5.1.2600 (WinXP Retail)
Date 2005-09-16
Time 16:14
--------[ Overclock ]---------------------------------------------------------------------------------------------------
CPU Properties:
CPU Type AMD Athlon 64
CPU Alias Venice S939
CPU Stepping DH-E3
CPUID CPU Name AMD Athlon(tm) 64 Processor 3000+
CPUID Revision 00020FF0h
CPU Speed:
CPU Clock 2456.56 MHz
CPU Multiplier 9.0x
CPU FSB 272.95 MHz (original: 200 MHz, overclock: 36%)
Memory Bus 204.71 MHz
CPU Cache:
L1 Code Cache 64 KB (Parity)
L1 Data Cache 64 KB (ECC)
L2 Cache 512 KB (On-Die, ECC, Full-Speed)
Motherboard Properties:
Motherboard ID 03/15/2005-MS-7100-6A61FM4BC-00
Motherboard Name MSI K8N Diamond / K8N SLI Platinum (MS-7100) (3 PCI, 2 PCI-E x16, 4 DDR DIMM, Audio, Gigabit LAN, IEEE-1394)
Chipset Properties:
Motherboard Chipset nVIDIA nForce4 SLI, AMD Hammer
Memory Timings 2-4-4-6 (CL-RCD-RP-RAS)
Command Rate (CR) 1T
SPD Memory Modules:
DIMM1: GeIL CL25-4-4DDR 500 512 MB PC4000 DDR SDRAM (2.5-5-5-9 @ 250 MHz) (2.0-5-5-9 @ 232 MHz)
DIMM2: GeIL CL25-4-4DDR 500 512 MB PC4000 DDR SDRAM (2.5-5-5-9 @ 250 MHz) (2.0-5-5-9 @ 232 MHz)
BIOS Properties:
System BIOS Date 03/15/05
Video BIOS Date 06/27/05
Award BIOS Type Phoenix - AwardBIOS v6.00PG
Award BIOS Message W7100NZ1 V9.0 031505 14:17:53
DMI BIOS Version 6.00 PG
Graphics Processor Properties:
Video Adapter nVIDIA GeForce 6600 GT PCI-E
GPU Code Name NV43GT (PCI Express x16 10DE / 0140, Rev A2)
GPU Clock 299 MHz
Memory Clock 522 MHz
--------[ Power Management ]--------------------------------------------------------------------------------------------
Power Management Properties:
Current Power Source AC Line
Battery Status No Battery
Full Battery Lifetime Unknown
Remaining Battery Lifetime Unknown
--------[ Sensor ]------------------------------------------------------------------------------------------------------
Sensor Properties:
Sensor Type Winbond W83627THF (ISA 290h)
GPU Sensor Type Driver (NV-DRV)
Motherboard Name MSI MS-7046 / 7100 / 7125
Temperatures:
Motherboard 32 °C (90 °F)
CPU 35 °C (95 °F)
GPU1: GPU 56 °C (133 °F)
GPU2: GPU 50 °C (122 °F)
Cooling Fans:
CPU 3444 RPM
System 2637 RPM
North Bridge 7337 RPM
Voltage Values:
CPU Core 1.38 V
+3.3 V 3.34 V
+5 V 5.08 V
+12 V 12.04 V
+5 V Standby 5.17 V
VBAT Battery 3.10 V
Debug Info F 40 31 17
Debug Info T 32 35 157
Debug Info V 56 D1 C6 BD 1C 14 34 (01)
--------[ Debug - PCI ]-------------------------------------------------------------------------------------------------
Benchmarking PCMARK04/score:4684 3DMARK03/score:15075
got any suggestions, Im just trying to learn how to do this, any help would be greatly appreciated

Twinmos timing settings

Similar Messages

Maybe you are looking for