FordGT90Concept
"I go fast!1!11!1!"
- Joined
- Oct 13, 2008
- Messages
- 26,259 (4.63/day)
- Location
- IA, USA
System Name | BY-2021 |
---|---|
Processor | AMD Ryzen 7 5800X (65w eco profile) |
Motherboard | MSI B550 Gaming Plus |
Cooling | Scythe Mugen (rev 5) |
Memory | 2 x Kingston HyperX DDR4-3200 32 GiB |
Video Card(s) | AMD Radeon RX 7900 XT |
Storage | Samsung 980 Pro, Seagate Exos X20 TB 7200 RPM |
Display(s) | Nixeus NX-EDG274K (3840x2160@144 DP) + Samsung SyncMaster 906BW (1440x900@60 HDMI-DVI) |
Case | Coolermaster HAF 932 w/ USB 3.0 5.25" bay + USB 3.2 (A+C) 3.5" bay |
Audio Device(s) | Realtek ALC1150, Micca OriGen+ |
Power Supply | Enermax Platimax 850w |
Mouse | Nixeus REVEL-X |
Keyboard | Tesoro Excalibur |
Software | Windows 10 Home 64-bit |
Benchmark Scores | Faster than the tortoise; slower than the hare. |
I discovered BOINC, set at 100% CPU/time was only running at 60%. I thought that problem was BOINC but seeing how it didn't fix itself over a month, I investigated further discovering the processor is running at ~1.6 GHz. ~1.6 GHz is 60% of 2.66 GHz, the stock clock of the processor. I knew it was power saving and, after Googling, I found my own thread which was about changing non-Turbo multiplier from 12x to 20x. I checked, and it was still set at 20x and the next logical conclusion was that Enhanced Intel SpeedStep Technology (EIST) was to blame. I checked and, sure enough, it was enabled. I disabled it, the processor is running at 2.66 GHz and BOINC is once again claiming 100% CPU usage.
I suspect what is happening is that, because BOINC runs at low priority, it assumes it is okay to throttle the PC while it is running. I think this behavior changed with EIST 2 because my i7-6700K is running at 4 GHz as expected. It could also just be my finicky DFI board.
Anywho, something to be on lookout for.
I suspect what is happening is that, because BOINC runs at low priority, it assumes it is okay to throttle the PC while it is running. I think this behavior changed with EIST 2 because my i7-6700K is running at 4 GHz as expected. It could also just be my finicky DFI board.
Anywho, something to be on lookout for.