Jump to content

TheStuck

Members
  • Posts

    4
  • Joined

Reputation

10 Good

About TheStuck

  • Birthday July 13

Converted

  • Occupation
    Engineer
  1. LS100 lighting kit no longer is one of the first in sequence when using type lighting. It is now the last in the sequence. Looks weird now that it doesnt not light up with the keyboard as you type way after you are done typing or clicking a mouse. I have a full corsair setup. This is the only issue I am having so far. 3.25.60 was my previous version and it worked fine. Can you reorder them somehow?
  2. 3.26.95 is hot garbage. Crashes all the time with no consistent reasoning. Even crashes right after startup of the computer. Type lighting is even out of sync. LS100 is now last to go instead of one of the first things. Looks stupid now. Im going back to 3.25.60. That is probably what I would do.
  3. I am running latest chipset and 1903 windows. Running latest ASUS bios but that isnt AB. I wouldnt be surprised if ASUS goes to ABB instead of AB on the next update. The new chipset was supposed to address software that had very aggressive system requests (~1ms). The new chipset seems to have fixed this for all the software I run with the fast service requests but iCUE. As soon as the iCUE is closed, the idle voltage goes <1. It is the only programs causing this. I do not know if iCUE has to have the fast system request or not as it relates to Corsair Services which is causing this issue. Note someone on Reddit said disabling enable full software control on the ram fixed it. It did not for me. I think this is a case where Ryzen 2 is the first CPU to be sensitive to fast service requests. I believe Ryzen 2 is reacting by design though. Windows says default request time is 15.6 ms and will give warnings for anything faster than this. You can check by running command in admin mode and typing "powercfg /energy /duration 5" and then reading the energy report it generates. Maybe the next BIOS update (ABB) will fix it but as of now the only software that I run that causes the idle voltage issue is iCUE and more specific the Corsair Service. Hopefully providing as much information as possible will speed up the fix.
  4. For additional information, I disabled Corsair Service and it indeed lowered the idle voltage to <1 V. All other monitor software did not peg the idle voltage out. However, I lost connection to: Commander Pro and all things attached to it. (RGB strips, 3x LL120 RGB fans) 2 x Veng Pro RGB RAM sticks H115i Platinum AIO (USB connections going through Command Pro) Basically anything connected internally. I retained connection to all USB peripherals: Void Pro RGB Headet, K70 keyboard, Glaive mouse, and MM800 mousepad.
×
×
  • Create New...