New
#1371
All of mine are fat32, I have never tried it NTFS.
For a small USB stick, there are no advantages formatting NTFS, and some drawbacks. Unless you need files over 4GB, there is really no reason to format NTFS. NTFS will also wear out the drive faster. A Guy
I notice that pretty much every overclock here seems to be accomplished solely through bumping the multiplier. Why no FSB increases? :)
Sandy Bridge is stock at 100, the max you can go (on my board) is 110 and from everything I hear, SB does not like it when you do. But to replace it, they give you an unlocked multiplier on the K chips. But, I'm sure you already knew that. Raising the FSB by 10 really isn't going to help that much.I raised mine a little to 100.3 with no ill effects.
Yep. Upping the BCLK isn't recommended for SB, the exact reason escapes me atm, but apparently there is a higher risk of damage.
The other major reason is that when you up the BCLK, it also affects the RAM speed which can potentially cause instability. But a few minute adjustments won't hurt.
I hadn't done much overclocking for some time. Back in the day a tried-and-true technique was to first try to push your FSB to max to check the limits of the RAM and chipset, then back it off a notch and work on the multiplier. In other words, once you knew what the rest of the system could handle you went for the max overall CPU overclock. My FSB does pretty well up to 105. Anything higher than that means lowering the multiplier so much that my overclock falls off dramatically.
Once I get the assignments for the week out of the way I may have to drop it back to 100 and see if I can get the multiplier a little higher. Right now I'm at 45 X 105 for a total of 4728 MHz. I view having my 1600 MHz RAM running at 1680 (the + 5% is due to the FSB increase) as a slight bonus, but if it's costing me several hundred MHz on the overall speed of the system I'll have a decision to make.
With SB, most of the old tried and true methods are turned on their head.
►Don't touch the BCLK
►Leave Speedstep/C1E enabled
►Use offset instead of fixed vcore.
I'll post a screen shot of my 24/7 4.6ghz offset stable settings (I want to test my BIOS screenie capabilities )
It might be useful for others as well to use as a guide.
Smarteyeballs settings. No guarantees
These are my 4.6ghz 24/7 stable with negative offset settings. *Ignore the DRAM voltages as my kit is rated at 1.65v. However, the VCCIO can help lower vcore. The rest of the settings are applicable. Upon further reading, up to 1.2000v on air with VCCIO is safe. I've also enabled the iGPU to fiddle with. If you don't use it, disable it.
These are my work in progress 4.7ghz 24/7 settings. I'm playing with lowering the DRAM volts.
And these are my 5.2 'encoding stable' settings. Fixed vcore, extreme this, extreme that. Not recommended for 24/7 use. (however give it a go guys, you might be surprised )
Thanks for posting. I wish more people would do the same. I think I will find them very useful.