MSI K7D Master-L Problem

[neorowen]

I've been tring to figure this out in another forum ( Click here to see the full thread ) without much luck.

I have a K7D Master L, bios 1.6, two MP 2400's, and 2 sticks of corsair 512mb ram. The problem is the board won't start up in 133 mode. It'll post from a cold boot but then start rebooting itself endlessly or freeze on the cpu detection. In 100 mode it'll start but then not detect a keyboard once windows xp install started running.

I really need help with this and have been working on it since 2/03. Also I have replaced all the hardware attached and tried a new PSU.

[jphelzer]

Welcome to the forum!

I'm going to move this to our dual processor forum. Good luck with the resolution!

[danzcool]

well I'll comment, even though I don't have a resolution. I tried to do 2400+ CPU's on an MSI K7D board without success. At the time they only had the 1.5 BIOS available, I would be able to run a single 2400+ processor, but no go on dual. I know there wasn't anything wrong with the processors because they are now working fine in my iwill mpx2. The thought at the time (11/2002) was that MSI was having trouble with the voltage regulation. Also, the CPU's showed up a 2 XP * 2400+, that was probably fixed with the 1.6 BIOS (or maybe they upgraded the 1.5). I was also using a 420 watt P/S. It turned out there were other problems with the board itself, but everyone else was having the same types of issues with the 2400+ CPUs and the K7D board. My only thought as to how to get it to work would be to get a higher rated P/S, better heatsinks (than retail), and bump the vcore voltage up to 1.85

Good luck, and maybe someone else here has had better luck and can tell you definitively what to do to get it to work.

[desertdave]

neorowen,
Geez, can't believe I just spent the last 30 minutes perusing your posts on 2cpu.com

One thing that came to light (and danzcool mentioned his experience), was that you never ran it with one cpu. Did I miss something? Or were you always running with two?

I had some really strange probs with my Tyan Tiger MP until I finally removed one.........still can't figure out why....check Tyan Motherboards here to see what I'm talking about.

One last note, with the different video cards you used.....did you ever throw in a PCI video card just to see what might happen?

OK, just one more final note! Dude, have you prayed to the computer gods lately?!? They are really mad at you!!!

Best of luck to ya!
desertdave

[64026402]

My Asus boards both had problems memory at 133 fsb.
The first one I manually changed the memory timings and had no more problems.
The second one I had my cheap ddr in the board. Ran fine at 100 but not at 133. Changed to crucial and it ran fine.
My MSI boards like registered. Is you memory registered.

The only other time I had a similar problem it was the PS.
The PS had enough to run one proc of both at a lower fsb/mhz setting.

Also make sure the heat sinks are well seated.

[neorowen]

I tried it with one cpu in the past, nothing new. MSI said they'd email me a new bios tomorrow. I'm hopefully about it.

I tried an old diamond stealth pci video card in there at one point, not anything new. It seems to be pretty stable now, just no 133 mode.

I didn't think corsair qualified as "cheap" memory. I really think it is the memory though, windows starts to boot in 133 and then just bombs. I just have no idea how to solve the issue.

[64026402]

Originally posted by neorowen
I tried it with one cpu in the past, nothing new. MSI said they'd email me a new bios tomorrow. I'm hopefully about it.

I tried an old diamond stealth pci video card in there at one point, not anything new. It seems to be pretty stable now, just no 133 mode.

I didn't think corsair qualified as "cheap" memory. I really think it is the memory though, windows starts to boot in 133 and then just bombs. I just have no idea how to solve the issue.

The comment about cheap memory was just my experience.
Corsair should work fine but stranger things have happened.
Make sure you ecc isn't on.
I would grab a stick of registered ram of a different brand. There could always be an unsual compatabilty issue.

[neorowen]

Actually ecc is on, it's set for correct and scrub. Is that a problem?

[Beezyweez]

NeoRowen,

Have you checked your D-LED configuration when the bios hangs? I've found that to be very helpful for diagnosing boot problems such as memory, HDD access, OS loading, etc.

Right now I'm running a 1700 Tbred B hard-modded to (15x133 w/ 1.775 vcore) that boots as a 2400+. I'm actually now running it at MP2600 (15x140 w/ 1.825vcore) with no hitches and I've got the 1.5 bios. I run Antec Trupower430 in this rig.

I agree with the 64026402 as I tried to boot with a stick of Samsung 512 ECC non-reg and it beeped like a banshee. Stuck a stick of 512 Registered ECC crucial in and it purrs like a kitten.

[64026402]

Originally posted by neorowen
Actually ecc is on, it's set for correct and scrub. Is that a problem?

If your memory is not registered then it could be a problem.
Turn the ecc off or disable then retest.

[neorowen]

My memory is registered. Still having problems in 133 mode, I ordered a stick of crucial memory to see it's just that model of chip that is not compatable.

[64026402]

Did you turn off ecc just to be sure it wasn't bothering your machine.

[Tkon]

I have a K7D Master, with 2 x 2400MPs, and while it boots fine, the BIOS only recognizes one cpu. I had to update the BIOS to even recognize the 2400MP, but that didn't help with the single CPU issue.

Any thoughts on why only one CPU is identified by the BIOS?

Also, the BIOS reports BOTH CPU's temperature as being about 10 degrees Celcius hotter then my Digidocs 5 reports. Has anyone else with this combination noticed the onboard temperature reading are inaccurate?

Thanks for you help in advance.

[neorowen]

Yes I turned off ECC, I also tried all sorts of different memory settings. Tomorrow a stick of crucial ram is arriving, I'll see if that'll help me.

[poopygood]

Originally posted by Tkon
Also, the BIOS reports BOTH CPU's temperature as being about 10 degrees Celcius hotter then my Digidocs 5 reports. Has anyone else with this combination noticed the onboard temperature reading are inaccurate?

Thanks for you help in advance.

I'm pretty sure that the MSI reads the temp from the diode, not a socket resistor, (there is no temp sensor inside the socket) so the temps will be higher than your digidoc 5, as that reads the temp on the outside of the CPU.