April 27, 201115 yr So I built my first computer back in January and I have been loving it ever since but I seem to be having a problem. When I change the setting in the bios for the ram to 1600 the boots are weird. It boots then shuts off the boots fine. I change it back to 1333 and it works how it should. I even did the auto overclock software and it leads the same thing when it overclocks the ram and cpu
April 27, 201115 yr Author 1305 and no. The thing thats throwing me off is it did it on rev 2 and does it on rev 3*also to add, recently on a few boots its giving me a overclock failure error.
April 27, 201115 yr A clear cmos should fix it. It's a known issue.There's a newer 1504 BIOS, I would update it following the "official" method:1. Reset your UEFI to Optimized Defaults, reboot, enter UEFI and then flash to the new UEFI build.2. After flash and restart, enter Windows/Linux, then exit and shutdown.3. Remove the power cord from the power supply, wait thirty seconds, press Power On button to clear any remaining charge, clear CMOS for five seconds, reattach the power cord, power on the system, enter UEFI, set to Optimized Defaults, save and exit.4. Enter UEFI, set your system to customized settings based on your system configuration (RAID, OC, etc), save and exit.
April 27, 201115 yr Author When you say "clear cmos for 5 seconds" what do you mean?EDIT: you saying remove the battery for 5 seconds?
April 27, 201115 yr Author Ok, I think I have concluded that it wasn't what I thought it was. Before this I didn't know how to overclock at all so I let itself overclock and I was getting this problem but not at default clocks but I just did a bit of reading on it. Not 100% on it but understand it enough and I think the problem was not enough voltages. I did the autoclock thing after the flash and still had the problem and now after doing the overclock myself it seems to be working. I think it was because it wasn't bumping up the cpu voltage enough. Well now I just booted into windows at 4.5ghz and on the reset it didn't shut off then boot but instead a continuous (like its supposed too) reboot. So, I thought I could have trusted that autoclock but I think it can't be trusted AT ALL. Anyways I got a 4.5ghz overclock and it just bluescreened on a intel burn test lol (guessing not enough voltage)EDIT: Thanks for the help Dario anyways! Much appreciated!
April 27, 201115 yr No problem Taylor. well, knowing how to clear the cmos will come handy sooner or later. How much full load Vcore do you have now?My settings in BIOS, just in case they work for you too:AI Overclock Tuner = ManualBCLK/PEG Freq = 100Memory Frequency = Start OCing with RAM underclocked (1333 CL9 or something like that). Once you have a rock solid CPU OC, set your RAM at 1600 and stress - test again OC Tuner = DisabledEPU Power Saving = DisabledEPU Settings = DisabledDram Timing Control = Same as RAM frequencyInternal PLL overvoltage = Enabled CPU Ratio = ManualTurbo Ratio = By All CoresBy all cores = 45 for 4.5GHz in your case, as you obviously already knowTurbo Mode = EnabledLoad Line Calibration = Personal preference, normally High at least. I use Extreme for a negative Vdroop.VRM Spread Spectrum = DisabledVRM Frequency = ManualVRM Fixed Freq Mode = AutoPhase Control = ExtremeDuty Control = ExtremeCPU Current Capability = 130% CPU Voltage = Offset. If you set it to Manual, Vcore will not throttle back when idle even with C1E enabled. You'll need to play with the offset value to get your Vcore where you want it to be. More later VCCIO = 1.1V (isn't that important anymore in Sandy Bridge, don't go higher than 1.2V if you want to play with it)Dram Voltage = whatever your RAM is rated to. maximum 1.65V Advanced -> CPU Configuration PageIntel Adaptive Thermal Monitor = EnabledActive Processor Cores = AllLimit CPUID Maximum = DisabledExecute Disable Bit = EnabledSpeedstep = Enabled (Throttles back CPU frequency to 1.6GHz when idle)Turbo = EnabledC1E = Enabled (Throttles back Vcore to some 0.9V when idle)C3 = Disabled (disabling C3 & C6 helped me stabilize my OC, worth a try maybe)C6 = DisabledThe offset value to achieve a certain full load Vcore depends on Vdrop, Vdroop, target clock speed and LLC level:Here's a table with aproximate values. I think it was messured at 4.6GHz (disregard the VID column):So for example, if you want 1.35V and your LLC is at Ultra High, set your offset value in BIOS to -0.010. It's not going to be exact, but it's a good place to start.Remember, Vcore at full load is what matters.Are you familiar with Vdrop, Vdroop and all that?
April 27, 201115 yr Author Here are what I got now for settings.Overclock Tuner = ManualBCLK/PEG Freq = 100Memory Frequency = 1600 OC Tuner = DisabledEPU Power Saving = DisabledEPU Settings = DisabledDram Timing Control = Same as RAM frequencyInternal PLL overvoltage = Enabled CPU Ratio = ManualTurbo Ratio = By All CoresBy all cores = 45 for 4.5GHz in your case, as you obviously already knowTurbo Mode = EnabledLoad Line Calibration = AutoVRM Spread Spectrum = DisabledVRM Frequency = autoVRM Fixed Freq Mode = AutoPhase Control = StandardDuty Control = T-ProbeCPU Current Capability = 130% CPU Voltage = I had it at 1.305 with manual seems like I should go with offset?VCCIO = 1.1VDram Voltage =1.5V Advanced -> CPU Configuration PageIntel Adaptive Thermal Monitor = EnabledActive Processor Cores = AllLimit CPUID Maximum = DisabledExecute Disable Bit = EnabledSpeedstep = Enabled (Throttles back CPU frequency to 1.6GHz when idle)Turbo = EnabledC1E = AutoC3 =AutoC6 =Enable
April 27, 201115 yr I think you simply lack volts there. At 1.305 and LLC in Auto, you will probably have no more than 1.27V full load. Full load Vcore is what determines stability, that's what we need to know Taylor.You don't need to, but setting LLC to High, Ultra High or Extreme will reduce Vcore when idle (Vdroop).Same with offset: you don't need to use it, but if you want your system to switch to a low power mode when idle or moderate load, offset is the way to go. Otherwise you will have your maximum vcore all the time, even when not needed. You can always use manual mode to find out what full load Vcore your 2500K needs to be stable and then switch to offset mode and find the offset value that will deliver the same Vcore at full load that you found stable in Manual mode
April 27, 201115 yr Author Yep, I am kind of figuring that out. I think before when I was doing it where it was overclocking itself it would boot up weird. I get the same result when I change it to 1.3 or less but 1.305 doesn't do the weird boot. By the way I tried LLC at high with -.025 and it bsod on boot. May I will try high but like -.01
Create an account or sign in to comment