D-led2 "PROG.CLK" error message.

Mangemongen

New member
CORPORAL
Joined
Nov 27, 2010
Messages
15
First of all: Why would you provide a debugging service which has error messages not explained ANYWHERE? There is no info anywhere about what PROG.CLK means. I cannot complete POST. Me and a friend have quadruple-checked everything in the MB.

Tried this: https://forum-en.msi.com/index.php?action=printpage;topic=123185.0
Nothing.

Tried CMOS reset. Tried using only one memory module.

And everyting used to work fine by the way. I have not changed any components. Which are the following: Intel Xeon i7 W5320, 3x2GB Crucial Ballistix Tracer 8-8-8-24 1.65v, HIS Radeon 5870 1GB, OCZ Vertex 2 60GB.

The power supply is a Tagan Turbojet 1100w.

No error beeps.

Edit: I have actually changed harddrive, I forgot. But well, I tried with and without harddrive, no change. I also never POST anyway. Also added the components.

Edit #2:

MSI X58 Eclipse SLI BIOS 1.1 without OS
Intel Xeon i7 w5320 2,66Ghz
Crucial Ballistix Tracer DDR3 PC12800/1600MHz CL8 Blue 3x2GB (BL3KIT25664TB1608)
Tagan Turbojet 1100w 12v-20A  3.3&5v-28A
HIS Radeon HD5870
OCZ Vertex 2 60gb
 
I added them in the description now.

Please, if the info is not enough at some point please tell me. I don't have the energy to go check numbers if they're not necessary. I've looked over that motherboard for hours today.
 
MSI X58 Eclipse SLI BIOS 1.1 without OS

Are you 100% sure that the BIOS Version is actually v1.1?  How did you determine that?  Do you have the info from the sticker on the BIOS Chip of the board?

I am asking because according to the CPU Support list, you need at least BIOS v1.9 to ensure proper support for the Xeon i7 W5320.  This could be one aspect of the problem.

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

 
Jack said:
Are you 100% sure that the BIOS Version is actually v1.1?  How did you determine that?  Do you have the info from the sticker on the BIOS Chip of the board?

I am asking because according to the CPU Support list, you need at least BIOS v1.9 to ensure proper support for the Xeon i7 W5320.  This could be one aspect of the problem.

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

I'm not 100% sure, it just says MS 7520 Ver 1.1 on the MB. I'm sorry, I was stupid. But I was out of patience. I have resetted CMOS, does that reset the BIOS? I don't know what BIOS was on before, for that I would have to ask the previous owner. I'm going to look for that BIOS Chip sticker.

Edit: I found this sticker close to the CPU: Amibios XB82 6023. Hope it's the right one.

Edit #2: According to the D-led the CPU boots fine though :/
 
I have resetted CMOS, does that reset the BIOS?

It resets (well, clears) the BIOS Settings and Configuration data, but has no effect on the BIOS Version as such. 

Please have a look at the board's BIOS chip to check the factory BIOS Version:

 

Attachments

  • eclipse bios chip.PNG
    eclipse bios chip.PNG
    537.6 KB · Views: 502
Jack said:
It resets (well, clears) the BIOS Settings and Configuration data, but has no effect on the BIOS Version as such. 

Please have a look at the board's BIOS chip to check the factory BIOS Version:

It says: A7520 IMS5170
 
That means, that the board left the factory with v1.7.  So, a lack of proper support for the Intel Xeon i7 W5320 could be a potential cause of the problem.  Can you get your hands on another processor (perhaps with the help of your friend)?

To eliminate other possible causes:

- you have tested with one memory module in the first black slot only?
- you have tested the board outside the case on a non-conducting surface in barebone configuration?
- you have checked the CPU socket for bent or broken CPU pins?
- all power connectors (also the one for the CPU) are properly hooked up to the PSU?

 
Jack said:
That means, that the board left the factory with v1.7.  So, a lack of proper support for the Intel Xeon i7 W5320 could be a potential cause of the problem.  Can you get your hands on another processor (perhaps with the help of your friend)?

To eliminate other possible causes:

- you have tested with one memory module in the first black slot only?
- you have tested the board outside the case on a non-conducting surface in barebone configuration?
- you have checked the CPU socket for bent or broken CPU pins?
- all power connectors (also the one for the CPU) are properly hooked up to the PSU?

He delivered the computer to me as he had used it with the processor, so he must've updated the bios. I waiting for an answer of the version.

I have done all of that except testing the board outside the case.. Disassembling again, gotta love it. I've worked on that computer for 20h the last three days all because I wanted to change the CPU Cooler.

I did not change the power connectors from when it all used to work fine.

 
He delivered the computer to me as he had used it with the processor

I see.  It is good that you mention that.

So, after the system was delivered to you (in a functional state), did you test the system right away or did you only find out about the problem after you changed the CPU Cooler?
 
Jack said:
I see.  It is good that you mention that.

So, after the system was delivered to you (in a functional state), did you test the system right away or did you only find out about the problem after you changed the CPU Cooler?

I never tested the system (stupid maybe) but it was so protected that the cardboard box it came in felt like it contained some soft light ball or something. So I felt secure nothing would have been damaged during transport.

Also, to get proper airflow I had to mount the cooler (CoolerMaster Hyper 212plus) the "wrong" way over the CPU, and not use that CPU-fastener-thing. But then again the cooler where it's in contact with the CPU is practically square. The pressure over the CPU is as even as it would've been the correct way.

http://benchmarkreviews.com/images/reviews/cooling/Best_CPU_Coolers_Q2-2009/Cooler_Master_Hyper_212_Plus_Heat-Pipe_Base.jpg
 
Anyway, if the system worked before, then either during transport or when you changed the cooler something must have happened that now affects the functionality of the system.

A short circuit issue inside the case is one explanation.  Did you completely remove the board from the case when you changed coolers?

Another explanation is that somehow there was in fact a change of pressure the cooler excerts on the processor causing a pin-contact issue (CPU <-> socket pins). 

These are the explanations that do not necessarely indicate a defective mainbaord.  So, there is hope involved here which should make disassembling the system again less annoying.
 
Jack said:
Anyway, if the system worked before, then either during transport or when you changed the cooler something must have happened that now affects the functionality of the system.

A short circuit issue inside the case is one explanation.  Did you completely remove the board from the case when you changed coolers?

Another explanation is that somehow there was in fact a change of pressure the cooler excerts on the processor causing a pin-contact issue (CPU <-> socket pins). 

These are the explanations that do not necessarely indicate a defective mainbaord.  So, there is hope involved here which should make disassembling the system again less annoying.


I see. I will get back to you when I have disassembled it and tried again. At one time the D-led stopped at CPU Ini but a little push on the cooler fixed it. I can have pushed it accidentaly so many times disassembling everyting so many times. I did however fasten the cooler very hard and thoroughly though.

EDIT: An update on the BIOS is it's from the 18th of May 2010. So that rules out that the BIOS would be old atleast.
 
EDIT: An update on the BIOS is it's from the 18th of May 2010. So that rules out that the BIOS would be old atleast.

Yes, I think we already ruled that out when you mentioned the fact that the system was worked before.  But it is good that you checked back with your friend on this.
 
Ok, so I have an update. Before removing everything I wanted to see what message the Dled would give without the GPU. Guess what? I goes past PROG.CLK to VGA Ini (which is obvious). And what does PROG.CLK mean?

Why is this? That means it basically works but doesn't. I will be so fed if it's that the GPU is not fully inserted, I spent hours this morning trying to get the MB higher up from the motherboard tray to be able to fit the GPU. Because I can't get the MB any higher or else the screws won't reach. I put a nut between the motherboard tray and the motherboard nuts that you fasten the MB to to get the MB 2-3mm higher up.
 
And what does PROG.CLK mean?

At a guess, I'd say 'Program Clock'?

You should have received a D-LED2 Quick Guide in your mainboard box, does it not say anything in there?
 
Oh OK, there is no PDF for it, so I have no idea either. :laugh:

You can always ask MSI about it: http://support.msi.com

 
Back
Top