Hard crashes NUC8i7HNK with clean Windows 10 Home install

[BSmit19]

Hi all,

Just received my new setup with Intel NUC8i7HNK. To get started quickly I first created an image of my old workstation (Intel NUC D54250WYK), but got hard crashes. Had to use the power button for a couple of seconds to reboot the machinTwo days ago I installed Windows fresh with all recent drivers (all from intel site) and bios (0040). Still have crashes. Even when only browsing with firefox with no other applications open.

Added components:

Memory: Kingston ValueRAM - DDR4 16GB - SO DIMM - 260PIN - 2400Mhz / PC4-19200 - C

SSD: Intel SSD 720p 256GB

Display: Dell Ultrasharp U3818DW

Keyboard/Mouse: Dell premier wireless

Please see output of ssu and ipdt attached. Hope someone knows the answer.

Best regards,

Bas

[idata]

Hello mwerks_bas,

Thank you for joining the Intel Community Support.Are you getting any blue screen error message? If so, which one?Does this happen if you swap components?Wanner G.

[BSmit19]

Hi Wanner,

Just before clicking on send in the forum the NUC crashed. :-) The positive thing is that it gave me the ability to take a photo of the BSOD...

About 60% of the time Windows is not even able to produce a BSOD. About 20% of the time it produces a partial BSOD with at the lower half a black screen with sporadic pixels but is not able to produce a crash dump. (It stays at 0%, see attached photo) About 20% I get (partial) memory dumps.

Since I was running a password manager, I'm a little hesitant to send the memory dumps, so I ran them myself through the dubugger. I used the following steps to generate these:

Downloaded and installed the Windows 10 SDK:

https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk

Followed this blog to analyze the memory.dmp:

https://weblogs.asp.net/owscott/reading-a-memory-dmp-or-other-dmp-file

Starting the debugger the screen also show a message of probable cause.

Please see attached the reports, bsod photo and a screenshot of starting the debugger.

I'm no Windows debug expert, but looking at the files my gut feeling says I'm running into a display driver bug.

Thanks in advance for your effort into resolving this.

Best regards,

Bas

[Ray_W_Intel]

Can you run a DirectX Diagnostic report and upload the results?

In the start dialogue enter dxdiag and press enter. Once in the tool click Save All information and then upload the resulting dxdiag.txt that it creates.

[BSmit19]

Please see attached the dxdiag.txt file.

Best regards,

Bas

[idata]

Hello mwerks_bas,

Thank you for your response. I will do some research about this issue. I will keep you updated.Wanner G.

[idata]

Hello mwerks_bas,

Thank you for the information provided.I was wondering if you ever tried to do a fresh install of the operating system and experienced the same issues.Do you still have issues with the image of your old workstation you created?Wanner G.

[BSmit19]

Hi Wanner,

Yes, after a couple of days working with the image of my old workstation I did a fresh reinstall of Windows 10 Home with current Intel drivers. Both situations generated hard crashes..

Best regards,

Bas

[idata]

Hello mwerks_bas,

Your system image may not work in your Intel® NUC Kit NUC8i7HNK because of the differences in hardware. https://ark.intel.com/compare/126141,76977These issues you are having with your new unit usually happen when the main components are not compatible. It seems that your Intel® SSD is compatible with your unit, but could you please provide your memory part number?Also, have you tried swapping other compatible memory/SSD?Wanner G.

[BSmit19]

Hello Wanner,

I use "Kingston ValueRAM - DDR4 16 GB - SO DIMM 260-PIN - 2400 MHz / PC4-19200 - C" in the system. This was advised by the reseller although it is not on the HCL. I will contact them to get the memory replaced.

Best regards,

Bas

[idata]

Hello mwerks_bas,

In these cases, it is recommended to isolate hardware components to discard faulty hardware or conflict with the unit. You can also check the system memory and compatible memory modules for your unit.System Memory for Intel® NUC Kits NUC8i7HNK https://www.intel.com/content/www/us/en/support/articles/000027038/mini-pcs/intel-nuc-kits.htmlIntel® Product Compatibility Tool http://compatibleproducts.intel.com/ProductDetails/ExportPeripheralInfo?moduleName=Intel%C2%AE%20NUC&productType=Kits&productName=Intel%C2%AE%20NUC%20Kit%20NUC8i7HNK# If you need any further help after replacing your memory, I will be glad to assist.Wanner G.

[BSaun]

May not be relevant, but I will mention that my NUC HNK was set up and running normally until I decided to image just the user data on my old (non nuc) laptop and restore it to my new NUC - bad idea... Basically locked my login so that my Ms password (which still worked on the laptop Ms account) would not unlock the new NUC. Had to do a refresh to get things fixed.

My point is that restoring images ( even limited ones) to dissimilar hardware seems to cause predictable headaches. You could start with a clean install, and then restore from " file history" to avoid the dissimilar hardware conflicts.

[BSmit19]

Hi mrbillz,

In both situations where I used a previously imaged NUC and a fresh install of Windows 10 produced the hard crashes.

best regards,

Bas

[BSmit19]

Hi Wanner,

The reseller accepted the RMA for the memory. While opening the NUC to remove the memory for return sending I saw that the memory was not fully seated in the SO-DIMM slot. I reseated the memory and since then no crash has happened (2 workdays of "normal kind of load" like browsing, outlook and office")

I will run some benchmarks which are memory/graphics intensive to be sure.

Curious enough memtest86 gave no errors when the memory was not correctly seated.

I will post an update within a week.

Thanks so far for your efforts.

Best regards,

Bas

[BSaun]

Hi Bas

Saw your note re: crashes after imaging...

Interesting, when I first built my NUC, it wouldn't boot - at all.. opened up and treated the memory which seemed ever so slightly misaligned - then boot and ran fine since - well except for the hum...

Memory slots must be very tight tolerances - there seem to be several memory related threads running.

Hoping for continued luck on your end...

Mrbillz