I agree with running a liveCD OS to test for software issues. Almost always do that to draw the line between software and hardware issues. Try Puppy Linux, if only because of the fast download, cute name, and it is of course, useful as well. SystemRescueCD too. And, to clarify about "fickle memory" - I meant running tests on memory can be tricky, as was mentioned by another individual. Still sounds like it could be spiking power and then lagging power in the supply circuit on the motherboard. Could be a single capacitor or (sadly) impossible to find economically. I hope it is something simple though, like the NIC idea, although those are usually onboard nowadays and a bad IC or circuit there may remain a problem even if not being used. You could try the same idea as our friend suggested of removing peripherals and adding them back by doing something similar in the bios by disabling all nonessential items. Turn off the NIC, the serial port, if applicable, etc. One thing I wasn't sure of: have you tried a different video card? You mentioned replacing the failed monitor in the original post. I always try to go back to previous failures and changes to trace current problems. It may be possible that some sort of power spike during the failure of that old monitor caused an intermittent (or pending) issue in your video card that is now showing up in your system. Since the video subsystem is such a 'major' part of the way we use computers these days and also very tightly bound to the power system and power requirements in a lot of instances, I would at least check it out. DaveC On 10/10/2012 1:24 PM, David P. Connell wrote:
How about the power capacitors and/or ic's on the board itself (as opposed the the power supply)? I have to admit, that is the first thing that came to my mind after reading the first few posts. I'm surprised nobody else went there. Of course, memory is a fickle thing and it still could be that, but I am feeling that it is something else.
DaveC
On 10/8/2012 11:30 PM, Brett Russ wrote:
On Sat, Sep 29, 2012 at 6:19 PM, Chuck Anderson <cra@wpi.edu> wrote:
I agree that the power supply is suspect. You can measure the voltage Alternatively, it may be easier to just try a replacement. I have a new one on the way. I'll reply here with the results. Well, brand new power supply and the system behaves the same
On Mon, Oct 1, 2012 at 7:57 AM, Brett Russ <bruss@alum.wpi.edu> wrote: problematic way as before.
So next try is the memory, as another list reply suggested. I've had memtest86 running against both DIMMs for 47+ hours and counting, 70 total passes so far, and 0 errors. Remember I'd already tried removing first one DIMM, then the other, and the problem repro'd either way. So by these measures it'd seem the memory is OK? I know some mem problems take days to show up so I'll just leave this running for a couple more days anyway.
Not much more I can do here, as I've seen repros with most everything else unplugged so I'm now thinking it must be the motherboard. Perhaps I will try reseating the CPU--haven't done that yet.
Recall the system is having trouble POST'ing: it hangs at various points before BIOS POST completes, i.e. I don't get a confirming 'beep' at end of POST and in some cases the monitor won't wake, other cases the BIOS splash screen stays splashed, etc. The full original email is here: http://mail.wlug.org/pipermail/wlug/2012-September/008059.html
Anyway, if anyone has other ideas here I'd welcome them.
Thanks again, Brett _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- David P. Connell "Watch where you're going; remember where you've been."