Originally posted by: excalibur313
I'm sorry to be repetitive but I was curious if my problem could be probed further. I had my computer on after having it on for about 24 hours total and 12 hours this session it was in sleep and it just turned off.
Well, symptoms like that could be due to a bad/underpowered PSU. I had a friend with a TigerDirect system, he added a V3 AGP card (to a generic Super7 board), the "220W" PSU could handle it, it would only power-on about half of the time. Sometimes there seemed to be a method to it (immediately turning off and on again, vs. waiting for an hour then turning it on), and sometimes it seemed to depend entirely on the phase of the moon. Eventually, we tried a new "250W" (but also better-quality) generic house-brand CompUSA PSU in there, and it had no problems, and later also handled the addition of more drives and things just fine. (You can imagine how poor-quality/low-end the stock T-D PSU was, if a CompUSA generic compared so favorably to it.)
Originally posted by: excalibur313
I don't really have the option to try this processor in another motherboard but i was curious what would happen if a motherboard was fine but the processor was broken. Would it still boot up or make some sounds? Furthermore when trying a friends crappy power supply it started to smoke but it did cause the cpu fan to spin a minute after the power button is pressed.
Uh-oh. Smoke = Bad Sign. Potentially, could have killed the mobo and/or anything attached to it, but who is to say that the mobo wasn't already kind of bad and killed the supply too. (And it died because it was an el-cheapo, instead of just safely shutting down like a decent supply would.)
Originally posted by: excalibur313
Nothing appeared on the screen though. Can anyone make any sense out of this? I just want to make sure that I am doing the right thing sending back the motherboard and that it isn't the processor (too?)
Thanks,
Stephen
I kind of hate diagnosing systems like that. You don't know which part has failed, exactly, and by swapping components with other known-good ones, you run the very valid risk of killing them too, and you don't learn anything additional about the problem component when that happens either.
In fact, I had a similar thing happen to a friend of mine a few months ago, case/PSU or mobo died, testing mobo with other PSUs killed it, etc. Not a good scene.
Depending on how much you have to spend on a replacement, I would replace *both* the PSU and mobo, possibly, and just throw the old ones into the "junk bin" or something. Alternatively, if you have a pretty-stout (and self-protecting PSU, not a cheapo), you could try it with that one.
Oh, and before I forget, they also sell just straight-up PSU testers too, that could help to diagnose isolate the PSU itself.
I agree with
stevty2889, CPUs, generally, don't go bad, unless you insert/remove them with the power on, or physically abuse/damage them. (Or overvolt/overheat them, but that requires a running system first to do so.)
I actually killed my favorite mobo, an Abit BX6-r2, during a failed Tualatin Slotket mod. It just wouldn't "go", so I started changing jumpers in desperation. (
Always a bad idea - don't ever do that. I was just mad at it.
) Well, the slotket had voltage jumpers, and I also wire-modded the CPU vcore, and ended up shorting vcore to gnd on the slotket. Well, I fried my mobo's CPU VRM circuits pretty good, and I've never seen a CPU heatsink heat up
that quickly. Yet, amazingly, that CPU survived just fine, and lived to tell the tale happily running in an ECS P6S5AT board. Go figure.
So CPUs tend to be fairly robust, and I wouldn't be all that afraid of sticking an unknown CPU into a working system, as long as it's not physically damaged or charred.
Facebook
Twitter