Rampage V Extreme Persistent Wake from Sleep Problems

[nonverbal]

Since I first owned this board (2014) I have had consistent wake from sleep problems with all OSs including Windows 8/10 and various LInux distros and different hardware configurations (e.g., Titan X SLI, 32GB of RAM, different SSDs). Specifically, 1 out 5 times after the computer has gone to sleep it will not wake-up and resume without requiring a hard reboot (i.e., holding down the power button). This happen regardless if I am running stock settings or overclocked and despite tweaking myriad voltages such as System Agent and memory.

Every time the system refuses to return from sleep the Qcode E1 is displayed and the PCIEX16_4 LED is blinking. Generally the system appears to return partially (there is system activity) but the display and USB connections are inactive and I have to hard restart and am greeted by the failed overclock BIOS screen, even if the settings are default and not overclocked. Only one PCIE slot 1 is populated with a Titan X.

A few BIOS versions ago I had persistent problems with some USB ports not working, but that seems to have resolved. I'm wondering if anyone has any advice or if this may just be an RMA issue either. Besides this issue with my system, it is stable and boots and behaves under load completely fine (surviving stress tests).

Thank you for any advice you can provide.

[badmojout]

GoatHumper wrote:
Well... first off: it happens regardless of whether I wake it up via keyboard, mouse, or power button.

Second, the reason I use suspend is precisely so I don't have to wait "too long" to get the computer back up from "shutdown" (i.e. cut down on power consumption, while also cutting down on booting delays).

Waiting longer than 1 minute for the box to come back up from suspend is a waste of time - I'm better off just rebooting at that point.

So thanks for the suggestion, but no thanks 🙂

I'm hoping someone will chime in and suggest a BIOS voltage tweak that might do the trick (Arne? You still there? :D).

Cheers!

I should have made it clearer that this was more of a troubleshooting step to see if your computer ever did boot into Windows. *Not that you should wait minutes every time you want to resume from sleep. :). And then chase down the possibilities based on that outcome. *

[GoatHumper]

Ok so I had another episode, and I've identified the PCI-E slot that's blinking: it's #4 (PCIE_X8_4), and it has an NVME drive on it. Perhaps the PCIE bus needs a voltage boost? I already have a molex power cable connected to the EZ_PLUG terminal even though I only have one graphics card (I figured it'd be prudent).

It would appear the NVME drive is either having trouble waking from S3 Sleep, or the motherboard is having trouble waking the PCIE bus up fully... Any ideas?

Thanks!

[Arne_Saknussemm]

1.1 is not high for VCCSA...I would set this to 1.2 and see if things stabilise...you can always work down from there...

I'd investigate VCCSA before VCCIO for example....even 1.25 for experiment's sake

I don't have experience with any OS other than windows so if what you are seeing is some driver/device conflict etc. I cant really help on that.