R5E - QCODE D6, 95 or 90 upon restart after wake from sleep with > 6 DIMMS (96+ GB)

[vacaloca]

Hi all,

This has been driving me a bit crazy today. No overclock on RAM or CPU, BIOS settings are set to optimized (stock)

reproducibility: always
issue: R5E fails to boot after restart with QCODE D6, 95 or 90 (depending on memory slots populated past 6 DIMMS) after a wake from sleep (QCODE 30) from Ubuntu 14.04.4 flash drive OR Win7 x64 on a 960GB Crucial M500 SSD

Note that the system will boot just fine from a shut down state, and will restart happily many times. The problem comes after a restart is made after waking up from sleep.

Components:

MB: R5E, BIOS 1701 (also tried 2001)
CPU: Intel Core i7-5930K
RAM: G.SKILL Ripjaws 4 Series 128GB (8 x 16GB) 288-Pin DDR4 SDRAM DDR4 2400 (PC4 19200)
Video: GeForce GTX 745 or GeForce GT 635 (tried both because of the D6 code)
PS: SeaSonic Platinum-1200(SS-1200XP3) 1200W
SSD: 960GB Crucial M500 SSD
case: Nanoxia Deep Silence 5 case (tried w/ USB 2, USB 3 and FP AUDIO header disconnected)

RAM slots designation (for reference, in order of manual): A1 A2 B1 B2 || D2 D1 C2 C1

Test procedure: Boot into Windows 7 x64 or Ubuntu 14.04.4, place system to sleep, wake it up from sleep, restart, QCODE will manifest before monitor output if more than 6 DIMM slots populated (A1 A2 B1 B2 || __ D1__ C1)

To debug, I started out with just 1 16GB DIMM on A1, and that worked. I proceeded until I populated the configuration above and tested it about 4 times with no issues. After this point, if I add another DIMM or 2 (7 or 8), no matter how I swap the DIMMs in the slots the system will hang on the QCODES mentioned after a restart is done after coming back from sleep (QCODE 30)

I also tried to connect the 4pin power connector in addition to the 8pin, in case it was some sort of power issue, but no change. Also tried the test procedure with USB drive w/o SSD connected, same thing.

Any further troubleshooting appreciated, as I've been at this for nearly 12 hours today and am on the verge of scrapping the build and returning all the components.

Edit: Also tried a Thermaltake TR2 600W power supply, and same behavior persists.

[vacaloca]

Qwinn wrote:
I'm not suggesting this to avoid the problem, if there's instability you should resolve it, but once you have, I recommend just disabling all forms of sleep and hibernation, including Fast Startup which is enabled by default in Windows 10. The fairly significant cons outweigh the negligible pros where desktops are concerned.

Unfortunately I do want sleep mode, 😕 having an idling system that consumes 120+ W is not ideal since I have to pay for the electricity it uses -- I usually just WOL it when I need it and I'm not home. My old R4E system handles 64G with none of these sleep issues. If I can't get it working tomorrow, I'm probably just going to return it all and stay with what I have. Would've been nice to have the 128G for the simulations I'm doing, but if I have to spend days to get it working, I might as well just stay with what works.

Would perhaps swapping out the CPU bring an improvement? Or for that matter swapping out the RAM kit for a different one? Or is it really more adjusting VCCSA voltage to get it working? Any other tips welcome.

[nsb__]

Hi, (firstly, sorry for my english)

I had the same issue, but in my particular case my system showed an usb error in OC Panel too. Sometimes it hanged
showing an USB error message in OC Panel and sometimes it disconnected all usb ports but only during the reboot, during
the POST; and all these problems always afer resuming from sleep mode and restarting later.

This is that I posted time ago:

https://rog.asus.com/forum/showthread.php?81152-All-USB-ports-fail-after-resuming-of-sleep-mode-and-...

After months of investigations and trial and error I solved this problem using this bios settings :

"Extreme Tweaker \ DRAM timing Control" :

MemTest : Enabled
DRAM Training : Ignore
Memtest On fast Boot : Enabled


I hope this info will be helpful to you..

[QuinValen]

Obviously it can I just read the specs on the i7-5930K, the listed max RAM @ 64GB, however not the first time they have ever understated the max RAM the CPUs could handle.There was also this article I found using 128GB with a i7-5820K. & Asus X99 Deluxe/U3.1.

Seems this has been narrowed to BIOS, and/or one of the APM settings, or a bad IMC.

Sorry you have to give it up...:confused:

[QuinValen]

Have you tried 1801?
Also, seen talk of 1901 being out, but haven't seen it on the US server site yet.

Does it happen after sleep and a shutdown, or just a fast restart? I am interpreting hot restarts /fast rebooting , is this correct?

[QuinValen]

Which model CPU is in use, and is another compatible 2011v3 available to swap out?

And am I incorrect to assume that this is only happening on warm boot/rebooting vs full shutdown and cold booting after sleep?

@Qwinn: I would agree with disabling the BIOS fastboot... but the OS portion of fastboot shouldn't matter if the lock comes prior to full POST.

I apologize if this is a double post, crap mobile connection and service tonight.

[vacaloca]

QuinValen wrote:
Which model CPU is in use, and is another compatible 2011v3 available to swap out?

And am I incorrect to assume that this is only happening on warm boot/rebooting vs full shutdown and cold booting after sleep?

@Qwinn: I would agree with disabling the BIOS fastboot... but the OS portion of fastboot shouldn't matter if the lock comes prior to full POST.

I apologize if this is a double post, crap mobile connection and service tonight.

Haven't tried 1801 or 1901, I will give it a shot momentarily. Happens after sleep -> wake up from sleep -> restart.
Restart I define as hitting restart in Win7 x64 or in Ubuntu live session. Will not happen if I shutdown and power it on again. So yes, this only happens on warm reboot/resets. Once I wake up from sleep and warm reboot it will happen, regardless if I have warm rebooted or cold booted previously.

I don't have another CPU handy. This is a 5930K (added to OP). I was debating exchanging it and see if that does it. I just tried disabling fast boot in the BIOS and no change, still get the 90 QCODE after sleep -> wakeup -> restart

With VCCSA 0.98 V (up from 0.856 V) it still happens.

[vacaloca]

One last update on this. I removed CPU, didn't see any bent pins, however I found some gunk on one of the top pins of the CPU, so I cleaned it, reseated it, same issue. Took it out again and found more gunk... saw that one of the pins had some prior thermal paste (open box item -- pin wasn't reflective when i shined light on it). I cleaned it again, reseated, same issue. At this point since I don't even know if the integrity of the motherboard itself is compromised so I'm just going to return everything and not bother with it because I've already spent too much time on this and it's just not working out for me. Thanks for everyone who chimed in with advice, but I'll just have to do with the 64G RIVE system I have for the time being.

[Chino]

Unfortunately memory at that density isn't plug-n-play for all CPUs.

[Qwinn]

Quinvalen:

BIOS fast boot is very different from Windows Fast Startup, it's not two parts of the same thing.

The former just delays some of the hardware initialization. (Tip: never delay any SATA device initialization, it will cause BSODs during Windows boot even if it's a secondary drive).

Windows Fast Startup is hibernation, essentially. During shutdown It dumps memory to a file and reloads it upon startup rather than redoing the entire boot process. I dislike it because if there are ever any errors or instability, they are preserved across all reboots (and just a restart doesn't always sort the issues). A true full shutdown every once in a while can resolve a lot of issues.

[Qwinn]

Initially the RVE could only handle 64gb of RAM. This was upped to 128gb in a BIOS update.