[SOLVED] G Skill trident Z Neo not working correctly

[mbhipp]

Basically I am a semi competent individual when it comes to trouble shooting issues with my pc myself, but that being said I have run into an issue and im stumped about it. Basically the other day I noticed that my ram and mobo rgb wasnt working (gigabyte aorus x570 pro wifi rev 1, gskill trident z neo 3600 2x16gb) I tried to boot the software to fix the issue (gigabyte rgb fusion 2.0) and it wouldnt boot. I then booted into the bios to see if there was something there that was wrong and I noticed that the bios version had factory defaulted itself to version f3 when I had updated it maybe a month or two ago when I got the trident z neo ram so the ram could run at the correct speed. since then I have re seated the ram and re updated the bios to the more current version so the ram is operating at the correct speed. I know rgb not matching doesnt seem worth worrying about but I was wondering if anyone had any experience with this issue or something similar as I am concerned there an underlying issue that was causing this.

 

[CountMike]

Basically I am a semi competent individual when it comes to trouble shooting issues with my pc myself, but that being said I have run into an issue and im stumped about it. Basically the other day I noticed that my ram and mobo rgb wasnt working (gigabyte aorus x570 pro wifi rev 1, gskill trident z neo 3600 2x16gb) I tried to boot the software to fix the issue (gigabyte rgb fusion 2.0) and it wouldnt boot. I then booted into the bios to see if there was something there that was wrong and I noticed that the bios version had factory defaulted itself to version f3 when I had updated it maybe a month or two ago when I got the trident z neo ram so the ram could run at the correct speed. since then I have re seated the ram and re updated the bios to the more current version so the ram is operating at the correct speed. I know rgb not matching doesnt seem worth worrying about but I was wondering if anyone had any experience with this issue or something similar as I am concerned there an underlying issue that was causing this.

That MB has dual BIOS feature so it may have switched to primary BIOS