Well, I reinstalled at the time I wrote above. And because I had found that .exe remaining, I decided to let it run with default settings. And it ran all day until just now. Crashed the same way. I copied the crash details below. Note this is with auto update on and it seems it updated at 4/18 14:30:51. So maybe it WAS trying to get an update, I don't know. I am disabling auto update now.
Read both, going with this one for the reply then.
Congrats, you're the official mascot of "sunspots and acne" for now since you've got a rather interesting and elusive one there! Heh. OK ... my first stab at "WTF" was the "5 minutes" thing. That, as I'd indicated, would point at something on the "countdown to startup try for an update" thing and would have been something "possible." Since it worked "all day" once, and then did something even stranger on the next run, I think we can safely eliminate the "4.00 minutes after startup default 'check for update'" as being any part of the problem, and along with that the "trick" I'd mentioned earlier will be "no joy" either.
For YOUR benefit though, I want to take this to IM while we work on this privately, since I'm going to need to ask you a big favor here ... I need some diagnostics data out of your copy of BOClean to analyse and it will contain some of your own personal, private information. So I want to allow you to bring the information I need into notepad and edit out anything you're uncomfortable about and then send the rest to me to have a look at. This is the reason I want to do the next step in IM as a matter of respecting YOUR privacy and not allowing others to have a look at it by posting it publicly here.
Need you to use the "search" feature (be SURE to adjust the settings so that it looks EVERYWHERE on your primary hard disk) and look for a file called BOC426.INI ... there will be one for certain in your \WINDOWS folder which is the "master copy" ... however, there might be
other copies of BOC426.INI located in obscure folders as "personal store" stuff ... Vista is a pain in the butt about making copies of copies of copies and then using the wrong one.
Look for whichever BOC426.INI is the *largest* file size, look it over in notepad, and then copy and paste the results into an IM for me to look over. No one else will ...
hopefully from what's listed in that, we can go the next step. If necessary, might also point you to another tool you'll need to do if this doesn't point me at some suspicious externals to check out, and we'll go to the next level if I can't guess from the INI file what might be going on. I now suspect the problem is either an errant driver, or something else interfering. Hopefully, there will be an "aha moment" within the contents of the INI file.
Now switching to the "professor hat" ... I imagine folks might want to know more about these "crash dummy" boxes and what they mean, particularly here. I'm in a good mood since I'll be going to bed soon, so let's have some fun learning about windows and crashes ... might be useful.
The "c00000005" errors which appear in many programs that make windows "pass gas" are the result of a program calling a section of memory which is "not defined." In other words, calling a black hole, being "shot into space." This can occur when a program calls a section of memory which just isn't *there* anymore, or went home based upon it being "unlinked." Bottom line is that the program is literally walking off a cliff because *something* went away.
The "crash" is an "unhandled exception." When program calls a function, or an address in memory, Windows looks in active memory for what you want. If it doesn't
find it, then it goes to the "swap space" on disk to look for it, figuring that it put if there. If it doesn't find it
there then it stops trying and "raises an exception" along with an error back to the software that asked for something Windows couldn't find. Microsoft's vision of how people should code is reflected in three kernel functions for "exception handling" called "__try, __except and __finally" wrappers around each and every function call. "Try" portion is the normal code. "Except" is "what do you want the program to do if it fails?" and "finally" is ... do this to
HIDE the error. Well, I don't code that way. If something goes sideways, I'd like to
know about it, and that's why you're here.
So FWIW, "crashes" are a major biggie as far as BOClean goes and if something goes wrong, to my mind at least, I want alarms sounded so loudly if that happens that folks will bring it up. Sweeping bugs under the carpet was never *my* style (though in the end, those that didn't bring out a new version immediately were never ours in the first place, but we dound the culprit at least) and COMODO has even less tolerance for buggy software than even *I* ever did!
Something's playing peekaboo there, and if you google the words "Vista SP1 crash" you'll see that there is a cast of thousands of culprits out there ... apparently SP1 "qwapping the bed" is rather commonplace unfortunately. All I can offer is that if there's anything in BOCLEAN itself going sideways, I wrote it ... I can FIX it!
If it's something else though, we gotta find it and let them know, and then find a way around it for YOU that will at least get us out of the "sunspots and acne" phase ... heh. So give a look for the longest of those files, send it to me in an IM and let's see what we can do ... as I've said before, you're the only one so far - I'm
SURE you won't be the last to be there, wanna do everything I can do. I have this personal thing about stab wounds down the road.
Author