You only increase vCore when you face stability issues.

If your OC is stable as it is, you shouldn't touch anything.

If you don't touch your Vcore you're leaving it to Auto, so the motherboard is actually overvolting for you.

You should double check it's not overvolting too much, temps are fine and test for stability.

That "bump the multi and go" overclock is not the best way to go about it

Yeah, leaving voltages at auto when overclocking is a big no-no in my book. I have heard countless stories where people have fried their motherboards and chips due to auto voltage (mobos more than cpus)

About setting the Vcore some help needed please.

 

My bios states under "Mother Board Voltage Control" / CPU Vcore:

Normal = 1.380

Current = [Auto]

 

Raising my CPU Vcore means replacing "Auto" with, for example, 1.380 V?

Does this mean that Voltage will be permanently steady and not exceed 1.380V?

 

Christos

About setting the Vcore some help needed please.

 

My bios states under "Mother Board Voltage Control" / CPU Vcore:

Normal = 1.380

Current = [Auto]

 

Raising my CPU Vcore means replacing "Auto" with, for example, 1.380 V?

Does this mean that Voltage will be permanently steady and not exceed 1.380V?

 

Christos

 

I guess that means that your board is setting 1.38V for that 45 multi.

Probably some 1.36V in Windows at full load without Load Line Calibration, which would be perfectly safe.

To make sure you should download CPU-Z to monitor your Vcore, Core Temp or Real Temp for temperatures, and run a stress test like Prime95 for a while.

If your temps are below 80ºC and your Vcore below 1.38V, you should be ok to test for stability for at least 8hours of Prime95.

Then you could optimize your OC finding the lowest Vcore at which you are stable at 4.5GHz.

I am already monitoring the Vcore throught the CPU-Z and I never noticed it exceeding 1.056 V.

Usually it is at 1.044.

 

 

Christos

I am already monitoring the Vcore throught the CPU-Z and I never noticed it exceeding 1.056 V.

Usually it is at 1.044.

 

 

Christos

 

You need to monitor Vcore at full load Christos (Prime95), or the power saving features will kick in. That voltage is too low, which means SpeedStep/C1E is doing it's thing and your CPU frequency is probably down to 1.6GHz since it's idle.

At full load you also factor in Vdrop & Vdroop and you get the real Vcore being applied to your chip. Full load Vcore is what matters, and full load temps

I have made a stress test with Prime95 for 3 hours now. (Later I will do an 8 hour test).

 

The readings so far:

All self test until 16k passed succesfully.

CPU Core Voltage: stable at 1.056 V

Core Speed: 4,5 ghz

Core temperatures highs (all at 100% load): #0 = 67, 1 = 70, 2 = 74, 3 = 68.

 

How does it look like as regards the performance and stability of my system?

 

Christos

I have made a stress test with Prime95 for 3 hours now. (Later I will do an 8 hour test).

 

The readings so far:

All self test until 16k passed succesfully.

CPU Core Voltage: stable at 1.056 V

Core Speed: 4,5 ghz

Core temperatures highs (all at 100% load): #0 = 67, 1 = 70, 2 = 74, 3 = 68.

 

How does it look like as regards the performance and stability of my system?

 

Christos

 

That Vcore can't be right. Is that a Gigabyte motherboard? I think CPU-Z failed to display the right Vcore with some GB boards.

Try HWMonitor or SpeedFan

 

Other than that, temps look good. How long did it take Prime to get to the 16K test? There's nothing set on stone for test lenght. Some run 8 hours, some 24 hours

Ok, I will later install HWMonitor to double check the Vcore voltage.

 

Yes, it is a Gigabyte motherboard Z68X-UD3P-B3.

 

By the way with Core Temp VID reading was 1.4011 V during the stress test. (I don't know if this is something different.)

 

Christos

Ok, I will later install HWMonitor to double check the Vcore voltage.

 

Yes, it is a Gigabyte motherboard Z68X-UD3P-B3.

 

By the way with Core Temp VID reading was 1.4011 V during the stress test. (I don't know if this is something different.)

 

Christos

 

VID is a different thing, ignore that. Once overclocked, that VID reading doesn't mean much anyway