Intel® NUCs
Assistance in Intel® NUC products
The Intel sign-in experience has changed to support enhanced security controls. If you sign in, click here for more information.
12966 Discussions

New NUC X15 - constant rebooting


Hi all, I have just bought a new NUC X15.  The laptop is great apart from the fact that it reboots or freezes constantly (usually within 2 hours but under load it could be just a few minutes).

I have logged a request with the supplier (Mwave) for help/RMA but wanted to see if anyone else had any issues.

It has 2 x Crucial Ballistix 16GB memory modules (not officially on the Intel compatibility list but meets the necessary criteria and the 8GB Ballistix modules are on the list).

I have tried with both Windows 10 and Windows 11, with a clean install only and with the Intel drivers (installed according to the specific order indicated by Intel)

I have also tried using each SODIMM individually as well as switching SODIMM slots (both single and dual SODIMMS)

I also tried with an 8GB DDR4 SODIMM from a Lenovo X270 (slower speed) which seems a bit more stable but still reboots.

When a memory DMP file is created (not often given it's usually an unexpected restart) it indicates that the issue lies with the MODULE_NAME being GenuineIntel.sys with code 124 which usually indicated a hardware issue (full bugcheck info below)


I suspect I have a faulty X15 unfortunately so just trying to work out if anyone else has had issues (or no issues if they have an X15) and whether I need to go to MWave or Intel for the return (order was placed only 17 days ago)




* *
* Bugcheck Analysis *
* *

A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffcc897b303028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000002110a, Low order 32-bits of the MCi_STATUS value.

Debugging Details:


Key : Analysis.CPU.mSec
Value: 2312

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2464

Key : Analysis.Init.CPU.mSec
Value: 780

Key : Analysis.Init.Elapsed.mSec
Value: 39864

Key : Analysis.Memory.CommitPeak.Mb
Value: 80

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1




BUGCHECK_P2: ffffcc897b303028

BUGCHECK_P3: be000000

BUGCHECK_P4: 2110a

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME: gamingservicesnet.exe

ffffa601`411bf908 fffff805`448b433a : 00000000`00000124 00000000`00000000 ffffcc89`7b303028 00000000`be000000 : nt!KeBugCheckEx
ffffa601`411bf910 fffff805`42c415b0 : 00000000`00000000 ffffcc89`7b303028 ffffcc89`73bb9d10 ffffcc89`7b303028 : nt!HalBugCheckSystem+0xca
ffffa601`411bf950 fffff805`449b5fde : 00000000`00000000 ffffa601`411bf9f9 ffffcc89`7b303028 ffffcc89`73bb9d10 : PSHED!PshedBugCheckSystem+0x10
ffffa601`411bf980 fffff805`448b5c61 : ffffcc89`7afd1900 ffffcc89`7afd1900 ffffcc89`73bb9d60 ffffcc89`73bb9d10 : nt!WheaReportHwError+0x46e
ffffa601`411bfa60 fffff805`448b5fd3 : 00000000`00000004 ffffcc89`73bb9d60 ffffcc89`73bb9d10 00000000`00000004 : nt!HalpMcaReportError+0xb1
ffffa601`411bfbd0 fffff805`448b5eb0 : ffffcc89`73524890 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffa601`411bfc20 fffff805`448b6101 : 00000000`00000010 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffa601`411bfc60 fffff805`448b536b : 00000000`00000000 00000000`00000000 ffffa601`411bfef0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa601`411bfc90 fffff805`448b7bb5 : ffffcc89`73524890 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
ffffa601`411bfcc0 fffff805`4490d2c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffa601`411bfcf0 fffff805`448061fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffa601`411bfd20 fffff805`44805eb7 : 00000000`00000000 00000000`00000000 00000000`000aa000 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffa601`411bfe60 00007ffa`a30345a7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
000000bb`3e0fde58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`a30345a7

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_CACHE_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release


OSNAME: Windows 10

FAILURE_ID_HASH: {b70a049a-4a17-5749-b5df-df070316ca7d}

Labels (1)
0 Kudos
2 Replies
Super User

So the Intel support engineers can have more information about your system, Please download and run the Intel System Support Utility ( ) for Windows. Select all data categories and then have it generate a report. Next, have the tool Save the report to a text file (don't try to use the Submit capability; it doesn't work). Finally, using the Drag and drop here or browse files to attach dialog below the edit box for the body of your response post, upload and attach this file to the response post.

Doc (not an Intel employee or contractor)
[Waiting for Windows 12]


I had the same experience as you. I used 5 computers with the same configuration and the same software environment to build a mini-cluster for data processing. Among them, 3 computers often crashed and stuck on one interface. I am looking for a solution on the forum