Emergency Christmas help needed

[oksza]

Hi LTT Forums,

I have an a baffling emergency - a problem I've given up on trying to solve. Let me preface that by saying I've build computers since early 90's and built a few, so some experience is there.

I'm trying to upgrade my son's old rig for Christmas, he has my ancient Intel machine that’s 10 years old, its only upgrade being a new Gigabyte 1650S I bought for him a year ago.

I bought an MSI PRO B660M-B and an Intel Core i3-12100F, and a Kingston Fury Beast 16GB kit, and some M.2 SSD.

Yesterday, I assembled all of that, connected my old Corsair SF Series SF600, booted up nicely, proceeded to a Windows install and the system died abruptly.

MSI EZ-Debug light turned red on the CPU led. Disassembled, checked the pins, re-pasted, re-seated, same thing. Also tried a couple of other PSUs, nothing changed. Checked the net and found this: https://forum-en.msi.com/index.php?threads/msi-h410m-pro-e-not-work-if-dual-channel.372313/#post-2108089

but no solution mentioned there helped.

Today, I said screw this, went out and bought a gigabyte bv660m, decided this must be MSI’s fault. Nope, Gigabyte board does the same thing, with different PSUs. Boots up, spins the fans, and resets.

I’ve never been so puzzled. I keep thinking maybe I’m doing something wrong with the CPU install (my first encounter with the 1700 socket), but I really doubt that. There’s no obvious compatibility issues as well.

Help me LTT Forum, you’re my only hope.

 

[NotFakeName]

Since you have tried different motherboard and psu, then try different cpu

[oksza]

5 minutes ago, NotFakeName said:

Since you have tried different motherboard and psu, then try different cpu

Yeah that would be my first thought, but I don't have a 1700 socked cpu around and I wanted to install this for him tomorrow for christmas...

[zipspence]

Im in the same camp that NotFakeName is in on this issue. CPU is most likely the issue here

[Applefreak]

14 minutes ago, oksza said:

Hi LTT Forums,

 

I have an a baffling emergency - a problem I've given up on trying to solve. Let me preface that by saying I've build computers since early 90's and built a few, so some experience is there.

 

I'm trying to upgrade my son's old rig for Christmas, he has my ancient Intel machine that’s 10 years old, its only upgrade being a new Gigabyte 1650S I bought for him a year ago.

 

I bought an MSI PRO B660M-B and an Intel Core i3-12100F, and a Kingston Fury Beast 16GB kit, and some M.2 SSD.

 

Yesterday, I assembled all of that, connected my old Corsair SF Series SF600, booted up nicely, proceeded to a Windows install and the system died abruptly.

 

MSI EZ-Debug light turned red on the CPU led. Disassembled, checked the pins, re-pasted, re-seated, same thing. Also tried a couple of other PSUs, nothing changed. Checked the net and found this: https://forum-en.msi.com/index.php?threads/msi-h410m-pro-e-not-work-if-dual-channel.372313/#post-2108089

 

but no solution mentioned there helped.

 

Today, I said screw this, went out and bought a gigabyte bv660m, decided this must be MSI’s fault. Nope, Gigabyte board does the same thing, with different PSUs. Boots up, spins the fans, and resets.

 

I’ve never been so puzzled. I keep thinking maybe I’m doing something wrong with the CPU install (my first encounter with the 1700 socket), but I really doubt that. There’s no obvious compatibility issues as well.

 

Help me LTT Forum, you’re my only hope.

 

 

Except for replacing the CPU, you can try updating the BIOS first. On MSI you probably need to update to a newer BIOS, Gigabyte shows compatibility out of the box but it can't hurt to update it. It's odd that it worked for a short time and now it doesn't. I'd also try swapping the PSU. Maybe the CPU EPS line on the PSU gave out, I've seen it happen on used PSUs before, not very common but it does happen. For testing purposes you can use something less powerful as well or have the GPU out, it should throw a VGA error instead, which is fine because it is comes after the CPU and only if the CPU is ok. One more thing, and that is probably not the case, try turning the system on with the M.2 SSD removed. And the obvious one, make sure that all the connectors on the motherboard and the PSU are inserted all the way. Any way you can get your hands on a compatible CPU to test out, maybe you know someone who would test your CPU on their system?

[oksza]

This is strange bc always thought CPUs are really thouroughly tested - I was not expecting the CPU to be faulty.

[BiotechBen]

3 minutes ago, oksza said:

This is strange bc always thought CPUs are really thouroughly tested - I was not expecting the CPU to be faulty.

Sometimes it can slip through QC or QA with being seemingly fine, but have some issue that renders it essentially DOA. With CPUs, you get a bathtub failure curve.

[oksza]

24 minutes ago, Applefreak said:

Except for replacing the CPU, you can try updating the BIOS first. On MSI you probably need to update to a newer BIOS, Gigabyte shows compatibility out of the box but it can't hurt to update it. It's odd that it worked for a short time and now it doesn't. I'd also try swapping the PSU. Maybe the CPU EPS line on the PSU gave out, I've seen it happen on used PSUs before, not very common but it does happen. For testing purposes you can use something less powerful as well or have the GPU out, it should throw a VGA error instead, which is fine because it is comes after the CPU and only if the CPU is ok. One more thing, and that is probably not the case, try turning the system on with the M.2 SSD removed. And the obvious one, make sure that all the connectors on the motherboard and the PSU are inserted all the way. Any way you can get your hands on a compatible CPU to test out, maybe you know someone who would test your CPU on their system?

Thank you, there's some ideas there I did not think of. I've tried different PSUs, but I will try tomorrow as well without GPU and with one from my personal rig. BIOS update is not something I cconsigered, but does not hurt I guess.

[oksza]

22 minutes ago, BiotechBen said:

Sometimes it can slip through QC or QA with being seemingly fine, but have some issue that renders it essentially DOA. With CPUs, you get a bathtub failure curve.

This would be my first, but I guess there'd be no other choice here by elimination...

[vertigo220]

Dealt with an issue in just the past couple days with someone else in a forum where it was the CPU. It's very rare but does happen. I agree this sounds like CPU, but an easy thing you can try is to use just one stick of RAM at a time and try different slots. Probably not the issue but a quick test just to be sure.