Gene-z not posting, LED give error 34

[Retired]

I've just setup a gene-z with a new 2500k and it is not posting. I get consistently error 34 in the LED and the BOOT_DEVICE_LED is red.

I've put only 1 4G stick in the slot farthest from CPU, removed graphics card, and still error 34

Upon close inspection, I saw that some pins were actually bended, and unbended them (now it looks ok at least visually). But it didn't change the error. I've also changed CPU (new unused 2600k), still same error.

Any hints? Look like I should RMA.

BTW, what do the LEDs display when the system has posted ?

[Retired]

Hello Forum Members / ASUS Support

I have the same problem as well:

I got a Gene Z uATX a couple of days ago and set it up with
- core i7 2600k
- 16 GB Kingston (4 x 4GB) KHX1600C9D3K4/16GX, which going by the product manual seems to be supported
- unplugged everything except CPU, heatsink, MEM, a couple of chassis-fans
- installed and uninstalled heatsink and reseated MEM multiple times (pain with larger heatsinks...)
- using only 1 or 2 MEM sticks in the red slots
- still no go
- ends up with error code 34 and boot device LED on

I haven't poked around much with the "RC Poster" and "RC TweakIt" tools.
- connecting the ROG cable to a laptop, "RC Poster" says the error string is "CMOS error"

Debugging this stuff is always fun... but I'm concerned if this points to a bigger problem.

Any help is greatly appreciated!

Thanks!

[xeromist]

@Ram
I would try installing 1 memory module and clear the CMOS to see if you can post. It sounds like you may have done this, but I wanted to make sure. Also I would try several of the modules in case one of them is bad.

@geantvert
If you had bent pins then I would RMA the board. Once they have been bent you cannot be sure that they will ever be the same again. If they sold you a damaged board then they need to replace it.

[Area_66]

geantvert wrote:
Upon close inspection, I saw that some pins were actually bended, and unbended them (now it looks ok at least visually). But it didn't change the error. I've also changed CPU (new unused 2600k), still same error.

those pins on the CPU socket ?

[Retired]

@xeromist, Thanks for the additional check-list. Yes, I tried CMOS reset, and cycling with all 4 MEM sticks and combinations thereof...

I don't see any visible damage on the MB.

@geantvert, what pins are you referring to?


I'll try updating the BIOS via the ROG/USB:
http://www.asusrog.com/forums/showthread.php?1142-How-to-use-ASUS-ROG-USB-BIOS-Flashback
Let me know if anyone thinks this is a bad idea... or any other relevant tips.

[Excruciation]

I was consistently getting a code 34 on POST with a Maximus IV Extreme-Z board, thinking I would have to RMA it. The debug code would go all the way up to 98, then go back down to 34 and had 1 long beep, 4 short beeps, a brief pause, then another short beep.

RCPoster said the issue was ROM init, so I thought the BIOS chip was bad. I tried flashing the ROM via USB/ROG from both a FAT formatted stick and FAT32 formatted stick, to no avail. The USB stick would flash for a few seconds but the BIOS light on the board would only flash once.

I finally gave up left the machine plugged in and came back from work yesterday, and noticed that the board code now said AA (sleep mode I believe). Well, this was new, so I reset the machine, and lo and behold, it went into the BIOS/UEFI! The 34 code turned out to be a CPU thermal warning. I didn't hook up any of the thermal sensors, and I doubt the CPU was really running close to 200F, but I just hadn't been getting any video output at all, and now I was (and I had tried 2 different cards). You might try hitting the F1 key once you get the 34 error.

Also turned out 1 RAM module wasn't seated all the way, but I don't think it was in any way related to the issue since I had tried extensively with just one stick in various slots and had got the 34 error every time.

[Retired]

@ram: I was referring to the pins on the CPU socket in the motherboard, some of it were actually bent. I very carefully tried to unbend them and it appears (using a light perpendicular to the socket) that it is now ok.

@excruciation: thanks for the explanation for the code 34 error being a CPU thermal warning: I am using a Noctua C14, and I connected of course the fan to the CPU Fan socket, but the temperature sensor is inside the chip so obviously I have nothing to "connect" there. As for the RAM, I tried all 4 locations, changed module, tried other RAM modules, still same result. However I haven't tried to leave the board on for a long time.

Anyway, I have now ordered a new GENE-Z, and it arrived today. I will give it a try, and if it works I will RMA the first one. Will keep you posted.

Thx for all replies

[Excruciation]

Well, good luck to you. I now think my CPU really was running at 86C; the stock Intel cooler must've had one corner not securely fastened, though that wasn't obvious. In any case, I added a Noctua D-14 to it today and it now idles at 17C if my air conditioner is on (which is fairly close to the PC), and 27-28C otherwise.

4.4 Ghz is no trouble but the system won't boot into Windows past that, yet, probably due to memory issues with the Corsair XMS3 2000 RAM... I probably should've just gone with a Gene-Z, in retrospect.

I should note (for others) that I received the beep pattern I mentioned mostly on a cold boot. On restarts, I'd just get a single short high beep, then a single short low beep when it hit code 34.

[Retired]

I have the same problem, but then on the maximus... will try to reinstall cooling first then 😞

[Retired]

bump/kick?

anyone knows what the problem can be? I reinstalled the cooler, it is fine... no idea where to look next 😞