BSoD issue on NUC8i7BEH (Thunderbolt related)

[MHo10]

Hi,

I've got one of the 8th Gen NUC Kit NUC8i7BEH and having the latest version of the BIOS 0083.

Once the BIOS had been updated I am no longer to get in to the Windows again and a BSoD screen appears and reporting as "DRIVER VERIFIER DMA VIOLATION". This issues happens when starting up Windows and Type-C device was plugged in.

The driver installed was the latest version already from the Intel Download website.

The Thunderbolt controller was enabled which is the default value of the BIOS release.

While in the BIOS 0081 it did not reproduce this issue above, as I cannot downgrade to 0081 once 0083 had been flashed.

[Esteban_D_Intel]

Hello MHo10,

Thank you for posting on the Intel® communities.  

I understand that you are experiencing some BSOD after the BIOS upgrade.

To better assist you I would like to gather the following information:

• Please provide your operating system version.
• How was the upgrade of the BIOS made? Did you use the Intel® Driver & Support Assistant?
• What is the device connected via type-c? Please provided model.
• Does the BSOD appear if the device is not connected while booting?

Please run the following tool and attach the reports generated.  

Intel® System Support Utility (Intel® SSU)  Download link  

1. Open the application and click on "Scan" to see the system and device information.
2. By default, Intel® SSU will take you to the "Summary View".  
3. Click on the menu where it says "Summary" to change to "Detailed View".  
4. To save your scan, click on "Next", then "Save".  

Esteban D.

Intel Technical Support Technician  

[MHo10]

Hi Esteban,

The Operation System used was Windows 10 Pro 1909. And updated via the Express BIOS update installer (BECFL357.86A.0083.EB.msi). The Type-C connected device was a HDMI monitor and its model was LG 24BK550Y-B via USB Type-C to HDMI cable. The BSoD did not appear when the monitor was disconnected, it's only happens when it is connected and Windows is being starting up.

The Diagnostics log file had been attached so it's easier to see what's the configurations are in there.

[Esteban_D_Intel]

Hello Mho,

Thank you so much for the additional information provided.

I was reviewing the report attached and I noticed that in terms of software/drivers your NUC is up to date.

I would like to confirm the following information:

1. Please provide the model or part number of the cable that you are using.
2. Do you get any BSOD if another device is connected via USB-C?
3. The thunderbolt controller is enabled in BIOS, correct?
4. What is the version of your Thunderbolt firmware

I would recommend checking that the Thunderbolt™  for your NUC is up to date using the following link: https://downloadcenter.intel.com/download/28735/Thunderbolt-3-DCH-Driver-for-Windows-10-for-Intel-NUC?product=126140

Additionally, you mentioned that your OS is in version 1909, can you please check for Windows* updates and if possible upgrade your OS to the latest version.

Please let me know how it goes.

Esteban D.

Intel Technical Support Technician 

[MHo10]

Hi Esteban,

The model and the cable was the ALogic USB-C to HDMI cable (ELUCHD-02RBLK).

I've tried an HP USB-C dock to connect to the NUC and it still have the same BSoD appears when it's connected on startup of the Windows. (https://support.hp.com/au-en/product/hp-usb-c-dock/14039866)

The Thunderbolt Option is enabled in BIOS. (It can get into Windows when this option is disabled and the device is connected to the USB-C port, it only comes up that error then the option in BIOS is enabled).

I cannot see what's the firmware is being used for that device as it does not appear either in the device manager and in apps and features setting screen.

Here's another diagnostics log file after the Windows had upgraded to 2004, and those results are be the same as 1909 before.

[IntelSupport]

Hello MHo10,

Thank you for your response and the information provided.

I would think that this behavior could be related to the compatibility of the components that we are using along the NUC.

In case you are interested I would like to share with you the Compatible products for Intel® NUC Kit NUC8i7BEH.

However, I understand that the device was working fine with the previous BIOS version. For testing purposes I would recommend rolling back to version 0081 and then check results.

In case you would like to give it a try, please follow the steps below:

1.     Download the Recovery BIOS (.BIO) file from the following link. 

2.     Copy the recovery file (*.BIO) to a USB device. 

3.     Shut down the computer and unplug the AC power adapter. 

4.     Open the chassis and remove the BIOS security jumper. Please check the Technical product specifications of the unit to see where the jumper is located.

5.     Plug the USB device into a USB port of the target computer and turn it on. 

6.     Wait 2–5 minutes for the recovery process to complete. 

7.     The computer turns off when the recovery process is complete, or it prompts you to turn it off. 

8.     Remove the USB device. 

9.     Replace the BIOS security jumper. 

10. Close the chassis. 

11. Restart the computer. 

Please let me know what the outcome is. 

Esteban D. 

Intel Technical Support Technician  

[MHo10 · Accepted solution]

Hi Esteban,

Unfortunately I've tried to rollback the BIOS to 0081 and the BSoD still in there.

However I've tried to clean re-install Windows again and reinstalled the latest driver (tried both 2004 and 1909), and seems works fine for that (with Thunderbolt option enabled in the BIOS). Also tried to update to the 0083 BIOS and it's working fine.

It's looks likely there's some sort of the driver conflicts with the existing drivers for the Windows installation to causing the Driver Verifier BSoD happens.

Thanks for your help anyway, if there's anything update regarding to this one I will be add that into the thread, just hopefully this won't happens again so far.

[Esteban_D_Intel]

Hello MHo10,

Thank you so much for the update.

I am glad to know that the unit is working fine after the clean installation of the operating system.

Hopefully this behavior won’t occur again, If you need any additional information, please submit a new question as this thread will no longer being monitored

Esteban D.

Intel Technical Support Technician  

[CropCorn]

Same issue since last bios/driver software download, cant find same file as described below comments, uninstall reinstall delete legacy, new latest  tried all.... if it does work the screen is blank until i blindly windows login, (space bar type password) and screen comes alive but, yes there is a but... looks like a second screen because no icons, no popup programs will show up. While operating went from HDMI cable to monitor via the NUC8I7BEH, thunderbolt cable connected to external graphic card to removing HDMI from NUC and plugging into external graphic card and poof nothing.  Had no issue prior to earlier last week when driver updates were installed from Intel.   Yes no other software was downloaded, no other updates, and how do I play World of Tanks without a video card its like mindcraft graphics 

Need a patch because you messed something up

[hubick]

My Samssung X5 SSD (Alpine Ridge) works fine on my NUC8i7HVK (Fresh install of Win 10 20H2), but plugging in my new LaCie Rugged Pro SSD (Titan Ridge) yields this same DRIVER_VERIFIER_DMA_VIOLATION BSOD.

Searching for this error and "thunderbolt" yields a long thread on the Dell forum of a similar issue, where investigation there indicates it was due to the ASMedia USB driver. My NUC also has an ASMedia USB port, but seems to be running the Microsoft driver though, so I'm not sure if it's the same problem.

[CropCorn]

I think I found my solution to the issue, its an older thread but followed it, deleted the files, and downloaded the correct thunderbolt driver. this after completely reinstalling windows which didn't help just made for a long day reloading windows which then deleted my word, excel, powerpoint.....and loaded the Onedrive and online dumbdowned Office option. All other help from previous threads didnt help, the toast file still couldnt be found, so the below thread worked for me, yep the DCH issue looks to be a common issue.  

plugable.com/2019/04/09/thunderbolt-application-not-in-use-anymore-error-on-windows-check-your-driver-types-and-versions/