This problem has appeared out the blue after a year of no problems at all… I am currently on 2014.0.0.2013 of the free version. When I update to 2014.0.0.2016 and reboot the PC won’t boot and I get a blue screen. The only way to get it to boot again is to restore the system to an earlier restore point.
The system is an HP Z820 workstation, running Windows 8.1. There is no other security or antivirus software installed.
I have tried completely uninstalling Avast, also using the Avast Cleaner and then reinstalling the latest version… and then it blue screens on completion of the install with the same message.
All my drivers, BIOS and firmware are the latest available.
I had the same problem back in Feb… I had tried to update Avast to the 2013 version but after installing I got some kind of error message so I did a system restore, disabled the shields until my computer was restarted, then after it re-started it showed the same as your screenshot. It re-started at least 10 times and still wouldn’t work so I finally gave up and hooked up one of my Windows 7 computers. My Windows 8.1 was only 2 months old at the time so since it was still under warranty I hooked it back up called Dell Support and a Dell Tech told me what to do, then he took control of my computer, not sure what all he did but he did manage to get it working again and re-installed Avast for me and I haven’t had anymore problems. I will never try to do another system restore on this computer.
If yours is still under warranty call HP support and tell whomever answers what kind of a problem you’re having and maybe a support Tech could help you fix yours.
Thanks for the reply, I don’t think it is anything HP would be able to help with as it looks to be a software problem rather than anything wrong with the workstation.
Here is the output from the memory dump analysis… hopefully it might mean something to the Avast techies…
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_PTE_MISUSE (da)
A driver has corrupted system PTEs.
Set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes
to a DWORD 3 value and reboot. If the same bugcheck occurs again the stack trace will
identify the offending driver.
Arguments:
Arg1: 0000000000000302, Type of error.
Arg2: ffffd0002e000000
Arg3: 0000000000000000
Arg4: 000000000000e000
Debugging Details:
------------------
Page 12eedf not present in the dump file. Type ".hh dbgerr004" for details
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xDA
PROCESS_NAME: AvastSvc.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff80366b24c0e to fffff80366bc6ca0
STACK_TEXT:
ffffd000`2ceb8508 fffff803`66b24c0e : 00000000`000000da 00000000`00000302 ffffd000`2e000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2ceb8510 fffff803`66b4dac7 : 00000000`00000002 ffffe000`2266d580 00000000`00000000 00000001`209de863 : nt!MiReleasePtes+0x1be
ffffd000`2ceb85a0 fffff800`0178f333 : 00000000`00000000 ffffd000`2ceb8b80 ffffd000`2e000000 ffffe000`0012ac60 : nt!MmUnmapIoSpace+0x9f
ffffd000`2ceb85d0 fffff800`0177a668 : ffffe000`22587010 00000060`0000002b ffffe000`036759e0 fffff803`66dfe870 : aswSP+0x1f333
ffffd000`2ceb8640 fffff800`0177965d : ffffe000`22587010 00000000`00000000 ffffe000`036759e0 fffff803`66d096bc : aswSP+0xa668
ffffd000`2ceb86f0 fffff800`0177a059 : ffffe000`22587010 00000000`00000001 00000000`00000000 ffffd000`20101008 : aswSP+0x965d
ffffd000`2ceb8740 fffff803`66e243e5 : ffffe000`22587010 ffffe000`22587010 ffffe000`22587010 ffffd000`00000001 : aswSP+0xa059
ffffd000`2ceb8870 fffff803`66e24d7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x845
ffffd000`2ceb8a20 fffff803`66bd24b3 : 00000000`00000000 00000000`0b31e498 fffff6fb`7dbed000 fffff6fb`7da00000 : nt!NtDeviceIoControlFile+0x56
ffffd000`2ceb8a90 00000000`77362772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0b31ed88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77362772
STACK_COMMAND: kb
FOLLOWUP_IP:
aswSP+1f333
fffff800`0178f333 8bc7 mov eax,edi
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: aswSP+1f333
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswSP
IMAGE_NAME: aswSP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5328af5b
FAILURE_BUCKET_ID: 0xDA_aswSP+1f333
BUCKET_ID: 0xDA_aswSP+1f333
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xda_aswsp+1f333
FAILURE_ID_HASH: {e17f534f-6dfa-536e-1508-2948a914b7fb}
Followup: MachineOwner
---------
Okay, sadly after updating to the mandatory Windows 8.1 Update 1 I’m getting a blue screen again. This is on a completely fresh install of Windows 8.1 with update 1.
This time it’s a “page fault in non paged area” error.
Incidentally, the support ticket I raised for the previous error, their response was “the dump file suggests the fault is nothing to do with Avast”, despite the fact that I debugged it myself (output above) and it points the finger squarely at the Avast service!
So, reluctantly, I think I’m done with Avast for the time being at least and am quite relieved I kept our 100+ work PC’s on McAfee Enterprise… for all its faults I have never had ME render a PC unbootable!
