sleep problem with standby when both s1 and s3 shows under powercfg

My supermicro X9SRA board only have the option diable, s1, s3 under acpi.... but if i select s3 then under windows powercfg /a it would give standby (s1 s3)

and that seems to be the problem that i can't properly wake the computer after it goes to sleep and power down everything. a touch of the keyboard would wake up the fan but you just have a blank screen and an unresponsive computer...

conversely, i notice a few other computers i have where s3 sleep works properly, under powercfg /a, you only have standby (s3)

is there a way to tell windows to specifically only use s3 when both s1 and s3 standby are listed under powercfg /a ?

anytime you enter sleep. could be trying to wake up in 20 sec after entering sleep or could be sleeping for a while many hrs and then try to awake.. i am wondering if the video component is somehow not refreshing when awaking and causing everything to lock up then after that?

on my asus z9pe-16 mb there is option for s1, s3, s1&s3. i enabled s1&s3 and under windows powercfg, standby (s1 s3) shows but the asus didn't have problem waking up.... so maybe having both s1 and s3 together inside windows powercfg is not a problem? but i do notice that most of my other computers that have proper s3 sleep and wake only show standby (s3) in powercfg /a....

hibernation is diabled on my computer.

i am using the latest bios and the latest drivers of everything so not sure why

yeah, i tried the latest drivers on supermicro site as well as intel's for the chipset. using latest nvidia driver .....

i am going to try changing to a few older bios ver as well as supermicro unofficial beta bios the engineer provides.

started as soon as i install windows and put it into sleep.. this is not a new problem .... have not got s3 sleep awakening to work ever since i got this board 5 days ago..... everything else for it works perfectly... there is no random crash or anything like that at all.

.Following contacting supermicro which shows that s3 sleep and resume does actually work. the supermicro guy actually post a video of it to prove that it work.....i started the board with just one ram stick in slot 1. sleep resume fine. it was then only a matter of time before i finally traced it down to a bad contact either in cpu socket or ram slot as it looks like the board had a lot of dust with some of the dust particles actually sit at the edge of the cpu socket around the pins and also some dust in ram slots. cleaned real good..... and now s sleep resume is fine.

IT was good that supermicro posted that video and i guess a light bulb somewhere went up in my head to start it with just one ram stick :).. but it's weird that i didn't get any error while the whole thing was running before...... ran a bunch of benchmarks and everything was super stable. it was only sleep awake that was problem.... so weird that it's such an isolated problem.....would ve figured a bad contact in cpu socket or ram would have affect other things beside sleep awake..