I found that info on 2 or 3 different forums. And WHEA was allways solved by replacing CPU Skylake- desktop processors. And also by my recommendation - when 1 or 2 WHEA-guys disabled 2nd core in BIOS, their NUC was working without WHEA error next 2-3 days. After that time the same issue so it affects also 1st core
But the question is: what damaged CPU? CPU itself? Or something outside CPU = something on motherboard? So what's bad? Please vote :-)
2, CPU and something on MB
3, something on MB
Yes, they had different MBs. I don't know exact manufacturers, but in 1 case it was Gigabyte. But I don't think it's directly Skylake's problem...those were desktop CPUs, not mobile CPUs. I think that these CPUs are used in many notebooks without problem. So it must be problem on board, but it probably destroy also CPU (because it worked ok few days on 1 core...)
So situation is like this:
1, something broke on motherboard
2, it destroys something in CPU
3, CPU displays WHEA error (not because damaged component on board, but because of own internal damage)
*that component on motherboard maybe isn't damaged completely, it can be damaged only partialy. And I have feeling that it have something to do with voltage/powering core(s), Maybe when it fails, it sends too high voltage to CPU and burn something inside CPU... but this is really question for Intel
Sorry, I’m not sure about this… I have to ask what’s about some issue at some Skylake CPU like this http://www.pcworld.com/article/3021023/hardware/how-to-test-your-pc-for-the-skylake-bug.html (btw: I done the test for 3 hours at my NUC6i5 without any problem)… I don’t know about which kind of Skylake CPU you're talking at post #1 (it doesn’t sounds like NB soc’s if you talk about MB from Gigabyte at post #4)… maybe Intel have a problem with 14-nm-FinFET ? It wouldn’t be the first CPU from Intel with problems…
and one more argument is, that they replaced the CPU and everything is fine (of course you could be right and a problem “outside” of the CPU, after a while, damage the CPU (like a bad chip-set ))…
But that's different problem. All Skylakes had problem with that bug. I ran Prime95 long time and without issue. That's other thing that WHEA issue. I think we have solved it in some of BIOS-es (I don;t know in which). I wrote that people solved WHEA_UNCORRECTABLE_ERROR boot loop by replacing CPU. If they received WHEA again after some time...I don't know. Maybe yes
Intel is actively investigating the “WHEA UNCORRECTABLE ERROR” issue reported on the Intel® NUC Kit NUC6I3SYH, Intel® NUC Kit NUC6I3SYK, Intel® NUC Kit NUC6I5SYH, and Intel® NUC Kit NUC6I5SYK products. We have replicated the issue with BIOS 0039. We do not currently have a workaround for this issue.
Customers who see this error repeatedly on this product are encouraged to contact Intel Customer Support. We will provide an additional update by Friday, April 8, or sooner if relevant information becomes available.
Intel continues to actively investigate the "WHEA UNCORRECTABLE ERROR" issue reported by end users on the Intel® NUC Kit NUC6I3SYH, Intel® NUC Kit NUC6I3SYK, Intel® NUC Kit NUC6I5SYH, and Intel® NUC Kit NUC6I5SYK products.
Intel has an internal task force diligently working to resolve this issue as soon as possible and deliver a robust solution for affected users. Intel does not currently have a workaround for this issue.
Intel confirms the issue currently being investigated is not corrected by any current BIOS, limiting C-states, updating the operating system software, or replacing peripheral components.
Intel appreciates the patience exhibited by affected users while we work to resolve this difficult issue. Users who see this error repeatedly on this product are encouraged to contact Intel Customer Support for assistance.
Intel will provide another update by Friday April 15, or sooner if relevant information becomes available.
This message was posted on behalf of Intel Corporation
Whea issue is already resolved; it is necessary to update the BIOS to version 42. .
Drivers & Software
Intel is providing further assistance for this issue through the contact center.