Spontaneous closing

[Guest]

Having a pesky sporatic problem with a program window closing spontaneously.
I frequently run several instances of the same telnet program simultaneously.
Have been doing this for years on multiple computers without any problems.
But on a new laptop I got a couple of months ago, one or more of the
instances will occasionally close for no apparent reason, with nobody
touching the computer. At first, I thought I was going crazy, but it has
happened enough times that I know it is real. Has never happened with the
same software on any other computer, so I don't think it's the particular
piece of software but rather something in the particular computer or Windows
installation (or some other piece of software running in the background). It
happens when the telnet software is not active or online - I launch the
window but before I connect to anything with telnet, so I don't think it's
anything network-related. Doesn't happen immediately on launching the
software, but minutes or hours later, usually when the computer is unattended.

I'm running XP SP2 with all the patches, Symantec anti-virus/anti-spyware,
Symantec Protection Agent firewall. I've run hardware diagnostics on the
computer, but nothing turned up. Computer is an Intel Core2 @ 1.83 GHz, with
1GB of ram. The Event Viewer doesn't have anything unusual after a window
closes, and SAV and SPA don't have anything interesting in their logs. It
only happens occasionally - overnight perhaps 1/3 to 1/2 of the nights. I
have seen it happen a couple of times, and I wasn't touching the computer,
and nothing unusual was going on.

I don't think it's a spurious mouse click on the close button, since it also
happens when I've started a VB script in the software that just waits for a
time of day to launch the telnet connection - the script running then
prevents the software from closing on a single click (you get a window asking
if you want to halt the script, so it would take 2 clicks at different
locations). And there are no cats in the house climbing on the keyboard.

Any ideas of how to diagnose and fix this problem? Has anybody ever heard
of a similar weird problem? Thanks in advance for any
ideas/suggestions/solutions.

 

[Guest]

Had this problem but not to the degree of yours.
Found out it was the AVprogram trying to auto update. And when it couldn't
find a web access or make one, the program I was running at the same time
would just close.
I came by this because the program I would run would close at the same time
of day. And doing checks through the system I noticed the AV program was set
to auto-update at that precise time. Turned auto-update off and all is well.

 

[Guest]

I can confirm that it is NOT due to an autoupdate. I just had a window close
in front of my very eyes - was sitting at the computer but not touching it.
Checked the logs of my Antivirus and Firewall - nothing out of the ordinary
there. Last auto update was hours ago. Nothing in the event viewer.

I should also note that I get an occasional complete crash of this machine
with an IRQ error.

 

[Guest]

I have experienced the random closeing in the last day. Not shut downs but
just a window closes to nothing but desktop.
I have "Defender Pro 5in1 2007". I had just installed the "Anti-Spam" and
Anti-Spy"
Which are two of the 5.
After the install,configuration and updating of these is when the
window/page closing started.
I went back and uninstalled these programs. And all is well again.
I do not know if this may be your problem but I thought it may give you
another direction.
If you remember the day/time all this started?
Hope this helps?
You might check to see if any new software was installed just prior.

 

[Bob I]

Usually the "IRQ" error is actually "IRQL", and caused by a software
driver which will usually be listed in the complete error message, along
with the stop code.

 

[Guest]

Sorry, it is IRQL_NOT_LESS_OR_EQUAL and gives Stop 0x0000000A. I did not see
a driver listed, but it happens frequently enough that I may be able to post
it in a couple of days. After rebooting and attempting to transmit the error
report to MS, invariably it says that the error report is corrupted. I'm not
certain if the BSOD crashes are related to the windows spontaneously closing,
or just another problem with this machine. Very frustrating for an expensive
notebook that is 2 months old.

 

[Bob I]

When you get the code look here
http://aumha.org/a/stop.htm