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 the FSB frequency and either a sub-division or the PCIE frequency itself overlap, and you get a lovely result which I've seen some of you guys post regularly
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
Originally Posted by mikeyakame
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.
Reply With Quote
Bookmarks