Mobo gives off memory-related errors (55,01,03)when waking up from sleep mode

pcsupport14

Commendable
Sep 6, 2017
9
0
1,510
Hey all,
Built a new pc a month ago, asrock z270 k6, i7 7700k etc. Everything worked perfectly until the past two days. I'd bring it out of sleep mode and the mobo would flash "55" and the monitor can't detect anything. So I'd shut down, start it up as normal and it works as usual.
Error 55 in the asrock z270 manual says this: "memory could not be detected. Please re-install the memory and CPU. If problem persists, install only one memory module or try using other memory modules.
Memory meaning RAM, yeah? They're corsair led 16x2 3200. This problem only pops up coming out of sleep. Normal usage is fine, including high-end gaming. How do I fix/troubleshoot this or is it even something to worry about? I shut it down normally every night, only put it to sleep during the day, fwiw.
Thanks!

PS: New development today, waking out of sleep mode flashed "01" and then moved to "03", no 55 again. I have an SSD so I don't mind avoiding sleep mode completely, but I am worried this could be something that bleeds into other issues.
 
Solution
Under system Power Options . . turn off or disable "Allow hybrid sleep". Hybrid sleep mode can cause conflicts between data written to disk and that contained in memory when waking system up.

pcsupport14

Commendable
Sep 6, 2017
9
0
1,510


I haven't been able to replicate the errors I mentioned above, thanks! When I wake it out of sleep now the mobo has the code "30" on it. Everything works fine, yadda yadda, it's still a memory-related issue according to the handbook. Any idea what this is / should I care?
 
At this stage, I don't think there is any real concern as the system seems to be running basically OK.

For reference, whenever I start up my computer I always get error codes on the motherboard which suggests memory issues also, but my system seems to run fine!

It may be because the computers are starting up and haven't reached their full operating voltages as yet that these (temporary) error messages appear(?)