Re: windows/internet explorer suddenly closes
From: Malke (malke_at_nospoonnotreally.com)
Date: 06/12/04
- Next message: Kevin: "Re: FAT32 not readable by XP"
- Previous message: Davey: "What is a component transfer error?"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: windows/internet explorer suddenly closes"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 12 Jun 2004 08:09:37 -0700
anonymous@discussions.microsoft.com wrote:
> a standalone 2.6GHz, 512MB computer working under XP has a
> problem of closing windows (sometimes file explorer,
> sometimes internet explorer) suddenly without prompting
> any error. The computer is connected to network via a
> 10/100M cable communicating by a network card. The most
> frustrating part of the problem is that I cannot identify
> if there is any action can definitely cause the problem
> and the problem does not always exist, i.e. say, re-open
> IE or re-copy the files from C: to D:, ... one time i
> guess it's due to Google toolbar pop-up blocker but
> disabling it does not make any effect, so as disabling
> remote desktop allowance in the firewall setting.
> actually, i remember even there's no network connection,
> the file explorer also can close itself. if any more
> information can help, i'll be very glad to provide so
OK, we're getting there. I'm still not sure what you mean by "connected
to network" because standalone machines aren't on a lan, but I'm going
to assume you mean "connected to the Internet" by that. In any case, if
the problem is random, that indicates a possible hardware problem.
Usually problems caused by software are repeatable and regular. This is
a generalization, but it's a good starting point. Very often hardware
troubles are solved by swapping out parts with known-good ones. Start
by replacing cables, making sure all connections are good and tight.
Perhaps try a different network card (nic). Otherwise, here are some
generic troubleshooting steps for hardware issues:
1) open the computer and run it open, cleaning out all dust bunnies and
observing all fans (overheating will cause system freezing); 2) test
the RAM - I like Memtest86 from www.memtest86.com - let the test run
for an extended (like overnight) period of time - unless errors are
seen immediately; 3) test the hard drive with a diagnostic utility from
the mftr.; 4) the power supply may be going bad or be inadequate for
the devices you have in the system; 5) test the motherboard with
something like TuffTest from www.tufftest.com. Testing hardware
failures often involves swapping out suspected parts with known-good
parts. If you can't do the testing yourself and/or are uncomfortable
opening your computer, take the machine to a good local computer repair
shop (not a CompUSA or Best Buy type of store).
For your situation, I would start by testing the RAM. You should also
look in Event Viewer (from the Administrative Tools applet in Control
Panel) to see if there are any clues. Also open Task Manager and check
what is running when you have the problem.
Good luck,
Malke
-- MS MVP - Windows Shell/User Elephant Boy Computers www.elephantboycomputers.com "Don't Panic!"
- Next message: Kevin: "Re: FAT32 not readable by XP"
- Previous message: Davey: "What is a component transfer error?"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: windows/internet explorer suddenly closes"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
