Correct if I am wrong but isn’t event log only available on NT-based OS(nt, 2000, xp)??? And were is system log??? Win millenium. Did u look at updating errors in the logs that I posted???
I’m afraid these logs won’t tell us anything about your problem.
Try to start DrWatson and let it create its own log…
K, I started DrWatson last night, and had 4 log files when I got home tonight. They all have the following contents in each log file:
XFIRE_CONURE_10 performed an invalid memory access.Module Name: XFIRE_CONURE_10
Application Name: Avast.setup
If the Taskbar is behaving strangely, try exiting Multimedia background task support module.
Module Name: mmtask.tsk
Description: Multimedia background task support module
Version: 4.90.3000
Product: Microsoft Windows
Manufacturer: Microsoft Corporation
Any help???
Not much yet… but as far as I remember, it’s possible to save the log from Dr.Watson somehow. Could you please do it and send it or attach it here (if it’s not too big)? There’s certainly more information in there…
Thanks!
k, there is more info in the log than that. Never used Dr. Watson, didn’t know, but I do now…lol. File too big to post on here, and your email is hidden so I dunno.
EDIT: I put it on a server for download, I will send you the download link via PM, igor. If any other Avast people would like to look at the file and offer their help, just email or PM me for the download link.
Here is download link for xfire_conure_10406.dll file that you asked for igor. Maybe others will view it also and give any information about this recurring error.
Download xfire_conure_10406.dll File
If anyone from the Avast team would like a download link to my Dr. Watson logs, PM me or email. I will send link for them.
Thanks again in advance for the help!
Recieved this error tonight. See attached pic.
So just now (12:30 a.m. Central Time 12/3/04) I manually checked for a program update, and it found one…ver .549. It installed and asked for restart as usual, but while windows was shutting down, I got the infamous BSOD (blue screen of death)…lol. This said error has occured…blah blah blah restart your computer. Here is error code “Error:0E:01D7:BFF8E1AA”. Having MANY random errors that Avast and Avast01 is causing. Not just in xfire_conure file. Such as the picture displayed in previous post. Started out as error only being in xfire_conure, and that error was caused by “Avast01”, now seems to be errors caused by “Avast” also. And not just errors in , errors in known files/programs. Never had this problem before. As a matter of fact, I work as a computer tech at a PC store in town and I always recommend avast home edition on customers home PC’s, no matter what AV is currently on there. I have taken Norton and AVG both off of pcs and were both up to date, yet Avast discovered viruses that BOTH programs missed. Messed with lots of PCs with Avast and never seen problems like this. This AV is without a doubt (at least my opinion) the very best AV software that is out there. Best of all, IT’S FREE. Point is, I really really love this AV, but I hate the random errors. Any advice??? Gonna try a clean install of a newer version of avast, seems like someone mentioned “avast01” as being part of the update feature, and when it causes error in xfire_conure, it is trying to access internet to check for update. My Avast was installed from older version of setup file than the one currently in the download section of avast website. So I could have gotten some corrupted files through the many updates that it has received. If anyone has info on something I should try to fix errors, please let me know.
Thanks
Well, the fact that the error occurred in kernel32 module doesn’t necessarily mean it was caused by avast. That xfire DLL is present in every loaded process - so it may certainly affect everything.
So what are you saying exactly??? I just would like the errors gone. Is it avast software causing the error or xfire software causing the error???
Every error I get is either Avast01 or Avast causing the error, not xfire or another program.
I’m just saying that the error can be in xfire - because the DLL it loaded into avast!.
Anyway, can you send me the DLL? I’m not saying I’ll find the cause, but it would certainly help.
You can view previous posts in this thread, I put a download link in 1 of them for this DLL file, but you have to right click on link and choose “Save Target As…” in order to download (for some strange reason) or choose “copy shortcut” then paste link in browser.
I re-post link here.
Ah, sorry, I didn’t notice the link.
I checked the DrWatson dump and the file… but I don’t really know where the problem is. The crash occurred in the xfire.dll after avast setup(01) has finished. So, if the xfire.dll wasn’t there, avast setup would simply terminate; in this case, however, the DLL craches during its detachment from the avast process.
So, I think it’s rather a problem of xfire. However, I don’t know in detail what the DLL really does in the moment it crashes, so I cannot say much more. :-\
well, I as I stated before, it has to do with setting your idle status for xfire. Are you sure it does it ONLY during shut down of Avast01 and not during start up of Avast01??
Well, by “in detail” I meant that I don’t know what is happening in the particular piece of code where it crashes. Xfire is deallocating a list of something there - and it accesses an incorrect place in memory. But what is stored inside of the list and why it looks where it shouldn’t… no idea.
I am talking about that one DrWatson dump you sent me - in that case, the crash occurred after avast process has stopped and the DLL was detaching from it.
Basically I just need to know if it is Xfire problem to fix or something you can fix on your end?? If xfire is accessing incorrect place in memory, then it is totally xfire’s fault (at least in my opinion). Hence why I get the BSOD sometimes(blue screen of death). As far as I know, the reason you get the BSOD error messages (besides the VxD errors) is because a program that was running accesses memory incorrectly and doesn’t have the code built into the program to recover from the error, so then windows OS tries to recover from the error, and if it can’t recover from the error, then you get the infamous BSOD. I think it is screwed up xfire files in my opinion, but don’t know much about the xfire code nor the avast code.
Would more Dr. Watson logs help you???
If you have some more dumps, you can send them to me.
At least I could say if the problem is always the same.
I am at work now, but I will start dr Watson tonight and give u a couple of the newest logs.
EDIT: (Sat. 12/18) Igor, I sent you 2 Dr. Watson logs generated today. Please check your inbox.