Question about SSDT patching and an overclocked system

This is in reference to my Desktop system, which uses a 3770K that is overclocked to 4.6GHz (from stock 3.5GHz) with Clover/Yosemite 10.10.3/UEFI booting.

Now, right now, I'm *not* using a patched DSDT or SSDT (the Clover "patched" folder on the EFI partition is empty), but using several Clover flags/patches at run time to patch the auto-generated DSDT. What this does is that the system runs perfectly fine functionally, and since there's no patched SSDT, the overclock works 100% with full power management/sleep etc.

(OS X of course doesn't show the overclocked frequency in the "About this Mac" or System Profiler, but that's ok, other tools show the right frequency).

Now, I'm planning to rebuild this system and use native DSDT and SSDT files and patch them vs using Clover patches/flags, but I'm running into a potential situation. Looking at the Clover F4 generated DSDT and SSDT files, there's "some" information in the SSDT files, apart from the CPU tables.

- I can generate an SSDT with the PikerAlpha/Revogirl script and it'll reflect my true overclock, but it won't have this additional information that's already in the generated SSDT files from Clover.
- If I drop all the generated SSDTs and use just the script generated SSDT, am I looking at potential system instability, because of the missing information?
- Should I edit the DSDT and remove all the External references to this information in the SSDT files and then drop them?
- Can I copy/paste that information from the generated SSDT files into the script generated SSDT?
- Am I overthinking this?

Any thoughts are much appreciated.

Thanks.

p.s. I'm slowly starting to learn ACPI/DSDT/SSDT programming, but still relatively new at it.

Hey man, I am also running a 3770K and having the hardest time getting Yosemite to recognize my overclock. I have already gathered that "About This Mac" will always show the base clock frequency, but I am testing using the Intel Power Gadget and no matter what, Yosemite will not go above 3.5. I have been messing with custom SSDT files being generated by using the ssdtprgen utility, to no avail. I'm happy to hear that you have gotten your overclock to work without any custom ssdt by only using flags. I too am using the Clover boot loader. Would you mind sharing with me how you are achieving this using Clover? I have the Cover Configurator installed.

This is what I have configured on the APCI tab:
Drop tables: Cpu0ist, CpuPM, Dmar (I didn't set these, they were already set by default)

under SSDT: Drop OEM checked

I have removed NullCPUPowerManagement.kext as I hear this might be a problem for this sort of thing.

My processor is an i7-3770k 3.5ghz running on an Asus p8z77-v lk motherboard.

Also I don't know if it matters but originally I installed Yosemite using Multibeast on the Chimera boot loader. I just recently switched to Clover, am booting using UEFI.

I'm a really tech savvy guy (been a software designer for close to 30 years) but I am really new to Mac. If you can point me in the right direction I would really appreciate it.