Freezing NUC I7?!

[Qwar]

Hi,

I ha a sff NUC, NUC8I7BEH2, that until this weekend have been running Win10-1903 without any problems at all. During the last few days I've been prompted to upgrade to 20H2 which I finally did now. The formal update itself worked well, nofreeze or BSOD or similar... but... When restarting again the computer freezed after a couple of minutes... Strange... Hard reset by pushing button until stop... Repeated several times... Same state... Again again...

Finally I decided that there myst have been some problem with the installation and reinstalled 1903 and again updated to 20H2... Same problem... Asked a friend to borrow his brand new version of 20H2... clean installation again... Same problem... Immediately, before even installing anything at all... Perhaps hardware problem? Tookout PCIe-m.2 ssd from the computer and installed an old 2,5' instead... Took a while to install ... worked little longer... I almost thought it would work... but no... freezed again and again... Took out all peripherials and put in only another wired mouse and keyboard... Same again... Reinstalled 1903... on both 2.5' and m.2 ,,, same on both now... immediately again... ntg works...Updated BIOS, another mouse, another keyboard, new installation without anything connected... Blah! Same stuff...

finally I'm now in a state where it doesn't really matter what I do.. .It freezes within about 1-10 min after start... varies a bit...

Attached are error dumps and specs!

Thanks for any sugestions!

//Q

[LeonWaksman]

In order to get better information about your system, please download the Intel System Support Utility (SSU). Run the SSU scan and save the results. The .txt file with the results please attach to your post.  Please, run this SSU Report on the drive with the version 20H2, you have updated.

Leon

[Qwar]

Thanks for your kind efforts to help me... Attached is the config file //Q

[LeonWaksman]

HI @Qwar 

1. In the SSU report I can see that although you have the latest BIOS, it is working in Legacy mode, instead UEFI mode. In order to working in UEFI mode, your drive should be partitioned with GPT partition, rather than MBR partition  (could be that this is the current status, I can't verify). Please read How to convert MBR to GPT drive to switch BIOS to UEFI on Windows 10 to see how to verify that your drive has GPT partition and if not, how to convert MBR partition to GPT using mbr2gpt utility.

2. In addition, please enter BIOS settings and reset it to default settings: click on F2 during boot, when you see the Intel NUC logo, click on F9 ("Y") and then F10 ("Y"). Your NUC will reboot into Windows in UEFI mode.

3. Next please download and install the Chipset Device Software and Management Engine Driver. Reboot your NUC.

4. Now, Download and install Intel Driver & Support Assistant. Run IDSA and check if there are other drivers needed installation/update.

5. Check now how your NUC works. 

6. If NUC still crashes, I suggest that you again perform BIOS update, but this time using BIOS Recovery by Power Button Menu. After finishing the recovery, reset again BIOS to default settings (see para. 2 above).

Leon

[Qwar]

Thanks a lot for your kind help. I'll look into it tomorrow and will rerurn with info of result !. Late evening now in Sweden! Take care... //Q

[LeonWaksman]

In case that the steps detailed in my post above will not help, please attach an image of Disk Management and new SSU report.

Regards

Leon

[Qwar]

Hi,

I've done all you suggested. The disk was GPT already. Bios resetted. Chipset, Management & drivers updated. Done the "bios using button". Unfortunately still the same....

Attached are both an updated config and a snapshot of the diskconfiguration. Once again thanks a lot for your help //Q

[LeonWaksman]

Hi @Qwar 

In the latest SSU report I can see that although you have reset BIOS to default settings, the UEFI boot in BIOS is still disabled.

Please enter BIOS settings  Advanced > Boot > Boot Priority and check the UEFI Boot option.  Then click on F10 to save settings.

What is strange to me that now you have the Secure Boot enabled, but the Boot mode is still Legacy Boot. Enabling Secure Boot should enable UEFI boot and disable Legacy Boot. However, for some reason it didn't happened in your system (according to SSU report). So, please check this and enable the UEFI Boot.

Did you updated BIOS using BIOS Recovery by Power Button Menu?

Leon

[Qwar]

Hi,

I did "Bios via Power Button" and updated again. Now entering Bios and can confirm that UEFI is selected. See attached pics. Now resetted and loaded defaults again... restart... same problem! //Q

[LeonWaksman · Accepted solution]

Hi @Qwar 

Lets check your hardware and Windows installation.

1. Download and install Kingston® SSD Manager With this application, you will be able to monitor your SSD heath and check/update the firmware. Now the firmware you have installed is version S5Z42105, while the latest version is S5Z42109. So, better update the firmware.

2. The crash can be caused also by failed RAM. So, please try to run only with one SO DIMM stick at time (check in each slot).

3. Since there is a little chance that this is caused by hardware failure (the problem started after Windows update), I will consider to repair Windows installation with an in Place Upgrade. Start in Step 6, using Media Creation Tool. Your data and application will not be affected.

Leon

[Qwar]

Hi again!.

Downloaded and updated FW for the SSD... Wiped windows installation again and did a fresh re-installation again... ! Same thing!!

But just before throwing the machine out I also did the memory trick and took out both SO DIMMs and reinserted just one of then in the socket where it didn't sat before....... And TADA! It suddenly works flawless!  Strange... Now inserted the second SO DIMM in the other socket and.... It still works!!! So... right now I'm up'n running with both SO DIMMs in shifted socket... All previously performed stuff and updates seems to work.! I s it probable that the sole error from the beginning was something with the SO DIMMs? That suddenly was solved by just switching places?

None the less.. The biggest of thanks to you Leon for helping the noob out. Ever so greatful for your time and efforts.!

Have a really nice weekend for now!! //Q

[LeonWaksman]

Enjoy your NUC. I was glad to help.

Leon

[n_scott_pearson]

It may have been the disconnection and reconnection of power or it may have been the reseating of the SODIMMs. Regardless, cross your fingers and hope it continues. ;^)
...S