Hi,
I'm running BOINC Manager 7.0.64 on freshly installed Win7 Home Premium, 64-bit.
The only project I'm running is World Community Grid.

Some background:
- My FX-8150 started having VRM throttling issues on my previous motherboard. It would throttle down from 3.6 GHz to 1.4 GHz every 10 seconds or so, and stay throttled for 10 seconds. This might have been happening for a whole year without me noticing.
- BOught a new Gigabyte motherboard with a better VRM system (8+2 phase, and a VRM heatsink)
- Even on the new motherboard I experience throtlling when running BOINC on the FX-8150 on default volts and clocks (VCore around 1.3V, clocking at 3.6 GHz). The throttling is significantly less frequent, though (like 1 second throttling every 10 seconds)

BOINC applications seem to not suffer from throttling. No task ended in an error. However, I didn't want to see throttling, so I went into BIOS and underclocked as follows:
- CPU VCore -0.1V
- Frequency Multiplier dropped from 18 to 15 (so now running at 3.0 GHz instead of 3.6 GHz.

The system runs very stable, and throttling issues are gone.

HOWEVER,
when I suspend or snooze BOINC, the whole system instantly freezes.
There is nothing in Event Viewer, or the BOINC log files at freeze time.
It seems BOINC needs to have run for a while for this to happen. If i suspend right after it has barely started crunching (less than a minute of having 8 apps running), it's ok.

BOINC is set to use 100% of cores and leave applications in memory while suspended. I tried to switch off the latter, with no different result.
Crunching, GPU crunching and network activity are always allowed, even when the computer is in use.

Currently I only have FightAIDS@Home units crunching.

The same thing also happened when I let BOINC run overnight with "no new tasks" on the project. In the morning, the screensaver had frozen, with a task at 98% completion. After rebooting, I noticed it was the only task left. So either the system had frozen on completion of the final task, or the one before that.

I think it's almost definitely an issue with the undervolt/clock because I didn't have a suspend->freeze issue when I was running normal volts and clocks. But then I was getting the throttling issues... perhaps the cpu has trouble coming down from a crunching state to idle state?

Push the CPU voltage back up in the smallest increments (like 0.0125 if possible) and see if the problem goes away.
Errors that occur from too little current are very odd and freezing then recovery with unusual functionality is typical.

If the BIOS can't handle those size increments then d/l a product called ThrottleStop and make the adjustments.

If your cooling system is working properly there should be a sweet spot where you are undervolted, getting max multiplier and no throttling at 100% CPU usage on all threads for hours and hours.