XPower X58:the system stops at debug code CO or C0

[Bbryon]

I just put together a new build with the following specs and the system stops at debug code CO or C0:
I assume it is C Zero as the manual shows three C Debug codes C0 C1 C2

Big Bang XPower LGA 1366 Intel X58
Intel Core i7-950 Bloomfield 3.06GHz processor
ASUS ENGTS450 DC OC/DI/1GD5 GeForce GTS 450 Vid card
12GB G.SKILL 6GB DDR3 1600
CORSAIR CMPSU-750TX 750 watt
WWD1001FALS 1TB 7200 RPM 32MB

Nothing fancy has been done to the machine. The phase power LED?s all show phase 2.
The CPU phase lights are all on, full 16.  No green light on monitor but fan on video card is running, so it has proper power.

The startup flashes FF then CF then C0 or CO.  FF is about .1 seconds, CF is about .2 seconds, and then it stops at C0 or CO.  The manual says ?Early CPU initialization?.  I really don?t know where to go with this. I would really be grateful for some help and direction on this one.  Also if someone can point me toward a complete and possibly better information source on the complete list of Debug codes.

 

[Jack the Newbie]

First of all: Unplug your PSU from A/C power and >>Clear CMOS<<

If that does not change anything, please make sure that you have the 12V CPU power connector of your PSU hooked up the mainboard.

Make sure your CPU and the heatsink are properly seated.  Check for bent or broken pins as well.

Test with onen memory module in the first black slot only.

-------------

In case nothing changes, please test the board outside the case on a non-conducting surface in barebone configuration.

 

[Bbryon]

First hurdle crossed.  It seems that on boot up if the OC Dashboard is plugged in without the USB cable (which t is supposed to be optional), it hangs.  Plugging in the USB cable along with the Dashboard Cable to the OC Dashboard lets the system process.  Or unplugging the OC Dashboard all together achieves the same result, the system process.

But now it fails to detect my HD.  The drive shows up in bios, and is selected as the second boot device.  The Sata DVD is first. Screen posts say the system sees the drive, even lists it along with the two Sata DVD drives.
Loading The Windows Disk starts the install process.  It finds the disk, and loads files, but on reboot, again the HD is not detected.  Off on another search for answers

I have checked all the available setting in bios, nothing seems to change this no hard drive detecton

 

[Jack the Newbie]

Loading The Windows Disk

What Windows Version are you using exactly?

What is your current BIOS Version?

 

[Bbryon]

The OS is windows 7 pro 64

I am assuming that the the bios version is this number
A7666IMS V1.3 082820          For me thats kind of a strange AM bios signature, but its all I see on screen.

 

[HU16E]

I have checked all the available setting in bios, nothing seems to change this no hard drive detecton

SATA III HDD's don't show up in the BIOS Standard CMOS Features that run off the Marvell controller. They show up in a separate quickly shown black screen during the load process. It's normal with this board, & just the way it works.

Added: BIOS version is V1.3, I do not recommend updating to V1.4. Maybe even bypass 1.5 & wait until a future final release of V1.6.

 

[Bbryon]

SATA III HDD's don't show up in the BIOS Standard CMOS Features that run off the Marvell controller. They show up in a separate quickly shown black screen during the load process. It's normal with this board, & just the way it works.

Oh I get that totally, I have another system that pops up a message that says ?not any drive found" worded exactly that way  , but at least it finds the drive and boots, this board does not find the drive, it goes to a blinking cursor at the end of the process. 

But if I boot the dvd drive to the install disk, the install finds the drive and installs files to it.  The board on boot will not detected the drive for boot, even though it list is on screen, and in the bios.  if I knew how to post images I would upload some screens of the post messages for clarification.

I am not a noob I am in my 50?s, and classically old.  I usually can work through stuff like this, but this has got me scratcin.

 

[HU16E]

I am not a noob I am in my 50?s, and classically old.

I guess being in my mid 60's makes me an antique then!

On both BB X boards I have, the SATA III does not show up other than in the boot sequence, but not in a normal expected BIOS screen. They show up in Windows & in Device Manager, so that's good enough for me.

 

[Jack the Newbie]

A7666IMS V1.3 082820          For me thats kind of a strange AM bios signature, but its all I see on screen.

A = AMI BIOS Code
7666 = your board's model number
I = Intel Chipset board
MS = MSI Standard BIOS Release
v1.3 = your current BIOS Version
082820 = BIOS Release Date [are you sure it says "20" at the end? --> anyway, not important]

I do not recommend updating to V1.4. Wait until a final release of V1.5.

v1.5 is already out there: http://eu.msi.com/product/mb/Big-Bang-XPower.html#/?div=BIOS

--------------

Bbryon, have you tested with one memory module only?

--------------

I am in my 50?s, and classically old

I guess being in my mid 60's makes me an antique!

Guys, I need you focussed!  

 

[Bbryon]

--------------

Bbryon, have you tested with one memory module only?

--------------

I dont see the relivance of pulling the memory, it just doesnt appear to be a memrory related issue, seems to be more of a sata controller bios or board issue, but I guess, I have gone this far, I will run a few more checks, then pull the mem to be able to say I covered that base

Removed all but A Channel 1DIMM and it made no difference, the board will still not see the boot drive

 

[HU16E]

WWD1001FALS 1TB 7200 RPM 32MB

It just hit me. Some of these drives of initial early release batches, needed a firmware update. I wish I would have written down the threads here at the forum that involved this. It may be a matter of the drive you have is of that batch requiring a firmware update. Not sure if the drive can be updated at the user level or not if that is indeed the problem here.  

 

[Bbryon]

one would think that if that were the case that nothing within the system would be able to see/write to the drive, yet the windows install sees and writes to it, the machine just wont see it as a boot drive.  I guess I can try another drive to check out the firmware aspect.  I don't think it would be possible for a drive I have had for a year or more would be affected the same as this brand new drive.  Least ways I hope not, i don't have much hair left, I like to keep what I do have.

 

[HU16E]

Just to clarify, exactly which specific SATA ports are you using with what device, & which controllers are enabled? Modes set to IDE, AHCI, RAID? My thoughts on the WD HDD you have are invalid, as your HDD drive is a SATA II. Firmware only affected SATA III WD HDD's best I can recall.

Excerpt from pdf manual;  "Important"
SATA1~6 & E-SATA1~2 are appearing when you connect the HD devices to the SATA
connectors on the mainboard.
Standard CMOS Features Menu does not display SATA 7 and SATA 8 items, which
are supported by the external controller chip.

 

[dilburt]

I think HU16E is on the right track.  My guess is that the "disk not found" message you see is from the Marvell SATA III system which may be just fine if your disk is plugged into the SATA 1-6 ports from the ICH10R.  You need to make sure that your BIOS settings are in sync with the drivers you have installed.  If one is IDE and the other is AHCI then you will get these results.  You also need to check the "Boot Sequence" settings to make sure the drive containing your OS is not disabled there.

I am also very concerned about your statement regarding the OC Dashboard.  It's very possible that something did not get connected correctly with the primary OC Dashboard cable.  I would completely disconnect it from both interfaces until you solve this problem.  When you reconnect it, use the dedicated cable only plugging it into the rear connector next to the CMOS reset button first - make sure the missing pin lines up with the plugged connector socket and that the connector is lined up with all pins.  Then do the same on the other end of the cable plugging it into the OC Dashboard display.  If this doesn't work or affects your system negatively in any way then the OC Dashboard or the motherboard interface for the OC Dashboard is faulty.

- D

 

[Bbryon]

I am also very concerned about your statement regarding the OC Dashboard.

I think I may have found the issue, related to the OC connection port. Inspection found no pin problem on either end, but when I disconnected the cable from the board , it went back to the original state of stopping at the  C0 debug.  Using a bore scope, I think I see a rogue drop of solder on the back side of the connector.  The board will have to come out, for further inspection.  Not sure if I can fix it or if it will have to go back in for repair or exchange.  Will post further as I know more.

 

[Bbryon]

Thank you dilburt, 

Without your post about your concerns about something did not get connected correctly with the primary OC Dashboard cable I may have been a long time finding the problem. Pulling the OC Cable set things in motion again. I found a small piece of solder rolling around inside where the OC console connector is soldered to the board. When it got moved, it would short pins causing the issue.  A pair of micro pliers and bending a couple of pin wires a bit to extract it was all I had to do.  My machine is up and running and seems to be good to go now. 

I wonder how that got past QC at MSI?  Things happen.

Thank you