(See below regarding why I posted this information)
Intel has removed the latest version of IRST, 11.5.0.1207, from their download pages. It has multiple issues including:
Memory leaks. Memory usage climbs slowly higher and higher for no good reason.
Some applications will BSOD when they are started when using this driver.
Windows will see the SATA interface as a SCSI controller with this driver, which is false.
The performance of this driver is below average.
There is nothing to be gained using this driver, so if you're using it, install an earlier version such as 11.2.0.1006, which now is the latest IRST driver Intel has available on their download pages. You don't need to uninstall it, and doing so will cause big problems if you have any RAID volumes on the Intel chipset. You can install an earlier version over 11.5, and you will see a warning displayed that you are installing an older driver. Just continue the installation and it will complete fine.
____________________________________________________________________________________________________________________________
The main reason I posted this here is because I was using this IRST driver, and when I started my favorite monitoring program, HWiNFO64, my PC BSOD, and rebooted. That was the first and only time I have ever had a problem like that with HWiNFO64. In reality, the problem was really not with HWiNFO64, but with this bug filled IRST driver. TBH, it is rare for Intel to release software that is as poor as this version is.
I then went to the HWiNFO forum, to see if anyone else had experienced this. I did see at least one thread that sounded like the same problem I had. The quick fix was to disable Drive Scanning, which worked. At the time in that thread, I think the author of HWiNFO was not 100% sure what was going on, or at least did not immediately blame Intel or attempt to pass the blame elsewhere. I'm not sure, but I think a fix was added to compensate for this problem.
It was only two days ago that I noticed Intel had removed this driver from their download pages. That confirmed IMO that the issue with HWiNFO64 was caused by that IRST driver all along.
I felt it was important to let everyone know what really happened in this situation, and to pass it on to the author of HWiNFO, in case he was not aware of it.
Intel has removed the latest version of IRST, 11.5.0.1207, from their download pages. It has multiple issues including:
Memory leaks. Memory usage climbs slowly higher and higher for no good reason.
Some applications will BSOD when they are started when using this driver.
Windows will see the SATA interface as a SCSI controller with this driver, which is false.
The performance of this driver is below average.
There is nothing to be gained using this driver, so if you're using it, install an earlier version such as 11.2.0.1006, which now is the latest IRST driver Intel has available on their download pages. You don't need to uninstall it, and doing so will cause big problems if you have any RAID volumes on the Intel chipset. You can install an earlier version over 11.5, and you will see a warning displayed that you are installing an older driver. Just continue the installation and it will complete fine.
____________________________________________________________________________________________________________________________
The main reason I posted this here is because I was using this IRST driver, and when I started my favorite monitoring program, HWiNFO64, my PC BSOD, and rebooted. That was the first and only time I have ever had a problem like that with HWiNFO64. In reality, the problem was really not with HWiNFO64, but with this bug filled IRST driver. TBH, it is rare for Intel to release software that is as poor as this version is.
I then went to the HWiNFO forum, to see if anyone else had experienced this. I did see at least one thread that sounded like the same problem I had. The quick fix was to disable Drive Scanning, which worked. At the time in that thread, I think the author of HWiNFO was not 100% sure what was going on, or at least did not immediately blame Intel or attempt to pass the blame elsewhere. I'm not sure, but I think a fix was added to compensate for this problem.
It was only two days ago that I noticed Intel had removed this driver from their download pages. That confirmed IMO that the issue with HWiNFO64 was caused by that IRST driver all along.
I felt it was important to let everyone know what really happened in this situation, and to pass it on to the author of HWiNFO, in case he was not aware of it.