Major! issue with avast!4 and HP's DLA

[n3whar7]

I haven't been able to use my packet writing software since I installed avast!4. I usually have the Standard Shield set to HIGH, but have been experimenting with a few options that I thought may be responsible for this behavior. Currently, Standard Sheild is set to Normal with "Scan diskette boot sectors", "Scan files on open", and "Scan created/modified files" disabled. Yet, I'm still unable to use DLA!

Please let me know how and if I can remedy this problem.

TIA!

[igor]

So, basically you have all the options disabled, only scanning of the started executables turned on, right?

You get an immediate restart - without any bluescreen? - i.e. without any possibility to obtain the crashdump that could help to nail the problem? (Or may it be that you've got the dump creation switched off?)

[n3whar7]

From my previous post:

"Standard Sheild is set to Normal with "Scan diskette boot sectors", "Scan files on open", and "Scan created/modified files" disabled." Unless the *Normal* sensitivity setting is different for everyone, I think I've clearly described my settings.

Yes, an immediate restart. No bluesceen.

 

[n3whar7]

Here's the intelligible information that was listed in the Minidump file:

\WINDOWS\system32\ntoskrnl.exe
\WINDOWS\system32\hal.dll
\WINDOWS\system32\KDCOM.DLL
\WINDOWS\system32\BOOTVID.dll
ACPI.sys
\WINDOWS\System32\DRIVERS\WMILIB.SYS
pci.sys
isapnp.sys
viaide.sys
\WINDOWS\System32\DRIVERS\PCIIDEX.SYS
MountMgr.sys
ftdisk.sys
PartMgr.sys
VolSnap.sys
atapi.sys

If you require more information, please let me know.

[igor]

So there is a minidump in fact?
I don't see the avast! driver listed there... but if you could send the minidump to vlk(at)asw.cz (maybe with a brief description of the problem - I'm not sure if he's checking the forum recently), I suppose he would like to take a look.

Thanks!

[n3whar7]

Igor,

I sent the .dmp file as you suggested. There's also an .xml file created, but it appears to me, to only list information about my computer's configuration. If anything more is needed, let me know.

(maybe we're getting somewhere with this)  

[Vlk]

This problem has been solved (likely). The fix will be in the next program update.