Z97X-UD5H Boot Loop Stops at Code 32

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
M

merk66

Distinguished
Feb 10, 2009
53
0
18,640
I am never satisfied with my machine's parts and constantly upgrade components and love to overclock things. I had been running very stable at 4.6 GHz on my i4790K processor with air cooling (Cooler Master 212 EVO). My temps were a little higher than I liked, so I decided to put in a Cooler Master Nepton 240M and at the same time I switched my ram from 8 GB Crucial Ballistix Sport running at 1600 MHz to 16 GB of Corsair Vengeance running at 1600 MHz. To complicate everything even more, I also installed 2x 250 GB Samsung 850 EVOs in Raid 0 with a fresh copy of Windows 10. I reset my BIOS and started from scratch.

Well, things seemed to be okay at first and as I got more comfortable with the new components, I started overclocking the CPU back up and encountered some issues. I can't be certain at what point things went bad, but I got to a point where my computer would endlessly reboot without posting and by looking at the LED readout on the Motherboard, I could see it stopping at number 32. This corresponds to CPU PEI initialization. I don't even know what this means, but I tried some things out to solve it and found that removing a couple of hard drives and a stick of ram seems to fix it temporarily. Once booted up again, I usually remove any overclock I have set and it seems to be okay. Right now, I still have the second stick of ram out of it. I ran memtest on the ram overnight a few nights ago and it passed 4 times with no errors.

Any help appreciated!
 
Sort by date Sort by votes


I stuck the ram back in and loaded optimized defaults in the bios. I changed only the items that I need to like raid mode on the sata and disabled onboard graphics, etc. I left all of the overclocking settings to auto and I'll let it run like this for a week or so to see if I experience the same boot loop issue.

Does anyone know what component is stopping the boot process at post code 32 "CPU PEI Initialization" or more specifically what voltage should be raised to push the pc past this point (vRIN, RING, System Agent, etc)??

Thanks
 
Upvote 0 Downvote


So after I put the ram in and reset the bios to optimized defaults, it booted a few times with no issue. Today when I turned it on, once again I was stuck in the boot loop, stopping on code 32. I unplugged every USB device and it still would not boot. I unplugged the network cable and still would not boot. I plugged all that back in, removed the Corsair Vengeance ram and put back in the Crucial Ballistix Sport. It booted right up, no problem.

I called Corsair tech support and ran the problem by them. The guy said that it may be the cpu. I checked gigabyte's compatibility list and the corsair ram is listed as being compatible with the board. I'm not sure what the problem is, but I don't think it is the cpu.
 
Upvote 0 Downvote


Thanks for trying to help. I do appreciate you posting back to me. Perhaps you missed the last sentence in my original post where I explained that I ran memtest overnight on the suspect ram and it passed 4 times with no errors.

I will add one more thing though. I called gigabyte after my last post and the guy I spoke to there confirmed that the post code 32 "CPU PEI Initialization" is related to the memory initializing. He made a few suggestions. First, he said to remove the battery for one minute to clear the cmos. Then put one stick of the ram into the slot nearest the atx power connection and boot the machine. He said to go into the bios and load optimized defaults, then enable XMP Profile 1. After that, boot into windows. If that all goes well, he then suggested putting the other module into the same slot and boot into windows again. Only after all that, put in both sticks and try it with 16 GB. He said that the XMP profile must be enabled for the ram to work right.

I personally believe that I may have some faulty ram or some other incompatibility causing the corsair ram not to work. Anyone else have any thoughts on anything I mentioned here?

Thanks again compgee for at least responding to me.
 
Upvote 0 Downvote
Just an update here.

I had removed the suspect Corsair RAM from my pc and reinstalled my old Crucial Ballistix Sport RAM. Just a day after, I had the exact same boot looping issue. It seems that it must be related to the cpu or motherboard. I have submitted a ticket with intel to get their opinion.

I performed the sequence of tasks that Gigabyte described and currently I have only one 8 GB stick of the Corsair RAM in the system. I am about to shut it down for the first time and we will see if it boots back up later.
 
Upvote 0 Downvote


So it's been a while. I think the second time I booted up after my last message, I got stuck in the loop. Once I managed to boot into the BIOS (I accomplished this by unplugging two hardrives in hotswap bays), I changed a couple of BIOS settings. There are two SATA controllers. The Intel controller has been set to RAID since I have had this issue. The Marvell controller was set to AHCI. I decided to try setting it on RAID as well, on the off chance that this was causing some sort of issue (I doubt it was though). I also increased the ram voltage to 1.55 V and the System Agent voltage by +.005. I have not failed to boot since I made those changes. I booted the first stick of ram several times. Then I swapped in the second stick and booted a few with no issue. I have both sticks in now and have booted a couple of times so far. I'm keeping my fingers crossed that it is solved by something and if it happens again I will probably go up on those voltages a little more.
 
Upvote 0 Downvote
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom