222 Operational Errors in Event Viewer

whoa.

check this out -- what does it mean? just dug this up in Event Viewer. i've had errors every day that i've had the computer on. and why is the first error date from APRIL 2008, when my notebook wasn't even made?

clicking on these don't give me much info -- or i'm not looking for it correctly. any ideas?

 

It is probably the left over when they created your system from a master drive.

Clear the log, and check it again later.

cheers ...

 

thanks for the reply.

what do you make of the others though? those warnings start from the date/hour of my fresh install to now.

 

Can you post the actual error codes and/or contents for the boot performance monitoring/shutdown performance monitoring events. I think these are things like "application is taking more than 30 secs to clean up" or stuff like that.

They are probably associated with a few different programs, which may need to be troubleshooted (errr.. troubleshot? lol) individually.

Do you get a new set of entries when you boot and shutdown respectively, every time?

 

Also, to get a little more info on those log entries based on the Event ID, try this website, which will summarize by Event ID number. Keep in mind, many different types of errors can throw up a single Event ID number, so that number alone will not be sufficient to tell you what the error is. For example, here's the listing for Event ID 109 and here's 200.

 

The diagnostics>Performance - Operational Log is a scary place for most people. Everything in it is a warning or error and it uses frightening words like CRITICAL a lot.

Word to the wise --don't worry about it. It can be somewhat useful for diagnosing system bottlenecks but the long and short of it is that on a perfect system with screaming hardware you will still get warnings.

Focusing briefly on the EventID column

100 class errors are start up errors/warnings,which means that in Windows opinion something took longer to load than expected or something did not load

200 class errors are shutdown errors/warnings,which means that in Windows opinion something took longer to shutdown or unload than expected or something did not load

300 class errors are standby or hibernate errors/warnings, which means that in Windows opinion something took longer to load or unload while entering standby than expected or something did not load or unload

The listings are all times (in milliseconds) something took to happen and most of them don't matter much unless your crazy OC trying to get the fastest boot time in the history of computing.

 

You need to either double-click on them, or simply scroll down in the Event Viewer main window to see detailed infomration about the conditions being referenced. But, yes, I agree with Gerry, in most cases the answer is to not worry about the errors from performance monitoring, unless your machine does exhibit problems. In the latter case, the performance log may give you some clues, if you know what to look for...

Boot Peformance and Shutdown Performance error usually are Vista whining about either the boot or shutdown taking a couple of milliseconds longer than it expected, which can happen due to all sorts of entirely harmless conditions.

 

Yeah, the above posters are correct, these are totally harmless events if you are not noticing any delays in shutdown or startup times... definitely don't go too crazy unless there is something locking it up for a long time.

 

Its really only useful for extraordinary delay issues because any given program may appear then disappear from the list. If your computer takes 4 minutes to start, then it might provide something useful

It is also worth noting that leaving your computer on overnight from Tuesday to Wednesday, when Vista performs its normal maintenance, for a couple weeks will allow Windows to reallign your files so some of these programs will be optimized for startup.

The information form this log is culled when defrag tries to place files for faster reading.

 

thanks for the replies, people. good to know that my box isn't breaking down.

still wonder what is causing this though. my Vista isn't tweaked -- the only thing i've changed is de-schedule the defrag and opt out of the experience metrics. i *just* booted up and i have two errors and three warnings .

here's a Boot Performance Monitoring Error

- EventData

BootTsVersion 2
BootStartTime 2009-01-22T16:38:38.656Z
BootEndTime 2009-01-22T16:41:22.130Z
SystemBootInstance 73
UserBootInstance 66
BootTime 65290
MainPathBootTime 31190
BootKernelInitTime 14
BootDriverInitTime 2500
BootDevicesInitTime 6068
BootPrefetchInitTime 59104
BootPrefetchBytes 674377728
BootAutoChkTime 0
BootSmssInitTime 13792
BootCriticalServicesInitTime 463
BootUserProfileProcessingTime 302
BootMachineProfileProcessingTime 11
BootExplorerInitTime 2733
BootNumStartupApps 10
BootPostBootTime 34100
BootIsRebootAfterInstall false
BootRootCauseStepImprovementBits 0
BootRootCauseGradualImprovementBits 0
BootRootCauseStepDegradationBits 256
BootRootCauseGradualDegradationBits 0
BootIsDegradation false
BootIsStepDegradation false
BootIsGradualDegradation false
BootImprovementDelta 0
BootDegradationDelta 0
BootIsRootCauseIdentified true

and here is a Shutdown Performance Monitoring Warning

EventData

ShutdownTsVersion 1
ShutdownStartTime 2009-01-22T09:28:43.652Z
ShutdownEndTime 2009-01-22T09:28:58.196Z
ShutdownTime 14544
ShutdownUserSessionTime 4477
ShutdownUserPolicyTime 0
ShutdownUserProfilesTime 1
ShutdownSystemSessionsTime 5979
ShutdownPreShutdownNotificationsTime 3717
ShutdownServicesTime 2172
ShutdownKernelTime 4087
ShutdownRootCauseStepImprovementBits 0
ShutdownRootCauseGradualImprovementBits 0
ShutdownRootCauseStepDegradationBits 0
ShutdownRootCauseGradualDegradationBits 0
ShutdownIsDegradation false
ShutdownTimeChange 0


what is the above supposed to tell me? i mean, there isn't even a service or app or dll or anything listed ...

 

Well, those are all time entries, most likely in milliseconds, for how long each named step in the boot process (or shutdown process) took.

 

You're not going to let this go, are you?

OK, well. First, DO NOT deschedule the defrag. Indeed, let it defrag normally by leaving your computer on overnight from Tuesday to Wednesday and disable sleep and hibernation. Do that for two weeks.

These reports are the collected analysis of the various warnings and don't tell us too much beyond

a) your start up took 65 seconds
BootTime 65290

Windows kernal and core componants took 31 seconds
MainPathBootTime 31190

Then we see thinks like how long in milliseconds it took various core componant categories, nothing to interesting until we see the number of startup apps (10)
BootNumStartu Apps 10

Then how long it took for all non c0re programs to load (34 seconds) BootPostBootTime 34100

Nothing installed after the start

BootIsRebootAfterInstall false


For shudown, we see it took 14 seconds
ShutdownTime 14544

and now a whole lot else.

Basically, Windows is saying "HEY LET ME FREAKING DEFRAG SO I CAN GET STARTED IN UNDER A MINUTE! STOP TWEAKING ME AND LEAVE ME ALONE!

 

Sigh... Nothing is causing this; these messages are entirely normal in the operation of any Vista system. If it helps, I have about 1,700 of these messages in my log, and there is absolutely nothing whatsoever wrong with my machine, which runs fast and smooth as can be. Just let it go...

P.S.: By the way, just for laughs, I also have messages complaining about "Desktop Window Manager is experiencing heavy resource contention", with the recommendation that "Reducing number of running programs and open windows may help resolve this condition." This is on a 2.3GHz dual-core machine with 4GB memory, and an NVIdia 7950GT-based graphics card with 512MB of memory that scores a perfect 5.9 score in Vista...