02-19-2017 07:28 AM - last edited on 03-05-2024 02:10 AM by ROGBot
02-26-2017 05:49 PM
Raja@ASUS wrote:
I won't be testing the kit myself - still checking if HQ has the same kit. If they do I will ask for a replication.
Trying the CPU in a different board would be a good idea.
02-26-2017 06:07 PM
Raja@ASUS wrote:
A bad mount can warp the board or cause uneven pressure on the socket - that can cause issues with memory detection.
02-26-2017 06:21 PM
Raja@ASUS wrote:
A bad mount can warp the board or cause uneven pressure on the socket - that can cause issues with memory detection.
02-26-2017 06:52 PM
lufiron wrote:
I had this exact issue with the Apex build I recently completed. *I kept getting error code 55 with no post. *Initially, I thought it was the memory so I tried a different kit but it still wouldn't post. I reseated the CPU and tried to see a POST with no cpu cooler and sure enough it came to life. *So what I did then was use a torque driver with an overrunning clutch set to 2.5 newton meters to torque the mouting screws of the Noctua alternating 90 degrees each screw until the specified torque was achieved. *It's been fine ever since.
03-01-2017 03:01 PM
lufiron wrote:
I had this exact issue with the Apex build I recently completed. *I kept getting error code 55 with no post. *Initially, I thought it was the memory so I tried a different kit but it still wouldn't post. I reseated the CPU and tried to see a POST with no cpu cooler and sure enough it came to life. *So what I did then was use a torque driver with an overrunning clutch set to 2.5 newton meters to torque the mouting screws of the Noctua alternating 90 degrees each screw until the specified torque was achieved. *It's been fine ever since.
03-02-2017 05:37 AM
03-02-2017 06:22 AM
Charliest wrote:
I am having similar, though intermittent problems. I am at the "grasping at straws" stage. Are you using an external graphics card? If so, you might want to remove it and use the on-chip graphics as a test. I did this and am not having issues, but it may just be coincidental and a matter of time before the problem resurfaces.
03-02-2017 07:07 AM
Gabrielmage wrote:
If by external you mean a PCI-E then yeap I'm on a GTX 1080. I could try the on-board GPU but that would be more of a workaround than anything else...
Just out of curiosity what ram are you using?
03-02-2017 07:20 AM
Charliest wrote:
I tied with two sets of RAM, GEIL and HyperX Fury, both 2x8Gb. Identical behavior for both. As I said, the problem is intermittent, so I cannot conclude with any certainty that the presence of a PCIE board is signficant. I am using the system right now with the built-in video and it is working for the present. Incidentally, this is on a Code board.