Reply to thread

Message

<blockquote data-quote="Lasherž" data-source="post: 8726969" data-attributes="member: 679555">Sorry I wasn&#039;t on when you encountered that. Secure-boot is one of the more problematic things that have been added in Windows and UEFI bioses but it&#039;s for anti-virus purposes so it should be enabled. It allows the boot to run in a secure environment and combats diversions to side-load nefarious code posing as drivers (worms) pretty well.I&#039;m pretty sure with secure-boot you need to choose whether you want it or not before installing the OS, but once you do then you&#039;ll want a &quot;known good settings&quot; UEFI preset to fall back on since overclocking can affect its ability to boot once it fails a check (often because memory or CPU cache read errors). Most (all?) overclocking motherboards have these programmable presets. People have lost their OS because of aggressive overclocking, but usually it doesn&#039;t happen. When it does go badly it&#039;s usually because the security key the hardware and drivers agree on is corrupt and they start disagreeing so the motherboard treats the legitimate driver/OS like a side-load.A side-note. When I overclock my memory I like to use a bootable memtest thumb drive to boot into instead of windows. It finds the obvious errors quickly and can help avoid corrupt files by not using important files when the memory is potentially exchanging information with the hard drive that could have bad memory states. Once you get it &quot;pretty&quot; stable (can pass a full memtest cycle) is when you start loading into Windows to run Aida64 on it.</blockquote>

[QUOTE="Lasherž, post: 8726969, member: 679555"] Sorry I wasn't on when you encountered that. Secure-boot is one of the more problematic things that have been added in Windows and UEFI bioses but it's for anti-virus purposes so it should be enabled. It allows the boot to run in a secure environment and combats diversions to side-load nefarious code posing as drivers (worms) pretty well. I'm pretty sure with secure-boot you need to choose whether you want it or not before installing the OS, but once you do then you'll want a "known good settings" UEFI preset to fall back on since overclocking can affect its ability to boot once it fails a check (often because memory or CPU cache read errors). Most (all?) overclocking motherboards have these programmable presets. People have lost their OS because of aggressive overclocking, but usually it doesn't happen. When it does go badly it's usually because the security key the hardware and drivers agree on is corrupt and they start disagreeing so the motherboard treats the legitimate driver/OS like a side-load. A side-note. When I overclock my memory I like to use a bootable memtest thumb drive to boot into instead of windows. It finds the obvious errors quickly and can help avoid corrupt files by not using important files when the memory is potentially exchanging information with the hard drive that could have bad memory states. Once you get it "pretty" stable (can pass a full memtest cycle) is when you start loading into Windows to run Aida64 on it. [/QUOTE]

Verification