Unsolved
This post is more than 5 years old
5 Posts
0
6606
July 28th, 2007 13:00
Optiplex Completely Dead Not A Power Problem-
Client that has a Dell Optiplex 170 which suddenly stopped booting- unit was purchased through the outlet without extended warranty in Feb of '06 and the manufacture date is Jan. The power light flashed orange, went solid orange in the process of booting (at the Windows progress screen) then died. We swapped with a known good power supply and didn't even get a light on the power button. We've swapped with known good cables, reseated all modules and get nothing. The power light on the motherboard lights up when there's juice in the power supply and occasionally if it is plugged in for a while we can get power to cycle on, go orange and then die. There are no POST code tones.
The next logical step is to replace the mobo but before they shell out the 80-90 bucks for a used system pull I wanted to get some idea about whether this sounds like maybe a complete meltdown. What are the odds that the processor is hosed too? I'm reluctant to pull a good one from one of the others in the office for fear that what ever is wrong will hose that one too; likewise for testing the processor in another machine.
Any guidance on this would be appreciated. I've never had something die with zero post codes.
Message Edited by teambnet on 07-28-2007 09:05 AM
No Events found!
rudicollins
207 Posts
0
July 28th, 2007 13:00
Bobman101
693 Posts
0
July 29th, 2007 07:00
No life at all means bad PSU.
Blinking amber light on front can be PSU or motherboard, usually in that order.
Solid amber light on front can be motherboard or PSU, usually in that order.
No diagnostic lights on the REAR and no POST code beeps usually means a bad motherboard, or possibly even CPU, usually in that order.
You do this at your own risk, so if you're hesitant, which you sound it, don't try, but I'd risk trying a CPU from another machine. It's possible, but if the board is simply dead, I doubt it'd kill a CPU if you tried. This way you can at least narrow it down. If you don't want to risk it, by the sounds of things, I'd guess it was the motherboard too anyway.