Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
1,047 Views

machine_check_exception NUC6i5SYK keeps on rebooting

Jump to solution

While I was using it, my 6i5SYK shut down after a BSOD and the machine_check_exception error.

From that moment on, it keeps on rebooting displaying that error.

Tried a different SSD as well as RAM. Nothing changed.

Tried its SSD and RAM on an identical NUC and they work fine.

Tried to update BIOS, but after pressing F7 on startup the USB with .bio doesn't show up in the list. Tried two USB.

Tried removing the BIOS jumper but after pressing F7 it says: "Please turn off power and reinstall the BIOS Security Jumper....".

Any suggestions?

EDIT: BIOS update worked fine using FAT32 formatted USB.

0 Kudos

Accepted Solutions
Highlighted
Valued Contributor I
47 Views

Qualifies for RMA, don't waste your time. Don't bother trying to fix, this is (very very) probably hardware related.

What BIOS were you on when the MCE occurred? If lesser than 0042, your NUC can't be revived by updating the BIOS. Or any other way for that matter.

Basically you won't be able to boot an OS, be it windows or linux or even a LiveCD.

If BIOS was 0042 or higher, this shouldn't have happened and hence reason for RMA also.

View solution in original post

6 Replies
Highlighted
Novice
47 Views

If you set the BIOS to defaults, does it resolve the problem?

Is your USB formatted as FAT32? I dont think UEFI works with NTFS or FAT16 or exFAT formatted USB drives.

Highlighted
Beginner
47 Views

Restored the defaults settings (I had never changed anything in the BIOS) but still the error.

Followed your advice and formatted in FAT32 (previously they were exFAT), the BIOS update worked fine, but the machine_check_exception error persists.

Restored the default settings, nothing changed.

I'd avoid to open an RMA, even if it's still on warranty.

0 Kudos
Highlighted
Valued Contributor I
48 Views

Qualifies for RMA, don't waste your time. Don't bother trying to fix, this is (very very) probably hardware related.

What BIOS were you on when the MCE occurred? If lesser than 0042, your NUC can't be revived by updating the BIOS. Or any other way for that matter.

Basically you won't be able to boot an OS, be it windows or linux or even a LiveCD.

If BIOS was 0042 or higher, this shouldn't have happened and hence reason for RMA also.

View solution in original post

Highlighted
Beginner
47 Views

It was equipped with v0028.

Thank you for these updates, I'll submit an RMA and waiting for a replacement.

Do you suggest to update the BIOS of every NUC running with lesser than 0042?

However, your reply clarifies what to do in this case, thank you very much again.

0 Kudos
Highlighted
Valued Contributor I
47 Views

hi cpx1,

you asked: "Do you suggest to update the BIOS of every NUC running with lesser than 0042?"

yes.

Once Intel acknowledged the issue (something with the overload of voltage regulation circuitry) and finally released a fix (BIOS 0042) they urged people to update and they updated all the machines in stock with 0042 and put a blue dot sticker on the updated, hence "safe" machines.

some links:

/message/390260# 390260?sr=search&searchId=f801a8cc-ca0f-4430-ad52-ff2fa2fc564a&searchIndex=0 https://communities.intel.com/message/390260# 390260?sr=search&searchId=f801a8cc-ca0f-4430-ad52-ff2fa2fc564a&searchIndex=…

0 Kudos
Highlighted
Community Manager
47 Views

Hello, cpx1:

I am following up your case, and noticed that the suggestions in your thread helped you. So, please let me know if you submitted the request for the RMA.

Regards,

Amy.

0 Kudos