- Dec 4, 2009
- 2,123
- 1
- 20,460
OK, I just bought an Asus Z97-WS, a (making sure it was on Asus's supported memory list) 16GB Gskill DDR3-2400 kit, and a Core i7 4770k. I put them in my system, and they worked beautifully for ten days. Then, suddenly, my system bluescreened and rebooted. Upon rebooting, the motherboard hung, giving a code 55 on the diag LEDs, meaning the memory was missing.
I tried moving around the memory and using 4 different kits, two of which were on Asus's supported memory list, but I got the same behavior: if the memory was in either or both slots A1 and A2, it would be recognized, if any memory was in slot B1 it would hang and give that 55 code, and if there was memory in slot B2 it would not be recognized at all. After all that messing around, I figured it was the motherboard, so I ran an RMA through Asus's system.
Either that wasn't it, or I got a replacement, brand new, board with the exact same problem. Highly unlikely, but not totally out of the realm of possibility.
So, I thought it must be the CPU. Maybe the slightly high voltage that board wants to run through the memory burned out the memory controller. So, I went over to Microcenter and bought the cheapest 1150 CPU they had in stock, a $40 Pentium G3220. Guess what: same story.
Different CPU, different motherboard, different memory, same problem.
So, assuming that getting a replacement board with the same problem is too unlikely, what the heck could cause this?
I tried moving around the memory and using 4 different kits, two of which were on Asus's supported memory list, but I got the same behavior: if the memory was in either or both slots A1 and A2, it would be recognized, if any memory was in slot B1 it would hang and give that 55 code, and if there was memory in slot B2 it would not be recognized at all. After all that messing around, I figured it was the motherboard, so I ran an RMA through Asus's system.
Either that wasn't it, or I got a replacement, brand new, board with the exact same problem. Highly unlikely, but not totally out of the realm of possibility.
So, I thought it must be the CPU. Maybe the slightly high voltage that board wants to run through the memory burned out the memory controller. So, I went over to Microcenter and bought the cheapest 1150 CPU they had in stock, a $40 Pentium G3220. Guess what: same story.
Different CPU, different motherboard, different memory, same problem.
So, assuming that getting a replacement board with the same problem is too unlikely, what the heck could cause this?
Facebook
Twitter
Instagram