Originally Posted by sixor
Originally Posted by Scotty99
In my experiences with SSD's ive found it best to enable AHCI and dont touch anything else, not even in windows. Taking this approach ive never had an SSD related blue screen, once i started doing "SSD optimizations" via SSD guides blue screens started showing. I think its because SSD's have come a long way in just a couple years.
is a must to:
disable pagefile, index, hibernation, defrag
have ahci or raid with latest intel irst,
i absolutely use this apps, 100% safe
I'm not so sure about pagefile/virtual memory.
Indexing I don't think matters, that was in regards to old drives. I think it's irrelevant either way, people disable because of additional writes (but those writes are so insignificant...), people keep it on because it's faster (but not by any significant margin at all..). Why bother turning it off. Or, why not turn it off, might as well not use those additional writes, right? I didn't mess with mine.
Hibernation, I actually have hibernation because that's what intel rapid start is. Or something like it.
w7 and w8 automatically dont defrag ssds.
What's the difference between the 3 different performance enhance profiles? There's normal, turbo, and extreme.
It's another one of the ways Gigabyte 'cheats' on the board so it gets better scores than others at stock settings, than places like TH will say omg what a great board it's faster at the same settings than the others!
It basically overclocks your RAM, one of the timings it changes. But the bad thing about it, is that it does it variably and on it's own.
So like during a benchmarking program, it'll specifically tighten a timing.
I forgot which one it is, it's only a specific, single timing. I'd be okay with it but the fact that it variably changes it means there's no way to stress test for it. If you don't overclock your RAM or just after benchmark numbers, extreme is great (even in benching though I'd be careful with it because it may cause instability issues) but if you overclock your RAM or run XMP then set it to normal.
Source: gigabyte admin guy on the gigabyte forum.
Running my z7xx-u4h, seem to be having problems with overclocking though. whenever I try and overclock (used 100x42 for 4.2) and set it up in the bios, it will boot fine, display the overclock and have no problems. When I start stress testing, it reverts back to 3.4Ghz stock clocks (I see it update in CPU-Z) it doesn't crash or reboot or anything like that.
running F2h bios.
It's because your overclock is unstable. This can also happen if your temps hit 105*C (throttling). Instability can manifest in thousands of ways but it's all the same - unstable is unstable. Increase voltage, lower overclock, etc...