[QUOTE=pegnose;422580]I already asked here about this difference, but gut no answer.[/QUOTE]

Gut no answer?

Oopsie.

Re-reading this thread...

others have experienced freezes as well, which seem to be cured by bios 1402:
[url]http://www.mersenneforum.org/showpost.php?p=420747&postcount=206[/url]

But it is discussed to be indicative of different bug:
[url]http://www.mersenneforum.org/showpost.php?p=420954&postcount=256[/url]

[QUOTE=pegnose;422584]Re-reading this thread...

others have experienced freezes as well, which seem to be cured by bios 1402:
[URL]http://www.mersenneforum.org/showpost.php?p=420747&postcount=206[/URL]

But it is discussed to be indicative of different bug:
[URL]http://www.mersenneforum.org/showpost.php?p=420954&postcount=256[/URL][/QUOTE]

Regarding the second link and the hard lockup, I'm not so sure it's related to this AVX bug (my 6700k system experiences both). I've been participating in that thread extensively and from the looks of it, it seems like either a chipset or Skylake IMC bug/incompatibility. Probably growing pains with DDR4. The reason I say that is because many people have had luck in at least increasing stability by increasing either VCC or VCCIO or both. I haven't been able to get rid of the hard lock completely yet, but in playing with timings and voltages I have been able to reduce the frequency of hard locking from about once per day to once per week. Because of how infrequently it happens now, trying new things and seeing if it makes any differences is taking a long time.

Oh and somewhat interestingly, it almost always happens when the system is idle (ie. no interrupts from user input).

[QUOTE=s1riker;422585]Oh and somewhat interestingly, it almost always happens when the system is idle (ie. no interrupts from user input).[/QUOTE]

Then you are dealing with a very different situation.

Until you have a nominal stable system you should go back and try to figure out what's wrong.

[QUOTE=chalsall;422595]Then you are dealing with a very different situation.

Until you have a nominal stable system you should go back and try to figure out what's wrong.[/QUOTE]

Yeah I agree. The point was this instability is affecting quite a few people with a whole range of motherboards and RAM modules, so it points to some CPU/chipset bug that is yet to be fixed. I've been building systems for years and I've never had this much trouble getting a new build to be stable (been trying since August). Anyhow just wanted to point out that this is likely another issue entirely and not tied to the AVX bug discussed in this thread.

[QUOTE=s1riker;422609]Yeah I agree. The point was this instability is affecting quite a few people with a whole range of motherboards and RAM modules, so it points to some CPU/chipset bug that is yet to be fixed. I've been building systems for years and I've never had this much trouble getting a new build to be stable (been trying since August). Anyhow just wanted to point out that this is likely another issue entirely and not tied to the AVX bug discussed in this thread.[/QUOTE]

Please forgive me for this, but I don't think you have a clue about what you are talking about.

If I'm wrong, then please present testable evidence to the contrary.

[QUOTE=chalsall;422611]Please forgive me for this, but I don't think you have a clue about what you are talking about.

If I'm wrong, then please present testable evidence to the contrary.[/QUOTE]

The evidence has already been presented that it's likely not linked to the 768k bug: Increasing voltages reduces the incidence of the lockup. Also, it happens at idle.

Why are you attacking him?

[QUOTE=VBCurtis;422626]The evidence has already been presented that it's likely not linked to the 768k bug: Increasing voltages reduces the incidence of the lockup. Also, it happens at idle.[/QUOTE]

No, it hasn't been presented. The evidence presented suggests that clocks nor voltages don't have any influence on the bug found.

[QUOTE=VBCurtis;422626]Why are you attacking him?[/QUOTE]

I'm not "attacking". I'm asking for supporting evidence of a claim.

[QUOTE=s1riker;422609]The point was this instability is affecting quite a few people with a whole range of motherboards and RAM modules, so it points to some CPU/chipset bug that is yet to be fixed. I've been building systems for years and I've never had this much trouble getting a new build to be stable (been trying since August).[/QUOTE]

So, I'm now under attack for questioning you...

My first question is, are you overclocking any of your systems and/or sub-systems?

My second question is, are you being methodical in your testing?

[QUOTE=s1riker;422585]Regarding the second link and the hard lockup, I'm not so sure it's related to this AVX bug (my 6700k system experiences both). I've been participating in that thread extensively and from the looks of it, it seems like either a chipset or Skylake IMC bug/incompatibility. Probably growing pains with DDR4. The reason I say that is because many people have had luck in at least increasing stability by increasing either VCC or VCCIO or both. I haven't been able to get rid of the hard lock completely yet, but in playing with timings and voltages I have been able to reduce the frequency of hard locking from about once per day to once per week. Because of how infrequently it happens now, trying new things and seeing if it makes any differences is taking a long time.

Oh and somewhat interestingly, it almost always happens when the system is idle (ie. no interrupts from user input).[/QUOTE]


Thank you so much, this is exactly what I am dealing with. I got my system stable at least for memtest86 by
- disabling the two unused dram slots
- enabling MCH Full Check (ASUS)
- setting dram voltage tolerance to 110%

But I still experience a freeze during Prime95. Yes, testing is a PITA. Currently I try setting 16-16-16-40 (instead of 39), which should be compatible in my case according to the manual.

From what I have heard, hard lock during idle could be a third problem. I had this when I had ASPM enabled for the link between SA and the PCH. Others suggested the PSU being incompatible with Haswell C-States (6/7). You could try disabling all power saving options altogether.