For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 31 30 34 35 35 31 31 32 10455112
0010: 31 30 0d 0a 10…
Well this is the real culprit the faulting module msvcr80.dll
Faulting application nitropdfprintermonitor.exe, version 5.5.0.16, faulting module msvcr80.dll, version 8.0.50727.3053, fault address 0x000046b4.
The msvcr80.dll file isn’t an avast one and nitropdfprintermonitor.exe crashed whilst using the msvcr80.dll module.
So how do you know this has something to do with avast, it doesn’t feature in the event viewer nor the images ???
Does nitropdf need to start on boot, seems strange to me that it would ?
What happens if you stop it starting on boot and start it manually after the system has booted, does the crash happen then too ?
Well I just found out (I disabled it in startup), rebooted, went to print something in word with its printer, the window asking you to save it as a pdf file, doesnt appear
Thats what the file in startup is for. And I’m not planning on going to C:\Program Files\Nitro PDF\Professional and clicking on nitropdfprintermonitor.exe every time I need to use it
If you placed a shortcut in the startup folder that may delay the start sufficiently so it doesn’t cause a problem. But what/why that is is beyond me, yes a coincidence, but it would need one of the Alwil developers to check say the dump files from the crash.
Or you could create a shortcut on your desktop or quick launch so you don’t have to go rummaging through explorer.
You could also try delay the start of the avast services (personally I would want my AV to load as early as possible), see image. But again I don’t see any interaction of avast and either of the two files other than they may be scanned when they load, depending on when a) avast loads and b) when they load.
I’ve submitted a bug to the guys at Nitropdf as well.
Its either Avast doesnt like NitroPDF, or vice-versa. Since Nitropdf’s printer driver is the only program that crashes (and there’s 14 other startup entries, in startup, none of them crash)
And it doesnt crash, if another AV program is installed
I’ll see what NitroPDF say, once they reply to me
I’ve just been given a case # from NitroPDF by reply email
Its not crashing the system, nitropdfprintermonitor.exe is the only thing that crashes. So, there are NO dmp files
As you have no doubt been told before avast doesn’t block but scans and alerts to infected files, so if you aren’t getting that alert then it has nothing to do with dislike with nitropdf but something else.
Printer drivers or rather intercepting print calls (for scan, etc.) can frequently be a problem if there happens to be remnants of your previous AV nod32 as they install low level drivers to hook calls to run files, etc.
I have seen this with a printer not working after changing to avast and that was related to remnants of Norton, which once all remnants were removed every thing worked as it should. However, none of this happened at boot, nor did it cause a crash of any application…
So I’m as confused as you are. Trying other AVs to see if it works there could potentially leave remnants which could also cause conflicts, however, these conflicts don’t usually present themselves in this way.
I would imagine the 13 other startup entries aren’t using the msvcr80.dll module responsible for the problem, which may account for that.
