Gigabyte asked me to try a slightly different setup - marvell in ide and intel in raid, hdd connected to marvell.
My response back:
The results are different - mixed - unpredictable - worse.
I have set up the board as per your request with the following steps.
Disconnect all power and connect a single hdd [wd 2tb] to a marvell port.
Press clear cmos and power on the system.
At the load defaults screen, choose load optimised defaults and reboot.
Press del to enter setup and change marvell controller to ide and intel controller to raid. Save and exit.
Install win 7 sp1 x86 with F6 Intel raid driver.
Install chipset and vga drivers.
A check of device manager showed the intel raid was correct with c600 drivers.
A restart worked fine with device manager still showing correct c600 raid.
I then put the system to sleep and then woke it up. I clicked the account icon and the welcome message was displayed.
The system remained on the welcome message for a long time - more than 1 minute.
It eventually went to the desktop and I was able to access device manager and the raid was still correctly showing c600.
I then put it to sleep again, but this time on resume the welcome screen quickly disappeared [normal] but the desktop was a black screen with an empty taskbar at the bottom.
The mouse was still working - could move it - but nothing more happened.
I then momentarily pressed power and the system momentarily showed the desktop but then went into shutdown mode.
Wether the system was about to show the desktop or wether my pressing the power button caused it to show the desktop, I can't say.
When the system rebooted, I checked device manager and all was still ok,
I tried sleep again, but this time it refused to fully sleep, it only turned the screen off but after a further minute or so, power was still on the board [various led's still illuminated]
So, I thought I would try and duplicate the results.
I reinstalled windows [delete existing partitions], but now on resuming I would either have a hang at the welcome screen followed by a bsod, or arrive at the desktop followed by a bsod, pic of which is attached.
So, it never did the same thing twice in a row, very unpredictable.