Overclocking the UD5 with 12gb of ram.

Could you post your full bios settings Brightside? The most obvious omission there is qpi, if it's still at 1.15V or so that's probably the issue.

Are you using load line calibration or anything else similarly exotic?

As a final check, this crash was with windows 64 bit host system, 64 bit linux in a virtual machine? bigadv seems to be very hard on the system, my hunch is that it's swapping such large amounts of data in and out of ram which causes the problem. Certainly my only issues at 4.4 were when combining bigadv with virtualbox, and my system is very sensitive to qpi changes.

I'll do my level best to help, another guy folding bigadv would be excellent :)
 
QPI is set to whatever the default is, if that is a reasonably well defined property for the UD5. I'd rather not reboot to check right now (have a lot running, and even hibernate takes an age with 12GB memory as you probably know). I will do at some point though - maybe later this evening - and post the QPI. Anything that I haven't mentioned is set to whatever the UD5 defaults are.

I'm not not using load line calibration, from what I've read it's not a good idea due to the risk of Vcore overshoot - admittedly it probably wouldn't take Vcore above the maximum at the levels I'm using but it's a risk I'd rather avoid. Especially since with Folding the machine will be under full load all the time anyway, so the lower voltage at idle would be of little benefit.

This crash was with 64 bit Windows 7 host and 64 bit Linux in a VMware virtual machine.

If my QPI is still at 1.15V when I reboot to check I will probably change it to 1.3V as you have yours, bump the base clock back up to 200MHz and see how it does like that.

Cheers for the suggestion.
 
Just checked QPI - although I had it on auto, it had been set to 1.35V due to me using the XMP profile of my memory, so I guess I need to keep looking to see what's causing the stability issue at 4.0GHz.
 
1.35 may be too high actually. There's a balance between vdimm and qpi which seems to be processor specific, 1.3 qpi and 1.66 vdimm works for me, but 1.375 qpi needs vdimm of 1.7 for stability.

Other things to check are pll, while it starts as 1.8 and intel say 1.88V max, lowing it seems to help. I'm most stable at 1.7, other people have noticed a benefit to lowing it as far as 1.3.

Should have put this first really, but what's your uclock multiplier? It has to be at least twice the ram frequency. With x6 ram which I believe you're also using, x12 won't boot for me. x13 won't post either, x15 seems to be good.

12gb just makes everything a little more difficult.
 
Cheers guys. The OP is getting a little incoherent, I'll reformat it in the nearish future. "Simple" 4ghz appears bombproof, I'll have to update the OP with them. Now testing 4.2 with ibt v2.4, hoping the new version will prove a better stability test than the last one.

You'll be alright MI, 12gb is exciting. How hot are the board heatsinks running? I can't get anything like these results without a 120mm fan aimed directly at them

edit: bluescreen => memory subsystem failing? I think that's how I interpreted it on my P45 board anyway
 
Last edited:
Well my northbridge went up to 94°c and my VREG went to 88°c so i have a 80mm fan aiming at both of them and my CPU is OK only going up to about 75°c with 1.388 vcore
My voltages look like this at the moment and seem to be stable but will probably change when i add more ram :)
voltage.jpg
 
Some of those look pretty high to me, but I'm struggling to translate evga notation to gigabyte. Is cpu vtt the same as qpi voltage?

Those are pretty scary chipset temperatures, I forgot you're using an matx case. Don't suppose anyone makes a waterblock for the matx evga board?
 
JonJ678 said:
Some of those look pretty high to me, but I'm struggling to translate evga notation to gigabyte. Is cpu vtt the same as qpi voltage?
Click to expand...

I don't know if they are the same thing i will need to find out, i would like to know so i can compare with other people.

JonJ678 said:
Those are pretty scary chipset temperatures, I forgot you're using an matx case. Don't suppose anyone makes a waterblock for the matx evga board?
Click to expand...

The only waterblock i know was custom built by someone on the EVGA forum looked really nice made from two pieces of copper but think he never made many to sell :(
 
Ah, I saw that. Didn't have a water channel over the mosfets iirc but achieved good results regardless. Dekez may do one at some point but I'm nothing like skilled enough to I'm afraid. Fans are about the only option then :(

I'll have a look as well, someone's probably written a gigabyte - asus -evga translation page. Otherwise I guess we get to.
 
Yes CPU VTT is QPI/Vtt...

I agree with Jon in that your voltages are a little on the high side mate..

You shouldn't be needing to have IOH core at 1.400v or QPI PLL for that matter.

IOH/ICH I/O doesn't seem to make any difference neither, or ICH core, at least it doesn't for me, even when pushing 4.4GHz stable, I leave this setting on Normal, and for IOH core I only raise it to 1.140v.

When I first started pushing past 200Bclk, I was trying to use higher voltages on all these settings, and I couldn't get it stable at all, it wasn't until I brought these back down that things became stable, so using to much voltage when it isn't needed can cause a system to become unstable..
 
QPI PLL VCore (default: 1.1v, <1.4v is pretty safe)
What it does:

Keeps on-chip memory controller in-sync with bclk.

When to raise QPI PLL VCore:

* Try raising this along with Vcore and VTT, but in smaller increments.
* Helps stabilize higher CPU Uncore frequencies and QPI frequencies (in CPU feature)
* Try raising this when you increase memory clock speed via multiplier.
* Try raising when LinX produces errors after a few minutes without BSOD
Click to expand...

I've done nothing to this at all, appears I may wish to. Think I'll try it in the near future.

Google confirms cpu vtt as qpi voltage. Intel say nothing over 1.35 at any time, google thinks under 1.4 is fine but 1.45 is pushing it. 1.5V is higher than I've seen anyone using outside of phase, certainly not on 3 sticks of ram, this may well be hurting your stability. That said, xs reckons anything under 1.6V is fine so don't be too concerned :)
 
Last edited:
Not a fan of overclocking really slowly and carefully then :D

If you've got some time to spend on it you can probably get 4.0 with just vcore/qpi increases and the right uclock/qpi/ram multipliers. Then put pci-e frequency up by 2 or 3, put bsck up to 210 and start increasing vcore/qpi again. Good odds that'll be all you need to do.

Hopefully I'll be stable around 4.4 when you get your new corsair and I'll know more.

4 loops ibt at 4.2, then bluescreened. irql less than or equal to. Upped qpi & vcore a notch and will repeat. Five loops...
 
Last edited:
JonJ678 said:
Not a fan of overclocking really slowly and carefully then :D

If you've got some time to spend on it you can probably get 4.0 with just vcore/qpi increases and the right uclock/qpi/ram multipliers. Then put pci-e frequency up by 2 or 3, put bsck up to 210 and start increasing vcore/qpi again. Good odds that'll be all you need to do.

Hopefully I'll be stable around 4.4 when you get your new corsair and I'll know more.

4 loops ibt at 4.2, then bluescreened. irql less than or equal to. Upped qpi & vcore a notch and will repeat
Click to expand...

Normally when i overclock i just bung it in throw some volts at it and im done for a year till i upgrade so no not really slowly :D

4.1 is easy never used to be but 4.2 is hard might throw some more volts up it my poor H50 is not gonna like that :D:D
 
Don't think more volts will help tbh, more likely lowing volts will be the way forward here. Hard to be sure though, as I don't know what settings you changed :)

As you may have noticed, I overclock slowly when I'm unsure what I'm doing. I quite like the approach of finding a profile from someone with the same hardware then tweaking it to match yours, but I think there's something to be said for the learning process.

Temps should be a lot better now qpi is lower than 1.5, either vcore or qpi increases do bad things for cpu temp. I'm not sure how it scales with temperature, you may find lower voltages => lower temperatures, and it's then stable at these lower temps but not at the higher ones before the voltage drop. Turning on vdroop will probably lower mosfet temperatures, you'll need to set a higher vcore in the bios but probably won't see higher cpu load temps.
 
You must log in or register to reply here.
Back
Top Bottom