Stumped on this one, is it a motherboard, RAM, or windows issue?

PCBuilderProbs

Reputable
Mar 24, 2015
780
0
5,360
So today my PC decided to not boot into Windows today. I have an i7 4790k, MSI Z97 Gaming 5, and 2 pairs of 4gb sticks I've been using for the past few months in this rig. The debug screen on the board would cycle through debug codes 50-69, which are early memory and early/late cpu initialization errors. I swapped out RAM, tested one stick at a time in multiple slots but to no avail. Note that I would be able to get past the MSI logo screen before these issues happen, so I still have access to BIOS.

I was hoping flashing BIOS would solve my problem so I flashed it to the latest version but it's still giving me issues. I'm pretty much stumped at this point. I have no idea whether this is a RAM or a board issue. Obviously the pairs of sticks I'm using aren't on the compatibility list for the board but they've been working well so far for the last few months since I upgraded my PC in March. No idea what could be happening.
 
Hello... Let's try a proper "battery removal" AND CMOS reset Clear to the MB ...ok? B /
Take your time here and be slow and careful to your MB... look in your MB manual/Pdf for pictures and location of the SW/pins. B )
1) un-plug PS from wall.
2) remove MB battery
3) place jumper pins/switch on MB to clear the capacitors... for ~3 mins
4) remove Jumper/switch
5) re-install battery
6) plug monitor into the MB video output OR Video card for a BOOT display
8) plug in PS to wall
9) Boot computer.
 
1) debug screen is during POST so Windows hasn't even loaded yet. Thus, not an Windows issue.

2) you should also verify with Memtest86 www.memtest86.com

It may not be bad memory if it fails. It could be timing issues or a bad motherboard. Or CPU.

3) Did you try XMP settings for the memory?

4) Just FYI, but likely there is one specific slot meant for a SINGLE stick of memory. See your motherboard manual.

5) *At this point I suspect the motherboard, CPU or CPU cooler.
 


Flashing the BIOS sets everything to default anyway. All the battery does is allow the changes made to be remembered.
 
Not to be too funny here but you do know that in order to complete a bios firmware update on any system.
That you must in fact factory default the bios manually as the final procedure to clear out any old code left over from the old bios firmware and refresh it to the new version.

That is how you are supposed to do it.

If you just flashed the bios with the new firmware file old bios code is in fact still left in the Rom part of the bios chip it is force flushed by factory resetting the bios PCBuilderProbs.
Any old bios code from firmware revision to a new version may cause a conflict.

I suggest you manually reset the motherboard back to factory defaults to ensure complete programming of the cmos bios rom.

And since you say the error relates to early, and late cpu init errors.
remember the bios checks and does a system test of hardware connected to the motherboard in a set defined order.

What I am saying is If it refuses to boot off the hard disk drive.
Then it may be down to the bios not being able to see the drive.
It could be as simple as replacing a Sata cable or checking it is seated to the drive and motherboard and also power connected to the drive.

If you are getting past the MSI logo screen.

 


I used MSI's m-flash utility so it should've handled all that
 
Remember the bios checks and does a system test of hardware connected to the motherboard in a set defined order.

What I am saying is If it refuses to boot off the hard disk drive.
Then it may be down to the bios not being able to see the drive.
It could be as simple as replacing a Sata cable or checking it is seated to the drive and motherboard and also power connected to the drive.

If you are getting past the MSI logo screen, it is used to mask the bios testing procedure of hardware.
The point where it gets past it, it should be looking for a boot able hard disk drive or boot able os partition.

As you said it does not boot windows.
So it would suggest the problem is with the hard drive or the boot able partition on it not being seen by the bios.

I could be wrong, but all the same check the sata cable and power to the boot drive, or replace the sata cable with another.


 


Good theory I guess, but nope. BIOS recognizes the SSD i have.
vFWzL96.jpg

8y3zr17.jpg