Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Jekku on November 20, 2011, 10:50:44 AM
-
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.
-
My other computer has this issue also.
-
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.
-
@ 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 ???
-
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.
-
@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 how do you get that graph in the Event viewer ???
The graph is accessed through the action centre-maintainence-view reliability history.
-
@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! :o
-
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
-
We need to get Tech, DavidR, and bob3160 involved as they run Windows 7.
-
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?
-
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 ).
-
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.
-
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 ???
-
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 ;D
-
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.
It's 1354 meanwhile. ;)
-
@ady4um
I think you have no clue about Windows 7
http://forum.avast.com/index.php?topic=88536.msg709746#msg709746
Posting a link to some (long) post in some completely different (and not-short) topic is not going to explain why you are assuming that (opinion, not fact). Do you expect from me to re-read that complete topic so to *guess* what you meant?
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.
You had never had to do what exactly? What is "that" in your sentence? Would / Could you be more specific, please?
Why do I not trust a person that does not even know what country they are in ???
I have no idea why wouldn't you. ::)
*I* know in what country I am. Whether I decide to publish that or not is a different matter. Whether *you* know in what country *I* am is a different matter. Whether the country I was born is the same country where I live in is a different matter. Whether the country where I live in is the same country where I am currently writing from is a different matter. Whether any of those countries is of any influence in my technical answers is not even a matter.
Whether a new user (not me), which is not going to tell you "his country" (whichever meaning he wants to give to that expression), is from one country or another is not a matter here either, and you still are able to post and help those new forum members anyway.
So, if you want to specify what you meant / imply about the Windows Seven issue (or any relevant technical issue), and if it is a matter in this topic (instead of being Off Topic), I have no problem at all in answering, including the possibility that I may have made a mistake or expressed myself not clearly enough.
-
Since I experienced no 6008 warnings anymore with .1289 I will update the system with the newest beta coming soon.
It's 1354 meanwhile. ;)
Ya, but for the time being it is withdrawn, will see what comes next!
-
Since I experienced no 6008 warnings anymore with .1289 I will update the system with the newest beta coming soon.
It's 1354 meanwhile. ;)
Ya, but for the time being it is withdrawn, will see what comes next!
How long has it been since you installed 1289 ? as i installed 1354 this morning and it took 5 reboots over 8 hours before the error reared its ugly head again :(
-
Since I experienced no 6008 warnings anymore with .1289 I will update the system with the newest beta coming soon.
It's 1354 meanwhile. ;)
Ya, but for the time being it is withdrawn, will see what comes next!
How long has it been since you installed 1289 ? as i installed 1354 this morning and it took 5 reboots over 8 hours before the error reared its ugly head again :(
It is actually running since 2 days, 5 def updates and numerous reboots!
-
@Jrace and craigb,
According to the report of Jekku, it is not about how many reboots you made, or how many updates, but about rebooting after a definition updates was in fact performed.
So rebooting 5 times during 8 hours, for example, may not catch the event until an update was actually applied. Statistically (well, just as a mean value), you get 1 update every 12 hours. No matter if you reboot 20 times, but if you reboot after receiving that next update.
During 2 days, if rebooting several times, you would see that the event is almost not reported except for one reboot after an update (or after 3 updates with no reboot in between, doesn't matter).
Of course, I am assuming that your systems are behaving the same as in Jekku's case.
-
@ ady4um:
I very well know about this specific problem, Since I had the same thing with version .1352 I downgraded to .1289 to see if it is still present. Answer is -no-.
To make my previous statement more precise for you:
It's running now for two and a half days, 6 def. updates with either shutdowns or reboots behind.
My system is not online for 24 hours, but only periodically may be a total of 3 hours per day. That implies shutdowns startups and reboots. So I have at least one shutdown or reboot after a def update.
-
My system is not online for 24 hours, but only periodically may be a total of 3 hours per day. That implies shutdowns startups and reboots. So I have at least one shutdown or reboot after a def update.
it is obviously clear that ady4um has no clue about Window 7 systems!
He should leave this problem to those that know and run Windows 7 and he does not want to disclose what country he resides in nor indicate what operating system he uses. ???
-
Since I experienced no 6008 warnings anymore with .1289 I will update the system with the newest beta coming soon.
It's 1354 meanwhile. ;)
Ya, but for the time being it is withdrawn, will see what comes next!
The problems have been fixed and .1356 is out now. :)
-
@jrace,
Yes, evidently you have rebooted after some definitions update, but craigb mentioned 5 reboots in 8 hours "only". That period of time (which in some cases would not be enough to trigger this event) and the rebooting frequency was the main reason for the comment.
@YoKenny,
I tend to avoid publicly posting personal impressions or opinions on other forum members. If I were to do such a thing, I would probably be wrong, since some simple forum posts coming from people from all over the world with different cultures are not even close to the vicinity of being enough to have some kind of valid impression of anyone / someone.
Evidently and obviously, it wouldn't add anything, just like your opinions with no fact at all. I *would* consider asking you, politely, to concentrate on the real issues and technical matters, but since anyway you already carefully read the signatures more than the main posts, my request to you would be a waste of time (to say the least).
I was about to repeat myself with previously posted explanations. This is the last time I fall into this worthless OT with you. If you want to share with me technical issues, I am very open to that. Otherwise, don't even bother; I don't care.
Let's move on into the next technical issue and the next Beta version.
-
Since I had this "unexpected shut down error (6008)" with version .1352 everytimes a new def update came in I reverted to version .1289 again and it was OK.
Now I tried .1356 as an over thetop update.
The error is immediately back after the first def update! :o :o :o
Came back to .1289 and observing the system now. After the next update this evening I will report back!
Edit: First big def update of .1289 to current status folowed by a reboot did not show the 6008 error in the event viewer.
-
Since I had this "unexpected shut down error (6008)" with version .1352 everytimes a new def update came in I reverted to version .1289 again and it was OK.
Now I tried .1356 as an over thetop update.
The error is immediately back after the first def update! :o :o :o
Came back to .1289 and observing the system now. After the next update this evening I will report back!
Edit: First big def update of .1289 to current status folowed by a reboot did not show the 6008 error in the event viewer.
@jrace: Could you try to uninstall the .1289 build and make a clean install of .1356? I did that and didn't get an error after first def update/reboot. However, I did get a strange error window during uninstall (.1354): DllRegisterServer returned 0x8002801c. I don't know if this has anything to do with our problem, but I remember seeing that error once before. That was when I first discover this 6008 error problem and unistalled my avast.
I bet I won't get that system shutdown error until the next program update when the next build is updated over the old one.
-
@jrace: Could you try to uninstall the .1289 build and make a clean install of .1356? I did that and didn't get an error after first def update/reboot. However, I did get a strange error window during uninstall (.1354): DllRegisterServer returned 0x8002801c. I don't know if this has anything to do with our problem, but I remember seeing that error once before. That was when I first discover this 6008 error problem and unistalled my avast.
I bet I won't get that system shutdown error until the next program update when the next build is updated over the old one.
Hi Jekku, may I call you now "Genius"? ::)
Like you I made a clean install of .1356, it made directly after install the first def update, I rebooted the whole load and what did I see: -nothing, no 6008-
That seems to have solved it. With crossed fingers I'm waiting now for the evening update and will check what comes. Hope you are right with your bet! ;D
But anyway even when it works out somebody should alert "Vlk" on this to have an eye on it!
-
Hi Jekku, may I call you now "Genius"? ::)
Like you I made a clean install of .1356, it made directly after install the first def update, I rebooted the whole load and what did I see: -nothing, no 6008-
That seems to have solved it. With crossed fingers I'm waiting now for the evening update and will check what comes. Hope you are right with your bet! ;D
Well, I don't think this issue is solved yet. What I meant to say was, that even if we didn't get any errors (I don't know this yet) with this current build .1356 (clean install), I bet we will start to get them again as soon as the next build installs itself over the current one.
Seems that a clean install will work without problems(?), but an update over the old version won't and we'll start to get those 6008 errors when def update/reboot is made(?). That's what has happened so far, isn't it? Well, this is just my speculation and we'll see how it goes when the next build is released...
And I was unfortunately wrong... :( I just got an 6008 error after def update/reboot with my clean installed avast .1356. So, we are back in square one again! >:(
-
And I was unfortunately wrong... :( I just got an 6008 error after def update/reboot with my clean installed avast .1356. So, we are back in square one again! >:(
One more in the "6008 Club"!
A few minutes ago I had the same experience with the evening def update of .1356. As you say, we are back to the start and I have absolutely no clue. ???
I will now finally go back to .1289 and try again when the new stable version is rolling out.
Still watching this post.
-
What do you mean, back to 1289?
I always thought that issue was present in this version, wasn't it?
I.e. it's not new in the latest betas.
Please confirm.
Thanks
Vlk
-
Not sure about the others but the problem was there for me with the 1289 version as it is still with the latest beta.
Yes the others were also getting the problem in 1289 http://forum.avast.com/index.php?topic=86694.msg698631#msg698631
-
Right. We're investigating the issue (and would really love to have it resolved before releasing the next program update), but we will likely not hold the release of the update until we find a solution - because the issue was present even in the last stable version, so the new update won't make things any worse.
Thanks
Vlk
-
What do you mean, back to 1289?
I always thought that issue was present in this version, wasn't it?
I.e. it's not new in the latest betas.
Please confirm.
I confirm. 6.0.1203 build was the last one which worked ok and the problem has been there since.
Thank you for investigating this issue, I hope you can find the cause.
-
What do you mean, back to 1289?
I always thought that issue was present in this version, wasn't it?
I.e. it's not new in the latest betas.
Please confirm.
Thanks
Vlk
@Vlk:
I definitely confirm that my system is running well and without 6008 errors on Version .1289.
Just had another def update on .1289 and the following reboot did not have any 6008 errors.
A weird happening. ::)
-
Well, one Windows Seven 32 bits is NOT having this problem using Avast 6.0.1289 (Jrace's system).
Jekku and Craigb are using Windows Seven 64 bits, and both are having this problem using Avast 6.0.1289.
Still, it might be a coincidence.
-
Well, one Windows Seven 32 bits is NOT having this problem using Avast 6.0.1289 (Jrace's system).
Jekku and Craigb are using Windows Seven 64 bits, and both are having this problem using Avast 6.0.1289.
Still, it might be a coincidence.
Also 2good-tenseur-stitt and YoKenny have reported this problem but there also with 64 bit win 7.
-
I am using Win 7 64 bits, and this problem definitely exists on 1289
-
A member of another forum directed me here as I'm getting related trouble. Avast Free latest version is on both of my pc's. The error I'm getting only occurs on my Laptop.
-
A member of another forum directed me here as I'm getting related trouble. Avast Free latest version is on both of my pc's. The error I'm getting only occurs on my Laptop.
Could you post also the specs of both your systems, indicating which one has the problem and which one doesn't?
Which Avast (Free / Pro / AIS ) and which exact version? Which OS, SP, 32/64 bits?
-
Kaspersky is having the same issue, they have no solution yet either, but apparently changing the WaitToKillServiceTimeout to a (much) higher value fixes it.
-
A member of another forum directed me here as I'm getting related trouble. Avast Free latest version is on both of my pc's. The error I'm getting only occurs on my Laptop.
Could you post also the specs of both your systems, indicating which one has the problem and which one doesn't?
Which Avast (Free / Pro / AIS ) and which exact version? Which OS, SP, 32/64 bits?
Hi ady4um, they can be found here PC Specs. (http://"http://img580.imageshack.us/img580/2873/spcspecs.jpg") Using Avast Free newest version. Win7 H Prem. 32bit. All updates inc. SP1
-
Kaspersky is having the same issue, they have no solution yet either, but apparently changing the WaitToKillServiceTimeout to a (much) higher value fixes it.
I have an APC UPS on my Windows 7 system and that will kill my UPS monitoring :'(
NOTE: Try not to increase the shut-down time. For example, if you lose power, it is possible that your uninterruptible power supply cannot provide backup power for the computer long enough to allow all the services to shut down properly, as well as the operation aystem.
http://support.microsoft.com/kb/146092
-
(http://img580.imageshack.us/img580/2873/spcspecs.jpg)
Using Avast Free newest version. Win7 H Prem. 32bit. All updates inc. SP1
Well, both systems have 2 GB of RAM and both are Windows Seven 32 bits, but only one have this problem.
I'm starting to think this is not related to a system specification, but rather to the "dirty bit" when Windows is not shut down correctly. I mean, it seems like if Avast definitions update would trigger the dirty bit, somehow (I'd rather not continue with the concept, because I don't really have any basis to it, and it would unnecessarily "scare" users about nothing really important). I know it sounds strange but...
Of course I am not an Avast Team member, so we still need to wait for them to find out the reason(s) for this strange behavior.
In the meantime, keep reporting so they can find some common denominator.
-
Hi,
I have checked my system. No such error with version 1289, 1356 or 1364 of avast free.
Greetings
Christian
-
(http://img580.imageshack.us/img580/2873/spcspecs.jpg)
Using Avast Free newest version. Win7 H Prem. 32bit. All updates inc. SP1
Well, both systems have 2 GB of RAM and both are Windows Seven 32 bits, but only one have this problem.
I'm starting to think this is not related to a system specification, but rather to the "dirty bit" when Windows is not shut down correctly. I mean, it seems like if Avast definitions update would trigger the dirty bit, somehow (I'd rather not continue with the concept, because I don't really have any basis to it, and it would unnecessarily "scare" users about nothing really important). I know it sounds strange but...
Of course I am not an Avast Team member, so we still need to wait for them to find out the reason(s) for this strange behavior.
In the meantime, keep reporting so they can find some common denominator.
When closing down, I close all open program then use shut down button in start menu.
-
When closing down, I close all open program then use shut down button in start menu.
Interesting post by JoeP517:
http://windowssecrets.com/forums/showthread.php/142560-Event-Viewer-ID-6008?s=bd78c6dd74976ae84810fc835b1a8e88&p=829816&viewfull=1#post829816I see OpenDNSupdater. I'd also disable the WinPatrol system monitor.
I have both on my system.
-
When closing down, I close all open program then use shut down button in start menu.
Interesting post by JoeP517:
http://windowssecrets.com/forums/showthread.php/142560-Event-Viewer-ID-6008?s=bd78c6dd74976ae84810fc835b1a8e88&p=829816&viewfull=1#post829816I see OpenDNSupdater. I'd also disable the WinPatrol system monitor.
I have both on my system.
I'm a member of Windows Secrets Lounge, He was replying to me.
-
Are there any experiences so far with the new .1367 release and the "6008 error"?
-
Are there any experiences so far with the new .1367 release and the "6008 error"?
Not so far on my Windows 7 system.
-
Same problem with the last version 1367 !. I have the problem since the 1289 version.
Not serious by avast >:( ... 2 months to wait for another update ... abused!
All is OK, if I kill the service avast before I restart or close my PC. The problem is avast
-
Same problem with the last version 1367 !. I have the problem since the 1289 version.
Not serious by avast >:( ... 2 months to wait for another update ... abused!
All is OK, if I kill the service avast before I restart or close my PC. The problem is avast
Well, I can't confirm this, because it seems that my two computers work as they should now (.1367). No 6008 errors after three def updates / reboots. I'll monitor my computers for a couple of days. Hope this lasts!
On the other hand, this isn't completely fixed since tenseur still have problems.
What about the others? craigb, YoKenny, jrace, RodeRunner etc...?
@tenseur:
Have you tried a clean install .1367?
@Vlk:
Did you do something about that issue for this build or is this just a coincidence?
-
Yes and nothing change !
-
What about the others? craigb, YoKenny, jrace, RodeRunner etc...?
No 6008 errors for three updates as well and installing v6.0.1367
-
I updated from .1289 to .1367 via the program interface hoping the "6008 error" (unexpected shutdown) would not show up again like in all the "betas" in-between.
Since update to .1367 I had 4 def. updates with shutdowns and/or reboots afterwards and guess what:
No "6008 error" anymore!
Vlk, is it now just a mystery, because everyone complaining had that behaviour also in version .1289 except for me, or did you find that little devil and killed it?
-
I have this problem, unless I kill the process avast. What to do?
Also when I try to update avast, well the windows slidebar to crash!
It is from lee 1289, and I think it has something to do
-
I have this problem, unless I kill the process avast. What to do?
If you use Avast Pro or AIS, backup your license file first.
What about the removal utility for Avast, cleaning ALL previous versions you ever had by running it for each one? Use Windows Safe Mode directly for better results.
After that, manually search for any hidden folders containing the words "avast" and/or "alwil" and delete them too.
Then install the latest stable version 6.0.1367 (please download anew), reboot and test for a couple of days (at least) before getting to any new conclusion about the 6008 event ID issue.
You would need to configure Avast again, and if you have files in the chest they will be gone too.
Of course, I can't guarantee you if this would solve the problem, but at least it gives you a clean base line.
Please report back.
-
I will retry the install :-\
-
I will retry the install :-\
You meant the removal of ALL versions. The utility is located at http://www.avast.com/uninstall-utility (http://www.avast.com/uninstall-utility), but the instructions there are a little bit different from what I suggested here.
-
Here is reinstalled. I have over the problem of crash slidebar when I look if I have an update of avast, so I think that's it. I hope it's ok, I would tell you
-
No problem yet but still early days, only been installed one day for me with a clean install but i have only rebooted once so far after the install, fingers crossed ;)
-
No problem yet but still early days, only been installed one day for me with a clean install but i have only rebooted once so far after the install, fingers crossed ;)
I have not had to do a clean install on my Windows 7 system and so far I have not had a Windows Event Log Error 6008 for four days after updating to 6.0.1367
-
No problem yet but still early days, only been installed one day for me with a clean install but i have only rebooted once so far after the install, fingers crossed ;)
I have not had to do a clean install on my Windows 7 system and so far I have not had a Windows Event Log Error 6008 for four days after updating to 6.0.1367
Good to hear, lets hope it stays that way.
I prefer to do clean installs with new versions, especially when there has been a problem with the previous, clean installs take me all of 15-20 mins by the time i manually clean out the registry which you have to do if you really want a true clean install :)
-
Just confirming that the 6008 error has still not returned in the 1367 version, very happy and thanks to the avast team for tracking this little bug down and nabbing it :)
I would be interested to know what it was that actually caused the problem but then again i probably wouldn't understand if you told me ;D
-
the problem is solved, I have no more error 6008
I will confirm it again in a few days
-
n any body help me in understanding why i am getting these error,i am using a drobo SAN BOX i have connected my lun through ISCSI.
but i am getting file corrupt msg again and again.i am attaching a log file of event viewer.
Welcome to the forum "immapleShemia".
It is better you open up a new topic for this problem, it seems to have nothing to do with this specific Error 6008!
-
I was ok for a day, I just noticed I got one on the last log off.
-
I was ok for a day, I just noticed I got one on the last log off.
Still all good for me, did you upgrade over the previous version or a clean install ?
-
Clean install, I made am image of my pc, straight after I installed windows and drivers, and i back up my files and games seperately. so It is always on a clean windows install with no other programs installed or removed. It rebooted 5 times, on the sixth (it had just auto updated defs) windows performance says last shut down was not expecting, however event viewer shows nothing?
this is exact message "The previous system shutdown at 21:11:42 on 02/12/2011 was unexpected."
the only kernal power event in viewer is when service pack was installed, and it always seems to show a hiccup there.
Edit, this morning, I notice security center states my avast firewall is off? these two problesm I have had with last 3 builds? maybe avast doesnt like my pc? (turning firewall off and on again fixes this for a while for me btw)
amd 940 be 3.8gz
2 x2 ddr2 8500@ 1066
2 samsung F1 raid 0
msi diamond
2 x gainwood 295 gtx @ +22%
windows 7 64bit home edition
I have licenses for eset, norton, dr web and avast
I only seem to get these problems with avast, which is a shame because avast runs the lightest.
built pc three years ago, it's getting on but still runs very well.
-
Still working ok after three days and several def updates / reboots -> no errors yet.
-
Still working ok after three days and several def updates / reboots -> no errors yet.
Same over here. Very much delighted! ;) ;) ;)
-
A complete reinstall also fixed this problem for me. There was definitely something wrong with the service. When uninstalling, I got a timeout error as the service didn't finish shutting down fast enough (<30 seconds), so after the normal uninstall I additionally used the uninstall tool just to be safe.
-
Help! I uninstalled Avast and installed a clean installation and it did not help anything! The computer still turns itself off (LogEvent 6008): / Does anyone have any ideas? I note with after removing avast registry cleaned.
-
I just got that *beep* error a few minutes ago after a reboot, so this isn't fixed yet after all. :( :'(
@burza501
There's nothing we can do other than wait for the next version and hope that avast has managed to locate the cause and fix this issue. :(
-
I just got that *beep* error a few minutes ago after a reboot, so this isn't fixed yet after all. :( :'(
@burza501
There's nothing we can do other than wait for the next version and hope that avast has managed to locate the cause and fixed this issue. :(
Still no errors on my Windows 7 system. :)
-
Ok nice, but I still have a problem :/ Someone can help me plz?
-
Ok nice, but I still have a problem :/ Someone can help me plz?
I believe avast would be still looking into this but it could take some time as it's not known what causes it, the issue has disappeared for many of us with the latest 1367 version so the only thing i could suggest is uninstalling with the removal tool in safe mode and if your up to it manually removing all avast registry keys by running and repeating the search for avast until nothing shows up anymore, there are quite alot of leftover avast keys including legacy but doing this worked for me, some of the others did not go to this extent of a clean install but like i said this was what worked for me and now i dont get any errors.
No guaranties it'll work for you though as this little bug is a mystery.
-
Many times I uninstall Avast and removed all remnants from the registry, and unfortunately after a fresh installation without any changes. : / I hope that the company really Avast still working on that. I believe that soon the problem will be solved by Avast.
-
Many times I uninstall Avast and removed all remnants from the registry, and unfortunately after a fresh installation without any changes. : / I hope that the company really Avast still working on that. I believe that soon the problem will be solved by Avast.
Looks like you are from Poland and there is no Polish area of the forum that I can direct you to.
By the way this is avast! and not Avast
Download avast! Free Antivirus 6
http://www.avast.com/free-antivirus-download
-
I have these error codes too everytime I start my computer.. ID 6008. Started to happen in september. No system crashes or anything, just the error code poppin on the event log.
-
I have these error codes too everytime I start my computer.. ID 6008. Started to happen in september. No system crashes or anything, just the error code poppin on the event log.
Welcome to the forum "wigloc"!
Try a complete "clean" install:
1. Download a fresh copy of your program from avast! pages and save it on the Computer.
2. Download "aswclear.exe" and save it on the computer. (http://www.avast.com/uninstall-utility)
3. In avast! GUI go to "Settings/Troubleshooting" and uncheck "enable avast! self-defence module".
4. Uninstall avast! via "Controll Panel" and reboot into "Safe Mode".
5. In "Safe Mode" run "aswclear.exe", select your version and continue uninstalling.
6. Reboot into windows when completed and reinstall downloaded program (setup*.exe).
7. Reboot again before doing any changes to the program!
Report any happenings please.
-
The problem is solved, thank you
-
For anybody having that problem... hasn't it disappeared in the last few days, by a chance?
-
For anybody having that problem... hasn't it disappeared in the last few days, by a chance?
Hi "igor",
I had this problem only in the last beta versions (.1352; .1356; .1364) and it's not existent anymore since the final version .1367! :D :-* :D
*** Well done ***
-
For anybody having that problem... hasn't it disappeared in the last few days, by a chance?
All fixed here to thanks :)
-
For anybody having that problem... hasn't it disappeared in the last few days, by a chance?
I haven't had any problems either.
Thank you!
-
I get this error again.
Can it somebody confirmed or it just occur another program on my computer?
AIS v1474
Windows 7 x64