If you change PCI-E frequency, you should slightly raise Vsb same time since higher PCIE clock results in higher DMI clock since same clocking source, and believe me you don't want to cause instabilities whether constant or random there. DMI carries all SB inbound traffic, for all devices attached to the root hub or branching off.
Changing PCIE clock on the RF at high FSB is something that must be done to stabilize certain behaviours, such as infrequent DVD-R write errors, unstable/inconistent HDD/DVD transfer speeds on any or all devices connected to SB, etc, hell even fixes some barely audible sound static you get at some particular small frequency bands. anything connected to the NB through PCIE lanes it provides don't suffer these same problems, and changing PCIE frequency fixes them, so it's both the boards insufficient design for the speeds we run and the clocking reference frequencies devices connected to the SB use which use the same synchronous clocking source as the PCIE frequency and while at the same time the SB also has direct clocking reference pins from the CPU which surprise surprise are clocking with the FSB , which when you mix both together on a device that was designed for stepped fixed clock frequencies where there will be never be overlap, overlapping of FSB frequency and either a sub-division or the PCIE frequency itself overlap....you get a lovely result which I've seen some of you guys post regularly and hasn't clicked this might be the culprit or not making it any better at best
I'll give you a hint, one is BSOD's with driver filenames, another is display hardlocks, another funny yet rarer one is when randomly a key will get caught in a loop as if it was physically jammed or the mouse will move on its own
I'll welcome the day when vendors sell us hardware that is actually properly designed for the broad range of frequency adjustment they give is, and on top of that go out of their way to test for these kinds of problems which as you imagine come up too often, and usually as a result of the freedom to change frequencies with 1mhz steps. It's lovely for end-user and marketing tools to lever, but in practice it's a dead ringer for a darwin award nomination...
"WHY ISNT MY MOTHERBOARD STABLE AT XYZ FREQUENCY, AND WHY DOES AT XX.XX TIME ON YY DAY OF THE MONTH IT CRASH OR BEHAVE WEIRD....WHAT IS WRONG WITH MY SETTINGS........*months later board is RMA'd when its perfectly fine and person has to buy temp board or out of commission the machine until they get a replacement which they RMA immediately because it has the same problem with the first one*....and 9 times out of 10 the problem is simple, some guy said some settings worked great for them, and passed prime95 or linpack...so 100 other guys used them thinking they could avoid learning to do it themselves....maybe 50 guys actually have those settings work, and you can be all 50 have a different error they can't fix, and the first guy who they got them from had it there as well...but due to whatever it never effected him, maybe his PSU or a raid card he ran his drives off or a sound/network pci/pcie card he runs that are designed for maximum compatibility with other hardware, and his onboard stuff is disabled? more reasons than you'd ever want to know, and it's these problems that I see all over forums requesting help, that are fault of the user to a degree, but more fault of the vendor for giving him flexible adjustment with minimal effort/time/knowledge/experience.
DFI are number one when it comes to sink or swim with bios settings. If you don't understand the basics, and you are scared by pages of bios options with no help data, and documentation for what they do available to those who are lucky enough to actually find the damn thing and then translate engineer to english frequently, then don't buy DFI or don't change the settings.
Asus/GB with their one touch overclock, and marketing-gimmick-change-20-registers with our cool new clock twister enhanced feature, it doesn't tell u what it changes hell they even make sure it changes things they give you control over, and when you tell them there is a bug they thats impossible or we can't reproduce it because we didn't expect you to do something as crazy as changing an actual setting that we gave you because we thought you'd never use it, and we didn't mention it either because we are paranoid our competitors will steal our stolen idea, and that is far more important than helping an actual customer solve a problem....lets tell them it's their fault, but we are working on a new beta bios which may fix it if we can find the email I just lost with the information I won't remember. New bios same problem, turns out they didn't fix it because they got carried away adding a new sub menu that doesn't nothing important, but looks cool and can claim bios support, the acutal problem got forgotten because the 1% of ppl who have it only make up 1% sales, the other 99% won't see any changes so they won't believe our claim we make themThats Asus in a nutshell by the way
Customer: "Your bios is broken, x doesn't work properly..." Asus Engineer "Try this bios it adds new options" Customer "Ok...." Customer "This bios has same problem, and new features don't work right" Asus "Wait 3 weeks for new beta bios we are working on which will fix up problems" Customer "This new bios I waited for still has the same problem, but new features work right" Asus "we ran 2 tests and we couldnt reproduce it so there is no problem for us to fix...it is probably your cpu or memory or other hardware causing it...replace them at your own expense and if it still happens you can RMA the board under warranty...*while snickering to himself, hopefully by time he does all that he'll give up and we won't have to lose any more sleep worrying about a fix for that issue!*
Reply With Quote
Bookmarks