I am using the i5 SSDT from MultiBeast with a 2400. According to MSRDumper I reach 4 states: 16, 20, 32, 33. These seem strange to me. First of all because there is a huge gap between 20 and 32, but also because it RARELY slows down to 16 while I stare at HWMonitor at idle.
I even made my own SSDT using SSDTPRGen.sh (may she R.I.P.) and got the same results. I tried booting into Windows and getting the table from AIDA64 but there were 6 of them, and I kept getting unfixable compile errors in DSDTEditor when trying to save one of the AMLs. I started thinking I'm supposed to have SSDT.aml, SSDT-1.aml, SSDT-2.aml, etc. since there were 6 tables in AIDA64. But I figured, if the one that was giving me errors isn't present, maybe something will go wrong so I didn't bother trying any of those in my /Extra folder.
Without an SSDT I am stuck at 16 and can't go any faster. This is weird because the original thread a while back about the new SSDTs in MultiBeast said the i5 2400 shouldn't need any SSDT - that's incorrect in this case, at least with my CPU and UEFI. Am I wrong or shouldn't there be more pstates and shouldn't the machine hover around x16 when for example, I'm just typing this post? Maybe driving my other monitor uses CPU power? But I have a discrete card...
Maybe someone can help.
Otherwise this is a great thread. Thanks.