Windows Event Log Error 6008 - request

[Jekku]

I'll open a new topic about this issue because there are so many messages in the beta topic (the stable version has this issue also).
So, I kindly ask everybody to test if this problem/bug affects you.

1) wait for the next automatic definition update and reboot your computer after that at any time
2) open your Windows event log after reboot and see if there was an error 6008 "The previous system shutdown at xx:xx:xx on xx/xx/‎2011 was unexpected."
3) report here with your avast and OS specs only if you had an error

I think this error has something to do with the def update process. I compared my Windows event log and avast setup.log and got these results:

16.11.2011 00:14am avast update
16.11.2011 01:01am reboot --> ERROR
16.11.2011 01:04am reboot OK
16.11.2011 01:06am reboot OK
16.11.2011 01:08am reboot OK
16.11.2011 01:11am reboot OK
16.11.2011 01:13am reboot OK
16.11.2011 08:41am reboot OK
16.11.2011 09:35am reboot OK
16.11.2011 10:26am reboot OK
16.11.2011 12:30pm avast update
16.11.2011 12:31pm reboot --> ERROR
17.11.2011 12:15pm avast update
17.11.2011 12:24pm reboot --> ERROR
18.11.2011 05:03am avast update
18.11.2011 08:18am reboot --> ERROR
18.11.2011 08:21am reboot OK
18.11.2011 10:23am avast update
18.11.2011 12:51am reboot --> ERROR
18.11.2011 01:05pm reboot OK
18.11.2011 01:24pm reboot OK
18.11.2011 02.25pm reboot OK
18.11.2011 02.50pm reboot OK
18.11.2011 06.10pm avast update
18.11.2011 07.50pm reboot --> ERROR
18.11.2011 11.25pm reboot OK

I get always that event log error 6008 during the next reboot after avast has updated itself. I don't get those errors at any other times when rebooting my computer. If I uninstall avast, the problem is gone.
The stable build 6.0.1203 was the last one which didn't have this issue. It's been there since.

[Jekku]

My other computer has this issue also.

[CraigB]

Vlk's already heard from me about this but just so im added to this thread as one of the affected by this issue, spec's are in my sig.
Iv seen jrace also mention he's getting the same problem with a 32 bit win7.

All the red X's below are shutdown errors from when avast was reinstalled on this system.

[YoKenny]

@ Jekku as you now have more than 20 posts you can go to PROFILE then Modify Profile then Forum Profile Information then update your Signature: with information like my signature as this helps the helpers offer pertinent advice.

@craigb how do you get that graph in the Event viewer

[ady4um]

Hmmm , Jrace, Craig and Jekku all using at least 4GB of RAM (or more) and all using some version of Windows Seven. Coincidence?

I don't have this event reported in Event Viewer, but I also don't have those 2 characteristics in my system.

[YoKenny]

@craigb how do you get that graph in the Event viewer

I use Event Log Explorer™ to view the event logs:
http://www.eventlogxp.com

I am getting the 6008 errors and it is after an update of the virus database.

The previous system shutdown at 8:51:30 AM on ?11/?20/?2011 was unexpected.

0000: DB 07 0B 00 00 00 14 00   Û.......
0008: 08 00 33 00 1E 00 4D 03   ..3...M.
0010: DB 07 0B 00 00 00 14 00   Û.......
0018: 0D 00 33 00 1E 00 4D 03   ..3...M.
0020: 08 07 00 00 3C 00 00 00   ....<...
0028: 01 00 00 00 08 07 00 00   ........
0030: 00 00 00 00 78 00 00 00   ....x...
0038: 01 00 00 00 00 00 00 00   ........

[CraigB]

@craigb how do you get that graph in the Event viewer

The graph is accessed through the action centre-maintainence-view reliability history.

[YoKenny]

@craigb how do you get that graph in the Event viewer

The graph is accessed through the action centre-maintainence-view reliability history.

Here is my picture.

I have had a heck of a time with the forum un-availability today! 

[Jekku]

Hmmm , Jrace, Craig and Jekku all using at least 4GB of RAM (or more) and all using some version of Windows Seven. Coincidence?

Could be this affects only Windows 7, but I don't think RAM has anything to do with it. I don't know...

So far this issue has been reported by me (2 computers), craigb, jrace and YoKenny. Also yhe1 and tenseur have reported same thing in this thread: http://forum.avast.com/index.php?topic=86694.msg699664#msg699664

[YoKenny]

We need to get Tech, DavidR, and bob3160 involved as they run Windows 7.

[Lisandro]

Hmmm... I was seeing a problem similar in Windows XP, i.e., the shutdown process fails at the first time.
User needs to do the action twice.
I can't imagine it could be related to avast...
Is there avast dumps in the \log folder?

[ady4um]

Hmmm... I was seeing a problem similar in Windows XP, i.e., the shutdown process fails at the first time.
User needs to do the action twice.
I can't imagine it could be related to avast...
Is there avast dumps in the \log folder?

That seems to be a different case. The reports here are not saying that the shut down fails completely. They just say there is some "strange" event registered (ID 6008 ). There is no memory dump (and it is not necessary, for now). Jekko and others already reported about the coincidence between the logged definitions updates and the specific event (ID 6008 ).

[Jekku]

Hmmm... I was seeing a problem similar in Windows XP, i.e., the shutdown process fails at the first time.
User needs to do the action twice.
I can't imagine it could be related to avast...
Is there avast dumps in the \log folder?

That seems to be a different case. The reports here are not saying that the shut down fails completely. They just say there is some "strange" event registered (ID 6008 ). There is no memory dump (and it is not necessary, for now). Jekko and others already reported about the coincidence between the logged definitions updates and the specific event (ID 6008 ).

That's correct. And I forgot to mention the obvious: If I uninstall avast, the problem is gone. So it's definitely avast related.

[YoKenny]

Hmmm... I was seeing a problem similar in Windows XP, i.e., the shutdown process fails at the first time.
User needs to do the action twice.
I can't imagine it could be related to avast...
Is there avast dumps in the \log folder?

I have never seen that event on my XP Pro system.

@ady4um
I think you have no clue about Windows 7
http://forum.avast.com/index.php?topic=88536.msg709746#msg709746

I have NEVER had to do that on my Windows 7 system nor my XP Pro system but I did have to on my very old XP Home system that I sold.

Why do I not trust a person that does not even know what country they are in

[jrace]

Hi all, here I am back in business.

I stated allready having exactly the same issue like "Jekku".
Since my "reliability monitor" in the meantime looked like a mess (2 stepdowns per day), I decided to brush it up again: uninstalled .1352 and made a clean install back to .1289.

Unlike your experience with .1289, Jekku, since that install I have not seen any 6008 error in the eventviewer allthough there were 2 def updates so far.

When this situation comes out to be stable (may be one more day) I will update again to .1352 and see if there is any change back to the previous problem. Will report back on that!

So I'm holding my fingers crossed.
Let's see what this crazy machine does