Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

frequent & random crashs in winXPpro


  • Please log in to reply
2 replies to this topic

#1 phawgg

phawgg

    Learning Daily


  • Members
  • 4,543 posts
  • OFFLINE
  •  
  • Location:Washington State, USA
  • Local time:12:44 PM

Posted 04 November 2004 - 02:00 AM

A little known fact: When Dorothy woke up in OZ, she and lil' Toto met some characters who needed to see the Wizard. Before she met the Tinman, Scarecrow & the Cowardly Lion she came across another strange guy wandering towards the Emerald City on the Yellow Brick Road. He had a green-gauze wrapped face and talked in way that was most difficult to understand, she thought. "Who are you?" she asked him as he muttered about error message dialog boxes & 'puter crashes. "I'm Phawgg and I'm so annoyed right now". After introducing herself politely and asking where she was, and as soon as Toto stopped growling in a low menacing way, he continued. "I'm off to see the wizard to find out why this darned box is givin' me fits. He's in that big city over that way and they say he knows all about the operating system." "Well, I sure hope you find him", she said in an innocent but sincere manner, to which his reply was "I do too, kid, and I'll probably see you there. Be careful in those ruby shoes, they sparkle plenty and ya' never know who's gonna slip in off the superhighway onto this old brick pathway. Don't take any wooden horses" and off he went leaving her wondering what to do next.

This I know because I am Phawgg.

Seems to me its taking me forever to understand the operating system that I've reloaded nine times this year. Heck, I've been here at bleeping computer since July and still haven't got a decent avatar to call my own. Anyway, today my computer has randomly auto-rebooted (crashed) 5 times. 3 of them trying to post details about it. In between I've been following leads prompted by the OS about how to fix it. Awfully nice of it to try, and I of course have attempted to self-analyze it's errant behavior as well.

Stay tuned for the continued developments. I need to watch the news to see who's Governor in Washington and take a break from this before it crashes again. :thumbsup:
patiently patrolling, plenty of persisant pests n' problems ...

BC AdBot (Login to Remove)

 


m

#2 phawgg

phawgg

    Learning Daily

  • Topic Starter

  • Members
  • 4,543 posts
  • OFFLINE
  •  
  • Location:Washington State, USA
  • Local time:12:44 PM

Posted 04 November 2004 - 12:33 PM

I still don't know who governs Washington yet, and I'll spare y'all the details of how I saw Toto pull the curtain back to expose the "All and Mighty Wizard of Oz" to be a smallish guy with glasses and a microphone. I do have problems with the PC, and when I do I'm sitting in front of a monitor looking at it. Next to me is the computer in a tower box making sounds. I've gotten used to the sounds it makes as I work with it. When something goes wrong, I can usually see evidence of the problem on the screen and sometimes I can hear a difference in the sounds it makes. A steady whirr is the most common sound. Also common are the sounds it makes at a normal boot sequence. A higher pitched whirr of the CD-RW "winding up". Some clicking noises. The distinct sound of connecting via dial-up modem to an ISP. Typical stuff. Spending hours at task using the PC gives you a "feel" for how it works by repetition of these little clues.

What I am going to do with this post is discuss what to do when things go haywire. I'm pretty sure most people who post problems here have put some time into trying to solve those problems before they post. That time I've found to be generally frustrating and leads to some degree of anger or annoyance. Why? Shouldn't I expect the PC to do a lousy job of operating? Periodically fail to do what it once did? Like a car, shouldn't I expect it to simply stop if it runs out of gas? Stumble if I ask it to do a lot of things simultaneously?

No. I expect it to run consistantly.

When it fails to do something it normally would do, my first thoughts are:
  • What did I do wrong?
  • How can I fix it?
Quickly following those thoughts are:
  • What exactly is IT doing wrong?
  • How should I react to IT'S self-correcting and/or error reporting functions?
The problem will be either:
  • Hardware related
  • Software related
  • or (less frequently) maybe both
If it's hardware related I must think about companies selling products.
If it's software related I must think about:
  • Microsoft Corporation
  • One of several shareware, freeware or retail software program authors
  • nameless, faceless "malicious hackers" or malware enthusiasts on the Web
Like it or not, those are typically the thoughts that lead to action when... I have to fix a problem. I've found that 90% of the time, the operating system sold by Microsoft Corporation is right in front on the list, mainly because it's product has alerted me to the problem in the first place. In fact it's product has been designed to popup dialog all the time, telling me stuff about everything else, even when my PC is experiencing no detectable problems at all.

That will be the subject of this thread. Dealing with how the OS deals with the problems. This I find to be difficult. If it were not so, forums like this would not be so busy, I'd think. This subject has taken me hours & hours of study to get where I am understanding it. I'm sure I'm not alone... I have not gone to college to learn how to use Windows Whatever Version. I am learning, though, and I'll share what I've learned. :thumbsup:
patiently patrolling, plenty of persisant pests n' problems ...

#3 phawgg

phawgg

    Learning Daily

  • Topic Starter

  • Members
  • 4,543 posts
  • OFFLINE
  •  
  • Location:Washington State, USA
  • Local time:12:44 PM

Posted 05 November 2004 - 12:17 AM

The GovernorRace is still undecided, apparently due to the slowness of counting the record numbers of absentee ballots. Hmmm. Oh well, I'm not goin' to mention a word about computerization & politics in this state. I'd rather sweat it out over an old HP keyboard and be patient about knowing whose in charge of the whole state executive branch. huh?

What I am going to do with this post is discuss what to do when things go haywire. I'm pretty sure most people who post problems here have put some time into trying to solve those problems before they post. That time I've found to be generally frustrating and leads to some degree of anger or annoyance. Why? Shouldn't I expect the PC to do a lousy job of operating? Periodically fail to do what it once did? Like a car, shouldn't I expect it to simply stop if it runs out of gas? Stumble if I ask it to do a lot of things simultaneously?
No. I expect it to run consistantly.
When it fails to do something it normally would do, my first thoughts are:

    * What did I do wrong?
    * How can I fix it?


RANDOM AUTO-REBOOTS (CRASHES) in winXPpro
So, it's Election Day and I'm at my PC mindin' my own business. After spending Halloween reloadin' the OS for a couple good reasons I'll skip the details of, I'm back online postin' here at BC. Suddenly the screen goes *black*. Subito as they say in sheet music... suddenly. I sit in uneasy anticipation of what will happen next. In under a minute, plenty long enough to think those things I just mentioned, the black screen goes away and since I am the only user (phawgg) in addition to the Administrator (password controlled) that was automatically setup when I loaded the OS, I just see the welcome screen and then my desktop. All programs that were open are of course not any longer and I'm not online anymore. This dialog box then appears:
Posted Image
I've encountered it before, so my first thought is to close it and get on with what I was doing instead of being side-tracked off on a wild goose chase. I do that and carry on like nothin' happened, but am more alert to the operations of whatever I'm doing. I might double-check the task manager and I'm probably am goin' to be slower about having a dozen open browser windows and stuff, but basically I let it go. A fluke thing. Something happened, but I'm not overly concerned.
Let's backup a moment, though. Suppose we pay attention to what the OS has to say, and read the box and make a decision based upon what it says. Actually we must, because it won't just go away.
1. The system has just recovered from a serious error. (I'd have to agree. I'd been working for several minutes at a real important post and it's gone. Pooff.)
2. A log of this error has been created. (Hmmm. That's interesting. Where?)
3. Please tell Microsoft about this. (Why? Will they fix it free? Now?)
4. We have created an error report that you can send to help us improve Microsoft Windows. (I can freely help the creator. Will it help me? How? New improved Windows, I guess)
5. We will treat this report as confidential and annonymous. (Its secret and we don't know you.)
6. Option one of three is "To see what data this report contains click here." (realizing my attitude must be wrong, and still suffering from ignorance, I do that)
Posted Image
The report details. Top two lines I have to admit I don't understand. Reading on I get a patiently presented legalesque explanation that basically tells me nothing about my problem. I respond, for the purpose of this lesson, with equal patience.
1. Option one of three is "To view technical information about the error reort click here." (this would be what I lack at the moment)
2. Option two of three is "To see our data collection policy click here" (I'm not particularrly interested in the further legal ramifications of a creator/user who bought it relationship right now)
3. Option three of three is "Close" (and admit defeat in a practical manner, as I still haven't a clue whats really wrong. So maybe... back to the top again)
Posted Image
I'm still stumped. This much I know... if I click for more technical information it will be at some risk of spending time searching for the answer. (I'll be guilty for a moment of selfishly wanting to get back to what it was I paid to be doing and simply click "close". As you will soon see the technical information can be gotten in more ways than just this one.)
So, a few mouse clicks and everything seems back to normal, sorta, and I resume my online status. Good, until a couple hours later it happens suddenly again.

This time, I ignore the dialog box in favor of checking out the Event Viewer. I right-click My Computer-->Manage-->Event Viewer.
Posted Image

Here I choose Application first, and scroll down through the log.
Posted Image
I see some warnings so I choose Action-->Save As-->text(.txt) in My Documents. I check it out there, where it resides in a notepad file. I choose to OpenWith-->Wordpad. This log shows exactly what has occured since I reloaded the OS on Halloween. I change the warns to red typeface. Nothing particularly unusual for this machine under these circumstances I notice, and having sought the meaning of all of it more than once before, I'm content to accept it as typical. For the time being. Nothing coincides with the exact times I had the problems with random crashes.

11/4/2004 12:09:01 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1024) The database engine stopped.
11/4/2004 12:09:01 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1024) SUS20ClientDataStore: The database engine stopped the instance (0).
11/4/2004 12:04:01 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1024) SUS20ClientDataStore: The database engine started a new instance (0).
11/4/2004 12:04:01 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1024) The database engine 5.01.2600.2180 started.
11/4/2004 12:03:23 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/4/2004 8:04:00 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1072) The database engine stopped.
11/4/2004 8:04:00 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1072) SUS20ClientDataStore: The database engine stopped the instance (0).
11/4/2004 7:59:00 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1072) SUS20ClientDataStore: The database engine started a new instance (0).
11/4/2004 7:59:00 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1072) The database engine 5.01.2600.2180 started.
11/4/2004 7:58:23 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/4/2004 2:28:23 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (908) The database engine stopped.
11/4/2004 2:28:23 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (908) SUS20ClientDataStore: The database engine stopped the instance (0).
11/4/2004 2:23:23 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (908) SUS20ClientDataStore: The database engine started a new instance (0).
11/4/2004 2:23:23 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (908) The database engine 5.01.2600.2180 started.
11/3/2004 11:33:46 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1048) The database engine stopped.
11/3/2004 11:33:46 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1048) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 11:28:46 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1048) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 11:28:46 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1048) The database engine 5.01.2600.2180 started.
11/3/2004 10:30:20 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1696) The database engine stopped.
11/3/2004 10:30:20 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1696) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 10:22:04 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1696) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 10:22:04 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1696) The database engine 5.01.2600.2180 started.
11/3/2004 10:21:52 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (748) The database engine stopped.
11/3/2004 10:21:52 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (748) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 10:15:28 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (748) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 10:15:28 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (748) The database engine 5.01.2600.2180 started.
11/3/2004 10:14:48 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 10:13:46 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (232) The database engine stopped.
11/3/2004 10:13:46 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (232) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 10:08:28 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (232) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 10:08:28 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (232) The database engine 5.01.2600.2180 started.
11/3/2004 10:04:21 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (484) The database engine stopped.
11/3/2004 10:04:21 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (484) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 9:59:11 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (484) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 9:59:11 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (484) The database engine 5.01.2600.2180 started.
11/3/2004 9:56:56 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1380) The database engine stopped.
11/3/2004 9:56:56 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1380) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 9:48:07 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1380) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 9:48:07 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1380) The database engine 5.01.2600.2180 started.
11/3/2004 9:45:24 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (964) The database engine stopped.
11/3/2004 9:45:24 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (964) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 9:40:19 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (964) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 9:40:19 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (964) The database engine 5.01.2600.2180 started.
11/3/2004 9:34:24 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (428) The database engine stopped.
11/3/2004 9:34:24 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (428) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 9:29:24 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (428) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 9:29:24 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (428) The database engine 5.01.2600.2180 started.
11/3/2004 9:28:49 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 9:24:29 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (348) The database engine stopped.
11/3/2004 9:24:29 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (348) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 9:19:29 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (348) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 9:19:29 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (348) The database engine 5.01.2600.2180 started.
11/3/2004 9:18:52 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 9:14:52 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (580) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 9:14:52 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (580) The database engine 5.01.2600.2180 started.
11/3/2004 9:14:49 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 9:13:46 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (396) The database engine stopped.
11/3/2004 9:13:46 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (396) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 9:08:45 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (396) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 9:08:45 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (396) The database engine 5.01.2600.2180 started.
11/3/2004 9:08:10 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 9:01:23 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (428) The database engine stopped.
11/3/2004 9:01:23 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (428) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 8:56:22 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (428) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 8:56:22 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (428) The database engine 5.01.2600.2180 started.
11/3/2004 8:55:48 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 7:47:12 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (628) The database engine stopped.
11/3/2004 7:47:12 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (628) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 7:42:11 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (628) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 7:42:11 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (628) The database engine 5.01.2600.2180 started.
11/3/2004 7:41:36 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 2:23:57 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (404) The database engine stopped.
11/3/2004 2:23:57 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (404) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 2:18:57 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (404) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 2:18:57 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (404) The database engine 5.01.2600.2180 started.
11/3/2004 2:18:22 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 12:44:42 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (312) The database engine stopped.
11/3/2004 12:44:42 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (312) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 12:39:42 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (312) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 12:39:42 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (312) The database engine 5.01.2600.2180 started.
11/3/2004 12:39:07 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 11:28:24 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (112) The database engine stopped.
11/3/2004 11:28:24 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (112) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 11:23:19 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (112) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 11:23:19 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (112) The database engine 5.01.2600.2180 started.
11/3/2004 11:05:39 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (328) The database engine stopped.
11/3/2004 11:05:39 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (328) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 11:00:38 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (328) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 11:00:38 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (328) The database engine 5.01.2600.2180 started.
11/3/2004 11:00:01 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 2:50:11 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (632) The database engine stopped.
11/3/2004 2:50:11 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (632) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 2:45:10 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (632) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 2:45:10 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (632) The database engine 5.01.2600.2180 started.
11/3/2004 2:44:34 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 1:33:28 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (408) The database engine stopped.
11/3/2004 1:33:28 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (408) SUS20ClientDataStore: The database engine stopped the instance (0).
11/3/2004 1:31:48 AM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
11/3/2004 1:31:48 AM LoadPerf Information None 1001 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
11/3/2004 1:28:27 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (408) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 1:28:27 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (408) The database engine 5.01.2600.2180 started.
11/3/2004 1:27:51 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 1:27:01 AM Userenv Warning None 1517 NT AUTHORITY\SYSTEM GRAYCASE9 Windows saved user GRAYCASE9\Administrator registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
11/3/2004 1:05:18 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (2024) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 1:05:18 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (2024) The database engine 5.01.2600.2180 started.
11/3/2004 1:04:38 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/3/2004 1:01:16 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (2012) SUS20ClientDataStore: The database engine started a new instance (0).
11/3/2004 1:01:16 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (2012) The database engine 5.01.2600.2180 started.
11/3/2004 1:00:38 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/2/2004 11:43:21 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1968) The database engine stopped.
11/2/2004 11:43:21 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1968) SUS20ClientDataStore: The database engine stopped the instance (0).
11/2/2004 11:38:21 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1968) SUS20ClientDataStore: The database engine started a new instance (0).
11/2/2004 11:38:21 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1968) The database engine 5.01.2600.2180 started.
11/2/2004 11:37:40 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/2/2004 8:12:06 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (136) The database engine stopped.
11/2/2004 8:12:06 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (136) SUS20ClientDataStore: The database engine stopped the instance (0).
11/2/2004 8:07:05 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (136) SUS20ClientDataStore: The database engine started a new instance (0).
11/2/2004 8:07:05 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (136) The database engine 5.01.2600.2180 started.
11/2/2004 8:06:25 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/1/2004 9:47:07 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1952) The database engine stopped.
11/1/2004 9:47:07 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1952) SUS20ClientDataStore: The database engine stopped the instance (0).
11/1/2004 9:42:07 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1952) SUS20ClientDataStore: The database engine started a new instance (0).
11/1/2004 9:42:07 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1952) The database engine 5.01.2600.2180 started.
11/1/2004 9:41:27 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/1/2004 1:00:22 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1984) SUS20ClientDataStore: The database engine started a new instance (0).
11/1/2004 1:00:22 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1984) The database engine 5.01.2600.2180 started.
11/1/2004 12:59:42 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/1/2004 12:58:10 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (340) SUS20ClientDataStore: The database engine started a new instance (0).
11/1/2004 12:58:10 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (340) The database engine 5.01.2600.2180 started.
11/1/2004 12:57:43 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/1/2004 12:42:08 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (2016) The database engine stopped.
11/1/2004 12:42:08 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (2016) SUS20ClientDataStore: The database engine stopped the instance (0).
11/1/2004 12:37:07 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (2016) SUS20ClientDataStore: The database engine started a new instance (0).
11/1/2004 12:37:07 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (2016) The database engine 5.01.2600.2180 started.
11/1/2004 12:36:29 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/1/2004 12:35:07 AM Userenv Warning None 1517 NT AUTHORITY\SYSTEM GRAYCASE9 Windows saved user GRAYCASE9\phawgg registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
11/1/2004 12:26:17 AM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1964) The database engine stopped.
11/1/2004 12:26:17 AM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1964) SUS20ClientDataStore: The database engine stopped the instance (0).
11/1/2004 12:21:16 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1964) SUS20ClientDataStore: The database engine started a new instance (0).
11/1/2004 12:21:16 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1964) The database engine 5.01.2600.2180 started.
11/1/2004 12:20:36 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
11/1/2004 12:16:16 AM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (2036) SUS20ClientDataStore: The database engine started a new instance (0).
11/1/2004 12:16:16 AM ESENT Information General 100 N/A GRAYCASE9 wuauclt (2036) The database engine 5.01.2600.2180 started.
11/1/2004 12:15:39 AM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
10/31/2004 11:44:37 PM ESENT Information General 101 N/A GRAYCASE9 wuauclt (1816) The database engine stopped.
10/31/2004 11:44:37 PM ESENT Information General 103 N/A GRAYCASE9 wuaueng.dll (1816) SUS20ClientDataStore: The database engine stopped the instance (0).
10/31/2004 11:40:20 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:40:20 PM LoadPerf Information None 1001 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
10/31/2004 11:39:34 PM ESENT Information General 102 N/A GRAYCASE9 wuaueng.dll (1816) SUS20ClientDataStore: The database engine started a new instance (0).
10/31/2004 11:39:34 PM ESENT Information General 100 N/A GRAYCASE9 wuauclt (1816) The database engine 5.01.2600.2180 started.
10/31/2004 11:39:31 PM WinMgmt Warning None 5603 NT AUTHORITY\SYSTEM GRAYCASE9 A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
10/31/2004 11:39:31 PM WinMgmt Warning None 5603 NT AUTHORITY\SYSTEM GRAYCASE9 A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.

10/31/2004 11:39:24 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the ISAPISearch (ISAPISearch) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:39:24 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the ContentFilter (ContentFilter) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:39:24 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the ContentIndex (ContentIndex) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:39:24 PM LoadPerf Information None 1001 N/A GRAYCASE9 Performance counters for the ISAPISearch (ISAPISearch) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
10/31/2004 11:39:24 PM LoadPerf Information None 1001 N/A GRAYCASE9 Performance counters for the ContentFilter (ContentFilter) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
10/31/2004 11:39:24 PM LoadPerf Information None 1001 N/A GRAYCASE9 Performance counters for the ContentIndex (ContentIndex) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
10/31/2004 11:39:13 PM MsiInstaller Information None 11728 GRAYCASE9\phawgg GRAYCASE9 Product: WebFldrs XP -- Configuration completed successfully.
10/31/2004 11:38:54 PM SecurityCenter Information None 1800 N/A GRAYCASE9 The Windows Security Center Service has started.
10/31/2004 11:35:04 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:35:04 PM LoadPerf Information None 1001 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
10/31/2004 11:27:02 PM WmdmPmSN Information None 100 N/A GRAYCASE9 The WmdmPmSN service was installed.
10/31/2004 11:27:01 PM WmdmPmSN Information None 101 N/A GRAYCASE9 The WmdmPmSp service was removed.
10/31/2004 11:26:33 PM WinMgmt Warning None 63 GRAYCASE9\phawgg GRAYCASE9 A provider, WMIProv, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
10/31/2004 11:26:33 PM WinMgmt Warning None 63 GRAYCASE9\phawgg GRAYCASE9 A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

10/31/2004 11:10:50 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:10:49 PM LoadPerf Information None 1001 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
10/31/2004 11:10:09 PM EventSystem Warning (52) 4354 N/A GRAYCASE9 The COM+ Event System failed to fire the StartShell method on subscription {A5978620-5B3F-F1D1-8ED2-00FA0035B753}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT 80004001.
10/31/2004 11:10:02 PM MsiInstaller Information None 11707 N/A GRAYCASE9 Product: WebFldrs XP -- Installation operation completed successfully.
10/31/2004 11:09:47 PM Winlogon Information None 1001 N/A GRAYCASE9 The type of the file system is FAT32.

A disk check has been scheduled.
Windows will now check the disk.
Volume Serial Number is 3849-1D0C
Windows has checked the file system and found no problems.
39614592 KB total disk space.
41472 KB in 10 hidden files.
4544 KB in 136 folders.
713248 KB in 5554 files.
38855296 KB are available.

32768 bytes in each allocation unit.
1237956 total allocation units on disk.
1214228 allocation units available on disk.

Converting drive \\?\Volume{ba9eef11-2b8e-11d9-a3b0-806d6172696f} to NTFS...

Convert will take some time to process the files on the volume.
When this phase of conversion is complete, the computer will restart.
Determining disk space required for file system conversion...
Total disk space: 39624291 KB
Free space on volume: 38855296 KB
Space required for conversion: 122151 KB
Converting file system

10/31/2004 11:08:58 PM EAPOL Information None 2001 N/A GRAYCASE9 EAPOL service was started successfully
10/31/2004 11:05:34 PM SceCli Information None 1500 N/A GRAYCASE9 Security configuration was backed up to C:\WINDOWS\security\templates\setup security.inf.
10/31/2004 11:05:10 PM WmdmPmSp Information None 100 N/A GRAYCASE9 The description for Event ID ( 100 ) in Source ( WmdmPmSp ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: WmdmPmSp.
10/31/2004 11:03:23 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:03:23 PM LoadPerf Information None 1001 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
10/31/2004 11:03:23 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:03:19 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the ISAPISearch (ISAPISearch) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:03:19 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the ContentFilter (ContentFilter) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:03:19 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the ContentIndex (ContentIndex) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:03:01 PM MSDTC Information TM 4097 N/A GRAYCASE9 MS DTC started with the following settings:
Security Configuration (OFF = 0 and ON = 1):
Network Administration of Transactions = 1,
Network Clients = 0,
Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 1

10/31/2004 11:03:01 PM MSDTC Information SVC 4104 N/A GRAYCASE9 The Microsoft Distributed Transaction Coordinator service was successfully installed.
10/31/2004 11:02:58 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the MSDTC (MSDTC) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:02:55 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the TermService (Terminal Services) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:02:32 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the RemoteAccess (Routing and Remote Access) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:02:07 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the PSched (PSched) service were loaded successfully. The Record Data contains the new index values assigned to this service.
10/31/2004 11:02:06 PM LoadPerf Information None 1000 N/A GRAYCASE9 Performance counters for the RSVP (QoS RSVP) service were loaded successfully. The Record Data contains the new index values assigned to this service.

There is no data to show in the Event Viewer Security log.
The Event Viewer System log is the last place to check:
Posted Image
Here we see errors, in addition to a warning or two and some events labled as information that do coincide with the exact times of the problem occurances.
[to be continued]
patiently patrolling, plenty of persisant pests n' problems ...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users