Windows 10: boot log shows attempts to load AMD files when machine is all intel

Trying to solve a different issue I looked at the bootlog and found it attempts to load AMD drivers - when I have an all-Intel machine.

I don't suppose it matters as they fail, but it annoys me and must take up at least a few milliseconds of my life each time it boots.

I also wonder if I then get updates of AMD files which I do not need.

I would welcome any suggestions.

Thanks,

Tony

:)

 

How to use Intel Rapid Storage Tech software with Kyhi boot rescue

When using the Kyhi boot if the Intel RST acceleration can be disabled the 750 GB drive in RAID 0 can then be moved to any computer and the files read.

Intel was contacted regarding the Intel RST and they indicated that the Intel RST is a HP driver.
HP was contacted regarding the failure to install the driver(s) and they indicated that they troubleshoot hardware and not software.

When using Kyhi boot rescue does the classification as to whether it is software or a driver impact the ability to install?

Are there any other steps to get the software or drive installed when using Kyhi boot rescue?

There was an error log for the Intel RST.
Amazingly there was no troubleshooting support of the log available at Intel or HP.



SIW2 the steps that were listed in the post #6 I was not able to interpret.
Please use alternative words and steps so that they can be followed by a beginner.

 

Saves log files ?

You can either read the files in Windows or my preferred method is.....

Download CCcleaner from here...........

CCleaner Professional | Try the world’s most trusted PC cleaner, free!

You can then run cleaner, you will see the log files listed, then if you right click you can save as a text file and then have a read. You may also get an "error reporting" log listed seperatly.

 

Attempted to do a Clean Boot but forgot to Hide Microsoft Services

Interesting scenario . . .

Try this:

• Reboot.
• Turn the machine off with the power button when the spinning circle appears.
• Repeat this exercise two more times.
• Reboot. You will now get the boot menu.
• Boot into Safe Mode and undo the fatal step. Alternatively you could use System Restore.