Community
cancel
Showing results for 
Search instead for 
Did you mean: 
AArch
Beginner
3,809 Views

NUC7PJYH constant BSOD (2-3 a day)

Hi,

I have bought an NUC7PJYH early august and have updated everything (BIOS 0044, Drivers, Windows).

The computer is mainly used to stream on my Tv and the computer either Freezes (screen isnt responsive anymore and need to hard reboot) and no dump files get created (so not BSOD) or I get a blue screen. BSOD can happen on idle after a long period not being used or when using netflix or on boot (driver ?). I can not figure out what the issue is (driver or hardware) from the dump files. Fast boot is turned off, and sleep is disabled. Hoping I can get some help from more experienced people.

For SSD, i purchased the Adata SU650 120GB, and for ram I took the Crucial Ballistix LT 4GBx2 kit BLS2C4G4S240FSD CL16(which has all same specs as the "Intel Validated" Crucial CT2K4G4SFS824A CL17 except latency, but same company). I have seen lots of people using the Ballistix version and everything is working well as latency 16 is supported for this NUC and at time of purchase, they were listed as supported on the crucial site (but I see now it says NOT).

The RAM has done 8 full passes of MEMTEST86+ on each stick individually and in each slot, as well as a 30 passes (28hours) in with both slots and not a single error detected. I ran Prime95 for CPU, and again, all good. SSD SMART is all good, chkdsk /f returns no errors, and the ADATA diagnostic tool returns no errors. I have tried reinstalling windows, doing sfc /scannow and DISM /Online /Image-Cleanup to no avail.

The link for the Dump files is :https://1drv.ms/u/s!ArdSCvUN_-4Bh0OSx6Kuz_FTq8ze https://1drv.ms/u/s!ArdSCvUN_-4Bh0OSx6Kuz_FTq8ze

I also included the system info, drivers, etc and the event viewer logs.

I am aware of the Dual Channel issue on this NUC, but my understanding is that everyone still has it running, just slower than expected...but not BSOD from this fault.

Edit: logs only https://1drv.ms/f/s!ArdSCvUN_-4Bh0Tg9gg-sF4vvSjh https://1drv.ms/f/s!ArdSCvUN_-4Bh0Tg9gg-sF4vvSjh

 

 

0 Kudos
23 Replies
rgord1
Novice
181 Views

I have a similar issue with this NUC. Occasional random blue screening while on idle, occasionally on playing a video file, but I have never seen it on boot.

I have reseated all connections, updated the bios, and using all latest drivers. I suspected the update to Windows 10 1803 as the initial culprit, but the amount of blue screening was reduced somewhat by re-installing the ethernet driver. There have also been suggestions that sound drivers might be a cause, but I haven't tried rolling back to earlier graphics/HD audio drivers to see if that has any effect.

There have also been suggestions that a complete rebuild of Windows 1803 from scratch can overcome some instances of blue screening, but I haven't resorted to that yet, nor tried an in situ (repair) install of 1803.

At this stage the amount of blue screening, about one a day in a six hour period, is tolerable, while I await some fix from Intel or Microsoft, if that is the problem. I also have a NUC7i5BNH with Windows 10 1803 which does not have a blue screening problem, but with that I am obliged to use an older version (100) of the HD audio drivers for audio stability. It could be the audio driver that makes the difference, but I suspect it may be more an issue with the hardware in the NUC7PJYH, possibly with the memory which has been subject of some debate elsewhere in this forum.

Hopefully someone here will be able to pinpoint cause(s) of blue screening with this NUC.

idata
Community Manager
181 Views

Hello mk6tdi,

 

 

Thank you for posting on the Intel ® communities.

 

 

I can see that you are having problems with BSODs when using your NUC device.

 

 

Regarding this, I would like to start by gathering some information of your system, specifically, the System Support Utility report, this report can be generated from our tool, you can refer to the link below so you can download it:

 

 

https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-

 

 

Make sure to attach the created report to this thread.

 

 

Also, I would like to add that you can try testing another RAM stick in the system, just for testing purposes and see if the BSOD occurs then. If it does then it could be also related to O.S, which in this case, another option, if possible, would be to try to re-install the O.S. This also applies to raymondjpg.

 

 

I hope this helps.

 

 

 

Regards,

 

David V

 

 

Intel Customer Support Technician

 

Under Contract to Intel Corporation
AArch
Beginner
181 Views

Hi,

i will run the SSU utility once i have access to the computer. However I do have the msinfo32 report in the OneDrive link i posted under " logs " as well as all software/driver info If that can help in the meantime.

As for RAM, i do not have a spare set compatible with the system. However, both sticks currently pass all memory diagnostic in all combinations (individually, in each slot as well as combined).

I have tried reinstalling the OS maybe 1 week after purchase because i was getting a few BSOD, but this didnt resolve the issue. I haven't reinstalled it recently as I didnt want to lose any info in case I didnt save all relevant crash files.

Edit: SSU logs attached

idata
Community Manager
181 Views

Hello mk6tdi,

 

 

Thank you for your response.

 

 

I am currently reviewing the information; however, since you mention it I want to confirm. You were experiencing this issue before and it was solved by an O.S re-installation? Did the problem appear again right now or is it recurring from the past one? I need this information for a better understanding of the situation.

 

 

I hope to hear from you.

 

 

 

Regards,

 

David V

 

 

Intel Customer Support Technician

 

Under Contract to Intel Corporation
AArch
Beginner
181 Views

Hi David,

sorry there was a typo in my previous reply. The OS reinstall did not resolve the issue. If anything, i am getting more random BSOD's since that time.

idata
Community Manager
181 Views

Hello mk6tdi,

 

 

Thank you for your response.

 

 

Now that it has been clarified I would like to request for screenshots/photos of the blue screen showing the error or crash code. This is important to determine what could be causing this random crashes. Please attach the picture/screenshot to this thread for further analysis.

 

 

 

Regards,

 

David V

 

 

Intel Customer Support Technician

 

Under Contract to Intel Corporation
AArch
Beginner
181 Views

Hi David,

I have included the kernel dumps and minidumps in the orginal post.

here is the link: https://1drv.ms/u/s%21ArdSCvUN_-4Bh0OSx6Kuz_FTq8ze

usual culprits are:

service_exception

memory_management

irql_not_less_or_equal

unexpected_kernel_mode_trap

i did get 1-2 errors 124 (whea_uncorrectable_error)

i had run driver verifier on all non microsoft drivers for 72hours and didnt get one BSOD, but I hadnt checked all settings to check, only the 4-5 more important settings.

idata
Community Manager
181 Views

Hello mk6tdi,

 

 

Thank you for your response.

 

 

I have sent you a private message so we can discuss some steps to follow from here in order to address the issue, please check your inbox.

 

 

 

Regards,

 

David V

 

 

Intel Customer Support Technician

 

Under Contract to Intel Corporation
rgord1
Novice
181 Views

It would be helpful for me, and possibly others experiencing random blue screening with this NUC, if the discussion of what steps might be taken to counter this were out in the open rather than subject to private messaging.

Like OP the blue screening I am experiencing comes with apparently number of different errors, so very difficult to pinpoint a cause.

PeterNUC
New Contributor I
181 Views

Hello raymondjpg and mk6tdi,

I just noticed this thread. I am also having severe BSODing problem (like 5-10 times a day), see Did you have any luck in isolating/resolving the issue?

Best, Peter

rgord1
Novice
181 Views

I saw your post but did not respond because my bluescreening/freezing issues were in no way due to a bios update.

I think I did try a bios update to resolve the issue, but it persisted.

What did resolve the issue was reinstallation of Windows 10 1709, because I thought that 1803 was at the root of the issue, but AT THE SAME TIME disabling all network adapters other than the ethernet adapter under "Change adapter settings" in Network and Internet Settings. There were two adapters that I disabled, wireless and bluetooth.

Updating Windows 10 to 1803, and at the same time disabling all network adapters other than the ethernet adapters, also saw the issue remain resolved. This time there was only a wireless adapter to disable. There was no bluetooth adapter visible under "Change adapter settings".

The issue was not, then, specifically related to Windows 10 1803.

At the time I suspected a badly behaved wireless adapter or driver. I did not investigate different wireless drivers to see if different versions would fix the issue.

The solution works for me because I do not use the wireless capability of this NUC. I prefer ethernet. For anyone who needs the wireless capability, selectively disabling network adapters under "Change adapter settings" might lead to some resolution. For all I know, if badly behaved network adapters are giving you these bluescreening/freezing issues then disabling the ethernet adapter might allow the wireless adapter to work trouble-free.

There is also the distinct possibility that the bluescreening/freezing issues were due to some interaction between Windows 10 updates and network adapters in this NUC. I really couldn't say, but I do know that my NUC still has no such issues with 1803 fully patched, with only the ethernet adapter enabled in Network and Internet Settings.

PeterNUC
New Contributor I
181 Views

Thanks a lot for your reply. It's good to hear that you were able to resolve the issue. I will disable WiFi (since I do not use it anyway) and, maybe, reinstall Windows.

I have a couple of questions:

  1. Where did you disable WiFi, in Windows or in BIOS?
  2. Can you see hotkeys prompts during POST, like "F2 for Setup"? I had them initially. After some BIOS update they disappeared, but I could still see the NUC logo and pressing F2 at that moment brought me to BIOS. However at some point I lost even that. Now when I reboot, the first thing I see is Windows UEFI boot screen (NUC logo with Spinning Circle of Dots). Pressing F2 at that moment does nothing. To get to BIOS I need to hit F2 while having black screen, before NUC logo with Spinning Circle appears. I believe that something is wrong with my BIOS.

Thanks, Peter

rgord1
Novice
181 Views

I'd just try disabling all network adapters other than ethernet. No need to reinstall Windows I think.

1. I disabled them in Windows, not the bios.

2. I can see the hotkeys during POST, but my bios version is 44.

If you see the spinning logo then Windows is already booting up and you won't be able to get to the bios. Have you tried advanced startup options? One of the options is to enter bios on restart.

PeterNUC
New Contributor I
181 Views

Thanks a lot for the info. It's very helpful.

I also have BIOS 44 now. Actually, I do not have any problems with getting to BIOS. I hit F2 when NumLock on the keyboard lights up. Works perfectly. But the absence of the hotkeys prompts during POST and now the absence of the whole POST screen indicate certain degradation in BIOS.

rgord1
Novice
181 Views

If I were faced with your situation where you have bios 44 already, I would probably try for a reinstall, in the knowledge that there is always potential for a bios flash to go wrong.

Not that I am advocating that you do that, simply saying that is what I would do!

n_scott_pearson
Super User Retired Employee
181 Views

For Raymond's issue, there was a known issue with the 1804 upgrade where it would screw up the wireless software stack. A (painful) manual uninstall of both the Wireless and Bluetooth drivers followed by a reinstall from scratch usually fixes this issue. I will come back to this in a moment.

Let's talk about disabling devices for a second. My usual input is to disable hardware in the BIOS since the BIOS will also hide the device completely and thus Windows will not load any available driver for it nor will it consume any resources. In this particular case, however, you cannot do this. There is a bug in the BIOS. I tried to disable both Wireless and Bluetooth. What I found is that, while it does disable both Wireless and Bluetooth access and it does fully hide the Bluetooth device, it does not hide the Wireless device. I find that Windows has the driver loaded and it is still consuming resources. You cannot use it, since it is disabled, but it is still there and consuming resources.

Ok, so, since this bug exists in the JY BIOS (I have reported this bug to the development team), we cannot avoid the issue during upgrade. We will have to do this the hard way:

  1. Download the latest Wireless and Bluetooth driver packages.
  2. Disconnect the NUC from the Internet. If using Ethernet, unplug the Ethernet cable. If using Wireless, disable it (powering off the Router for a few minutes is the simplest).
  3. Uninstall both the existing Wireless and Bluetooth driver packages.
  4. Reboot.
  5. Install the Bluetooth and then Wireless driver packages.
  6. Reboot.
  7. Reconnect the NUC to the Internet.
  8. Test.

Hope this helps,

...S

rgord1
Novice
181 Views

When you say "A (painful) manual uninstall of both the Wireless and Bluetooth drivers followed by a reinstall from scratch usually fixes this issue." are there instances where it does not?

My issue was with instability of the NUC when wireless was enabled. Would this symptom be apparent as a result of this wireless stack issue? If so, would this symptom be resolved on a successful reinstallation of wireless and bluetooth drivers?

Are we talking about two different issues here? I do not recall ever having tried to use the wireless capability of this NUC, although throughout installation and updating to current version of Windows 10 I never saw any errors reported. Not to say there weren't any. At that stage I was using an older wireless driver, and did not encounter any instability, although the NUC was not running for any length of time so may not have had time to exhibit instability.

The instability became apparent later when I was using the NUC more extensively, and I had by that time also updated the wireless and bluetooth drivers to current versions.

I tried a fresh installation of Windows 10 1803 to rule out the possibility that the issue was due to an update to1803, and still encountered the instability. After discovering that the issue was resolved by disabling all wireless adapters, I entertained the possibility that the instability might be due to the more recent wireless drivers, but never tested it because I had no need for wireless capability and was reluctant to meddle further with a device that was now running stably.

If I were an IT tech responsible for maintaining these NUCs then I would definitely investigate further. However I am but a humble user that was thankful I did not need to RMA the NUC, and am happy to let sleeping dogs lie.

PeterNUC
New Contributor I
181 Views

In Raymond's case the BIOS seem to be functioning properly. At least, there are no explicit indications that it is malfunctioning. In my case something is wrong with the BIOS. So I guess, I need to focus on fixing the BIOS first. Anyway, I disabled WiFi in Windows after the last hang, just to try it.

Peter

SChau10
New Contributor II
181 Views

I'm starting to wonder if the NUCs can properly support memory modules that carry Intel XMP 2.0 profiles, such as Crucial Ballistix Sport.

I recently picked up a used NUC5i5MYHE with a pair of Crucial Ballistix Sport 4GB DDR3L 1866MHz SODIMMs. This NUC got so messed up I had to replace the memory with Samsung 4GB DDR3L 1600MHz SODIMMs then invoke a BIOS recovery. I nearly thought the NUC was trashed as it just kept blinking the power LED indicating memory error and couldn't be reset with conventional methods.

It almost looks like the BIOS in some of these NUCs are mis-detecting the Intel XMP 2.0 timing set in the modules as a "standard" timing set and trying to use it. Assuming most NUC platforms do not support Intel XMP 2.0, the task for their BIOS is to use one of the "non-XMP" timing sets reported by the module SPD and ignore the XMP 2.0 timing set. Failure to do so can lead to system instability or even unbootable unit like what happened to my NUC5i5MYHE.

In contrast, my NUC7PJYH has been rock solid for several weeks. I run Win10 in headless mode, with just power feed and LAN cable attached. No BSODs as far as I can tell.

Memory: 2 x Samsung M471A5244CB0-CRC 4GB 1Rx16 PC4-2400T-SC0-11 SODIMM

Storage: Samsung 860 PRO 256GB SATA 2.5" SSD

For NUCs exhibiting persistent stability issues (BSODs, hangs, etc.) it may be worth substituting in "standard" memory (i.e. no Intel XMP 2.0 support) to compare. I'm somewhat partial to Samsung memory as these have never failed me in any way.

It is also possible for Windows OS files to suffer silent corruption when system is running unstable with improper memory timings, so re-installing OS may be necessary after the NUC regains stability with memory modules featuring "standard" memory timings.

n_scott_pearson
Super User Retired Employee
64 Views

[To Ray]

Yes, the symptoms were rock solid, then Windows update, then not-so rock solid. Microsoft screwed this up in the transition from 1709 to 1804 (and admitted it) but, since Microsoft continues to NOT learn from their mistakes, I am presuming that the same thing will likely be occurring going from 1804 to 1809.

I say 'usually' because, invariably, people have issues following instructions and screw things up. There are cases where, for example, they ~forget~ to disable internet access (or simply refused to do so because it is ~difficult~ (read: sickening whiny emphasis on those word)) and Windows Update sneaks in there and reinstalls the screwed up portion. There are other cases where they install the Wireless module before the Bluetooth module and this sometimes doesn't work (I have never understood why this happens; I do know that, even though the Bluetooth module is accessed via USB, the transmitters are handled via PCIe so the Bluetooth module is actually installing some of the same drivers that the Wireless package is installing (perhaps it is a versioning thing?)). Anyway, you need to be able to get both the Bluetooth and Wireless driver packages removed, the system rebooted and then the two drivers, Bluetooth then Wireless, installed from scratch without interference from Windows Update.

I also say 'usually' because you have established only a causal relationship between Wireless/Bluetooth and your system stability. It is entirely possible that the issue has nothing to do with the two other than, for example, the changes in timing having the services enabled and running. I have noticed a few other things that this could be. For example, I have noticed there seems to be higher rates of issues related to Samsung 860 PRO, WD Black and Corsair Force HDDs that most others (but this may be them just sticking in my head more ).

[To Peter]

I presume you posted this before you figured out the issue with Secure Boot. Yea, I agree, making Secure Boot the default is painful for a lot of reasons, but we *are* talking about a security improvement and this *is* important. Of course, I should have thought of this in our discussions, so shame on me too...

[To Sam]

If you have 1866 SODIMMs, then the default is always going to be to run at 1866. This is not a NUC thing, this is an industry thing. Every system out there tries to do this. Now, the NUC BIOS has support for backing off to lower settings if the default settings do not work -- and this should have addressed your issue. The problem occurs when the settings appear to work and then later on the system suffers resets or BSODs. This is the classic incompatibility case. You, as the owner, are expected to understand this, realize you chose the wrong memory and get it replaced. You are purchasing a kit-level product, after all.

At the same time, in the past, I have purposefully purchased Crucial Ballistix Sport or Tracer DIMMs -- even though I know of (and have fought with) all sorts of issues with their usage (and especially their inability to actually run at their rated speeds) -- because they are the only DIMMs out there that come with TSOD (Thermal Sensor on DIMM) support and I absolutely love being able to monitor actual DIMM temperatures. Unfortunately, they are not supporting TSOD in any of their SODIMM products, so I steer well clear of these products -- but don't get me wrong; I still almost-exclusively purchase Crucial memory; I just don't purchase from the Ballistix line.

...S

Reply