NUC7i5DNHE and wd.sys BSOD, microsoft watchdog timer

[SAljoshin]

Hello,

I have here brand new NUC7i5DNHE. Latest BIOS installed v0040. If I install Windows 10 using WDS - after copying image it gives me BSOD with wd.sys.

As far as i investigated - it is related to Microsoft watchdog timer. But I have no such device in device manager. (watchdog disabled in BIOS) And still after 20 minutes of burn-in testing it gives BSOD with another description.

If I make Windows 7 clean install - it gives me also wd.sys BSOD, but I can see Microsoft watchdog timer with yellow mark in device manager.

How to solve it?

Regards,

Sergei

[idata]

Hello SergeiAljoshinI understand that you are having Blue screen issues with your Intel® NUC Kit NUC7i5DNHE.Based on the brief description of your case, we will need to try a couple of things in order to isolate the issue.The WD.sys error could be caused by several things such as registry damage (OS level), corrupted or infected files, hard drive damage, ram incompatibility or even corrupted BIOS.First I would like you to recover the BIOS, I understand that you already have the latest one, however I would like to discard a BIOS corruption, and you can follow any of these methods:https://www.intel.com/content/www/us/en/support/articles/000005532/mini-pcs.html https://www.intel.com/content/www/us/en/support/articles/000005532/mini-pcs.htmlHere you will find the latest BIOS:https://downloadcenter.intel.com/download/27626/NUCs-BIOS-Update-DNKBLi5v-86A-?product=122488 https://downloadcenter.intel.com/download/27626/NUCs-BIOS-Update-DNKBLi5v-86A-?product=122488Only if it is possible to do it without going BSOD, please provide me only with the .txt file that the System Support Utility will generate. To attach a file, you must click the "Attach" option on the bottom right-hand corner of the response box.https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows- https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-As well let us know, is there any specific stop code/ error code that you can shared with us?As well please provide us with your RAM model and Drive model Number. I really hope to hear from you soon.Best Regards, Diego S.

[SAljoshin]

Hello Diego!

Thank you very much for quick reply!

- I tried to recover BIOS-same story.

-please find a a report .txt in attachment.

-moreover, I found that this NUC reduce CPU speed as well.Changing power modes didn't change anything. Please take a look at screenshot attached.

Machine gives BSOD with error "wd.sys" and "system thread exception not handled", no stop code.

Most interesting that after BSOD, it resets and try to boot to network and not able to boot from SSD. I have to Ctrl+Alt+Del and then it starts to boot.

Rolling back BIOS to 39 version didn't help.

I have Samsung SSD (SATA) and 8 Kingston RAM 8 GB 2400 MHz. Nothing special.

Regards,

Sergei

[idata]

Hello SergeiAljoshin,

Thank you for your response.Based on the report and your brief description at the moment we do not really think that the actual BIOS has something to do with your issue.According to the boot behavior of your machine, it seems that the unit is not recognizing your SSD when booting, that's why it goes to LAN boot unless you force it to look for the SSD itself.We would like to diagnose and test your SSD and RAM through the following tools:Samsung* SSD tool http://www.samsung.com/semiconductor/minisite/ssd/download/tools/Windows Memory Check: https://technet.microsoft.com/en-us/library/ff700221.aspxThe content on the above sites is not controlled by Intel. This information is offered for your convenience and should not be viewed as an endorsement by Intel for the merchants or services offered there.We hope to hear from you soon.Best Regards, Diego S.

[idata]

Hello SergeiAljoshin,

I was checking your case, and I just wanted to know if there is anything else that we can do for you at this time.

Please do not hesitate on replying back if you need more assistance.

Best Regards,

Diego S.

[SAljoshin]

We changed SSD and problem gone.

Despite the fact all SSD test were passed changing it, solved the problem.

Thank you for support.

[n_scott_pearson]

You might want to take a moment and try putting that other SSD back in to see if the issue was (just) placement in the socket...

...S