- Joined
- Jan 27, 2015
- Messages
- 457 (0.12/day)
| System Name | Marmo / Kanon |
|---|---|
| Processor | Intel Core i7 9700K / AMD Ryzen 7 5800X |
| Motherboard | Gigabyte Z390 Aorus Pro WiFi / X570S Aorus Pro AX |
| Cooling | Noctua NH-U12S x 2 |
| Memory | Corsair Vengeance 32GB 2666-C16 / 32GB 3200-C16 |
| Video Card(s) | KFA2 RTX3070 Ti / Asus TUF RX 6800XT OC |
| Storage | Samsung 970 EVO+ 1TB, 860 EVO 1TB / Samsung 970 Pro 1TB, 970 EVO+ 1TB |
| Display(s) | Dell AW2521HFA / U2715H |
| Case | Fractal Design Focus G / Pop Air RGB |
| Audio Device(s) | Onboard / Creative SB ZxR |
| Power Supply | SeaSonic Focus GX 650W / PX 750W |
| Mouse | Logitech MX310 / G1 |
| Keyboard | Logitech G413 / G513 |
| Software | Win 11 Ent |
My neighbour's 10 years old PC crapped out last week and he's asked me to help him build a new one.
It's a very basic unit with i3 7100, Gigabyte B250M-D3H, 8GB DDR4-2400 and 1TB WD Black. We first flashed the BIOS to the latest version F9b which includes patches for IME and Meltdown/Spectre security issues. Then we proceeded to install Win10 Pro without any issue (Full UEFI install, BIOS set to Windows 8/10, CSM Support disabled). After the first boot, Windows Update sorted out most drivers except Intel RST and Realtek HD Audio. Instead the installation used the standard MS drivers for them (Standard AHCI Controller & High Definition Audio Device). We then downloaded the latest drivers from Gigabyte website. Since the boot problem we have happened before the Realtek driver was installed, we can take that out of the equation.
The Intel RST we've been trying to install is 15.9.0.1015. The installation itself went ok. But the subsequent reboot would always fail and Windows 10 would attempt to repair itself without success if Secure Boot was kept enabled in the BIOS. As soon as it was disabled, the PC would boot into Windows 10 successfully. When we restored the PC back to the point before Intel RST had been installed, it would boot up fine no matter whether Secure Boot was enabled or not. We've tried to re-download the same driver from Intel directly, but that didn't make any difference.
Can anyone please explain what could have been going on here? Is there any known issue with the latest Intel RST? If so, which version would you recommend that is compatible with Win10 ver. 1709? Although I can simply tell my neighbour to just keep using the standard MS AHCI driver, personally I would always prefer manufacturer specific drivers if they are available.
Thank you very much for your help.
It's a very basic unit with i3 7100, Gigabyte B250M-D3H, 8GB DDR4-2400 and 1TB WD Black. We first flashed the BIOS to the latest version F9b which includes patches for IME and Meltdown/Spectre security issues. Then we proceeded to install Win10 Pro without any issue (Full UEFI install, BIOS set to Windows 8/10, CSM Support disabled). After the first boot, Windows Update sorted out most drivers except Intel RST and Realtek HD Audio. Instead the installation used the standard MS drivers for them (Standard AHCI Controller & High Definition Audio Device). We then downloaded the latest drivers from Gigabyte website. Since the boot problem we have happened before the Realtek driver was installed, we can take that out of the equation.
The Intel RST we've been trying to install is 15.9.0.1015. The installation itself went ok. But the subsequent reboot would always fail and Windows 10 would attempt to repair itself without success if Secure Boot was kept enabled in the BIOS. As soon as it was disabled, the PC would boot into Windows 10 successfully. When we restored the PC back to the point before Intel RST had been installed, it would boot up fine no matter whether Secure Boot was enabled or not. We've tried to re-download the same driver from Intel directly, but that didn't make any difference.
Can anyone please explain what could have been going on here? Is there any known issue with the latest Intel RST? If so, which version would you recommend that is compatible with Win10 ver. 1709? Although I can simply tell my neighbour to just keep using the standard MS AHCI driver, personally I would always prefer manufacturer specific drivers if they are available.
Thank you very much for your help.
Last edited:
