This message was posted on behalf of Intel Corporation
Thank you for contacting the Intel community.
In this case, if Intel already replaced the Intel NUC and the issue persists, most likely the issue is not with NUC itself, another component, device or perhaps a driver is causing the freezing issue.
I know that you get this problem 6-18 hours of the NUC's up-time, but try to access the system in safe mode and check if you get the same behavior at the moment you access it, the purpose of accessing the system in safe mode is the computer loads the basic files and drivers absolutely necessary to run the operating system.If the system freezes at that moment it is a hardware issue, if not it could be a driver or app causing the issue. This is just in case you get the problem at the moment you start the system is safe mode.
You can try to run Windows update and make sure all important updates are installed; you can also try reinstalling some drivers to make sure they are correctly installed. You can download the latest drivers for your Intel® NUC here:
Also, make sure you have the latest BIOS installed, please check F7 BIOS Update Instructions for Intel® NUC
If this does not work and Intel already replaced the NUC, I suggest trying to do a system restore if it is possible or try to use different ram, you may want to check System Memory for Intel® NUC Kits NUC6i3SY/NUC6i5SY
I hope that can help.
Here is the information I have:
1) When I access the system in safe mode, should I leave it running for the same amount of time, 6-18 hours? Right now, I have tried disabling VMware Workstation 12.5.2 completely off the NUC, to see if it had anything to do with the freezing. When this test is complete and if it still freezes, I will try doing safe mode for 6-18 hours and see if the freezing disappears.
2) I ran Windows update and currently am up to date. I reinstalled all the NUC drivers from the link you provided.
3) My BIOS was reflashed and is up to date on version 0057.
4) My exact specs for the RAM installed in my Intel NUC is attached below:Memory Summary For NUCPC
Number of Memory Devices: 2 Total Physical Memory: 32657 MB (32768 MB) Total Available Physical Memory: 30370 MB Memory Load: 7%
Item Slot #1 Slot #2 Ram Type DDR4 DDR4 Maximum Clock Speed (MHz) 1067 (JEDEC) 1067 (JEDEC) Maximum Transfer Speed (MHz) DDR4-2133 DDR4-2133 Maximum Bandwidth (MB/s) PC4-17000 PC4-17000 Memory Capacity (MB) 16384 16384 Jedec Manufacture Name Crucial Technology Crucial Technology SPD Revision 1.1 1.1 Registered No No ECC No No DIMM Slot # 1 2 Manufactured Week 41 of Year 2016 Week 41 of Year 2016 Module Part # CT16G4SFD8213.M16FB CT16G4SFD8213.M16FB Module Revision 0x0 0x0 Module Manufacturing Location 0 0 # of Row Addressing Bits 16 16 # of Column Addressing Bits 10 10 # of Banks 16 16 # of Ranks 2 2 Device Width in Bits 8 8 Bus Width in Bits 64 64 Module Voltage 1.2V 1.2V CAS Latencies Supported 9 11 12 13 14 15 16 17 18 19 9 11 12 13 14 15 16 17 18 19 Timings @ Max Frequency (JEDEC) 15-15-15-36 15-15-15-36 Maximum frequency (MHz) 1067 1067 Maximum Transfer Speed (MHz) DDR4-2133 DDR4-2133 Maximum Bandwidth (MB/s) PC4-17000 PC4-17000 Minimum Clock Cycle Time, tCK (ns) 0.938 0.938 Minimum CAS Latency Time, tAA (ns) 13.500 13.500 Minimum RAS to CAS Delay, tRCD (ns) 13.500 13.500 Minimum Row Precharge Time, tRP (ns) 13.500 13.500 Minimum Active to Precharge Time, tRAS (ns) 33.000 33.000 Minimum Row Active to Row Active Delay, tRRD (ns) 3.700 3.700 Minimum Auto-Refresh to Active/Auto-Refresh Time, tRC (ns) 46.500 46.500 Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC (ns) 350.000 350.000 DDR4 Specific SPD Attributes Maximum Clock Cycle Time, tCKmax (ns) 1.900 1.900 Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC2 (ns) 260.000 260.000 Minimum Auto-Refresh to Active/Auto-Refresh Command Period, tRFC4 (ns) 160.000 160.000 Minimum Activate to Activate Delay Time different bank group, tRRD_Smin (ns) 3.700 3.700 Minimum Activate to Activate Delay Time same bank group, tRRD_Lmin (ns) 5.300 5.300 Minimum CAS to CAS Delay Time same bank group, tCCD_Lmin (ns) 5.355 5.355 Minimum Four Activate Window Delay (ns) 21.000 21.000 Maximum Activate Window in units of tREFI 8192 8192 Thermal Sensor Present No No DRAM Stepping 0 0 DRAM Manufacture Micron Technology Micron Technology SDRAM Package Type Monolithic, 1 die, Single load stack Monolithic, 1 die, Single load stack Maxium Activate Count (MAC) Unlimited MAC Unlimited MAC Post Package Repair Supported No No Module Type SO-DIMM SO-DIMM Module Height (mm) 30 30 Module Thickness (front), (mm) 2 2 Module Thickness (back), (mm) 2 2 Reference Raw Card Used Raw Card B Rev. 16 Raw Card B Rev. 16
cvare, I am not able to to try another pair of DDR4 RAM sticks due to the cost it will leave on me. DDR4 RAM is still a bit expensive. I don't have any other DDR4 RAM sticks on hand to try. Is there something else that I can try?
I would like to also report that VMware Workstation 12.5.2 has been disabled since 12:45 AM of 2/11/2017, and the NUC has not had any "freezing" issue re-occur since. I have heard from Intel chat support that VMware Workstation is not a supported product to run on top of Windows 10 with the NUC. Could VMware Workstation cause problems like the one I described in post #1?
Do you know if Hyper-V is supported by Intel NUC when they were testing the NUC6i5SYH?
cvare Thanks. I'm curious to know about both Hyper-V and VMware workstation 12.5.2 testing.
Also, I would like to report my results so far since I uninstalled VMware Workstation Pro 12.5.2 completely from the NUC. Since the boot time (2/11/2017, 3:06:33 PM) I moved all my virtual machines over to Microsoft's Hyper-V in Windows 10. After doing so and running for a full day, I have not had to restart the NUC once. I am also not getting any more operating system freezing problems. While it might be too early for me to say that the problem is gone, I think VMware Workstation 12.5.2 might have done something to affect the stability of my NUC.
I've read a few threads over at VMware forums and this one, including other threads, mention VM hosts freezing with VMware Workstation 12.5.2 on machines that have Intel Iris graphics (like the one my NUC has). Some solutions they suggested involved downgrading VMware Workstation to a previous version, but I didn't want to do that since the older versions had security vulnerabilities.
Maybe VMware Workstation was causing my NUC to freeze, but I'm not sure how I could test it other than completely removing it and seeing it I encounter the freezing problem again.
Since I received the replacement Intel NUC, the only changes that I did was flash the 0057 BIOS using the usb method. I left all the BIOS settings at their defaults.
Also, this is another day with the NUC running using Hyper-V instead of VMware Workstation. So far, still no freezes, so I am hopeful now.
Jeffrey, I loaded VMWare yesterday and installed Win8.1 and Win10 as VMs. I haven't done much else, but I'm not experiencing any issues.
I'll try to do 5 like you had, but a question about this statement: 'Within 6-18 hours of the NUC's uptime, the NUC will "freeze" at the Windows Login screen.'
Does that mean you're rebooting? Or is it sleeping and you have to log back in when you wake it up?
cvare What I mean by freezing at the login screen is that, when I realize that my Intel NUC doesn't respond to a webserver request (I am hosting Windows Server 2016 IIS in a virtual machine), I would manually connect a mouse, keyboard, and a monitor with an HDMI cable connecting directly to the NUC to check out the problem.
Upon checking, the Windows Lock screen (or login screen) shows. When I attempt to login (clicking the lock screen to reveal the login form), nothing happens. I can't login. The form never appears. Also, the time shown on the lockscreen is off by 6-12 hours when I notice it. That leads me to believe that the freezing problem happened at whatever time the lockscreen shows.
This requires me to hard reboot the NUC via the power button.
The 5 VMs that I am using are all Server 2016 virtual machines. Some VMs have host-only network adapters and others have dedicated nics directly connected to a network switch via USB ethernet adapters. Dynamically allocated memory is not enabled for the VMs, meaning all these machines were getting full RAM on boot.
cvare It looks like I spoke too soon. After a week of the Intel NUC being stable and online, it has now frozen again, this time without the ability to see anything on the monitor (no output from HDMI port on the NUC to check for frozen time on the Windows lock screen). This is really frustrating that this happens on this computing unit but not on regular desktop and laptop machines. Why is the Intel NUC very prone to problems that general everyday hardware seem to handle just fine with virtualization?