I have overclocked my cpu to 4.5ghz. For some reason, I had to use a vcore of 1.37. Everytthing was stable but after the cpu was stressed for about 30 minutes (with a dvd making program), I got a blue screen. So I increased the vcore to 1.375. Again, while encoding dvd's, after about 45 minutes, I received a blue screen. So now I am at 1.38 vcore, but this is way high for a 4.5 ghz overclock on this cpu as I have seen others with a 4.6ghz overclock with like 1.32 vcore. I have load line calibration enabled in my bios. Do you have any ideas why my vcore is so high or any recommendations you have.Thanks.

Can you post your complete OC BIOS settings?What BIOS version? does it support PLL overvoltage?

I have overclocked my cpu to 4.5ghz. For some reason, I had to use a vcore of 1.37. Everytthing was stable but after the cpu was stressed for about 30 minutes (with a dvd making program), I got a blue screen. So I increased the vcore to 1.375. Again, while encoding dvd's, after about 45 minutes, I received a blue screen. So now I am at 1.38 vcore, but this is way high for a 4.5 ghz overclock on this cpu as I have seen others with a 4.6ghz overclock with like 1.32 vcore. I have load line calibration enabled in my bios. Do you have any ideas why my vcore is so high or any recommendations you have.Thanks.

I think it is your memory being overclocked. You need to download Blue Screen Viewer (Google) and run it and see exactly what was causing the blue screen. It will highlight the file that caused the crash. You can then Google that file and you'll probably find a solution. I know when I first started overclocking I was getting BSODs too and I ran the Windows Memory diagnostics and it stated I had a hardware failure (memory overclocked too much). The bios will usually increased the memory settings so you need to check that before you save the bios and restart. In any case, the blue screen viewer will give you a pretty clear description of what's happening and I wish Microsoft had included this program with Windows 7.Best regards,Jim

Can you post your complete OC BIOS settings?What BIOS version? does it support PLL overvoltage?

Yes I have f6 bios from gigabyte. I had the f6 beta and it supported PLL overvoltage but now the final release of f6 I don't see the PLL anywhere. I have a multiplier of 45, load line calibration to enable, and of course my vcore modified. These are the only things I've touched. I also have speedstep enabled.

I think it is your memory being overclocked. You need to download Blue Screen Viewer (Google) and run it and see exactly what was causing the blue screen. It will highlight the file that caused the crash. You can then Google that file and you'll probably find a solution. I know when I first started overclocking I was getting BSODs too and I ran the Windows Memory diagnostics and it stated I had a hardware failure (memory overclocked too much). The bios will usually increased the memory settings so you need to check that before you save the bios and restart. In any case, the blue screen viewer will give you a pretty clear description of what's happening and I wish Microsoft had included this program with Windows 7.Best regards,Jim

Okay I'll try that and see what I get.

Here are my results from blue screen viewer.Also how do I check if my memory was overclocked?

I think I am on to something here! I followed this guidehttp://www.bit-tech.net/hardware/cpus/2011/01/07/how-to-overclock-the-intel-core-i5-2500k/4And I was able to boot into the os at 1.32 vcore at 4.5 ghz which i tried before and I couldn't even get into windows and I ran cinebench with no bsod's! Is there anything you guys recommend to do differently than what this guide says? Also, one of the settings in this guide disable my speedstep and I would like to have this on. Does anyone know how which option to change based on this GUIs to regain speedstep.

Here are my results from blue screen viewer.Also how do I check if my memory was overclocked?

The hal.dll error indicates a hardware failure. I searched using Google for hal.dll bsod and found a related problem (hal.dll and bug check 0124) and one individual corrected the problem by increasing the voltage on the cpu and memory modules - http://answers.microsoft.com/en-us/windows/forum/windows_other-gaming/blue-screen-haldll/1b9d61b2-7935-451a-90ae-dbab0643b1bf . In your case you might have exceeded the voltage. There are several other potential solutions. I would reset your bios to the default and then look for the proper voltages for your motherboard/cpu and memory for overclocking. On my Asus board I have an item stating "Memory Frequency". If it is above my rated memory frequency (1600), then I will get a crash and when I automatically try to overclock, the bios always raises the frequency above my rated frequency. I reset it to Auto and the problem is gone.Best regards,Jim

The hal.dll error indicates a hardware failure. I searched using Google for hal.dll bsod and found a related problem (hal.dll and bug check 0124) and one individual corrected the problem by increasing the voltage on the cpu and memory modules - http://answers.microsoft.com/en-us/windows/forum/windows_other-gaming/blue-screen-haldll/1b9d61b2-7935-451a-90ae-dbab0643b1bf . In your case you might have exceeded the voltage. There are several other potential solutions. I would reset your bios to the default and then look for the proper voltages for your motherboard/cpu and memory for overclocking. On my Asus board I have an item stating "Memory Frequency". If it is above my rated memory frequency (1600), then I will get a crash and when I automatically try to overclock, the bios always raises the frequency above my rated frequency. I reset it to Auto and the problem is gone.Best regards,Jim

Yeah I think you were right about the memory because it was at auto and I set it to 1333 and like I said, I was able to boot into windows and run a cinebench on only 1.32 vcore (I did also change the ram voltage and turned off the c states like it said in the guide and like I've found other people have been doing). Of course, I ran a prime95 test and I bsodded after 1 minute so I still have to tweek the vcore but the fact that I was able to boot into windows and run a cinebench at only 1.32 to me shows me that I am on to more correct settings than I had before. Once I get everything stable I'll post here my final results.

I have another question. I read somewhere that the VID is the voltage the cpu is asking for and the VCORE is what it's getting. In coretemp, my cpu shows a VID of 1.3611 volts. Does this mean that I should set my vcore to a minimum of 1.365?

I'm at 1.35 vcore, using the same settings as the guide I showed above, and I can only run prime for about 5 minutes. Up until how much vcore is still considered normal for a 4.5 ghz overclock?

0x00000124 tends to indicate that the volts are too low. For me 1.365V gave 4.7Ghz but it depends on the chip. I would have though 1.35V would have been good for 4.5Ghz. Dont blow the chip up!

0x00000124 tends to indicate that the volts are too low. For me 1.365V gave 4.7Ghz but it depends on the chip. I would have though 1.35V would have been good for 4.5Ghz. Dont blow the chip up!

What exactly is the difference between vcore and vid. Coretemp shows a VID of 1.3611 or 1.3661, but cpuz shows that my vcore is only at 1.308 under prime95 stress. So why when I set the vcore to 1.35 I bsod if my vcore was only at 1.308 while running prime earlier.

I think I found what the culprit is-vdroop. I put 1.31 vcore (since CPUs told me that my CPU was running prime fine with 1.308 vcore)(for the vcore to be at this level I had to put a vcore of 1.38 and it drooped all the way to 1.308. So when I set the vcore to 1.31 (which my CPU should be able to do at 4.5 ghz fine, my vcore actually drooped to 1.268 and I got a bsod. I have load line calibration enabled so is there any way to reduce or eliminate this ridiculous vdroop? Thanks.Edit: I have done research and this high vdrop/vdroop seems to be a problem with my motherboard so I have gone back to stock clocks to see if a future bios update will solve the problem.

Try selecting Offset Mode in bios, then set offset volts to 0.095 and LLC to medium. Should be good enough for 4.7Ghz. (not sure what the exact terms are on the Gigabyte board). On the Asus board this allows the volts to change depending on CPU load.

I am on a ud4; make sure you enable llc in bios; that helps my vdroop to drop from 1.40 to 1.38-1.39 underload...I run at 4.8 with no issues on the ud4. UD5 and UD7 have more levels of llc; so if you are taking your ud3 back when you get the revised chipset after the recall; see if you can up to a ud5 or so; that will help with the oc stability as the bios has more options for llc. I only have on or off settings for llc on my ud4:(