Re: Spontaneous closing
- From: Bob I <birelan@xxxxxxxxx>
- Date: Mon, 10 Sep 2007 08:48:24 -0500
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.
vranab wrote:
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.
"poatt" wrote:
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.
"vranab" wrote:
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.
.
- Follow-Ups:
- Re: Spontaneous closing
- From: vranab
- Re: Spontaneous closing
- Prev by Date: Re: Error message in start up C:\Windows\system32\bynglatk.dll
- Next by Date: Re: xp will not boot
- Previous by thread: RE: Spontaneous closing
- Next by thread: Re: Spontaneous closing
- Index(es):
Relevant Pages
|
