Post Your Overclock!

[essenbe]

I think you are right Gene, I set the values but it would change them back. In fact it changed almost everything I set. I disabled firewire as I don't use it. It was enabled next time I went in. I think it is Gremlins and the board is possessed.

@Gary, the biggest problem I have is your luck has rubbed off on me. I never have problems like this.

 

[GeneO]

Yuch. My settings stick at least. I am sure you exited saving changes.

 

[Britton30]

@Gary, the biggest problem I have is your luck has rubbed off on me. I never have problems like this.

But you've taught me all I know.

 

[essenbe]

Well Gary, you don't know much then. And, yes Gene I saved the settings. Man would I feel stupid if I hadn't. Honestly, I wish I could blame it on something that simple. As tired as I am, I would be taking it back out of the box. I can honestly say, I have never had a board that was bad right out of the box. That is, until I met Gary. Darn him!

 

[Britton30]

Well Gary, you don't know much then. And, yes Gene I saved the settings. Man would I feel stupid if I hadn't. Honestly, I wish I could blame it on something that simple. As tired as I am, I would be taking it back out of the box. I can honestly say, I have never had a board that was bad right out of the box. That is, until I met Gary. Darn him!

:roflmao:Gene musta caught it too.

 

[profdlp]

I'm beginning to feel very lucky.

 

[essenbe]

I'm glad one of us is. But, I'm happy for you.

 

[profdlp]

The fact that both of you got burned at the same times makes me wonder if they had a bad batch. What revision of the board did you guys get?

 

[smarteyeball]

I'll take your word for it smarty. I have to admit that I was glad for a windowless case.

lol, that does help too.

The three I have in my current case (2 CPU, 1 exhaust) are hidden. In a perverse way, I actually miss seeing them like I could in the HAF

Patrick, my case will have blue LEDs inside so the "puke" effect will be somewhat lessened.

That will help. They tend to 'blend in' okay with most colours from what I've found. Blue will be nice.

Although if the love transition is just not coming, you could always use coloured masking tape on the outer rim as an a cheaper/less destructive alternative to painting.

Actually they look better in hand than in pictures...a little bit.

Congrats, you've passed your transition step - no immediate revulsion!

 

[smarteyeball]

with standard LLC. I think I somewhat killed my previous processor with LLC, so I want to keep it at Intel standard.

I'm not sure what setting your P55 LLC default was, but the default on your new board should be Auto/Regular=0% which follows the intel spec.

I had to set a negative .06V Vcore offset to get the load voltage down to near 1.2V. This resulted in very low processor voltages when idle and C1E kicked in. Since these freezes usually happened under light load, I suspect that maybe Vcore dropped too low. [/quote]

Yep. I had drama and Bsod's using -.06, but none around the -.05v mark iirc. I Primed at .03v, but haven't encountered any problems using -.045v offset for a while after using that. It does sound like your idle vcore was just a bit to low.

On M4 + driver front, I know the default Windows iaStor.sys 10.8.0.1013 version is stable. (only because I just noticed I haven't updated that driver yet ) Presuming the drive itself is fault free, that can be ruled out.

So far my take on the BIOS on this MB is it really isn't that accurate. The offset voltages are very strange and for manual setting of Vcore the Vdrop is pretty high.

The reported fluctuations are a tad suspect.

If not, then it might actually be the new architecture in effect. Part of Sandy+this mobo preservation and stability tricks we're not as used to seeing.

the maximum for the Intel spec for this CPU is 1.56 or thereabouts.

As long as the VCCIO (QPT) stays within the .5 variance of the DRAM voltage, it's good up to around 1.7v. Same variance rule as the older socket.

 

[essenbe]

The V-Pro has pretty good ratings at Newegg. I'm just surprised. Mine was a total wreck, I tried everything I know and it wouldn't respond. I'm just debating on getting a replacement or a refund and get something else. I never tried to OC it, I spent 2 hours just getting it to post.

 

[A Guy]

Damn shame Steve, I know you were probably (initially) excited to have a new board coming. A Guy

 

[essenbe]

Thanks Bill. I had illusions of grandeur.

 

[GeneO]

with standard LLC. I think I somewhat killed my previous processor with LLC, so I want to keep it at Intel standard.

I'm not sure what setting your P55 LLC default was, but the default on your new board should be Auto/Regular=0% which follows the intel spec.

I had to set a negative .06V Vcore offset to get the load voltage down to near 1.2V. This resulted in very low processor voltages when idle and C1E kicked in. Since these freezes usually happened under light load, I suspect that maybe Vcore dropped too low.

Yep. I had drama and Bsod's using -.06, but none around the -.05v mark iirc. I Primed at .03v, but haven't encountered any problems using -.045v offset for a while after using that. It does sound like your idle vcore was just a bit to low.

On M4 + driver front, I know the default Windows iaStor.sys 10.8.0.1013 version is stable. (only because I just noticed I haven't updated that driver yet ) Presuming the drive itself is fault free, that can be ruled out.

So far my take on the BIOS on this MB is it really isn't that accurate. The offset voltages are very strange and for manual setting of Vcore the Vdrop is pretty high.

The reported fluctuations are a tad suspect.

If not, then it might actually be the new architecture in effect. Part of Sandy+this mobo preservation and stability tricks we're not as used to seeing.

the maximum for the Intel spec for this CPU is 1.56 or thereabouts.

As long as the VCCIO (QPT) stays within the .5 variance of the DRAM voltage, it's good up to around 1.7v. Same variance rule as the older socket.[/QUOTE]


I have LLC on regular. I have it set to manual voltage now of around 1.22 unloaded (the BIOS set to 1.25). I have tried the latest iastor as well. Still freezing/locking up here. I did see a couple of errors in the log as a result of these freezes. One was the discrete GPU quit responding and another time the iGPU quit responding. So something is locking them up. If the audio is playing during a freeze it makes an god awful continuous noise too.

 

[GeneO]

As long as the VCCIO (QPT) stays within the .5 variance of the DRAM voltage, it's good up to around 1.7v. Same variance rule as the older socket.

Right, and the limit for VCCIO in the spec is about 1.07 which would put the maximum Vram at about 1.57 and this is about what the spec says is the maximum RAM voltage. So putting your RAM at 1.7 and following the 0.5 rule puts VCCIO way out of spec.

 

[essenbe]

Looks like my problem was the board. I put the ram in my Asrock P67 and it booted first try,

 

[GeneO]

Wow, that is pretty good memory performance Steve.

 

[smarteyeball]

I have LLC on regular. I have it set to manual voltage now of around 1.22 unloaded (the BIOS set to 1.25). I have tried the latest iastor as well. Still freezing/locking up here. I did see a couple of errors in the log as a result of these freezes. One was the discrete GPU quit responding and another time the iGPU quit responding. So something is locking them up. If the audio is playing during a freeze it makes an god awful continuous noise too.

Interesting the iGPU is showing up in the errors. Do you have the Lucidlogix vitru software installed at all?

As long as the VCCIO (QPT) stays within the .5 variance of the DRAM voltage, it's good up to around 1.7v. Same variance rule as the older socket.

Right, and the limit for VCCIO in the spec is about 1.07 which would put the maximum Vram at about 1.57 and this is about what the spec says is the maximum RAM voltage. So putting your RAM at 1.7 and following the 0.5 rule puts VCCIO way out of spec.

Hmm. The spec sheet does say that, yet I've read multiple places that the VCCIO is fine up to 1.2v for 24/7 air...

My kit is rated for 1.65v and I've been running my VCCIO at 1.15v - Might be time to look into that a little further I think.

Looks like my problem was the board. I put the ram in my Asrock P67 and it booted first try,

View attachment 199516

Winrar!

Sounds like it was a bad board. The thing with Asus boards that good ones are great and the bad ones are rage inducing.

If it's not flat out DOA, nailing down a gremlin is almost an art form.

 

[GeneO]

No the Virtu software is not installed.

Well I have I think good news. It looks like my problem was with the Nvidia drivers. They came out with a new official release today and I haven't had a freeze or stutter since this morning - KOW! I had been running their beta driver since last November or so as their last official release had a serious bug that affected me. It was so long ago I cannot even remember what the bug was. They had fixed it in beta but haven't released an official driver until today. Funny it didn't have any problems on my P55 board.

Coincidentally, Asus came out with a new BIOS for this board today with Stability and compatability fixes which I just flashed. It is looking good know (again KOW!).

I will give Asus a break for my original dud with the sound issues because the shipping was so poor. The housing with the sound connectors didn't fit into the shield template very well when I installed the motherboard. I can imagine that it might have got slammed in the shipping and resulted in the sound issue. Sound is great on the replacement.

Gene

 

[profdlp]

...The thing with Asus boards that good ones are great and the bad ones are rage inducing...

You stirred a long-dormant memory from my past.

Back in the Socket 7 Days I spent about six months wrestling with an ASUS A7V. It would have actually been better if it had been a total loser, since I would have wasted less time with it than I did. It had a remarkable knack for running fine for weeks, then going on a three-day crapfest. If a motherboard could behave like a binge-drinking alcoholic, this was it.

For some reason I can't remember (carelessness on my part, maybe?) I ended up replacing it with an ASUS A7V133, the only difference being that the replacement board had been upgraded to the (virtually inconsequential) ATA133 controller. It turned out to be one of the best boards I ever had.