BIOS and Chipset Driver info

Hello all,
Sorry for not searching for finite details, I will do better in the future.

System
Corsair HX750 PSU
AB350M Pro4
AMD RYZEN 5 1600X
GeIL 32GB (2 x 16GB) Orion AMD DDR4 PC4-24000 3000MHz GAOR432GB3000C16ADC (new)
Hynix p31 1TB NVMe M.2 SSD on motherboard (new)
Hynix p31 500GB SATA on SATA III 6.0Gb (new)
WD 2TB Black Edition (new)
WD 1TB Black Edition (old)
EVGA GTX6600 OC 2GB Graphics Card (hand me down)

Keep in mind that with the original components in the system, it worked flawlessly out of the box until the SSD filled up.

This all started when we decided that her aging Samsung 970 EVO 450GB SSD was nearly full. The goal was to use an SSD adaptor in the spare PCIe slot to do the cloning. I forgot the second PCIe slot was disabled and that failed - of course.
Then I tried an external Sabrent NVMe M.2 to USB 3.0 case and it worked at USB 2.0 speeds - predicted 27 hours. (was probably a bad cable from Sabrent*)
I gave in when I saw the Hynix p31 500GB SATA drive on sale and completed the task in excellent time.

In the midst of all this, I started looking at BIOS & Chipset revisions.
Much to my dismay, they were all out of the box versions
BIOS 3.0
Chipset Driver - original install disk

I brought the BIOS up to 5.10 disregarding the comment about the Raven CPU. Then I noticed that later versions stated that the All-In-One driver package needed to be installed with no comment regarding CPU type. I don't have an AMD graphics device in the system or the CPU.

A.) Do I still need to install the All-In-One even though I have an NVIDIA graphics card?

B.) Is it safe to upgrade to BIOS Rev 5.90 without the All-In-One driver?

Next issue:
Regarding the AMD Chipset driver install package...
It faults out with an EVENT message that goes something like this...
Unable to find "C:\AMD\.....blah, blah, blah <some file>.msi"
And indeed, there is no .msi file.
Not in the directory path.
Not in the install package.
I tore the thing apart using 7-Zip and no ".msi" files.

Downloaded the chipset drivers directly from AMD, same problem, same fault.

I used some info to troubleshoot the system and SFC found an "overlap" error.
Fixed this by setting "C:\" sharing properties
SCF ran without errors.
I ran out of time right then and had to leave the system in operating, but a less than optimal condition.

I originally had the CPU overclocked to 4.1GHz and the previous memory (Balistix) at XMP settings.

However, I screwed up and forgot to check the CPU clock that reset to stock after the BIOS updates and memory is actually running at DDR4 2134MHz. But, that is not part of the current problem.

If the fixing the system files and sharing properties does not fix the Chipset installation problem, does anyone know of an alternate method of getting this done?
Thank you in advance...

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
midigark Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 19 May 2021 Location: Illinois, USA Status: Offline Points: 160	Post Options Post Reply Quote midigark Report Post Thanks(0) Quote Reply Posted: 19 May 2021 at 1:57pm
	oops * the Sabrent external USB 3.1 case worked on my computer with a new cable. https://www.userbenchmark.com/UserRun/43066998

midigark Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 19 May 2021 Location: Illinois, USA Status: Offline Points: 160	Post Options Post Reply Quote midigark Report Post Thanks(0) Quote Reply Posted: 19 May 2021 at 1:45pm
	Hello all, Sorry for not searching for finite details, I will do better in the future. System Corsair HX750 PSU AB350M Pro4 AMD RYZEN 5 1600X GeIL 32GB (2 x 16GB) Orion AMD DDR4 PC4-24000 3000MHz GAOR432GB3000C16ADC (new) Hynix p31 1TB NVMe M.2 SSD on motherboard (new) Hynix p31 500GB SATA on SATA III 6.0Gb (new) WD 2TB Black Edition (new) WD 1TB Black Edition (old) EVGA GTX6600 OC 2GB Graphics Card (hand me down) Keep in mind that with the original components in the system, it worked flawlessly out of the box until the SSD filled up. This all started when we decided that her aging Samsung 970 EVO 450GB SSD was nearly full. The goal was to use an SSD adaptor in the spare PCIe slot to do the cloning. I forgot the second PCIe slot was disabled and that failed - of course. Then I tried an external Sabrent NVMe M.2 to USB 3.0 case and it worked at USB 2.0 speeds - predicted 27 hours. (was probably a bad cable from Sabrent*) I gave in when I saw the Hynix p31 500GB SATA drive on sale and completed the task in excellent time. In the midst of all this, I started looking at BIOS & Chipset revisions. Much to my dismay, they were all out of the box versions BIOS 3.0 Chipset Driver - original install disk I brought the BIOS up to 5.10 disregarding the comment about the Raven CPU. Then I noticed that later versions stated that the All-In-One driver package needed to be installed with no comment regarding CPU type. I don't have an AMD graphics device in the system or the CPU. A.) Do I still need to install the All-In-One even though I have an NVIDIA graphics card? B.) Is it safe to upgrade to BIOS Rev 5.90 without the All-In-One driver? Next issue: Regarding the AMD Chipset driver install package... It faults out with an EVENT message that goes something like this... Unable to find "C:\AMD\.....blah, blah, blah <some file>.msi" And indeed, there is no .msi file. Not in the directory path. Not in the install package. I tore the thing apart using 7-Zip and no ".msi" files. Downloaded the chipset drivers directly from AMD, same problem, same fault. I used some info to troubleshoot the system and SFC found an "overlap" error. Fixed this by setting "C:\" sharing properties SCF ran without errors. I ran out of time right then and had to leave the system in operating, but a less than optimal condition. I originally had the CPU overclocked to 4.1GHz and the previous memory (Balistix) at XMP settings. However, I screwed up and forgot to check the CPU clock that reset to stock after the BIOS updates and memory is actually running at DDR4 2134MHz. But, that is not part of the current problem. If the fixing the system files and sharing properties does not fix the Chipset installation problem, does anyone know of an alternate method of getting this done? Thank you in advance...