Is there any chance someone would help me to understand what this "Strap" thing is about? I've heard the term before but I'm unaware what it refers to? Thanks guys for any help you can give!
Printable View
Is there any chance someone would help me to understand what this "Strap" thing is about? I've heard the term before but I'm unaware what it refers to? Thanks guys for any help you can give!
apparently when your at 425 fsb or above, the looser timings kick in
When you refer to "looser timings" is that with the RAM or latency of something else? I realize this is probably a noob question but this isn't the only place this discussion has come up so I'm very curious!
Looser timings are chipset/memorycontroller related, and are the "strap" that is refered to.Quote:
Originally Posted by Roger_D25
The 'strap' refers to internal chipset timings for the NB that are set for each FSB interval (ie: 533, 800, 1066, etc)Quote:
Originally Posted by Roger_D25
They usually become looser the higher the strap, to let the NB be capable of running at faster speeds (fsb)
Some are also hidden, and not selectable in the bios (such as this one)
http://www.xtremesystems.org/forums/...0&postcount=36
Quote:
Originally Posted by guess2098
Thanks guys for the explanation, much apprecaited! Now at each FSB interval is there a "Strap" which reduces NB/Memory Controller latencys or is there only one on this board up around 1699-1700Mhz as stated/showed by guess2098?
On a different note there has been some talk about a setting in the BIOS called "Execute Disable Bit", some say to leave it enabled and some say to disable it. Does anyone know one way or the other what should be done with this setting on the 680i? At the moment I have it disabled, but in the past I've also had it enabled and couldn't notice any difference. Then again I'm only running "Unlinked" at FSB: 1400Mhz and MEM: 1150Mhz so maybe at these lower speeds it doesn't come into play?
Disable bit is hardware antivirus, kinda. I pulled this right from windows help and support:
Some errors may be interpreted as "bad data", and may cause this to enable, and may be why some set it to disable.Quote:
Understanding Data Execution PreventionData Execution Prevention (DEP) helps prevent damage from viruses and other security threats that attack by running (executing) malicious code from memory locations that only Windows and other programs should use. This type of threat causes damage by taking over one or more memory locations in use by a program. Then it spreads and harms other programs, files, and even your e-mail contacts.
Unlike a firewall or antivirus program, DEP does not help prevent harmful programs from being installed on your computer. Instead, it monitors your programs to determine if they use system memory safely. To do this, DEP software works alone or with compatible microprocessors to mark some memory locations as "non-executable". If a program tries to run code—malicious or not—from a protected location, DEP closes the program and notifies you.
DEP can take advantage of software and hardware support. To use DEP, your computer must be running Microsoft Windows XP Service Pack 2 (SP2) or later, or Windows Server 2003 Service Pack 1 or later. DEP software alone helps protect against certain types of malicious code attacks but to take full advantage of the protection that DEP can offer, your processor must support "execution protection". This is a hardware-based technology designed to mark memory locations as non-executable. If your processor does not support hardware-based DEP, it's a good idea to upgrade to a processor that offers execution protection features.
In regards to the strap...it's really dependant on BIOS. not all chips are capable of all speeds at the same settings(as is well known), so a "norm" is introduced. Some board makers will modify these settings to gain performance, sometimes at the sacrifice of high clocks ;), blah blah blah.
Interesting cadaveca, I've heard of DEP before but I didn't know it was related to the "Execute Disable Bit" setting in BIOS? My initial thought is that these two things are not related but I've really got no idea? I've read through the Owners Manual but it's fairly vague about this setting which is the same explanation I get by searching online for this setting. I guess I should just test it myself in both enabled and disabled. Thanks for your help cadavaeca!
"Execute disable bit" would be the "hardware support" the tidbit above alludes to.
Oh yeah, sorry about that! Now that I know a bit more about this setting is it something that actually has an effect on overclocking or stability? I realize some have said it does but given what this setting is, it doesn't make much sense that it would effect overclocking stability or booting/not booting issues?
My ballistix just died overnight. Wouldn't even let the board boot they were so dead. Started off by crashing windows. I tried another cpu, still wouldnt boot, so I swapped back to my old 512MB d9 fatties...and voila! Boot. So I guess I'll be rmaing. How weird is this?
What happened:eek:
Running CAS 3 on non-anniversary ballistix, maybe? Try CAS4.
:eek: how ? too much voltage? :slap:Quote:
Originally Posted by EnJoY
Not even close, I was running 2.25v actual through them and they were always cool to the touch. I really have no idea why they failed. I can tell you though, something about Ballistix just makes them love to die on me. :confused:Quote:
Originally Posted by GrimReaper
Yea, lol...maybe if they still booted I could try cas 4... :rolleyes:Quote:
Originally Posted by cadaveca
Timings wouldn't have killed them, I'm really not sure what happened, maybe just duds?
You got to get those bad crucial exorcist:D
Can you try to set Vdimm @ at least 2.2 (all else at default) and reboot?
2.2v for CAS3 800mhz+ is not a long-lived setting, unless you got sticks rated @ CAS3, or are willing to give 2.4v+, from what I have found. I only have a few sets tho. The kits the USED to do CAS3 don't anymore either, but will run CAS4 with no issues, and now scale over 1150mhz w/ 2.2v CAS5.
Dumo, the system won't boot at all with them in. I tried holding alt, insert, and I even cleared CMOS twice. No go... :( They are dead.Quote:
Originally Posted by Dumo
Now I'm forced to use Kris's D9 Fatty's that he lent me awhile back, which are probably the worst fatbodies every created....one stick can't handle more than 2.15v without freaking out. :confused:
(edit, I'm also testing an e6400 right now...so the ram couldn't have died at a worse time, I could really use there high clocking potential right now.)
Well fortunetly Crucial is known for great customer support so your RMA should go smooth, hopefully their not replacing the D9's with Promo's though on new modules, lol!
I'm RMAing through Newegg actually. I've seen quicker turnaround times through them than through Crucial.Quote:
Originally Posted by Roger_D25
Crucial IS part of Micron, so no worries about that.Quote:
Originally Posted by Roger_D25
:eek:
EnJoY
you could boot up with the old fatys and set the the voltage to 2.3, shutdown and try the cursed ballistix again :p:
Ya know, I think I will actually. ;) I'll see if they come back from the dead after sitting here on my desk, cold. ;)Quote:
Originally Posted by GrimReaper
Its this ram SPP default for N680 board...Quote:
Originally Posted by cadaveca
http://img108.imageshack.us/img108/4...shot017kx5.jpg