a BAD windows XP professional bug

Question

I'm going to describe a Windows XP bug (in my opinion) that forces me to manually power down my computer.   Perhaps one out of two hundred requests by a computer application to the operating system result in that application freezing/hanging. Examples of a computer application making a request to the operating system would be: * Open a file * Close a file * Save a file * Go up one folder level The hour glass symbol shows on the application screen. A fascinating characteristic of this bug is that the file/edit/view/etc toolbar goes BLANK. Clicking the X in the upper right corner of the application window normally closes the application, but here has no effect.   I try Ctrl/alt/Delete which brings up the windows task manager. It shows TWO copies of the application running. This is another fascinating clue for anyone who really knows current operating systems. I ask the task manager to end the application. It tells me, 'This application is not responding. End it now?' I respond, 'yes'. But the task manager cannot end either instance of the application.   So I proceed to shut down all other running applications, and then start the 'Close windows' sequence. The close windows sequence takes perhaps 20 times as long as it normally would - again a notworthy clue. Windows FINALLY reaches a point where the screen shows the message 'windows is shutting down'. At that point windows goes no further, no matter how long I wait. The only remaining option is to manually power down the computer.   This problem has shown up in two applications that I run: WordPerfect and AOL software. The fact that it shows up in two different applications and the fact that it happens seldom leads me to suspect that it's a TIMING issue ... where if the timing is slightly wrong in the communication between windows XP and the application, then the application freezes.   I've done some extensive google searches, including searching this forum site to try to find this problem described by other people. Nothing showed up in the search results. Here's an irony. A few minutes ago I talked with a multilevel marketing associate, and he said he has the same problem; but he just lives with it. Wouldn't that be interesting if all kinds of people experience the same problem but 'just live with it' rather than reporting it.   Rich in Minnesota USA   My Fun Stuff for you blog: http://fun-stuff-4u.blogspot.com/

RoHe · Answer

The first thing I'd do is extensive scans for viruses and malware using anti-viral software, Adaware, and Spybot Search & Destroy. If this just started to happen, you could try doing a System Restore to a date when you know it was ok.

If that doesn't fix it, and assuming it's free of malware, run a system file check:

click start>run
type in: sfc /scannow
(space between sfc and /)
click ok

sfc will replace any missing/damaged XP system files. Insert XP CD if sfc requests it. Reboot when it's done.

Ron

rputman · Answer

Thanks for the suggestions, Ron, I followed them. Nothing showed up as a possible cause.

I suspect that the problem is a timing issue related to application requests to the operating system. I.e., an old fashioned bug. I find it very disappointing that these days software manufacturers don't have a simple way for their customers to communicate details of suspected software bugs. In this case, I have a revealing collection of circumstances that could help a capable systems programmer to track down the cause of the problem. Instead, the common software manufacturer attitude is, "There must be something the user can do to solve this problem."

Granted, there is the automated Windows "send a report" system which users routinely encounter. But in all the years of my submitting such automated reports, I have yet to see any evidence that such a report resulted in an actual bug fix.

At least some good news is that I find Windows XP to be more stable than any previous version of Windows I've used. If Microsoft's next operating system can make a similar improvement in stability that will be great. But for now, the problem I've described is still unsolved. The most recent occurrence was yesterday.

Rich Putman in MN USA

RoHe · Answer

Since this is happening with 2 well-known, major apps, I'm not convinced it's a real bug, but perhpas something on your system. Otherwise, lots of people would be screaming about it all over these forums and elsewhere.

You never mentioned how much free hard drive space and RAM you have. It's possible the problem is just related to inadequate PC resources. You should, in order:
a) run chkdsk /f to fix any errors on HD
b) Delete all tmp files
c) Run Windows Disk Cleanup utility
c) Empty internet browser cache
d) Defrag HD
and if all else fails,
e) Run hardware diagnostics on RAM

Ron
I'm glad you used a smaller font this time. Your original post was screaming. ;)

Windows General

Was this post helpful?