Thank you for the information provided, aw_kreawit
I was wondering, were you using UEFI with the other computers that were mentioned (the ones working with Ubuntu 17.10)
Thanks,
Esteban C
Thank you for the information provided, aw_kreawit
I was wondering, were you using UEFI with the other computers that were mentioned (the ones working with Ubuntu 17.10)
Thanks,
Esteban C
Yes I try to find a solution to my problem. I contact the assitance of intel and now it works.
I mount the image iso with commands line in W10.
Thanks
vs2, thank you for your patience.
We detected an issue with BIOS 053 and we have already fix it on BIOS 054. You can find the version here: Download BIOS Update [BNKBL357.86A]
Regards,
Amy C.
Hi Okel.
Thank you for bringing this to our attention, I understand you are currently running Linux* Mint.
In this case, you need to check with the Linux distribution for drivers in regard to the Bluetooth device.
Let me do a research about this matter and I will get back to you with my findings.
Regards,
Allan J.
Hi CitizenNuc,
I have been investigating this issue with no success, part of the difficulties I have been dealing with are due to my location and usage of VPN services to reach out to Foxtel streaming services.
I believe it may be a good idea to have a local team looking into this situation, if you are okay with this, can you please send me a Private Message with your phone number so that the local team can call you and work on this directly? You can also call us (if you will, here is the contact us information, please make sure that you select the correspondent region: https://www.intel.com/content/www/us/en/support/contact-support.html#@6) and make reference to case 2948230
Regards,
Ronny G
Hi Chris
I have been discussing my issue with various support people at INTEL. Actually Scott Pearson suggested that you would be interested in this issue and the analysis I have ran using SSU and attached above.
Don't know if this will reach you. If not can you tell how to reach you. An e-mail would be great and I will keep posting as I try different things.
So far no solution.
My post is on the Community - Category 4 - NUC6i7KYK - Titled - NUC6i7KYK and LG 27UD88 - 4K Monitor.
Let me know how to make this post reach you
Thank you
Regards
Sasharoo
Hi Allan,
Thanks for your response. I forgot to update this thread but I managed to get the Bluetooth working in the end by simply updating the Linux Firmware manually.
All is working well now.
Hi folks,
today I have changed the DIMM to scenario 4 according to this table, no BSOD in scenario 3, but a OS update to build 16299 on October 29th. The reliability report shows 12 critical events in the timerange of the OS update, but I havn't seen a blue screen there.
Scenario | DIMM A | DIMM B | From | To | recorded Mini- Dumps | Duration [d] |
init | L | U | Start | 06.10.2017 17:00 | 4 | > 90 |
1 | L | out | 06.10.2017 17:15 | 10.10.2017 17:17 | 0 | 4,0 |
2 | out | L | 10.10.2017 17:27 | 25.10.2017 22:45 | 9 | 15,2 |
3 | U | out | 25.10.2017 22:50 | 01.11.2017 18:25 | 0 | 6,8 |
4 | out | U | 01.11.2017 18:30 |
Regards
Holger
As long as you mention me, as you did, I'll see it.
Let me take some time to check this out and I'll get back to you later today or tomorrow (PST).
Forum,
The setup is NUC7i5, Samsung S34E790C display, and a HDMI cable OR USB-C to DisplayPort cable (ALOGIC)
When the display is connected via HDMI cable, on boot I see the "Intel NUC" splash screen then the Windows 10 Home splash screen. When it is connected via USB-C, on boot the "Intel NUC" splash screen is not displayed then the Windows splash screen is.
When connected via HDMI, BIOS interface displays as expected. When connected via USB-C, BIOS interface does not display.
Please advise if this is expected behaviour?
Thanks
Shannon
I have not had any issues these days. It seems that the problem has gone with new driver.
Thank you.
Same issue with NUC7i5 connected to Samsung S34E790C via USB-C to DisplayPort cable (brand ALOGIC).
Display adapter = Intel(R) Iris(TM) Plus Graphics 640.
I am glad to hear you were able to get this working as desired. zazou35
Feel free to contact us back if required.
Thanks,
Esteban C
I am glad to hear you got in touch with us by chat, and also to hear about the case being handled to check the cross ship options for you.
I hope this gets done at the soonest so you can continue to use the product.
If you face further questions, feel free to contact us back.
Thanks,
Esteban C
I hate to say it, but it is starting to look like there is an issue with the Upper DIMM connector. Of course, Paul is not wrong; there is still the chance that this is a compatibility issue with these DIMMs, but I have a pair of the same DIMMs in my 7BN and I have *never* had any issues.
I don't have any suggestion other than it is probably time to contact Intel Customer Support and request a replacement unit...
...S
When I play 4k I get video stutter and chopping.
Madvr settings are low performance using jriver as media player.
Driver ver 21.20.16.4678
Win 10 pro 16gb ram.
Thanks for your help.
I bought a NUC i7 a while back and returned it because the noise was unbearable. I got the I5 version, thinking it wouldn't get as hot, so the fan wouldn't need to run so much. It was nice and quiet, but I was having issues getting the HDMI display to wake up after turning on my TV/Receiver...so I updated the BIOS from whatever 04/2017 version it had, to the latest one. As soon as I turned it booted it up again...same damn noise as the i7....Loud whirring sound, like a jet engine. Open a web browser...it goes even louder like a hair dryer.
Can I roll back my BIOS to what it was??? I did set the fan to quiet, which helps a bit...but I can't sleep with this thing in my room the way it is.
I'm sorry rogelio and CodeMonkey, but where is it advertised as supporting HDR? I'm truly curious as we were very specific NOT to do that.
Ah yes, this is a pain isn't it. I truly here/feel your frustration Sasharoo. I would be too if I were in your place. As Scott has said, this has been around for some time now.
I use a bunch of different NUCs at my home-so I can try to see issues like these that customer's tell me about-but this is one I've never been able to reproduce.
I agree with Scott, try miniDP and or Type C, but the only way I know for certain how to not make this happen is to have the NUC never sleep, use hibernate instead, or turn it off. I am intrigued on what you mean by "chriping" though.
Check your PMs.
Let me try to explain the "chirping" . When the Monitor enters the power saving mode and goes to sleep (black screen) within 10-20 seconds the chirping starts. What I mean is that it sounds like a USB stick or other hardware has been attached and a sound is made. Except this sound continues to repeat itself as if its stuck on a never ending loop. Wiggle the mouse or hit any key on the keyboard to try to wake up the monitor nothing happens, as if no signal goes to the monitor to wake it up.
On the monitor if I select another port HDMI #2 or DP and return to HDMI #1, sometimes the monitor wakes up and returns to normal, "chirping" stops, at other times it does not. Have to hold the NUC power button until it shuts down and restart it again.
I purchased this monitor due to the fact that the ports on the monitor are identical to the ports on the NUC, thought it would be a perfect match.
I use this NUC as a PC for my work, my wife wanted the office cleaned up and did not like the big box. I don't use the NUC as a HTPC, does not mean that I will not in the future. It becomes difficult due to the instability, especially when you are working and have to take a call and the Monitor goes to sleep, loss of work becomes a major pain.
At this time I am using the DP which so far seems to be stable. The only item is that any windows that are open when the monitor goes to sleep will shrink and be placed on the upper left corner of the screen. This is not so bad to live with.
I hope this clarifies the "chirping". Let me know if it does not. I'll try to find a way to describe it differently.
Thanks for your assistance. Let me know what else I can assist with to try to resolve the problem.
Regards
Sasharoo