| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: [OS2HW] unstable system |
Daniel Lee Kruse wrote:
>--- In os2hardware{at}yahoogroups.com, Ed Durrant wrote:
>
>
>>Daniel Lee Kruse wrote:
>>
>>
>>
>
>
>
>>I'd be looking for the latest firmware (bios) updates for both your
>>
>>
>motherboard and the Network card, with these kinds of symptoms. If the
>card has "wake-on-LAN" capability, turn it off as well.
>
>
>>Cheers/2
>>
>>Ed.
>>
>>
>
>Thanks for the reply.
>
>The motherboard is completely up-to-date on the BIOS firmware. Never
>have updated the firmware on the network card though. I made sure the
>wake-on-LAN option was turned off in the BIOS. When it comes to
>security one can never be too careful. Although all this is moot now
>as the system won't even POST. See my reply to Felix's post on this
>thread for all the gory details.
>
>Have a good day,
>Daniel Lee Kruse
>
>
>
>
Yes I saw your other post. The reason for turning off wake-on-LAN was
not a security question, rather that if not properly implemented, it can
cause this problem.
Back to the major problem.
Power off the system, let it cool down, remove all external cables, open
the case and check there are no points of the motherboard that could be
touching the metal case where they shouldn't be (ie shorting out). Look
very carefully for any burn marks on the board.
If you have an anti-static strap, put it on your wrist and connect it to
the case so that you are at the same potential. If you have no strap,
make sure you are always touching the case with one hand while touching
components with the other. Now remove all plug in components, including,
cables, adapter cards, memory DIMMs. If you are skilled in this area
and have some heatsink paste, also remove the processor, Make sure all
sockets contacts appear clean and no pins are bent.
Now re-assemble everything, ensuring everything "clicks" into place - ie
dont force anything but everything should "positively" sit in their
connectors. Where possible put components in different sockets - eg
memory DIMM pairs in opposite sockets, PCI cards in different sockets.
Make sure once more that there is nothing now on the motherbord that is
touching the case that shouldn't be.
Close the case up and re-attach all external cables. Turn the system on
and go into the BIOS setup, select reset to factory defaults and allow
to re-start.
Now see how you go.
If the problem still exists, power off, open the case again and remove
any components that are non-essential, for example if you have four
memory DIMMs and the system can run with two, remove two. If the DIMMs
in use go in single rather than pairs, go down to just one DIMM. Remove
any adapter cards that are not needed for the system to boot up, eg the
network card.
Once you have the system in the "base" configuration, see if it boots
without any hardware errors (you'll have driver load errors for the
components you removed of course).
If there are STILL problems, try exchanging the memory that is still in
the system with the memory you removed (if appropraite).
Hopefully at some point you will again have a stable system. At this
point power down and start putting the "non-essential" components back
in one by one. Once the problems return - you know which component is
causing the problem, replace it.
Good Luck
Cheers/2
Ed.
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/os2hardware/
To unsubscribe from this group, send an email to:
os2hardware-unsubscribe{at}yahoogroups.com
Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
---
* Origin: Waldo's Place USA Internet Gateway (1:3634/1000)SEEN-BY: 633/267 270 5030/786 @PATH: 3634/1000 12 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.