Hello,

I have an issue regarding audio on my new NUC.

First of all let me explain my setup:

I have 2 monitors: one is your common somewhat old PC monitor that connects to the NUC through a HDMI-to-DVI cable. The other monitor is a recent model LGTV which is connected directly through a HDMI cable. Since the NUC only has 1 HDMI port, I alternate between them depending on my needs.

The PC monitor doesn't have its own audio, I use speakers for sound. There are no issues with this setup.

The problem arises when I try to play certain games in fullscreen on my LGTV: the audio device manager will detect my TV and keep doing so when the game is started in window mode, however, when fullscreen is activated the TV will dissapear from the audio device manager. It will reappear after a second or two when you alt-tab to check the device manager.

Since this only happens to certain games, this should be a software issue.

Games that don't have this issue: Cuphead, Xanadu Next.

Games that do have this issue: Little Nightmares, Grandia II Anniversary Edition

As you can see this is a mix of old and new games.

According to Intel's GPU GUI, my driver version is 22.20.16.4815.

I have made quite a bit of research regarding this annoying problem and haven't been able to produce any desirable results, please help me fix this oddity that no doubt devaluates my NUC.

UPDATE: Amy C. from another, similar topic suggested that installing version 15.45 (21.20.16.4678 according to the GUI) should fix the issue and indeed it does.

ADDITIONAL INFO: I encountered some mild nuisances with Windows 10 regarding driver installations in general and thought I'd mention them in this post to help anyone that has this same audio issue.

- Windows 10 will keep driver files (in this case Intel GPU + Intel Sound on the hardware manager), even if you uninstall the hardware. Make sure to get rid of the driver files by checking the box on the uninstall hardware confirmation screen, otherwise Windows 10 will update to the faulty drivers again.

- Windows 10 will automatically try to find the newest drivers for any of your PC components. Unfortunately, this means that it will find and install the faulty drivers again after some time has passed. What's worse is that  there doesn't seem to be a simple way to deactivate the automatic update feature for one specific component. You would either have to fiddle with Windows Registry or disable automatic updates for your PC as a whole.

Thank you very much, I hope that this fix is integrated into future driver updates.

Hello

Nuc6cayh BIOS Version AYAPLCEL.86A.0041.2017.0825.1152

Ballistix Sport 8GB Kit (4GBx2) DDR3 1600

BLS2C4G3N169ES4CEU

Physical Memory

Total 8041 MB

Module Name Crucial BLS4G3N169ES4.16FE

Serial Number 521700E4h (3825211218)

Module Size 4 GB (2 ranks, 8 banks)

Module Type SO-DIMM

Memory Type DDR3 SDRAM

Memory Speed DDR3-1600 (800 MHz)

Module Voltage 1.35 V

The problem is that when turning on NUC two 4GB and it turns on,  displays a message that the memory density is not and that the memory is smaller than 4GB have 1GB or 2GB.

After accepting Y, the system starts normally and works without problems. There is no memory problem and is seen as 8GB. Work perfect

I use the latest bios from intel, it annoys me a lot every time I turn on my computer

Also does not work in this fast boot system.

One 4GB memory works fine and there is no message.

You need to improve bios

Hi.

We bought a Lenovo USB-C to HDMI adapter, and get exactly no image on the HDMI port (even after setting thunderbolt up as primary Screen in BIOS)

From Reddit, I can see that it is not an uncommon issue to not et HDMI on USB-C adapters.

Which adapters are tested and confirmed as "working"?

gunleik

Just finished bringing up my NUC7i5BNH with a clean install of Windows 10.

When the generic Windows driver was in charge before I installed the Intel Graphics driver, I had the native 2560 x 1440 displayed on my monitor over the HDMI cable. As soon as I installed the iGFX driver (GFX_WIN10_64_15.46.2.1.4729) the display dropped to 1920 x 1080 and I cannot for the life of me find a way to return to the display's native resolution.

I tried a custom setting in the Intel Graphics Setting application and it says that the requested setting is outside the bandwidth limitations for the device (which it shouldn't be).

Under the "Options and Support" section of the Intel Graphics Setting application, the application does see that 2560 x 1440 @ 60p Hz is a supported monitor mode. The monitor is from Monoprice and it's a 27" display.

The Intel Driver Update Utility doesn't register a version number for the graphics driver and reports it as "Unknown".

I don't know if it's related, but the system also doesn't recognize the audio capabilities of the monitor either.

More information from the Iris Graphics Control Panel:

----

Intel(R) Iris(TM) Plus Graphics 640

Report Date: Saturday, August 26, 2017
Report Time [hh:mm:ss]: 1:21:03 AM
Driver Version: 22.20.16.4729
Operating System: Windows* 10 Home (10.0.15063)
Physical Memory: 32659 MB
Vendor ID: 8086
Device ID: 5926
Device Revision: 06
Graphics Output Protocol (GOP) Version: 9.0.1066
Current Resolution: 1920 x 1080

Processor: Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz
Processor Speed: 2208 MHz
Processor Graphics in Use: Intel(R) Iris(TM) Plus Graphics 640
Shader Version: 5.1
OpenGL* Version: 4.5
OpenCL* Version: 2.1
Vulkan* Version: 1.0.38

* Microsoft DirectX* *
Runtime Version: 12.0
Hardware-Supported Version: 12.0

* Devices connected to the Graphics Accelerator *

Active Displays: 1

* Digital Display *

Display Type: Digital
Serial Number: YSP12310001
DDC2 Protocol: Supported
Gamma: 2.2
Connector Type: DisplayPort
Device Type: Digital Display

Maximum Image Size
Horizontal Size: 23.62 inches
Vertical Size: 13.39 inches

Supported Modes
640 x 480 (60p Hz)
640 x 480 (75p Hz)
720 x 400 (70p Hz)
720 x 480 (60i Hz)
720 x 480 (60p Hz)
720 x 576 (50p Hz)
720 x 576 (50i Hz)
800 x 600 (60p Hz)
800 x 600 (72p Hz)
800 x 600 (75p Hz)
1024 x 768 (60p Hz)
1024 x 768 (75p Hz)
1152 x 864 (75p Hz)
1280 x 720 (50p Hz)
1280 x 720 (60p Hz)
1280 x 1024 (60p Hz)
1280 x 1024 (75p Hz)
1440 x 900 (60p Hz)
1680 x 1050 (60p Hz)
1920 x 1080 (60p Hz)
1920 x 1080 (60i Hz)
1920 x 1080 (50i Hz)
1920 x 1080 (50p Hz)
2560 x 1440 (60p Hz)

Power Management Support
Standby Mode: Supported
Suspend Mode: Supported
Active Off Mode: Supported

Raw EDID:
00 FF FF FF FF FF FF 00 66 70 60 27 00 00 00 00
0F 17 01 04 80 3C 22 78 FE EE 95 A3 54 4C 99 26
0F 50 54 A5 CB 00 71 4F 81 C0 81 80 95 00 B3 00
D1 C0 01 01 01 01 56 5E 00 A0 A0 A0 29 50 30 20
35 00 55 50 21 00 00 1A 00 00 00 FF 00 59 53 50
31 32 33 31 30 30 30 31 0A 20 00 00 00 FD 00 17
4C 0F 63 19 00 0A 20 20 20 20 20 20 00 00 00 FC
00 32 37 69 6E 63 68 20 48 44 4D 49 0A 20 01 5B

02 03 1F F1 4C 01 02 03 04 05 07 90 12 13 14 16
1F 23 09 07 07 83 01 00 00 65 03 0C 00 10 00 02
3A 80 18 71 38 2D 40 58 2C 45 00 FE 1F 11 00 00
1E 01 1D 80 18 71 1C 16 20 58 2C 25 00 FE 1F 11
00 00 9E 01 1D 00 72 51 D0 1E 20 6E 28 55 00 FE
1F 11 00 00 1E 8C 0A D0 8A 20 E0 2D 10 10 3E 96
00 FE 1F 11 00 00 18 01 1D 00 BC 52 D0 1E 20 B8
28 55 40 E8 12 11 00 00 1E 00 00 00 00 00 00 07

* Other names and brands are the property of their respective owners.

When connected through HDMI ports on NUC and Monitor ( both HDMI 2.0's), when the Monitor goes to sleep it can not be reawaken and the speakers start chirping as if you just connected some other device and they do not stop.

The only way to wake the monitor is to switch to another input and revert back to the original HDMI1 or HDMI2 on the monitor.

On the Display ports it seems to work fine.

All Drivers are up to date !!!!

Configuration is

NUC6i7kyk

  32Gb of RAM

  M.2 - 512 Gb - SSD 960 Pro

Latest Drivers are:

  BIOS  Version 050

  Iris Pro 580 - Driver version (Win 10-64 - 15.46.05.4771 KY  download)  22.20.16.4771

  LG - LG ultra HD (HDMI)

  HDMI 2.0 Firmware  version 0x07 0x20

  Realtek High Definition Audio - Ver 6.0.1.7982

Is anyone out there having a similar problem.  Or is there any suggestions on how to fix this annoying problem.

Thank you

So this was mentioned in another discussion that was marked as answered but looks to have just been abandoned by the original poster (Thread 115121).  I am seeing UEFI PXE boot problems on the 7th gen nucs similar to what was mentioned in that thread.  We have 50+ of each of the following NUC models...D34010WYK, NUC5i3RYK, NUC6i5SYK.  All of them transitioned fairly well from Legacy PXE Boot to UEFI PXE Boot (Some did need BIOS updates but that is to be expected).  However our newest stock of NUC7i5BNK's will not boot to PXE in UEFI (BIOS updated and all).  The options exist in the BIOS options and the device recognizes and serves up the option to network boot.  Selecting the IPv4 boot option event initiates the process and sees the network (Media detected message), but it wont go any further.  I can even flip the device to non-secure boot non-UEFI, and PXE boot the device perfectly fine using Legacy network boot.  I would REALLY prefer to move forward and not build the newest NUCs in legacy mode while all the older model NUCs transition over to UEFI and secure boot.

Bonjour! Mon mini-pc Intel-Nuc NUCPYH ne démarre pas et l'écran reste noir.

La solution pour qu'il démarre c'est qu'il faut  débrancher mon cable HDMI de la tv et de démarrer le mini-pc  apres  quelques seconde la lumiere arrire rouge Optical s'allume et je rebramche mon cable HDMI a la tv et tout est reparti.

Pourquoi et comment réparer ce probleme?

I want to leave my NUC in the suspend state and reactivate it with an Infrared signal.

It's possible? How would I have to configure it?

Hi

For about 1/2y I got my NUC7i5BNH which I didn't use much up to now but there are numerous problems and issues nevertheless which is veery annoying for a new device not that cheap!

To have it said right from the beginning - I tried everything: Misc. Win 10 versions and reinstalls (Now fresh install of Fall Creators Update), driver uninstall, reinstall, updates, Bios updates, Bios reset and settings, LAN / WLAN connection and adapter deactivation, different HDMI cables, Remote desktop, ...

Intel Ready Mode: Had problems from the beginning like others - (Immediate) wakeup after entering Ready mode, not entering Ready mode or what I found out and it seems now that it just doesn't display it properly on the device (LED). Not sure if just the display is still off then or it's still in Ready mode. It does use less power indeed and when pressing the power button it does not shut down but reactivate / wake up totally - assumed display is waking up again (Possibilities: No signal at all, signal but black screen, Picture is green / purple as with RGB / YcPbr mismatch between GFX and screen).

What I found out (in the event log and on the device): From remote desktop it wakes up from ready mode or at least changes LED color when connecting or when pressing "standby" and then disconnecting (Disconnecting: wakeup reason "Unknown"). After manually entering ready mode from the device itself by pressing standby it wakes right back up again, normally after a few seconds, sometimes after a few minutes. Event log shows these entries right when entering ready mode this way or also under other circumstances - no idea if it matters and what it says (translated from DE to EN):

- The policy path of "{a1841308-3541-4fab-bc81-f71556f20b4a}" was reset by "{C: \ Program Files \ Intel \ Intel (R) Ready Mode Technology \ IRMTService.exe" (process ID: 3464) to "a1841308-3541-4fab-bc81-f71556f20b4a} ".

- From the process "C: \ Windows \ System32 \ dllhost.exe" (process id: 4104), the policy scheme of "{a1841308-3541-4fab-bc81-f71556f20b4a}" was reset to "{381b4222-f694-41f0-9685-ff5bb260df2e } "

- (a18... to a18..., a18 to 381 and vice versa)

Interestingly it seemed to work for a short while now after clean installing Fall creators update with all recent drivers. No idea what changed yesterday. What I tried was changing from WLAN to LAN and totally deactivate WLAN (power - does it even make a difference between WLAN off or WLAN adaptor deactivated?). I also installed Teamviewer yesterday. But after Ready mode didn't work properly anymore I uninstalled Teamviewer and changed and de-/re-activated LAN / WLAN back and forth and rebooted and so on but didn't really help... (BTW: The ready mode version on the NUC page isn't recent. does this make a difference?)

Display wakeup from ready mode / sleep as described above. Only shut down the device and power on again helps in that cases. Found out, this mostly only occurs when having been connected through Remote desktop earlier. Also when playing a sound from the NUC like when changing windows audio volume, at the beginning there is a noise, some kind of distortion. no issues afterwards with playing audio. Only the first time audio plays after everything was silent before. every time... (LCD, HDMI 2.0).

Rarely display goes black for a few seconds and comes back again then.

Random bluescreens since the beginning with different windows / driver versions as described above.

Didn't notice this for a few days now but right now it crashed again after beeing away for a few minutes!! VEEERY glad I saved this text before I went away...!!

Came back, moved mouse, display got signal, remained black, lost signal. After a while got signal again when windows was fresh booted... This may not happen!!!

- Event log (translated DE to EN): The computer was restarted after a fatal error. The error code was: 0x0000007e (0xffffffff80000003, 0xfffff80054820275, 0xfffffc8880a75d98, 0xfffffc8880a755e0). A full image was saved in: C: \ Windows \ MEMORY.DMP. Report ID: 1f8da98e-b63d-42d9-9860-c83df23160eb.
No idea what to do with those memory dumps. Luckily, bluescreens rarely occur during normal usage...

About the software installed: Primarilly IIS web server and hMailServer are running. But i guess this should not have any influence since I understand that ready mode is for having the PC running in a low power when not active using it but needing it remain on for servinc services - like in my case web and email...!?

P. S. It is possible to make the NUC totally quiet by using "Fanless" in BIOS which makes no sense but it is not possible to make it totally quiet otherwise during normal idle or ready mode because max fanless cpu temp. possible in bios is 48°C?!? This is ridiculous and makes no sense. Also, that for RAM max themp is on the other side 55°...!? I'm running it now at 25% fan up to 55° cpu I think having it around 50° this way in idle. In ready mode I saw a min. cpu temp of 45° or less.

P. P. S. What's interesting about the ready mode / standby / wake up problem: Power consumption isn't higher when it seems to "wake up" from ready mode (as said display is still off then). Power is the same if not even less as when the LED indicated ready mode...!

Thx & regards

Recently bought the Skull Canyon Nuc and went through the Windows 10 install /drivers/bios/firmware updates...

After the whole process discovered that after "shut-down" the fan will turn on itself very very high and persists,

but on a restart and the NUC is powered on the fan spins low and quiet, only on high loads do the fan kick in a bit but never full blown like when its shut down.

I tried windows 10 recovery/ another clean windows 10 install/update BIOS again/ re-installation of every single drivers but to no avail trying to figure out the problem.

Until once I unplugged the HDMI cable while the NUC was shut-down the fan stops! Must be a bad update on the HDMI 2.0 Firmware???

~ I messed up updating the HDMI 2.0 firmware on a non Device (Dell U2414H) and crashed, and only after did I do a proper HDMI 2.0 update on a compatible device, thinking it'll be fine.

Firmware updated with a 2.0 HDMI connected device (Samsung 6 series 4K TV), while remaining plugged to the TV the NUC shuts down perfectly with no fan activation.

But once booting in or shutting down while connected to a non HDMI 2.0 Device (Dell U2414H) the fan issue starts again and will become persistent until another update of the 2.0 firmware is done.

HELP!! how do I fix this and is the HDMI firmware issue or do I actually have a faulty unit.

Hello everybody,

today I was making a speed test of my Internet connection (fiber, with 1 Gbps download, 200 Mbps upload) with the Speedtest application for Windows 10 (https://www.microsoft.com/en-us/store/p/speedtest-by-ookla/9nblggh4z1jc?SilentAuth=1&wa=wsignin1.0), which I already did several times before. Today, instead, during the upload speed test, suddenly the ethernet connection of the NUC crashed, and I couldn't have it working again since I restarted the NUC. Since I haven't any keyboard or monitor attached to the NUC, which I control only by remote desktop, and I have disabled wireless connection on it, this s quite annoying.

Is there anybody experiencing the same issue, maybe under similar conditions of load on the onboard ethernet card?

is there a way an hardware way to turn on the wireless connection in these circumstances?

I am not sure if it is a bug or a missing feature but since it’s announced that this remote is compatible (NUC Ecosystem Catalog July 2017) should work.

https://www.intel.es/content/dam/www/public/us/en/documents/technical-specifications/nuc-ecosystem-catalog-2017.pdf

Please add support in BIOS or remove from advertised products as compatible.

NOTE: some old NUC’s has this support in BIOS:

However in last generation NUC’s (NUC7I5BNK) this option is missing in BIOS.

Related threads:

NUC7I3BNH IR Power On not working

NUC6CAYH switch on with Remote not working

Intel NUC7i3BNK can't turn it back on with remote

I work about 15 years in IT, mainly as a Windows server specialist, but also desktop support / integration and software testing.

Since they first came out, I've been using and recommending Intel NUC's, by now I've installed about 30 of them, mostly with very happy customers as a result.

About the NUC6CAYH..

Recently a client of mine needed some simple Windows 10 pc's with a VGA connection, so I installed 3x NUC6CAYH.

The NUC's have very different production dates, yet ALL of them have the same issue of 1-2 seconds of black screen, sometimes as much as every 2 minutes.

After trying everything (changing screens, changing cables, trying different BIOS versions, trying different graphics driver versions, ...), without any result, I discovered on this forum that a lot of users are experiencing the same issues.

An issue like this is not something I would expect in a 2017 product (especially coming from Intel).

The client bought new screens with a HDMI connection, only to find out this also gives flickering every few minutes, again, on ALL of them! (the screen doesn't go completely black as when using VGA, it's less severe, a kind of fast flicker).

Needless to say this is a very disappointing experience for both my client and me.  Not to mention the cost of troubleshooting, only to find out it's a faulty product.

This looks like a design flaw, I can't believe Intel is still selling these!

Probably only a few % of the people with this issue will find the way to this forum, so that means a huge amount of frustrated customers will hesitate to buy an Intel product again.

I'm sure Intel knows exactly what the issue is, they should, after all these months and probably thousands of these units returning.

So my question is:

To other NUC6CAYH (with Windows 10) users:

Is there anyone here who's problem was actually completely solved (Please specificy if you use HDMI or VGA) if yes, which actions did you exactly take?

To Intel support:

As this issue seems so widespread, please tell us what the root cause is.  If you're not aware of the root cause, please escalate this to the right engineers to troubleshoot.  My feeling is that this specific issue is causing damage to Intel's good name, not to mention the huge troubleshooting costs for all people still buying this product.

Is there an actual solution? Will the problem be 100% solved with a replacement from Intel?

Thanks!

I have all the latest bios/drivers installed and noticed my network speed fails to initialize a 1000Mbps connection and uses a fallback to 100Mbps.

(Network driver is version 22.7.1)

I have the nuc connected to a gigabit switch which shows the connection speed with its leds ... orange being 100Mbps, green 1000Mbps

When the nuc boots, I see the network come up 3 or 4 times for 1 or 2 seconds in gigabit mode always losing connection (all lights out), then eventually it stays active in 100Mbps mode.

When I go to the properties of the network adapter, I see in the link speed tab, (its set to auto negotiation) current speed is: "100Mbps Full Duplex (EEE: Not Negotiated))"

I know gigabit was working before, unfortunately I cannot say what version of the driver was working and when it stopped ...

When I bought my NUC, I made the update to version 057 and everything went well, using the Express method, very simple, fast and easy.

So, in my NUC I had the BIOS 057 and today I did the update again to version 062 and everything went well again, (image2) but after completing the update, the NUC reset and displayed the message, (image1). This worried me because if I understood correctly, the BIOS is not compatible with my NUC ??

Everything seems to be working fine as it has accessed Windows 10 64 Pro normally. When checking the BIOS version, I noticed that it was updated, (image3).

I hope some message will reassure me, please. Thank you

I have an Intel NUC NUC5i3RYH that is having a peculiar problem. Here are the details.

Setup:

1. Intel NUC NUC5i3RYH

2. One Internal Seagate 1 TB Hard Drive - OS is installed on this.

3. 16 GB RAM - 8 x 2 GB SO-DIMM's - Crucial

4. Two External USB 3.0 WD 2.0 TB drives connected to Rear USB Ports. Both are data drives, no boot partitions on these. These are both WD's but two different models.

5. USB Mouse and Keyboard - Connected to front USB Ports

Symptoms: The system is working fine except when cold rebooted. After a cold reboot the NUC goes into an indefinite boot loop. I just see the NUC Logo and then it reboots after a few seconds. Cannot enter the BIOS since the F2, F7 etc message does not appear on the bottom right of the monitor. The keyboard and mouse are unresponsive.

Procedure to boot: Unplug both the external hard drives and reboot. The system proceeds to boot normally. Once booted, I can then plug in the two external drives and they appear to work fine. A warm reboot causes no problem and the system works properly and boots up just fine.

Things tried to resolve the issue: Tweaked all the BIOS settings like, UEFI Boot -> disable/enable, Watchdog -> disable/enable, USB xhci mode -> disable/enable and many other parameters as discussed throughout the forum. However the problem remains. I am running the latest BIOS as well. Version RYDBWi35.86A dated 1/18/2017.

Other Observations: Have tried powering up the external USB drives with a powered USB hub which has no effect, the system still goes into a boot loop. Also noticed that when the drives are attached the keyboard and mouse become unresponsive. It seems as the whole USB bus is hung till I remove the external USB drives. If I remove "both" the drives during the boot loop, I immediately get a message on screen saying that POST has failed and I could either press F2 to go into BIOS or F9 to continue. The keyboard and mouse come alive at this stage and I can press F2 to go into BIOS and start twiddling my thumbs . Last point, I did install this system using a 16GB Pen drive so apparently pen drives may be working after a cold reboot. I think the issue is with the two external drives plugged in.

Would appreciate if Intel support can look into this matter and provide a resolution. Would be happy to provide any more details as required.

NUC 5i7RYH

Kingston G4 8GB USB created by Standard Ubuntu USB-utility with Ubuntu 17.04

The USB is found by BIOS but it won't boot from it.

I have tested several BIOS settings and updated BIOS Firmware too.

Any ideas?

The recent models of Intel NUC seems to have taken a bad path of soldering the wireless features (BT, WIFI and whatelse) onto the motherboard making it hard to remove these features if you want a device with no wireless features at all.

Are there any plans from Intel to revert from this bad decision and making it again possible to make the wireless features optional rather than mandatory?

I got my nuc about 1.5 months ago, about a week ago I updated bios/graphics driver and ever since have been experiencing issues. The NUC seems to lock up whenever the display is disconnected. Either by windows putting it to sleep, or even if I unplug the hdmi cable. Primary display is a 2017 Vizo E-60-e3, but I have confirmed it on a 1080p pc monitor as well. I tried rollling back the drivers, but it wont boot with anything but the most recent drivers and the stock windows drivers. The issue does not happen on the windows drivers. Thanks in advance for assistance!

Just finished bringing up my NUC7i5BNH with a clean install of Windows 10.

When the generic Windows driver was in charge before I installed the Intel Graphics driver, I had the native 2560 x 1440 displayed on my monitor over the HDMI cable. As soon as I installed the iGFX driver (GFX_WIN10_64_15.46.2.1.4729) the display dropped to 1920 x 1080 and I cannot for the life of me find a way to return to the display's native resolution.

I tried a custom setting in the Intel Graphics Setting application and it says that the requested setting is outside the bandwidth limitations for the device (which it shouldn't be).

Under the "Options and Support" section of the Intel Graphics Setting application, the application does see that 2560 x 1440 @ 60p Hz is a supported monitor mode. The monitor is from Monoprice and it's a 27" display.

The Intel Driver Update Utility doesn't register a version number for the graphics driver and reports it as "Unknown".

I don't know if it's related, but the system also doesn't recognize the audio capabilities of the monitor either.

More information from the Iris Graphics Control Panel:

----

Intel(R) Iris(TM) Plus Graphics 640

Report Date: Saturday, August 26, 2017
Report Time [hh:mm:ss]: 1:21:03 AM
Driver Version: 22.20.16.4729
Operating System: Windows* 10 Home (10.0.15063)
Physical Memory: 32659 MB
Vendor ID: 8086
Device ID: 5926
Device Revision: 06
Graphics Output Protocol (GOP) Version: 9.0.1066
Current Resolution: 1920 x 1080

Processor: Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz
Processor Speed: 2208 MHz
Processor Graphics in Use: Intel(R) Iris(TM) Plus Graphics 640
Shader Version: 5.1
OpenGL* Version: 4.5
OpenCL* Version: 2.1
Vulkan* Version: 1.0.38

* Microsoft DirectX* *
Runtime Version: 12.0
Hardware-Supported Version: 12.0

* Devices connected to the Graphics Accelerator *

Active Displays: 1

* Digital Display *

Display Type: Digital
Serial Number: YSP12310001
DDC2 Protocol: Supported
Gamma: 2.2
Connector Type: DisplayPort
Device Type: Digital Display

Maximum Image Size
Horizontal Size: 23.62 inches
Vertical Size: 13.39 inches

Supported Modes
640 x 480 (60p Hz)
640 x 480 (75p Hz)
720 x 400 (70p Hz)
720 x 480 (60i Hz)
720 x 480 (60p Hz)
720 x 576 (50p Hz)
720 x 576 (50i Hz)
800 x 600 (60p Hz)
800 x 600 (72p Hz)
800 x 600 (75p Hz)
1024 x 768 (60p Hz)
1024 x 768 (75p Hz)
1152 x 864 (75p Hz)
1280 x 720 (50p Hz)
1280 x 720 (60p Hz)
1280 x 1024 (60p Hz)
1280 x 1024 (75p Hz)
1440 x 900 (60p Hz)
1680 x 1050 (60p Hz)
1920 x 1080 (60p Hz)
1920 x 1080 (60i Hz)
1920 x 1080 (50i Hz)
1920 x 1080 (50p Hz)
2560 x 1440 (60p Hz)

Power Management Support
Standby Mode: Supported
Suspend Mode: Supported
Active Off Mode: Supported

Raw EDID:
00 FF FF FF FF FF FF 00 66 70 60 27 00 00 00 00
0F 17 01 04 80 3C 22 78 FE EE 95 A3 54 4C 99 26
0F 50 54 A5 CB 00 71 4F 81 C0 81 80 95 00 B3 00
D1 C0 01 01 01 01 56 5E 00 A0 A0 A0 29 50 30 20
35 00 55 50 21 00 00 1A 00 00 00 FF 00 59 53 50
31 32 33 31 30 30 30 31 0A 20 00 00 00 FD 00 17
4C 0F 63 19 00 0A 20 20 20 20 20 20 00 00 00 FC
00 32 37 69 6E 63 68 20 48 44 4D 49 0A 20 01 5B

02 03 1F F1 4C 01 02 03 04 05 07 90 12 13 14 16
1F 23 09 07 07 83 01 00 00 65 03 0C 00 10 00 02
3A 80 18 71 38 2D 40 58 2C 45 00 FE 1F 11 00 00
1E 01 1D 80 18 71 1C 16 20 58 2C 25 00 FE 1F 11
00 00 9E 01 1D 00 72 51 D0 1E 20 6E 28 55 00 FE
1F 11 00 00 1E 8C 0A D0 8A 20 E0 2D 10 10 3E 96
00 FE 1F 11 00 00 18 01 1D 00 BC 52 D0 1E 20 B8
28 55 40 E8 12 11 00 00 1E 00 00 00 00 00 00 07

* Other names and brands are the property of their respective owners.