Intel® NUCs
Support for Intel® NUC products
Do you have improvements you would like us to make on this community site? If so, we would love to hear your feedback! Click here for an 8 question survey. Thanks!

11305 Discussions

Intel NUC8I5BEH and BIOS v. 83 & 85 - BSoD - Driver Verifier Dma Violation



We have issues with NUCs especially when wake up from Sleep. I tried to follow this guide:

So I took my NUC and, first as suggested, tried to update the BIOS which was on version 78. I applied the update to version 85 and then, after a successful update, I have a BSOD while Windows is boot with the following error: Driver Verifier Dma Violation.

I tried to install v78 back but there is no way to do it directly. So I downgrade to v83 (ok), then I tried v83 to 81 but I have a message which says that downgrade is not possible.

I have done some searches and the problem is similar to these cases:

Except that I didn't have to disable the Thunderbolt controller but the "USB Legacy" to have our computer working again !

Even if "USB Legacy" is not really necessary nowadays, I would like to know why the BSoD occurs? Is there a way to fix this?

FYI, we're using Windows 10 Pro v1803 for the moment and I had the problem with 2 different Intel NUCs after upgradingthe BIOS to version 85 (problem is also present on v83).

There are lots of problem with Intel NUCs so far... If the workarounds bring new bugs, these are not really workarounds !

Kind Regards,




0 Kudos
6 Replies
Super User Retired Employee

I believe the issue is your version of Windows 10. Intel typically validates on and supports drivers on the current version and three versions back. This means 20H2, 20H1, 1909 and 1904 are covered. 1809 and 1803 are, I believe, problematic and you need to upgrade to a newer version.
Hope this helps,


Hello Scott,

I will try to do a test when an up-to-date version of Windows 10.

I did a mistake in the first link above, the correct URL is:

On the two links, problem seems to happen with Windows Pro 1909... According to what you said, you shouldn't be a problem on this version.



Super User Retired Employee

Don't go by what you see in any other conversation. Every person's issue is different, different hardware, different drivers, different installation order, etc. Let's attack your problem methodically.

We know that the Windows 10 versions are chock full of bug fixes, closures for security vulnerabilities, etc. Sticking with one release - especially one that Microsoft has on the verge of dropping support for - you eventually end up with exposed issues rioght and left. Thus, IMHO, upgrading is a good thing regardless (even if Microsoft *is* experimenting on us). If you are leery of the bleeding edge (I have lots of scars from being there), you can always stop one major update short of the latest (i.e. at 2004) and then upgrade when things are better settled.



Hello, I agree with you.

I will proceed to update to Windows 10 20H2 next week (I didn't have the computer next to me for the moment) and I will keep you in touch.




Hello guys,

As promised: I tried the update to Windows 10 Pro v20H2 and the problem disappeared (both with "USB Legacy enabled or not).

I tried a rollback afterwards and then the problem occurred again with "USB Legacy" enabled.

Is there any other solution than migrate to Windows 10 v20H2? It's not a good moment to do this during the COVID crisis in our company.

If not, we will find a workaround for our initial issue: NUC which is waking up from sleep state.I hope Intel will fix this one day...



Thank you very much for the information and explanation, I had a similar problem, and my 8th Gen Intel NUC was running on the 0089 BIOS version. I did not see this BSOD happen on BIOS 0073. After reading thru the whole story above, I had managed to get the system (Windows 10 IOT 2019 LTSC - 1809) load into Windows and run as many possible windows updates as the system can get. Once after the windows update, I noticed the system is able to load into windows normally and so far no BSOD is appearing, believe that the issue will not appear again.