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]

Stuff is all packed up, heh. I suspect a different CPU might have been worth a try, but just too little time to deal with this anymore.

FWIW, I did try this configuration on a 5820K before I swapped it for the 5930K and I believe it acted the same way, but because I hadn't narrowed down the issue fully then, I can't say for sure that the sleep -> wakeup -> restart POST hang was happening for sure because I had attempted 2400 at that configuration and the hangs were mostly on AE->AA transitions. If I ever do find a need for 128G+ I will just deal with getting a pre-built system (gag, but at least that way I know it works)

Thanks all 😃