BSOD approx 10 min after Boot up; Wdf010000.sys

I have a custom pc build. Full install of Windows 10 64 1 week ago. Only issue during install was with the Gigabyte Z370 HD3 motherboard- network adapters would not be recognized by windows. Tried updating and downloading drivers from both Gigabyte and Intel (Driver is Intel I219-V) both current and older versions. Found an old Netgear Wireless N USB network adapter, which worked to get online; system performed without further incident for 1 week, but I wanted better speed and ordered both a current usb ethernet adapter and a usb wireless ac adapter. Installed the ethernet adapter, and it works and is properly recognized by Windows, but now after Windows bootup, I get a BSOD with error "System Thread Exception Not Handled" and failure Wdf010000.sys- this occurs whether I am using any applications or even logged into Windows, between 2 and 15 minutes after bootup. Any way to stop the BSOD and get properly working ethernet?

MoBo drivers for LAN are here and relatively fresh?

Z370 HD3 (rev. 1.0) | Motherboard - GIGABYTE Global

axe0;

Thank you for the reply. I want to be sure I understand: when you write new ethernet adapter, you are referring to the usb ethernet adapter and its driver, not to the onboard network adapter from the motherboard, correct?

axe0,

The USB device is a usb 3.0 gigabit adapter from amazonbasics, when I purchased it, the device was listed as being compatible with Windows 10. Driver is Asix AX88179 USB 3.0 to Gigabit network adapter. In Device Manager when I right click and go to Properties, it is listed as working properly, and if I go to Update Drivers, it lists current drivers as being best available. The device itself obviously works, as otherwise I could not get online to this forum. I am unfamiliar with Asix drivers in general, did not know they were that old.

An update:
After my original post, I went into Windows 10 device manager to double check for errors, and found the Intel Network Adapter driver listed, with a yellow error warning. It had not previously occurred to me for some reason that there might be a conflict between it and the Usb network adapter. I right clicked on the Intel driver, uninstalled and rebooted, then uninstalled it again when it was detected during boot up. Have not made any other changes; the system has now been up for nearly 2 hours without the BSOD error re-occurring.

Is it possible that the two drivers had a conflict that would generate that error?

Also, replying to Krzemien; I did download the current (version 23.2) driver for the onboard adapter and try to install. Driver registers, and is listed in Apps and Features, and the driver shows up in device manager, but with a yellow error warning. When I go to properties for it, I receive an error warning that properties cannot be displayed; then after a few seconds, the properties window does open, indicating: This device cannot start (Code 10) [Operation Failed] The requested operation was unsuccessful.

If I try to update the Intel driver via device manager, it lists the current 23.2 driver as being best available.

In any case, despite the adapter showing up in device manager (with warning) and in apps and features, it does not show up in Network connections. I have tried the 23.2 drivers from both Gigabyte and Intel sites, as well as from the Gigabyte DVD- same result. I have also tried 22.0 and 21.0 versions- again, same result, except that attempting to update them will give an update to the 23.2 version. The adapter simply never appears in Network connections.

Check this out?

Gigabyte z270 HD3 ethernet coneection - [Solved] - Motherboards

Since the BSOD error has not re-occurred, I will go ahead and use the pc normally and see what happens. I would like to keep the thread open for another day or two in case the error repeats, but for now it seems possible that a simple conflict between two network adapter drivers might have been the cause of the error.

If I get another BSOD, I will post again. Thanks,