Just thought I would contribute with a problem and my resolution.
Put together a new build with P8P67, 2500k, Windows 7 32bit, Sapphire 5770, Dell monitor ST2410 with HDMI. Ran Asus auto tune software to bump up my clock speed to 4.3.
My problem was resuming my computer from sleep, specifically my monitor. The computer would go to sleep, I would press enter/esc/move mouse and hear the computer wake up but the monitor would stay in sleep mode.
Tried unplugging HDMI, turning monitor off/on etc. and still couldn't get the monitor to display. Had to turn off the computer and back on.
Through the several iterations of rebotting trying to figure out the problem, there were in some (not all I think) where I got an Asus message saying had to re-overclock again (sorry, don't remember the exact message) which I did.
Had an epiphany yesterday and decided to let the computer/monitor go into sleep without the overclock. It went into sleep and I was able to resume the computer/monitor with enter/esc.
My conclusion is the Asus overclocking caused the problem.
Hope this helps others.
Put together a new build with P8P67, 2500k, Windows 7 32bit, Sapphire 5770, Dell monitor ST2410 with HDMI. Ran Asus auto tune software to bump up my clock speed to 4.3.
My problem was resuming my computer from sleep, specifically my monitor. The computer would go to sleep, I would press enter/esc/move mouse and hear the computer wake up but the monitor would stay in sleep mode.
Tried unplugging HDMI, turning monitor off/on etc. and still couldn't get the monitor to display. Had to turn off the computer and back on.
Through the several iterations of rebotting trying to figure out the problem, there were in some (not all I think) where I got an Asus message saying had to re-overclock again (sorry, don't remember the exact message) which I did.
Had an epiphany yesterday and decided to let the computer/monitor go into sleep without the overclock. It went into sleep and I was able to resume the computer/monitor with enter/esc.
My conclusion is the Asus overclocking caused the problem.
Hope this helps others.