last edit : case closed. i accidentally changed my oc mode to auto. probably when i change my ram to 32GB. i was using 16GB before. it is a recent change. only about 3 months i think. i did not noticed that i changed my OC mode to auto. thanks to Truder for making me check my bios again. was about to sleep. but can't help but wanting to check the bios again. and it's true. i did not noticed this. because i very rarely change anything on my bios. edit : forgot to put in my current configuration. ryzen 5 2600x asrock x470 taichi team ddr4 32GB 3200mhz nvme 512gb cougar 750w gold psu. win 10 pro 64 bit. edit 2 : my win 10 is a fresh install, because a few months ago. it suddenly got corrupted for no reason. i haven't been using ryzen master for more than a year. because i thought that uefi are enough. uefi settings that i use are either of these 2 : - 3600mhz and 1.11875v - 4000mhz and 1.1875v while the settings that was applied automatically on startup is : - 4100mhz and 1.45v edit 3 : forgot to mention that weirdly my RAM settings on UEFI stays the same. so i think there is something inside win 10. that told my 2600x to always ran at 4100mhz and 1.45v edit 4 : i tried using the reset function. on ryzen master. it asked for a restart of windows. and after window restart.... the clock that was set are now 4150mhz with 1.45v and sometimes more than 1.45v. original : i just notice this recently after i reinstalled ryzen master. it's that my 2600x doesn't ran at my uefi configuration. but instead it ran at 4100mhz and using 1.45v. i need help on fixing this. so that windows loads my uefi setttings. for now the only fix is by using ryzen master at startup and then applying the same settings that i have on my uefi. oh and also if i close ryzen master. it will revert back to 4100mhz and 1.45v. and i think it stays constantly at that clock and voltage. the thing is at launching ryzen master. it will tell us our current clock and voltage. and it's always at that 4100mhz and 1.45v... i did not notice this. because i haven't been using ryzen master for a long time. about a year. so no idea when this bug started.