Quantcast
Channel: Intel Communities : Unanswered Discussions - Intel® NUC
Viewing all 6918 articles
Browse latest View live

Controladora simple de comunicaciones PCI

$
0
0

No puedo identificar a que dispositivo corresponde este aviso Qué driver es necesario ?


NUC drops Ethernet Connection

$
0
0

Am using NUC5i3RYK in remote control application.

Have over 100 sites.

Last 10 days have had 3 units drop their ethernet connection.

These units then drop off the network and I have to go to site with keyboard mouse and monitor to correct.

Any thoughts

Rgds ancient 1914

NUC 7i7 Devices plugged into USB-C port not recognized

$
0
0

I have

 

  • a camera (IDS UI-3131LE) with a USB-C port and
  • a NUC 7i7BNH with a USB-C port running Ubuntu 16.04 (kernel version 4.10.0-40).

 

Seems like a perfect match, but the camera is not being recognized when connected to the PC's USB-C port. It only gets power.

It seems the USB-C port does not work at all.

 

What I've tried so far:

 

  • updated BIOS
  • turned Thunderbolt both off and on in BIOS
  • both disabled and enabled USB Legacy support in BIOS
  • connected a phone to the USB-C port: it only charges
  • confirmed that the two USB-C cables I am using work in another setup
  • connected the camera to a regular USB port on the NUC (with a USB-C to regular USB cable): works.
    /var/log/kern.log says:
        Nov 30 14:51:47 D2330 kernel: [ 1558.558892] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
        Nov 30 14:51:47 D2330 kernel: [ 1558.580601] usb 2-1: New USB device found, idVendor=1409, idProduct=3130
        Nov 30 14:51:47 D2330 kernel: [ 1558.580608] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
        Nov 30 14:51:47 D2330 kernel: [ 1558.580612] usb 2-1: Product: USB 3.0 Camera
        Nov 30 14:51:47 D2330 kernel: [ 1558.580616] usb 2-1: Manufacturer: Camera Manufacturer
    Nothing shows up there when connecting to USB-C though. (same with sudo dmesg)

 

The only thing lspci -k states about USB is:

    00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)

        Subsystem: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller

        Kernel driver in use: xhci_hcd

I don't know if this includes drivers for USB-C.

 

How can I get my USB-C port working?

Unable to play 4k 10bit HVEC on NUC5i5MYHE, what am I doing wrong?

$
0
0

Hi

 

 

I am unable to play 4k files properly on a PC connected to a TV.

When I open a MKV file which is a 4K HEVC x265 I get no Video only audio. And when I forward the time, the audio plays fine, but the video shows a very choppy screen then the video is frozen and the audio continues.

I am not sure what the issue is.

Maybe I need to change settings, but I dont know what settings to change. (currently using default settings.)

Maybe my PC is not powerful enough to play this content at 4k? (but they advertise that they can do 2 screens at 4k just fine)

 

 

My Equipment:

Screen: LG OLED55B7V

Computer: NUC5i5MYHE (CPU: i5-5300U CPU @ 2.30GHz (4 CPUs) / RAM: 8GB / Using Intel SSD as content is stored locally / Intel HD Graphics 5500)

Media Player: VLC 2.2.6 Umbrella

 

 

My Files:

File 1

[quote]Format                                   : Matroska

Format version                           : Version 4 / Version 2

File size                                : 39.3 GiB

Duration                                 : 2 h 6 min

Overall bit rate                         : 44.3 Mb/s

Movie name                               : LoP

Encoded date                             : UTC 2017-01-31 21:31:45

Writing application                      : mkvmerge v9.3.1 ('Mask Machine') 64bit

Writing library                          : libebml v1.3.4 + libmatroska v1.4.5

FileExtension_Invalid                    : mkv mk3d mka mks

 

 

Video

ID                                       : 1

Format                                   : HEVC

Format/Info                              : High Efficiency Video Coding

Format profile                           : Main 10@L5@Main

Codec ID                                 : V_MPEGH/ISO/HEVC

Duration                                 : 2 h 6 min

Bit rate                                 : 33.6 Mb/s

Width                                    : 3 840 pixels

Height                                   : 2 076 pixels

Display aspect ratio                     : 1.85:1

Frame rate mode                          : Constant

Frame rate                               : 23.976 (23976/1000) FPS

Color space                              : YUV

Chroma subsampling                       : 4:2:0 (Type 2)

Bit depth                                : 10 bits

Bits/(Pixel*Frame)                       : 0.176

Stream size                              : 29.8 GiB (76%)

Title                                    : LoP

Writing library                          : x265 2.2+2-998d4520d1cf:[Windows][GCC 6.2.0][64 bit] 10bit

Encoding settings                        : cpuid=1050111 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=3840x2076 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=1 / no-allow-non-conformance / repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / bframes=3 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=40 / lookahead-slices=0 / scenecut=40 / no-intra-refresh / ctu=32 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=2 / limit-refs=0 / no-limit-modes / me=2 / subme=7 / merange=57 / temporal-mvp / weightp / weightb / no-analyze-src-pics / no-deblock / no-sao / no-sao-non-deblock / rd=6 / no-early-skip / no-rskip / fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / rdpenalty=0 / psy-rd=4.00 / psy-rdoq=8.00 / no-rd-refine / analysis-mode=0 / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=22.0 / qcomp=0.80 / qpstep=1 / stats-write=0 / stats-read=0 / ipratio=1.10 / pbratio=1.00 / aq-mode=3 / aq-strength=1.00 / no-cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=51 / qpmin=0 / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=1 / chromaloc-top=2 / chromaloc-bottom=2 / display-window=0 / max-cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / opt-qp-pps / opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05

Language                                 : English

Default                                  : Yes

Forced                                   : No

Color range                              : Limited

Color primaries                          : BT.2020

Transfer characteristics                 : PQ

Matrix coefficients                      : BT.2020 non-constant

[/quote]

 

 

 

 

File 2

[quote]Format                                   : Matroska

Format version                           : Version 4 / Version 2

File size                                : 14.2 GiB

Duration                                 : 50 min 49 s

Overall bit rate                         : 40.0 Mb/s

Movie name                               : PE

Encoded date                             : UTC 2017-04-04 21:49:02

Writing application                      : mkvmerge v9.9.0 ('Pick Up') 64bit

Writing library                          : libebml v1.3.4 + libmatroska v1.4.5

 

 

Video

ID                                       : 1

Format                                   : HEVC

Format/Info                              : High Efficiency Video Coding

Format profile                           : Main 10@L5@High

Codec ID                                 : V_MPEGH/ISO/HEVC

Duration                                 : 50 min 49 s

Bit rate                                 : 29.4 Mb/s

Width                                    : 3 840 pixels

Height                                   : 2 160 pixels

Display aspect ratio                     : 16:9

Frame rate mode                          : Constant

Frame rate                               : 25.000 FPS

Color space                              : YUV

Chroma subsampling                       : 4:2:0 (Type 2)

Bit depth                                : 10 bits

Bits/(Pixel*Frame)                       : 0.142

Stream size                              : 10.4 GiB (73%)

Title                                    : PE

Writing library                          : x265 2.3+23-97435a0870be:[Windows][GCC 6.3.0][64 bit] 10bit

Encoding settings                        : cpuid=1173503 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=3840x2160 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=1 / no-allow-non-conformance / repeat-headers / annexb / aud / hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=25 / keyint=250 / bframes=3 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=40 / lookahead-slices=0 / scenecut=40 / no-intra-refresh / ctu=32 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / dynamic-rd=0.00 / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=2 / limit-refs=0 / no-limit-modes / me=2 / subme=7 / merange=57 / temporal-mvp / weightp / weightb / no-analyze-src-pics / no-deblock / no-sao / no-sao-non-deblock / rd=6 / no-early-skip / no-rskip / fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / rdpenalty=0 / psy-rd=3.00 / psy-rdoq=6.00 / no-rd-refine / analysis-mode=0 / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=21.0 / qcomp=0.80 / qpstep=1 / stats-write=0 / stats-read=0 / vbv-maxrate=100000 / vbv-bufsize=100000 / vbv-init=0.9 / crf-max=0.0 / crf-min=0.0 / ipratio=1.10 / pbratio=1.00 / aq-mode=3 / aq-strength=1.00 / no-cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=51 / qpmin=0 / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=1 / chromaloc-top=2 / chromaloc-bottom=2 / display-window=0 / max-cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / opt-qp-pps / opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / refine-level=5

Language                                 : English

Default                                  : Yes

Forced                                   : No

Color range                              : Limited

Color primaries                          : BT.2020

Transfer characteristics                 : PQ

Matrix coefficients                      : BT.2020 non-constant[/quote]

 

 

Dx System Info

[quote]------------------

System Information

------------------

      Time of this report: 12/12/2017, 16:20:31

             Machine name: TTFHTPC

               Machine Id: {4265D848-FEA6-4846-80FF-A017A0E9DBE6}

         Operating System: Windows 10 Pro 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)

                 Language: English (Regional Setting: English)

      System Manufacturer:                                 

             System Model:                                 

                     BIOS: MYBDWi5v.86A.0039.2017.1016.1545

                Processor: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (4 CPUs), ~2.3GHz

                   Memory: 8192MB RAM

      Available OS Memory: 8062MB RAM

                Page File: 2412MB used, 6928MB available

              Windows Dir: C:\WINDOWS

          DirectX Version: DirectX 12

      DX Setup Parameters: Not found

         User DPI Setting: 216 DPI (225 percent)

       System DPI Setting: 288 DPI (300 percent)

          DWM DPI Scaling: UnKnown

                 Miracast: Available, with HDCP

Microsoft Graphics Hybrid: Not Supported

           DxDiag Version: 10.00.16299.0015 64bit Unicode

 

 

------------

DxDiag Notes

------------

      Display Tab 1: No problems found.

        Sound Tab 1: No problems found.

          Input Tab: No problems found.

---------------

Display Devices

---------------

           Card name: Intel(R) HD Graphics 5500

        Manufacturer: Intel Corporation

           Chip type: Intel(R) HD Graphics Family

            DAC type: Internal

         Device Type: Full Device

          Device Key: Enum\PCI\VEN_8086&DEV_1616&SUBSYS_20588086&REV_09

       Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]

Device Problem Code: No Problem

Driver Problem Code: Unknown

      Display Memory: 4158 MB

    Dedicated Memory: 128 MB

       Shared Memory: 4030 MB

        Current Mode: 4096 x 2160 (32 bit) (29Hz)

         HDR Support: Supported

    Display Topology: Internal

Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709

     Color Primaries: Red(0.659680,0.340344), Green(0.244641,0.670422), Blue(0.130383,0.040539), White Point(0.313000,0.329602)

   Display Luminance: Min Luminance = 0.010000, Max Luminance = 1499.000000, MaxFullFrameLuminance = 799.000000

        Monitor Name: Generic PnP Monitor

       Monitor Model: LG TV

          Monitor Id: GSM0001

         Native Mode: 3840 x 2160(p) (60.000Hz)

         Output Type: Displayport External

Monitor Advanced Color Capabilities: BT2020RGB BT2020YCC Eotf2084Supported

Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP

         Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll

Driver File Version: 20.19.0015.4624 (English)

      Driver Version: 20.19.15.4624

         DDI Version: 12

      Feature Levels: 11_1,11_0,10_1,10_0,9_3,9_2,9_1

        Driver Model: WDDM 2.0

Graphics Preemption: Triangle

  Compute Preemption: Thread group

            Miracast: Supported

Hybrid Graphics GPU: Integrated

      Power P-states: Not Supported

   Driver Attributes: Final Retail

    Driver Date/Size: 08/03/2017 00:00:00, 39864472 bytes

         WHQL Logo'd: Yes

     WHQL Date Stamp: Unknown

   Device Identifier: {D7B78E66-5556-11CF-26F1-5700B5C2D935}

           Vendor ID: 0x8086

           Device ID: 0x1616

           SubSys ID: 0x20588086

         Revision ID: 0x0009

  Driver Strong Name: oem3.inf:5f63e53468b7076c:iBDWM_w10:20.19.15.4624:pci\ven_8086&dev_1616

      Rank Of Driver: 00D12001

         Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C

        D3D9 Overlay: Supported

             DXVA-HD: Supported

        DDraw Status: Enabled

          D3D Status: Enabled

          AGP Status: Enabled

       MPO MaxPlanes: 1

            MPO Caps: Not Supported

         MPO Stretch: Not Supported

     MPO Media Hints: Not Supported

         MPO Formats: Not Supported

    PanelFitter Caps: Not Supported

PanelFitter Stretch: Not Supported

 

 

-------------

Sound Devices

-------------

            Description: LG TV (Intel(R) Display Audio)

Default Sound Playback: Yes

Default Voice Playback: Yes

            Hardware ID: HDAUDIO\FUNC_01&VEN_8086&DEV_2808&SUBSYS_80860101&REV_1000

        Manufacturer ID: 1

             Product ID: 100

                   Type: WDM

            Driver Name: IntcDAud.sys

         Driver Version: 6.16.0000.3197 (English)

      Driver Attributes: Final Retail

            WHQL Logo'd: Yes

          Date and Size: 10/05/2016 00:00:00, 481768 bytes

            Other Files:

        Driver Provider: Intel(R) Corporation

         HW Accel Level: Basic

              Cap Flags: 0xF1F

    Min/Max Sample Rate: 100, 200000

Static/Strm HW Mix Bufs: 1, 0

Static/Strm HW 3D Bufs: 0, 0

              HW Memory: 0

       Voice Management: No

EAX(tm) 2.0 Listen/Src: No, No

   I3DL2(tm) Listen/Src: No, No

Sensaura(tm) ZoomFX(tm): No

[/quote]

Problem with centos 7 on NUC (NUC7i5bnh) - fixed

$
0
0

This forum really helped me out, so wanted to share my experience with CentOS7 install on a NUC7i5BNH using a USB Fob/key in case someone else can use it:

 

TL;DR: Switched from a junky USB 1.0 8GB fob to 'brand name' USB 3.0 32GB fob using same ISO CentOS7 image (installed with RUFUS), and it fixed my install problems and I was able to successfully run CentOS7 install from USB to my NUC (NUC7i5BNH).

 

Couple Key Points that really helped me:

 

1) I followed Intel instructions for updating my NUC BIOS using a USB fob.  Pretty easy and the tool def works letting you download the BIOS file locally, then using F7 at boot on the NUC, starting the BIOS update, and having it look for the BIOS update file you downloaded to the USB.

 

2) If you are creating your USB CentOS installer on a Windows machine, use RUFUS to make it.

 

2) This was my biggest hurdle....some people may swear this isn't possible...but this made mine work:  I tried repeatedly installing CentOS7 "minimum install" from a junky USB 1.0 stick I had made a month ago, and had SUCCESSFULLY used on a separate laptop CentOS7 install.  I had used this CentOS7 minimum install USB probably 6-7 times in the past month with no problems.  So...I used the same 8GB USB with the CentOS7 image already on there on my NUC. Installing on the NUC it would run the installer, but when it got to the GUI page of install where you choose your language, I would get random errors which would never let me continue the install.  Running a media check would result in "failed" but I was still able to use the USB to install on a test laptop, no problem.

 

So...for a more thorough test, I used RUFUS and overwrote the old beater 8GB USB with an UBUNTU install image I'd also used recently.  Using the same 8GB USB stick now imaged with an UBUNTU image using RUFUS I also get an error part way through the install (but it would start the install, just never would finish).

 

So...ultimately, for fun, I got a clean USB 3.0 32GB Fob, and installed the original CentOS7 ISO I already had, and after I did that, the install was flawless.

 

You can do checksum/tests to make sure your packages you downloaded are fine, and I did those sorts of things...so I'm pretty sure my old junky USB1.0 was somehow the problem on the NUC  (again, I used that USB on a crappy test laptop a lot recently and it worked fine instaalling CentOS7 minimum).   ...and moving to a decent USB that was USB3.0 seemed to fix everything.   Also (not that it matters) I tried this in front and rear ports of the NUC...and that had no effect (not that it would).

 

Happily humming along with CentOS7 on a NUC7i5BNH now.

 

Hope this helps someone avoid some wasted time.

(NUC - NUC6CAYH) Not accept SanDisk SSD PLUS ?

$
0
0

Hello

_____________________________

My NUC - NUC6CAYH (NEW)

and

SanDisk SSD PLUS (NEW)

https://www.sandisk.com/home/ssd/ssd-plus

__________________________________

 

The NUC not accept SSD

 

This BIOS

wWjdzb0.jpg?1

 

The SSD does not appear !

 

I make sure the SATA Cable is Good

6kJhLyn.jpg?1

And SSD In the right place

YeG173q.jpg?1

 

 

Where is the problem and what is the solution?

NUC6CAYH screen goes black every few minutes

$
0
0
CategoryQuestionsAnswers (N/A if not applicable)
DescriptionProvide a detailed description of the issue
Screen goes black for a couple of seconds every 1 to 5 minutes.

Always (100%):

Hardware (HW)Brand and Model of the system.nuc6cays
Hybrid or switchable graphics system?
ie Does it have AMD or NV graphics too?
N/A
Make and model of any Displays that are used to see the issue (see note2 below).
LFP
= Local Flat Panel (Laptop panel)
EFP = External Flat Panel (Monitor you plug in)
HP W1907v
How much memory [RAM] in the system (see note2 below).8GB (2x4GB)Hynix HMT451S6AFR8A-PB DDR3 PC3L-12800S-11-12-B4
Provide any other hardware needed to replicate the issue.
ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc
Toshiba  HDD MQO1ABF050
Hardware Stepping (see note1 below).
Software (SW)Operating System version (see note2 below).Windows 10
VBIOS (video BIOS) version. This can be found in “information page” of CUI (right click on Desktop and select “Graphics Properties”.
Graphics Driver version; for both integrated Intel and 3rd party vendors (see note2 below).Intel ® Graphics Driver Version:"23.20.16.4849"
SW or Apps version used to replicate the issue.windows 10
ConfigurationsSingle display, clone, or extended (see note2 below).Single VGA display
Display resolution & refresh rate setting of each display (see note2 below).1440x900 59Hz
AC or DC mode, i.e. is power cable plugged in or not?AC
How to reproPlease provide steps to replicate the issue.  These steps are very crucial to finding the root cause and fix.
A screenshot to illustrate the issue is a huge plus. A video of the failure is even better! Attach to the post or provide the YouTube link.
  1. Power on Intel NUC
...
Note1:
  1. Go to “Device Manager”. Double click on “Display adapters”, right click on “Intel(R) HD Graphics…” and select “Properties”, select “Details” tab, select “Hardware Ids” in Property drop-down box.  Capture this info (save as screenshot) and include as an attachment in the Intel Community Forum posting.
NOTE2:      Please follow these instructions below to collect info for the 3 areas. This greatly helps engineering with replicating the issue and investigating and is a requirement from them.
Intel SSU (System Support Utility): (Note - This is a new Intel tool that will eventually incorporate gathering all the data needed in one click. Targeting end of year to be fully featured. Until then, please provide the DxDiag and DispDiag as well)Download Intel® System Support Utility
  1. Download the utility
  2. Run the exe and select 'Scan'
  3. Save and include as an attachment int he Intel Community Forum
DxDiag Instructions:
  1. Click on the “Start Menu” -> Type “DxDiag” -> Press “Enter” -> Wait for the DirectX Diagnostic Tool to finish loading
  2. In the DirectX Diagnostic Tool, click “Save All Information” -> Save the file DxDiag.txt
  3. Include DxDiag.txt as an attachment in the Intel Community Forum
DispDiag Instructions:
  1. Click on the “Start Menu” -> Type “cmd” -> Then a command shell window will open
  2. In the command shell, type “dispdiag -out %homepath%\Desktop\DispDiag-Intel-Issue.dat” -> The command shell will output something similar to “Dump File: C:\Users\[username]\DispDiag-########-######-#####-#####.dat”
  3. Locate the .dat file on your desktop and include DispDiag-Intel-Issue.dat in the Intel Community Forum
-- This post ends here --

 

[NUC6i7KYK] - Can't get no persistence w/dual monitors - all windows move to primary monitor after sleep

$
0
0

My setup is a NUC6i7KYK with 2x16Gb of DDR4 RAM and a V-NAND SSD 850 EVO M.2 from Samsung. I bought two identical 28" 4K UHD ASUS PB287Q monitors and was immediately disappointed I couldn't daisy chain them using the Display Port. My bad, didn't do my research, nothing to do with the NUC.

 

So I'm running two identical monitors; main monitor connected using the Mini DisplayPort, secondary connected with HDMI.

My issue: Every time the screens wake up from sleep all my open windows on the secondary monitor have moved to the primary one, and I have to re-arrange all my windows all over again.

What I expect to happen: On wake-up I want my monitors to persist my program windows the way I had them arranged before the monitors shut off.

 

* I'm running Windows 10 v1709 (OS build 16299.125)

* ASUS doesn't offer display drivers for these monitors, they use the Microsoft Generic PnP Monitor drivers.

* The Intel Iris Graphics Control Panel identifies the main (DPLink) monitor as a Digital Display, the second monitor (HDMI) as a Digital Television.

* BIOS/Firmware/drivers all up to date as per Intel Driver & Support Assistant 3.1.0.12

 

I'm very happy with the Skull Canyon (my first NUC) and I'd be the first to admit this is a minor issue. But it does get old and I hope that one of you guys can help me out. Fingers crossed!

 

m.


Drivers for NUC6i7KYK

$
0
0

I installed Latest Intel Driver & Support Assistant Tool (v.3.0.0.9), it says there are 3 updates but when I start it, it launches Chrome browser and at Intel® Driver & Support Assistant page and I get an error message:

[Oops, something went wrong while trying to scan. Please try again, or see our FAQs for help.]

There is no error code, obviously the FAQ section does not contain any clue that might help.

with v2 of this tool, even if it did not detect properly all intel drivers on the system I could install and see driver versions for most of them, with v.3 I can not do anything.

Bluetooth Device Stopped Working After Driver Update

$
0
0

I have Intel NUC6i5SYH and recently I have updated my Bluetooth driver to version 20 from that time forward my Bluetooth device became unrecognizable by my OS Windows 10 x64, I have opened a support request from Intel, but I want to see if anyone else experienced the same issue.

NUC7i7BNHXG no win 10 boot after bios update

$
0
0

Hoping someone will give me some good idea how to solve issue I have with my new NUC7i7BNHXG, 32GB Optane plus 2TB HD.

So, after bios update to the newest version, windows 10 cannot load any more. I tried to recover with image that I made on external drive, but apparently I cannot recover this way cos there is no any account as administrator set it up. Then I tried windows reset, but it is stuck on 1%.

For me looks like there is something with Optane memory that is cosing this, but I am not sure what.

Settings in bios seems ok, as far I understand it.

Is there any way to recover my dearest NUC in working condition again?

NUC7I5BNH/K Intel Iris 640 driver

$
0
0

Hi at all,

We need to use Windows 10 x86 on this NUC and i have found all driver but not the graphics driver, we missing only that.

So the question is simple, since only the video drivers are missing to run Windows x86 sooner or later they will come out? or will this model of the NUC always be locked to Windows 10 x64 ?

Bios update on DC53427HYE fails

$
0
0

I'm trying to update my DC53427HYE to BIOS version 49 via the F7 procedure. The updater recognizes my USB drive and the RK0049.bio file on that drive but after confirmation the system immediately reboots instead of starting the update. After the reboot the BIOS Event Log shows the message "Flash Update Failed (21)". Does anyone know the meaning of this error 21?

 

Jos

Mi NUC7i3BNH no reconoce el disco SATA

$
0
0

Tengo un nuevo NUC7i3BNH con un disco CRUCIAL MX300 275GB SATA M2 con Win10 Pro. Le he querido instalar un segundo disco CRUCIAL MX300 2,5” SATA pero no lo reconocen ni aparece en la BIOS ni lo ve Windows. Pienso que he hecho algo mal, pero no como arreglarlo. ¿Alguna idea?

NUC7I3BNK - connect to DVI

$
0
0

Hi, I have one of the above that I want to connect to a DVI monitor, I have used a HDMI - DVI adaptor & HDMI - DVI cable and neither output a display.

 

HDMI & DVI should be the same technology so I am very surprised that this doesnt work, any ideas?


Can't get 4:4:4 color to output

$
0
0

In windows advance color it only does Ycbcr420 10 bit 4k 60p. I have a Samsung js8500 TV with UHD on. Up to date with all the latest updates for my nuc7i5bnk and windows with HDR.

NUC7i5BNH 32GB memory, very slow cold boot and post error after 57 bios update

$
0
0

Hello,

 

We are experiencing a problem with NUC7i5BNH running with two 16GB SO-DIMMs. After updating the bios from the original 42 to 57 the unit powers up really slow from cold state. It takes about 45s-1min to reach the Intel NUC logo page and it takes several seconds until the "F2/F7/F10" texts appear. Normally all this happens in <10 seconds pressing the power button.

 

A post error message "(a7) me fw downgrade request mespilock failed" is briefly displayed before the boot process is started. Warm restarts seem normal (=fast) and the memories pass Memtest normally. The unit seems to operating normally besides the very slow cold boot and the post error message. We definitely cannot deliver the unit to a customer in this condition.

 

We have reproduced the problem with two NUC7i5BNH units. On the second unit we did everything in a very controlled manner. The unit worked perfectly with the 42 version; all problems appeared after the update to 57. I do realise that the problem might be some incompatibility with the Corsair memories but they work individually and also pass memtest together after the slow cold boot has finished. I really hesitate to spend ~400eur just try out a second set of memories.

 

Things done/tried:

  • BIOS update with proper "Reset bios settings to defaults" after the update
  • Tried bios recovery with jumper and power menu methods -> no effect
  • Tried with memories individually in either slots -> worked fine without problems (fast, no post error)
  • Tried different (Kingston, Adata) smaller memories individually in the unit -> worked fine without problems (fast, no post error)

 

Things not tried:

  • Different 2 x 16GB modules. Unfortunately we do not have Kingston/AData 2133MHz 16GB modules available. We could get our hands on 2 x 16GB 2400MHz Adata. However the memories are really expensive to just try out. The Corsair modules themselves pass memtest and work individually in the same units. Also their specifications meet the requirements stated in the Technical Product Specification.
  • Any smaller memories in dual channel configuration. We have a chance for this on Monday. However it does not really help us to find out that 2x4 or 2x8 works.
  • Downgrading BIOS to anything earlier to 57 (see BIOS downgrade question below)

 

Components:

Intel NUC7i5BNH original BIOS 42 updated to 57

2 x Corsair CMSO16GX4M1A2133C15 (16GB, 2133MHz, 15-15-15-36)

No SSD installed at the moment (AData SX8000 will be installed once the memory problem is solved)

 

BIOS release notes state that you could downgrade from 57 -> 54: "Due to a security enhancement, it will not be possible to go to any BIOS earlier than BIOS 0054."

However the BIOS update readme states the following: "If you are trying to downgrade to a previous BIOS version and its Intel® ME Firmware version is older than that currently on the motherboard, then the downgrade is NOT supported."

The ME FW in 57 is newer than in 54 (11.8.50.3425 vs 11.6.27.3264). Is the downgrade to 54 allowed/supported or not?

 

Questions:

  1. What is this post error message "(a7) me fw downgrade request mespilock failed"? We have definitely not downgraded anything. Is the unit internally trying to perform some kind of revert to previous bios when the post is taking too long? Could not find any google hits on NUC with this error.
  2. Is the BIOS downgrade from 57 to any previous version allowed/supported? Since the documentation would indicate that we cannot downgrade (see above), we seem stuck with 57.
  3. Has any of the relevant BIOS settings changed between 42 to 57? These do not seem to be listed in the release notes.
  4. Are there any BIOS settings we could try to change? Eg. memory timings or the "Round trip latency optimisation".
  5. Anything else we could try?

 

We provide Intel NUC solutions as a business and have installed several hundred units since 2013. This is the first time we experience this kind of problem. We have also provided NUC6 and NUC7 units with 32GB memory without problems but the NUC7i5BNH+Corsair 2x16GB combo is our first.

 

Any help is well appreciated!

 

Best Regards,

Henri / TeraStore

NUC6CAYH Freezing/Crashing... LAN troubles, etc

$
0
0

I picked up a NUC6CAYH with the plan of using it for Libreelec.  I realize this is not a supported OS, but there are many others using the NUC6CAY for this without issue.

 

I have 2 x HyperX Impact 4GB 1866MHz DDR3L CL11 SODIMM 1.35V HX318LS11IB/4 installed. (tested with memtest for 48 hours without issue.)  I have used both a Samsung 830 SSD, and an ADATA SP600

 

I have consistent crashing and freezing with Libreelec, that others are not experiencing.  Sometimes it runs without crashing for an hour or so, sometimes only minutes.

 

I have experienced freezing in the visual bios, requiring a hard reset, at least a few times, and with both 0041, and 0042 bios.

 

I decided to install windows 10, as a test of an "approved" OS.  Windows Setup experienced a crash during install, and after install, the Win 10 install itself experienced a BSOD.  Additionally with Win 10, I am unable to install the LAN driver, no realtek lan is recognized... nothing is shown in the device manager either (no, it is NOT disabled in the bios)

 

I can gather info if it would help, but I am thinking there may be something wrong with my NUC.

 

What needs to be done to get a replacement?

 

 

 

NUC5i3RYK bios setup for clean install WIN 10 on Adata M.2 ASX6000NP-128GT-C

$
0
0

I had Win 7 64 BIT Pro installed, I cloned that drive to my new M.2 Adata drive.

Told BIOS to boot to that drive. Works fine. Still not as fast as a 6 year old Acer REVO with M.2 drive.

Would like to know the Visual BIOS Settings to Fresh install WIN 10 on the M.2 drive.

BIOS and WIN 10 BOTH see the M.2 drive. My BIOS VER is RYBDWi35.86A.0367.2017.0929.1059.

Intel driver update says my drivers are current.

Intel says my drive is not been tested and approved. Any Help for my question?

Boot Issue DC3217IYE - Intel ICE Canyon NUC Core i3-3217U 1.8GHz QS77 DDR3 2xHDMI / Gbit LAN / USB (Next Unit of Computing)

$
0
0

Hi,

 

I have two NUC's DC3217IYE. I think that makes them 3rd Gen.

 

The issue I have is from time to time the NUC's do not see the internal drives on boot and start to try to boot from the Lan.

 

The drives are Msata 60gb Intel's. Both NUC's are mounted upside down under office desks.

 

The only way I can get the drive to be 'seen' again is by opening the NUC removing and re-inserting the drives.

 

Does anyone have any idea what could be going on, please?

 

I updated the bios to the latest version about a year ago. One of the NUC's I have just upgraded the mSata drive to a new 128gb crucial Msata drive but the same issue has occurred.

 

Thank you!

Viewing all 6918 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>