Windows 10 WHQL RIVBE Drivers + BIOS (NVME Support & Spectre/Meltdown Mitigation)

[SparkyBoy006]

4/28/19:

Updated Drivers:
-Asmedia_USB3_1.16.56.1
-Intel_Chipset_10.1.17969.8134
-Intel_LAN_23.5.2
-Intel_RST_Drivers_&_Software_Set_v17.2.6.1027 (Install when SATA is set to RAID mode)
-Intel_RSTe_5.5.0.2012 (Install when SATA is set to AHCI mode)
-Realtek_HDAudio_8688

Updated BIOS:
-CPU Microcode 306E4 IVB-E - 42E (3-14-2019)

Updated Utilities:
-ASUS_AI_Suite3_WIN10_V3.00.51

WARNING: Per Intel instructions, make sure to disable Bitlocker (if you have it enabled) before flashing BIOS with CPU Microcode update! (You can safely re-enable after flashing)

Download the Latest Windows 10 WHQL RIVBE Driver/BIOS/Utility Pack HERE
MD5: d4ae2b6e95da6eacffab9828bf3a70a6
Read the included "ReadMe" files for important instructions and notes!!

--------------------------------------------------------------------------------------------------

Initial Release 07/29/15
Change History: Read the included "ReadMe" file for complete history of releases.

[NoLife]

sgrundy wrote:
Can't say for sure but I would assume no. For example, I think the formula has DIMM restrictions that the black edition doesn't.

ok,thanks

[Snakeyes]

I presume/hope that these drivers will be compatible with the "nonblack" RIVE?

[SparkyBoy006]

Snakeyes wrote:
I presume/hope that these drivers will be compatible with the "nonblack" RIVE?

They sure are Snakeyes. The reason for being a RIVBE driver pack is because that's what the pack was made for. EffortLess and I both have the RIVBE. Just skip install for the Wifi driver and the Bluetooth driver as I think both of those are only on the black RIVE (if I'm not mistaken).

All the other components are identical and use the same drivers.

[Snakeyes]

Thanks, I owe you one pal.

[chemcup]

Updating to Intel_Chipset_10.1.2.9 cause bsod 0x00000139 ntoskrnl.exe when connecting external usb 3 drive

[SparkyBoy006]

chemcup wrote:
Updating to Intel_Chipset_10.1.2.9 cause bsod 0x00000139 ntoskrnl.exe when connecting external usb 3 drive

Is it instant and every time the drive is connected? Will submit feedback to Intel. Thank you. For reference, we're using external Samsung USB 3 drives with no issues. What model of USB 3 drive do you have?

[chemcup]

SparkyBoy006 wrote:
Is it instant and every time the drive is connected? Will submit feedback to Intel. Thank you. For reference, we're using external Samsung USB 3 drives with no issues. What model of USB 3 drive do you have?

I am using Samsung SSD 840 EVO 500GB in external USB3 RaidSonic Icy Box IB-253U3. The BSOD happened instantly when connecting the usb3 drive.
I went back to the Intel Chipset 10.1.2.8 and no BSOD.

[SparkyBoy006]

What's strange is that chipset drivers aren't really drivers. They're null drivers... meaning they just label the devices in device manager with a name. When you install them, they "disconnect" the device to rebrand it with a new null driver date and time and name. 10.1.2.8 should behave exactly the same as 10.1.2.9 unless it's confused and is rebranding your real external hard drive driver with a null one. I'd watch for that in the future with chipset drivers to see if that's the case. I will report it anyway. Thank you for yor feedback.

[chemcup]

Any driver for the unknown device hardware id root\NetTap6?

[zoomee]

chemcup wrote:
Any driver for the unknown device hardware id root\NetTap6?

I've got the same issue with mine from a clean build - think its related to the Intel NIC.
Tried installing all the advanced driver stuff from the intel driver but no joy.

Searching around some users say the issue resolves itself when upgrading to a different build of windows 10, unfortunately thats no comfort when we're on the final build. Guess it needs something from microsoft to sort it?