Issue with Dual Epyc 7601 on Windows 10
Issue with Dual Epyc 7601 on Windows 10
Hey there, I've recently moved from my i7 11700k to a dual Epyc 7601 because I was frequently reaching full CPU usage. At first it worked fine, but now something odd started happening. The CPU load appears to be limited at around 10%, making even simple tasks like web browsing feel slow. I checked some forums mentioning CorePrio, but it didn’t help much. Thinking about a Windows scheduling problem, I wanted to test if all cores could actually run at 100%. Using Prime95 SmallFFTs surprised me—it actually improved performance. I’ve never seen anything like this before. I was hoping everything would slow down and focus on p95, but I could still play OBS, run games, and maintain better performance without stressing the system. I really value your advice and would appreciate any suggestions, especially regarding BIOS settings or system info. OS: Win 10 for Workstations (latest update 10.0.19045). 2x Epyc 7601, 32 cores, 256GB ECC RAM, Supermicro H11DSi-NT Rev1.0, RTX 3080ti.
Checked if power profiles were activated in the Supermicro BIOS. Verified whether a fresh Windows installation was performed or if the setup came from an Intel system.
I have switched on the Performance Profile, and yes it's a fresh install.
No noticeable irregularities in CPU speed during light tasks. Clock speeds remain stable and within expected ranges for web browsing.
Nothing really, but i haven't checked with anything but taskmanager. One thing to note is, that i tried installing the Chip set Drivers for Windows Server 2016 and CPU load was pinned at 100%, even with nothing but the OS running. Installing the 2012 R2 ones worked fine for a while, but alas...
It wouldn't be wise to mix and match drivers, but troubleshooting is essential. Have you attempted a simple Ubuntu installation? If Linux functions properly, the issue likely lies with Windows settings rather than the BIOS.
I haven't tried yet, though it worked before. It seems like the BIOS might be having issues with some settings, but I'm going to test it now.
I overlooked that the Server 2016 update was rolled back and replaced with a new setup; the 2012 R2 model remains the sole version running here.