It usually happens when you set too low or too high CPU or CPU-NB voltages or too high CPU-NB clock ( but 2400 is not so high ). Window manager is crashing and after service restarts it's running with disabled aero.
+1 on my end. Below I've described my process for isolating the cause of my win7 Aero malfunctions. To make a long story short, despite all voltage, power, & multiplier configurations (including the stock 18x) tested, win7 aero would crash upon system resume and in many circumstances on initial system boot for a CPU/NB/HT Link frequency at 2400Mhz (with DDR3 1600).
Over the last several weeks, I have manipulated my updated BIOS (ASUS 1001) from every suggestion mentioned in this forum and others. I have taken the CPU voltages from 1.250 to 1.5 (1.425 stock) in conjunction with CPU/NB voltage manipulations from 1.25 (stock) to 1.35 at several intervals (i.e. 1.325 CPU @ 1.25, 1.275, 1.3 CPU/NB voltages etc). At each of these intervals, I tested multipliers of 18, 19, 20, & 21. Additionally, I tinkered with all available power options for my MOBO and with core unlocker and turbo mode enabled & disabled. While I passed prime95 blend tests at all of these configurations (albeit for some trials < than an hour due to aero failing and being too frustrated to sit and allow prime95 to run on a set up that I knew I wouldn't use) with core temperatures never rising above 60 degrees C, win7 aero continued to falter performing everyday tasks. It was only when I had the epiphany to reduce my CPU/NB & HT link frequencies that I began to see results (seems obvious, I know..). After repeating an abbreviated version of the above process with 2200MHz CPU/NB, I continued to have aero errors but they were experienced less frequently and I could reset aero from the command line and services menu (which could not be done at 2400MHz). Finally, I reduced the CPU/NB & HT link to stock at 2000MHz and all appeared normal for multipliers of 18, 20, & 21. I am currently running my OC @ 4.2GHz with CPU/NB and HT link frequencies and voltages set on auto. While this entire process has been a failure in my opinion, I hope that my many hours & system reboots can benefit someone else in their quest for a fully operational win7 aero experience. As a final caveat I would like to admit that I am new to the overclocking scene so I apologize if I am missing something obvious in this write up. In the near future I will not have to time test additional configurations but I welcome additional suggestions that I should be able to test in the upcoming months.
My Build:
MOBO - ASUS M5A88-M, CPU - AMD FX-4100 @ 4.2Ghz (Stock Cooling), MEM - G.SKILL 8GB (2 dimm) DDR3 1600, PSU - RAIDMAX 730W, VID - XFX HD Radeon 6770 (1GB), HDD1 - WD 320GB SATA 3 (Win7 HP Sp1), HDD2 - Seagate 160GB SATA 3 (Ubuntu 12.04)
