Pwr. Supply incompatability?

imported_JonLane

Junior Member
Jun 9, 2004
11
0
0
I recently migrated a working AMD MATX mobo/mem/cpu and a working Intel ATX mobo/mem/cpu from one case to another. Power supplies changed, as did some expansion cards, but the rest is unchanged. Neither system will boot to POST or even video. Nothing I can think of brings them to life. Both will run fans, light LED's, seek drives, etc., but no video and no POST. And no floppy seek for a BIOS rewrite.

Obviously this is pissing me off. Is there something I don't know about ATX supplies that's breaking mobos?

Maybe not related, I also had a brand new Intel 915 mobo break its BIOS after I installed a second HD. It was brand new but adding just one more drive may have had something to do with it also not booting. I think it was just a bad board.

So, three different boards, all working, but make one small change and all three bite the dust. New Egg replaced the bad-BIOS Intel board, but I'm on my own with the other two.

Any ideas?
 

montag451

Diamond Member
Dec 17, 2004
4,587
0
0
No hw specs.
But at a guess - you are using the psu that came with the case.
Get yourself a TAGAN 480 or Antec or Enermax etc
 

SuperSilicon

Member
Dec 16, 2005
119
0
0
Im guessing they both work before you switched them around, possible static shock damage? I will reccomend re-seating everything agian checking that everything is firmly in place.
 

Atheus

Diamond Member
Jun 7, 2005
7,313
2
0
Check for shorts, then try the old PSUs again, just sit it on top of the case and plug it in. If it works then you know the PSU is the problem.

No idea about the hard drive thing, but changing a drive can't hurt anything. What do you mean by break the BIOS?
 

imported_JonLane

Junior Member
Jun 9, 2004
11
0
0
Originally posted by: Atheus
What do you mean by break the BIOS?

On the newer Intel 915 board, rebooting after adding the #2 HD didn't succeed. Fans, LED's, video, but no POST. Considering the number of times I've added HD's, this was a real first.

The running main HD was a SATA Hitachi 80meg, the add-in was a working, written Western 80meg non-SATA. Weirdest thing. Resetting the BIOS jumper got me a partial reboot, but every attempt after that just went dead.

Uh-oh: Just occured to me that this afternoon's build bombed on the mobo I'd run that same Western drive in for two years. I tried to use it to boot this new build in a new case with the original Intel 865 board. I wonder if I have a messed up HD that's somehow burning up mobos?

 

imported_JonLane

Junior Member
Jun 9, 2004
11
0
0
Originally posted by: montag451
No hw specs.

Intel 865PERL, 2.4Ghz, 2Gb OCZ 3200 mem, standard WD 80meg. Lian Li case with this supply.

I love that case, by the way. Nice supply too, if the rig just worked...

Like I say, this entire setup ran in another case with a different PS for two years. I can't remember what the PS was, though.

 

SuperSilicon

Member
Dec 16, 2005
119
0
0
Do you have a friend(with hardware you can barrow) you can use to swap and test? If not you should consider taking it to a shop and having things tested. Thats what I had to do since no one I know has the kind of hardware I run.

Its weird that niether system will boot, make sure its not something really stupid first before you end up spending more $$ Check every possible thing u can think of, if your still stumped I would consider moving on with hardware swap.
 

imported_JonLane

Junior Member
Jun 9, 2004
11
0
0
Originally posted by: SuperSilicon
I will reccomend re-seating everything agian checking that everything is firmly in place.

Heh. Reseating the CPU -- it having not budged for two years -- solved the Intel 865PERL problem. Fired right up.

One down, one to go. Now to mess with the AMD.

 

SuperSilicon

Member
Dec 16, 2005
119
0
0
Originally posted by: JonLane
Originally posted by: SuperSilicon
I will reccomend re-seating everything agian checking that everything is firmly in place.

Heh. Reseating the CPU -- it having not budged for two years -- solved the Intel 865PERL problem. Fired right up.

One down, one to go. Now to mess with the AMD.

Good to hear